-
Notifications
You must be signed in to change notification settings - Fork 351
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
Contributing oddness. #14
Comments
Now I'm not a lawyer... But it seems that the statement in the README.md is erroneous. Unless I'm using some other definition of the word "copyright."
|
The short answer is that Google says so. The longer answer is that I wrote Dart Sass as a Google employee, which means Google owns the copyright. I went through Google's official open-sourcing process to put it up on GitHub, and part of that process involves declaring that the project is "unofficial" (which I believe indicates that it's maintained in my 20% time rather than having dedicated headcount). Another part involves ensuring that Google continues to own the copyright by asking for CLAs. I'm not an expert on this, but maybe @willnorris can say more. |
The "not an official google product" is more about setting expectations for support and releases. The CLA is required of all projects that Google is the custodian of (official or not); it's designed to protect both Google and the users of the project by ensuring that all contributed code is provided under the same terms. |
Ok. Thank you to the both of you for clarifying. Not knowing any of that it just seemed super off-putting. I guess, as you state, there is more to it. |
The previous token didn't seem to be recognized. See https://travis-ci.com/github/sass/dart-sass-embedded/jobs/364028782. It's unclear why it didn'twork, but I'm hoping regenerating fixes it.
In the README.md it says:
In the CONTRIBUTING.md it says:
I fail to see the correlation in me having to sign the CLA if I want to contribute if this is not an official Google Product.
Care to explain? This seems really weird to me.
The text was updated successfully, but these errors were encountered: