07/24/2016
NodeSummit 2016







06/15/2014
Node REPL

Contribute to Node in 10 "Easy" Steps

05/31/2016
Tweet about this blog entry:

This is an exciting time in the NodeJs community(1). Heck, even my dog, Professor (pictured above), got himself ready at my laptop to hack at some code and contribute! Actually, I think he smelled food on my desk and went after it, till I caught him in the act.

Seriously, though, as @rvagg mentions(1), "2015 was arguably the year that Node.js grew up", the foundation was formed, big companies backed its progress, and, in fact, the data shows how much progress was being made. Alas, this entry basks in all of the above and tries to help with the next step for all of us, contributing.

Anticipated Question: How is this article better than all the other how-to-contribute articles(2) out there?

Answer: It's not better! It is, however, different, in that I tried to meet the goal, that I feel is, the happy medium between brevity and verbosity. Big words! There's the payoff for my bachelor's degree. :-P What do I mean? I hope most, if not all, readers find this to be a good reference for a quick memory refresher when we're in the middle of trying to give back to our community out there.

One last note, I put quotes around the word, "Easy", in the title for good reason. Depending on where you're at with git or GitHub, the topic in this article could actually be really difficult. But, again, my goal was to provide a compromise between being too wordy and not having enought detail, to serve as a quick reference when we're contributing to the community. So, some experience with git and/or GitHub is assumed.

One other difference about this article is that, although I don't mention Node much in here, these are the steps that will work for contributing to it--as I have recently, albeit not to core, yet. I would also like to refer everyone to @rvagg's JSConf (Uruguay) video, where he gives some really good tips on how to start contributing to Node.

Enough rambling...

TL;DR

These are the steps to contribute. The links are to in-depth documentation for each.

  1. Fork
  2. Clone
  3. Branch
  4. Code
  5. Test
  1. Commit
  2. Push
  3. PR
  4. Discuss
  5. Land

Illustrated Version

1. Fork

2. Clone

3. Branch

4. Code

5. Test

6. Commit

7. Push

8. PR

9. Discuss

10. Land


Tweet about this blog entry:

Comments/Discussion