Moodlerooms, joule, "Forks," and GPL

Ever since Moodlerooms released the joule e-Learning platform during EDUCAUSE in 2009, we're consistently asked the question, "Is joule a fork in the Moodle open-source community code? If so, why isn't Moodlerooms bound by GPL (General Product Licensing)?"

Typically, a fork in open-source software occurs when developers take a legal copy of source code from one software package and start independent development on it, creating a distinct piece of software. When the source code to that distinct piece of software is released and/or made available, it is bound by GPL.

The short answer to the question has always been, "No, joule isn't a fork." The best way to explain why joule isn't a "fork" is to remember the following equation:

• joule = Managed Open-Source Moodle + Services + Extended Features

With joule, Moodlerooms delivers a turnkey Software-as-a-Service Moodle solution to satisfy the enterprise needs of colleges and universities, schools, corporations and non-profit organizations.

• Moodlerooms harnesses the most up-to-date Moodle source code at the core of the joule platform and then "wraps" the code with in-house developed extended features, tie-ins and integrations with third-party products so the software operates in a seamless fashion.

• The joule codebase is managed and maintained in-house by Moodlerooms developers.

• joule users have extensible access to all of the updates and innovations from the Moodle community, as well as to Moodlerooms' own in-house developments.

• By providing a wide variety of services (hosting, support, course conversion, implementation, SIS/ERP integration, training, and customization) Moodlerooms can deliver the software to customers.

So, we've established why joule isn't a "fork." But that's only a piece part of Moodlerooms' larger story. Stay tuned tomorrow information on how Moodlerooms established its delivery model and became a member of the Moodle partner network

In the meantime, if you have any questions or comments, please send them to us in the comments below.