"Shawn O. Pearce" <spearce@xxxxxxxxxxx> wrote: > That said, I think the license choice that makes the most sense > here is probably LGPL or GPL+gcc exception, like you note below. > BSD and MIT are probably not serious contenders. I should clarify that I said the above paragraph... > That said, I think many authors of git.git code would be more > comfortable with a GPL->LGPL change, where they wouldn't be OK with > a GPL->BSD/MIT change. There may be some folks though who still > wouldn't accept a GPL->LGPL move. because of this paragraph. Like Pierre I also prefer a BSD style license, and JGit is under that, as it offers quite a bit of freedom for the consumer of the code. I'm also not too worried about not getting changes back. If someone forks away from the base project and doesn't contribute back, that's their problem. So long as the base project has sufficient momentum under it making changes and improving things, everyone else will want to pull and either face merge-hell once in a while, or send changes back upstream to avoid merge-hell. But I doubt Git regulars share our views on this, and I think most of the major contributors to git.git have stated multiple times that they prefer a GPL style license on their code. I want those people to contribute to libgit2 (assuming the project moves past the pie-in-the-sky theory stage), so I want the license to be something they will be comfortable with. -- Shawn. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
