The VCL block is an optional (non-core) extension to Moodle, which itself in completely independent of the VCL project. That is, there is no dependency relationship between the two projects.
It just happens that many campuses that run the VCL also run an instance of Moodle (a learning management system). The code I am referring to runs inside of Moodle (as an extension) and communicates with the VCL over its XML-RPC API. Aaron On Aug 10, 2012, at 5:37 PM, Kevan Miller wrote: > The VCL block is optional? Or Moodle is optional? As long as the VCL does not > require GPL/LGPL (or other category X licenses), then that would seem to be > ok. > > --kevan > On Aug 10, 2012, at 2:35 PM, Aaron Coburn wrote: > >> I have cleaned up the VCL block I wrote for Moodle and tested it with >> version 2.3. I would like to release it, but one of you might be able to >> give some insight into the licensing details. >> >> Moodle is licensed under the GPL v3 and the VCL is licensed under the Apache >> license v2. Are there any incompatibilities there? Is there any reason that >> the moodle plugin needs to be licensed under the GPL or can it be released >> under the Apache license? I would like to make the license as compatible as >> possible with the VCL so that the project would be able to distribute this >> code as well (since there seems to be interest). >> >> Thanks in advance! >> >> Aaron >> >> >> -- >> Aaron Coburn >> Systems Administrator and Programmer >> Academic Technology Services, Amherst College >> [email protected]<mailto:[email protected]> >> >> >> >> >> >> >
