-
Notifications
You must be signed in to change notification settings - Fork 339
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
Change license to MIT #125
Comments
Hi Omar, |
Hi Omar,
Makes sense for all tutor plugins and Tutor itself.
Yes, definitly. As the owner of code (overhang/edly) can re-license to whatever license you need if you've got a Contributor License Agreement (CLA) from all non-edly contributors.
👍🏼
Understood. So what do you recommend regarding copyrighted materials? Say if Edly creates a theme for a customer, would that mean the logo and all the CSS styles have to be AGPL? It used to be the customary that Open edX is AGPL except for the custom plugins like (marketing site, Carin, Figures, Theme Designer and Theme). |
This is not the case, so we are not able to change the license.
I'm not sure I understand. What copyrighted materials are you referring to? You mean logos? It's perfectly OK to include a copyrighted logo in an AGPL codebase.
Yes, if it is based on Indigo.
I'm confused. You're saying the edx-platform themes are not AGPL? According to the license, all files in edx-platform are AGPL, including in themes/. Whatever is the status of themes in Open edX, the choice of AGPL for Indigo is one that I made a long time ago, way before Edly became the custodian of Indigo, so we can't really do anything about it... And in a certain way, it's also for the better, right? Because it guarantees that Indigo remains free forever for everyone. We wouldn't have the same guarantee if Indigo was MIT. |
Thanks Regis. I'll check and let you know. |
Thank you @OmarIthawi and @regisb for discussing this @regisb , just to double check. By plugins, when you said:
you mean only the official plugins for tutor, right? if someone created a plugin from scratch or cookiecutter, it would be included in the (must be AGPL) --- there is actually a license field question when using cookiecutter to create a plugin. Please correct me if I'm wrong 🌷 |
Yes, this is correct. The Tutor plugin system is licensed as Apache 2.0 https://docs.tutor.edly.io/#license Which means that developers can create plugins with the license of their choice, as long as they don't import directly from Tutor non-API functions. |
Thanks @regisb for your kind replies. I'll mark this as complete :) |
Hi, thanks for creating this high quality theme!
Is the AGPL license choice an intentional one?
I'm unsure if it's appropriate for the theme. It makes sense for Tutor and other parts of the platform but it's customary that theme is full of copyright materials that would conflict with AGPL (as far as I understand) even if it's made a public repository because the AGPL license is a vairal license.
What do you think?
The text was updated successfully, but these errors were encountered: