scratchfoundation/scratch-blocks
1
0
Fork 0
mirror of https://github.com/scratchfoundation/scratch-blocks.git synced 2025-08-28 22:10:31 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Add missing CLAs info to the contributing file (#1119)

Browse source 
* Add missing CLAs info to the contributing file

* Added larger changes paragraph
This commit is contained in:
RoboErikG 2017-05-22 11:33:30 -07:00 • committed by GitHub
parent 65908e8874
commit c53605fef4
1 changed files with 31 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

33
CONTRIBUTING.md
View file

@ -1,5 +1,34 @@
# Contributing to Blockly
Please make pull requests against develop, not master. If your patch needs to go into master immediately, include a note in your PR.
Want to contribute? Great!
- First, read this page (including the small print at the end).
- Second, please make pull requests against develop, not master. If your patch
needs to go into master immediately, include a note in your PR.
For more information, head over to the [Blockly Developers site](https://developers.google.com/blockly/guides/modify/contributing).
For more information on style guide and other details, head over to the [Blockly Developers site](https://developers.google.com/blockly/guides/modify/contributing).
### Before you contribute
Before we can use your code, you must sign the
[Google Individual Contributor License Agreement](https://cla.developers.google.com/about/google-individual)
(CLA), which you can do online. The CLA is necessary mainly because you own the
copyright to your changes, even after your contribution becomes part of our
codebase, so we need your permission to use and distribute your code. We also
need to be sure of various other things—for instance that you'll tell us if you
know that your code infringes on other people's patents. You don't have to sign
the CLA until after you've submitted your code for review and a member has
approved it, but you must do it before we can put your code into our codebase.
### Larger changes
Before you start working on a larger contribution, you should get in touch with
us first through the issue tracker with your idea so that we can help out and
possibly guide you. Coordinating up front makes it much easier to avoid
frustration later on.
### Code reviews
All submissions, including submissions by project members, require review. We
use Github pull requests for this purpose.
### The small print
Contributions made by corporations are covered by a different agreement than
the one above, the
[Software Grant and Corporate Contributor License Agreement](https://cla.developers.google.com/about/google-corporate).