First, Canvas is a compelling product, with some great usabilty and features. I also welcome Instructure's move to a (forked?) open source path, which I think helps evolve platform options and the marketplace in useful ways.
I am unconvinced, however, by a main thread Instructure CEO Josh Coates takes up in his recent blog post on Instructure's open source strategy.
Josh says that software owned by a single commercial entity is preferable because "critical bug fixes, integration and innovation only come out of the folks that own the technology." I think history has shown that Josh's assertion is not true. Many open and community source projects that do not have a single commercial entity at their core consistently demonstrate high rates of maintenance, innovation, and integration. At the same time, what might be called "corporate" open source offerings do not always generate the qualities Josh describes.
Underneath this issue is an even more fundamental perspective that I also question: that there are only two paths of software ownership/development, which Josh defines in his question: "would you rather have a closed system owned by a commercial entity, or an open system not owned by anyone?" Josh goes on to suggest Instructure's open source strategy offers "the best of both worlds."
I'm now keeping a recipe cataloging the technologies and configuration that drive this xolotl.org site.
Continue to check the recipe as the site evolves.
Once the site reaches a certain maturity, I'm thinking to build a Drupal install profile to make it easier for others to duplicate this installation.