Some people see this as a loophole in the GPL (which wasn't written with web applications in mind) and it may be changed in the next version of the GPL.Ĭontent loaded into Moodle by you or anyone else is not covered by the GPL, any more than an email written in an open source email client, or image created with open source graphics software becomes open source.įinal nitpick: Public Domain is a precise technical term that doesn't really apply here. Note that hosting a website and allowing people access to it is not the same as distribution. If you modify Moodle code and sell or distribute that code to people outwith your own organisation, then you must also make the code changes available to anyone you sell or distribute the code to under the terms of the GPL (which in turn allows them to give away or sell that code). Id be interested in peoples opinions and any other pointers. Specifically, do I give away rights to the content (the videos, animations etc)? Do I give away rights to the modified Moodle code? And do I give away rights to the source code for the stand-alone flash activities?
I think that I am able to sell the product, but my question has to do with which parts of my source code fall into the public domain. For example, I want to modify the code for Moodle's discussion forum and grade book, and then link to them from my principle application. I also want my application to make use of some of the terrific functionality within Moodle. In turn, these activities make calls to a series of proprietary images, videos, and animations. The design will involve an extensive front end using a series of interwoven Flash activities that we will be producing in-house. I am creating an on-line course that I will be selling to colleges and universities. I have a question about the GNU General Public License and Id like to get peoples opinion.
0 kommentar(er)
