nextcloud-filelink
nextcloud-filelink copied to clipboard
License and Acknowledgements
Thank you for working on this add-on. I've noticed that you have mentioned my name under "created by". I appreciate the attribution, but my role in this is not necessarily the creation. In order to avoid confusion maybe you can separate this to a section for authors whose sources you have used.
Also, as far as I am aware, those files that you have re-used from my MPL-licensed extension must be dual licensed MPL/AGPL, or if all files are derivatives of my extension then it must remain MPL.
@kewisch - Thanks for the feedback and your work :). We'll take a look.
Also, as far as I am aware, those files that you have re-used from my MPL-licensed extension must be dual licensed MPL/AGPL, or if all files are derivatives of my extension then it must remain MPL.
@schiessle Can you confirm? If it is, then I'll take a look to see how we re-used the original code.
Any update on this?
@schiessle could you confirm (next week) that all files which are derivatives have to remain under the MPL license? Last time we talked, I was under the impression that we were able to change the license to AGPL.
Still waiting on a response here. Can we bring this issue to a close?
sorry that it took me so long to response here. Somehow I missed this issue completely.
@kewisch you are right. The MPL is a GNU (A)GPL compatible license as as such it can be used for Nextcloud apps. But the files licensed under the MPL will of course stay under the MPL. Changes to files licensed under the MPL could be labeled as dual licensed MPL/AGPL or just MPL (would be my recommendation to keep it easy). New files can be licensed under the GNU AGPL only (my recommendation), the MPL only or again dual licensed. But we can't remove the MPL license from any MPL licensed code.
Compatible only means that you can combine software under both licenses and that the stronger license will defined what you can do with the combined work (in this case this will be the GNU AGPL). But each individual code will keep its license.
We will fix this as soon as possible. Again sorry, for the delay.
I just realized now, that it is about the Thunderbird plugin and not about a Nextcloud app. I shouldn't answer github issues that late in the evening :wink:
So please ignore the part about the AGPL and the compatibility, it is not relevant here. In this case I would just stick to the MPL for the whole addon to keep it simple, if possible. If we already had community contributions under the AGPL we should keep the original code MPL and the rest AGPL because we can't change copyright of other people code.
So, how do we proceed since some code has already been released under the AGPL?
We have 6 contributors. Should be possible to get their approval:
We need a approval from:
@oparoz @jospoortvliet @nickvergessen @guillaumev @tbille @c4539
Please comment below if you agree to relicense the whole plugin under the MPL. Thanks!
I agree that the whole plugin is relicensed under MPL
I agree that the whole plugin is relicensed under MPL
I agree that the whole plugin is relicensed under MPL
I agree that the whole plugin is relicensed under MPL
I agree that the whole plugin is relicensed under MPL :+1:
Ping @tbille ;)
Sorry for the late answer
I agree that the whole plugin is relicensed under MPL
Awesome, thank you all.
@schiessle - Next step is to create a PR to change all the headers?