-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[GH Request] Change openedx-events library license #826
Comments
Thank you for your report! @openedx/axim-oncall will triage within a business day. Simple requests usually take 2-3 business days to resolve; more complex requests could take longer. |
@arbrandes I can take this one if you like, since I've been on it for a bit. It's just waiting on legal to get back from PTO to get an official resolution. |
Alright, thank you @bmtcril! I'm reassigning it to you. |
Per issue #184 and openedx/axim-engineering#826 and with input from Axim and 2U legal we are re-licensing this code and package to more explicitly allow private plug-in functionality on top of it.
This should be resolved with openedx/openedx-events#258 . I'll close this when that merges. |
Firm Name
eduNEXT
Urgency
Low (2 weeks)
Problem/Request
Change the license of
openedx-events
from AGLP V3 to Apache 2.0.Reasoning
2 different members of 2U have requested that we change the AGPL V3 license of the
openedx-events
repository to something that allows having private repos with a dependency onopenedx-events
.The issue were the conversation is happening: openedx/openedx-events#184.
Drawing from previous experience in this project the xblock library was licensed as Apache 2.0 I believe for this same reason.
I believe this decision should apply to openedx-filters as well, but I understand if they need to be made separately.
Finally, as co-author of the library, I should state my personal opinion on the matter. I think given that openedx-events are the gateway to event bus which already separates different pieces of running code neatly, there is already a hard API there that could be leveraged through many workarounds to keep code private and not have a dependency on
openedx-events
. It is not a matter of the license not allowing developers to use events this way, but more like officially validating this option.I'd would like to see more organizations collaborating on the core and having more and better defined events. I don't mind that implementations of what is done after the event propagates can remain private. History on this project has shown that is is not the publication of the code, but the documentation, maintenance and ongoing on-boarding of new comers what makes a package valuable.
The text was updated successfully, but these errors were encountered: