Switch license to AGPL to harmonize with the other pleroma projects. #6

Closed
opened 2019-03-05 15:41:08 +00:00 by lambadalambda · 9 comments
No description provided.
Member

switching project's license requires you to have a significant copyright ownership, I am quite sure admin-fe has more than 50% of it's code from vue-element-admin

switching project's license requires you to have a significant copyright ownership, I am quite sure admin-fe has more than 50% of it's code from vue-element-admin
Author
Owner

MIT is AGPL compatible, so we should be able to relicense it. Either way, having something like "admin-fe is licenced under APGL. It is based on vue-element-admin, which is licensed under the MIT license" should work.

MIT is AGPL compatible, so we should be able to relicense it. Either way, having something like "admin-fe is licenced under APGL. It is based on vue-element-admin, which is licensed under the MIT license" should work.
Member

From the text of MIT license:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

I am not a license expert, but I undestand it as "as long as you are not the copyright owner you should distribute this software under an MIT license".

And even if I get it wrong relicensing it under AGPL just to keep consistency disallows the author to incorporate changes from us, which to me seems like a rude move tbh

From the text of MIT license: > The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. I am not a license expert, but I undestand it as "as long as you are not the copyright owner you *should* distribute this software under an MIT license". And even if I get it wrong relicensing it under AGPL just to keep consistency disallows the author to incorporate changes from us, which to me seems like a rude move tbh
Member

The way that you handle this is by putting the AGPL text first, then the MIT text. I can prepare a MR which does this in a little bit.

The way that you handle this is by putting the AGPL text first, then the MIT text. I can prepare a MR which does this in a little bit.
Member

So it will be dual licensed? Not sure what's the point tbh, it is not like we can't include MIT-licensed software to AGPL licensed software

So it will be dual licensed? Not sure what's the point tbh, it is not like we can't include MIT-licensed software to AGPL licensed software
Member

The code related to vue-element-admin will remain MIT, but what we build on top of it will be AGPL.

The code related to vue-element-admin will remain MIT, but what we build on top of it will be AGPL.
Member

Oh, makes sense

Oh, makes sense
Member
Does this look appropriate? @rinpatch @kaniini @lambadalambda https://git.pleroma.social/maxf/admin-fe/tree/chore/readme#license
Member

I merged it, reopen this issue if you think we need anything changed

I merged it, reopen this issue if you think we need anything changed
Sign in to join this conversation.
No labels
blocked
stale
No milestone
No project
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pleroma/admin-fe#6
No description provided.