-
Notifications
You must be signed in to change notification settings - Fork 847
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a CLA to VVV #366
Comments
Is a CLA a Contributor License Agreement? |
Yes. I'm still wrapping my head around whether it's really necessary. I think once we have a license, most of this kind of goes away. |
Have a look at https://www.clahub.com/ - maybe it is an option you like. License and CLA text is still needed, of cause. |
I'd recommend closing this out as "won't fix". It deters people from participating and makes it impossible for many corporate employees to contribute.
http://www.infoworld.com/t/javascript/joyent-makes-it-easier-contribute-code-nodejs-244152 http://www.infoworld.com/d/open-source-software/red-hat-joyent-and-others-break-down-licensing-barriers-244727 is also a good read. |
@lloydde Agreed. I think once we get the licensing in order, being explicit about that in Contributing.md will be enough. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Acronyms. :)
As we figure out where to go with licensing in #346, we should also think about whether the use of a CLA is appropriate for VVV.
If we do use a CLA, I don't want it to be a difficult process. Contributions should be easy. It's possible that we just need to be explicit about licensing in the contributing document.
The text was updated successfully, but these errors were encountered: