Closed gmarcos87 closed 6 years ago
+1 Can you write on lime-dev mailing list proposing the license which better fits in your opinion?
I would add a default LICENCE file on the root of the repository which will act as default LICENCE in case there is not a specific licence inside the specific package.
I vote for AGPLv3
I'm quite ignorant on this but AGPLv3 seems good also for me. In my opinion it's important to have this sorted out as soon as possible. I read devs discussing about using a custom license/modifying heavily an existing one, I'm against this.
If you run:
git log --pretty="%an %ae%n%cn %ce" ./ | sort | uniq
This is the list of contributors:
There are several duplicate users, filtering in total are between 15 and 20 people. Do we need the approval of all of them?
I trust and support your collective decision, and agree about urgency
It would take too long to wait for al contributors to answer.
But there are few which contriuted most of the code, so I would wait to have the approval of this 5-6 people. If some of the "minor contributors" is not speaking now and he has problems with AGPLv3, we will manage it in the future (in the worst case we can rewrite the code, but I don't think it will be necessary).
https://github.com/libremesh/lime-packages/graphs/contributors
I vote for accepting this PR as soon as possible... it is worst to have no license than having one too free.
@altergui can you aprove the PR so your opinion will be officialy recorded?
Closed by merge of #226
I was analyzing the licensing situation in the lime-packages repository. There is no file that indicates the global license, there is no CLA (Contributor License Agreements) and there are copyright headers set in some files inconsistently. Talking with some of the developers we consider it appropriate to establish a license (such as GLPv3 or AGPLv3). This would affect future contributions, but it would be necessary for contributors to accept that their already written code is also licensed. To solve this situation I propose: