node/CONTRIBUTING.md

Contributing to io.js

Issue Contributions

When opening new issues or commenting on existing issues on this repository please make sure discussions are related to concrete technical issues with the io.js software.

Discussion of non-technical topics including subjects like intellectual property, trademark and high level project questions should move to the node-forward discussions repository instead.

Code Contributions

The io.js project has an open governance model and welcomes new contributors. Individuals making significant and valuable contributions are made Collaborators and given commit-access to the project. See the GOVERNANCE.md document for more information about how this works.

This document will guide you through the contribution process.

Step 1: Fork

Fork the project on GitHub and check out your copy locally.

$ git clone git@github.com:username/io.js.git
$ cd io.js
$ git remote add upstream git://github.com/iojs/io.js.git

Which branch?

Now decide if you want your feature or bug fix to go into the master branch or the stable branch. As a rule of thumb, bug fixes go into the stable branch while new features go into the master branch.

The stable branch is effectively frozen; patches that change the io.js API/ABI or affect the run-time behavior of applications get rejected. The current stable branch is set as the default branch on GitHub.

Respect the stability index

The rules for the master branch are less strict; consult the stability index for details.

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 and up are off-limits.

Dependencies

io.js has several bundled dependencies in the deps/ and the tools/ 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 projects. Do not send your patch to us, we cannot accept it.

In case of doubt, open an issue in the issue tracker or contact one of the project Collaborators (IRC 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 does not align with the project team.

Step 2: Branch

Create a feature branch and start hacking:

$ git checkout -b my-feature-branch -t origin/v1.x

(Where v1.x is the latest stable branch as of this writing.)

Step 3: Commit

Make sure git knows your name and email address:

$ git config --global user.name "J. Random User"
$ git config --global user.email "j.random.user@example.com"

Writing good commit logs is important. A commit log should describe what changed and why. Follow these guidelines when writing one:

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 subsystem (e.g. "net: add localAddress and localPort to Socket").
2. Keep the second line blank.
3. Wrap all other lines at 72 columns.

A good commit log can look something like this:

subsystem: explaining the commit in one line

Body of commit message is a few lines of text, explaining things
in more detail, possibly giving some background about the issue
being fixed, etc. etc.

The body of the commit message can be several paragraphs, and
please do proper word-wrap and keep columns shorter than about
72 characters or so. That way `git log` will show things
nicely even when it is indented.

The header line should be meaningful; it is what other people see when they run git shortlog or git log --oneline.

Check the output of git log --oneline files_that_you_changed to find out what subsystem (or subsystems) your changes touch.

Step 4: Rebase

Use git rebase (not git merge) to sync your work from time to time.

$ git fetch upstream
$ git rebase upstream/v1.x  # or upstream/master

Step 5: Test

Bug fixes and features should come with tests. Add your tests in the test/simple/ directory. Look at other tests to see how they should be structured (license boilerplate, common includes, etc.).

$ make jslint test

Make sure the linter is happy and that all tests pass. Please, do not submit patches that fail either check.

If you are updating tests and just want to run a single test to check it, you can use this syntax to run it exactly as the test harness would:

$ python tools/test.py -v --mode=release simple/test-stream2-transform

You can run tests directly with node:

$ node ./test/simple/test-streams2-transform.js

Step 6: Push

$ git push origin my-feature-branch

Go to https://github.com/yourusername/io.js and select your feature branch. Click the 'Pull Request' button and fill out the form.

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 feature branch. Post a comment in the pull request afterwards; GitHub does not send out notifications when you add commits.

Caine's Requirements

Hello!

I am pleased to see your valuable contribution to this project. Would you please mind answering a couple of questions to help me classify this submission and/or gather required information for the core team members?

Questions:

• Issue-only Does this issue happen in core, or in some user-space module from npm or other source? Please ensure that the test case that reproduces this problem is not using any external dependencies. If the error is not reproducible with just core modules - it is most likely not a io.js problem. Expected: yes
• Which part of core do you think it might be related to? One of: debugger, http, assert, buffer, child_process, cluster, crypto, dgram, dns, domain, events, fs, http, https, module, net, os, path, querystring, readline, repl, smalloc, stream, timers, tls, url, util, vm, zlib, c++, docs, other (label)
• Which versions of io.js do you think are affected by this? One of: v0.10, v0.12, v1.0.0 (label)
• PR-only Does make test pass after applying this Pull Request. Expected: yes
• PR-only Is the commit message properly formatted? (See CONTRIBUTING.md for more information) Expected: yes

Please provide the answers in an ordered list like this:

1. Answer for the first question
2. Answer for the second question
3. ...

Note that I am just a bot with a limited human-reply parsing abilities, so please be very careful with numbers and don't skip the questions!

In case of success I will say: ...summoning the core team devs!.

In case of validation problem I will say: Sorry, but something is not right here:.

Truly yours, Caine.

Responsibilities

• indutny: crypto, tls, https, child_process, c++
• trevnorris: buffer, http, https, smalloc
• bnoordhuis: http, cluster, child_process, dgram