1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: add final full stop in CONTRIBUTING.md

Browse Source 
PR-URL: https://github.com/nodejs/node/pull/3576
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
This commit is contained in:
Emily Aviva Kapor-Mater 2015-10-29 14:52:36 -07:00 committed by Rich Trott
parent be65f5f250
commit b7cc19c8f5
1 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
CONTRIBUTING.md
View File

@ -45,21 +45,21 @@ and built upon.
The rules for the master branch are less strict; consult the The rules for the master branch are less strict; consult the
[stability index](./doc/api/documentation.markdown#stability-index) for details. [stability index](./doc/api/documentation.markdown#stability-index) for details.
In a nutshell, modules are at varying levels of API stability. Bug fixes are In a nutshell, modules are at varying levels of API stability. Bug fixes are
always welcome but API or behavioral changes to modules at stability level 3 always welcome but API or behavioral changes to modules at stability level 3
(Locked) are off-limits. (Locked) are off-limits.
#### Dependencies #### Dependencies
Node.js has several bundled dependencies in the *deps/* and the *tools/* Node.js has several bundled dependencies in the *deps/* and the *tools/*
directories that are not part of the project proper. Any changes to files directories that are not part of the project proper. Any changes to files
in those directories or its subdirectories should be sent to their respective in those directories or its subdirectories should be sent to their respective
projects. Do not send your patch to us, we cannot accept it. projects. Do not send your patch to us, we cannot accept it.
In case of doubt, open an issue in the In case of doubt, open an issue in the
[issue tracker](https://github.com/nodejs/node/issues/) or contact one of the [issue tracker](https://github.com/nodejs/node/issues/) or contact one of the
[project Collaborators](https://github.com/nodejs/node/#current-project-team-members). [project Collaborators](https://github.com/nodejs/node/#current-project-team-members).
([IRC](http://webchat.freenode.net/?channels=io.js) is often the best medium.) Especially do so if you plan to work on something big. Nothing is more ([IRC](http://webchat.freenode.net/?channels=io.js) is often the best medium.) Especially do so if you plan to work on something big. Nothing is more
frustrating than seeing your hard work go to waste because your vision frustrating than seeing your hard work go to waste because your vision
does not align with the project team. does not align with the project team.
@ -81,8 +81,8 @@ $ git config --global user.name "J. Random User"
$ git config --global user.email "j.random.user@example.com" $ git config --global user.email "j.random.user@example.com"
``` ```
Writing good commit logs is important. A commit log should describe what Writing good commit logs is important. A commit log should describe what
changed and why. Follow these guidelines when writing one: changed and why. Follow these guidelines when writing one:
1. The first line should be 50 characters or less and contain a short 1. The first line should be 50 characters or less and contain a short
description of the change prefixed with the name of the changed description of the change prefixed with the name of the changed
@ -124,15 +124,15 @@ $ git rebase upstream/master
### Step 5: Test ### Step 5: Test
Bug fixes and features **should come with tests**. Add your tests in the Bug fixes and features **should come with tests**. Add your tests in the
test/parallel/ directory. Look at other tests to see how they should be test/parallel/ directory. Look at other tests to see how they should be
structured (license boilerplate, common includes, etc.). structured (license boilerplate, common includes, etc.).
```text ```text
$ ./configure && make -j8 test $ ./configure && make -j8 test
``` ```
Make sure the linter is happy and that all tests pass. Please, do not submit Make sure the linter is happy and that all tests pass. Please, do not submit
patches that fail either check. patches that fail either check.
If you are updating tests and just want to run a single test to check it, you If you are updating tests and just want to run a single test to check it, you
@ -160,9 +160,9 @@ $ git push origin my-feature-branch
Go to https://github.com/yourusername/node and select your feature branch. Go to https://github.com/yourusername/node and select your feature branch.
Click the 'Pull Request' button and fill out the form. Click the 'Pull Request' button and fill out the form.
Pull requests are usually reviewed within a few days. If there are comments Pull requests are usually reviewed within a few days. If there are comments
to address, apply your changes in a separate commit and push that to your to address, apply your changes in a separate commit and push that to your
feature branch. Post a comment in the pull request afterwards; GitHub does feature branch. Post a comment in the pull request afterwards; GitHub does
not send out notifications when you add commits. not send out notifications when you add commits.
@ -201,7 +201,7 @@ CoC](http://www.rust-lang.org/conduct.html).
* Please keep unstructured critique to a minimum. If you have solid * Please keep unstructured critique to a minimum. If you have solid
ideas you want to experiment with, make a fork and see how it works. ideas you want to experiment with, make a fork and see how it works.
* We will exclude you from interaction if you insult, demean or harass * We will exclude you from interaction if you insult, demean or harass
anyone. That is not welcome behavior. We interpret the term anyone. That is not welcome behavior. We interpret the term
"harassment" as including the definition in the [Citizen Code of "harassment" as including the definition in the [Citizen Code of
Conduct](http://citizencodeofconduct.org/); if you have any lack of Conduct](http://citizencodeofconduct.org/); if you have any lack of
clarity about what might be included in that concept, please read clarity about what might be included in that concept, please read
@ -211,11 +211,11 @@ CoC](http://www.rust-lang.org/conduct.html).
you feel you have been or are being harassed or made uncomfortable you feel you have been or are being harassed or made uncomfortable
by a community member, please contact one of the channel ops or any by a community member, please contact one of the channel ops or any
of the TC members immediately with a capture (log, photo, email) of of the TC members immediately with a capture (log, photo, email) of
the harassment if possible. Whether you're a regular contributor or the harassment if possible. Whether you're a regular contributor or
a newcomer, we care about making this community a safe place for you a newcomer, we care about making this community a safe place for you
and we've got your back. and we've got your back.
* Likewise any spamming, trolling, flaming, baiting or other * Likewise any spamming, trolling, flaming, baiting or other
attention-stealing behavior is not welcome. attention-stealing behavior is not welcome.
* Avoid the use of personal pronouns in code comments or * Avoid the use of personal pronouns in code comments or
documentation. There is no need to address persons when explaining documentation. There is no need to address persons when explaining
code (e.g. "When the developer") code (e.g. "When the developer").