And what of the commits that have already been made by contributors that refuse to sign the CLA or cannot be reached? Do you have to get buy-in from everyone who has worked on the repo up until this point for the CLA to have any value?
Michael Ficarra On Saturday, October 11, 2014 9:18:54 AM UTC-7, Nicholas Zakas wrote: > > Hi all, > > I've hinted at this in the past, but I've now finally gone and setup a > Contributor License Agreement (CLA) for ESLint. I've generally been opposed > to doing so because I feared it would create an undue barrier to > contributions. Unfortunately, the lack of a CLA has meant that other open > source projects have been hesitant to use ESLint or otherwise only use > pieces of it. Orion, for example, will only use the core and any rules I > wrote, because those are the only pieces guaranteed to be under the ESLint > license. That's really lousy. > > So I created a CLA that covers the code in such a way that Orion and other > projects like it should be able to use code by anyone who electronically > signs it. Additionally, the "signature" is information that is readily > available online: GitHub username, your name, email address, and country. > I'm hoping that this balance between being a very short, readable agreement > and a very small amount of data collected will be acceptable to the > community as whole. > > If you could please take a moment to electronically sign the CLA, I'd > greatly appreciate it: > http://eslint.org/cla/ > > Thanks. > > -- > > ______________________________ > Nicholas C. Zakas > @slicknet > > Author, Professional JavaScript for Web Developers > Buy it at Amazon.com: > http://www.amazon.com/Professional-JavaScript-Developers-Nicholas-Zakas/dp/1118026691/ref=sr_1_3 > > -- You received this message because you are subscribed to the Google Groups "ESLint" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
