Re-licensing email

Bill Barry after.fallout at gmail.com
Wed Oct 14 13:29:51 UTC 2009


I got it too. I was surprised that the options were either keep 2 only 
or add 2+. I expected at some point for a potential relicensing email to 
say either keep 2 or add gplv3 to make it dual gpl2/gpl3 (but not gpl > 3).

I am actually of the opinion that we should do something like:
1. put a file in the root of the repo as a contract [a].
2. have every committer add their name to this file (and do not accept 
commits from new people without them having agreed).
3. let the people with push access have the choice to decide copyright.


a: The file would say something like (maybe after a lawyer looks at it):
By placing your name below you agree to give the persons with PUSH 
access to the repository located at 
http://hg.intevation.org/mercurial/crew the authority to make legal 
decisions regarding the Mercurial codebase including but not limited to 
the ability to change the license under which Mercurial is distributed. 
Such decisions can only be made when all such persons are in agreement 
and when the decision is in keeping with the ideal of keeping the 
Mercurial code open, available and unencumbered.


Names should be placed below this line in alphabetical order:



More information about the Mercurial-devel mailing list