I don't really know where/how I would start with this though, do I just browse NPM, find some package that I'm familiar with, check the issues log and go to work on one? Do I approach the developers beforehand and get their thoughts/consent to work on something and submit a pull request, (putting all the work in for a pull request that gets ignored seems like it would be quite annoying)? I'm confident that I can contribute solid code, I guess the process itself is what I'm inexperienced with. If there is anyone on here that is in need of some open source junior level JS development please feel free to contact me, I'll be over at the Who's Hiring Thread.
Ask HN: Where can I begin contributing to Node, MEAN stack, JavaScript projects?
1–9 of 9 posts
Re: Ask HN: Where can I begin contributing to Node, MEAN stack, JavaScript projects?
#2If you're a noob and do wanna go the FOSS route, find libraries you use and are familiar with and contribute. Contributing can be in the form of issue identification and potentially fork/PR's. OR scratch your own itch, even if it's not totally productive. I helped build a Dota2 API gem and I have yet to use it for a project. If you want to go into the actual application building mode, then do check out Assembly. Plenty of JS projects there: https://github.com/asm-products
[0] - https://assembly.com/
Re: Ask HN: Where can I begin contributing to Node, MEAN stack, JavaScript projects?
#3http://blog.smartbear.com/programming/14-ways-to-contribute-...
Re: Ask HN: Where can I begin contributing to Node, MEAN stack, JavaScript projects?
#4Re: Ask HN: Where can I begin contributing to Node, MEAN stack, JavaScript projects?
#5I'm still convinced Assembly[0] is the greatest platform for budding developers to get experience, potentially earn some money, and network with other developers. Trying to commit to open source as a newbie is...well...hard. Most mature FOSS products feel like monstrosities and culturally are intimidating (omg dhh is gonna think I suck). If you're a noob and do wanna go the FOSS route, find libraries you use and are…
I agree about intimidation. Some FOSS have very steep contribution requirements.
Here's a slightly exaggerated example:
Oh, you want to add a patch that moves line of code up by 5 lines? Well, first, you need to sign up in our separate issue tracker. Create new issue with properly formatted title and description and add bunch of tags you know nothing about. Don't forget screenshots and demo webpage where you can clearly see the problem. Now, you can do a PR, but you absolutely have to adhere to our issue title formatting. If there's even a tiny typo or it is not in a correct format it will be closed immediately. And then you wait for who knows how long.
Re: Ask HN: Where can I begin contributing to Node, MEAN stack, JavaScript projects?
#6> putting all the work in for a pull request that gets ignored seems like it would be quite annoying
This happens. Popular, active projects especially can be hard to break into. You can start in chat or issue threads first, then PRs once you get a feel for what's expected. Often they'll ask for PRs up front.
However if you have a clearly-beneficial, well-constructed fix, by all means submit an unsolicited PR. They ignore it at their own peril/embarrassment :)
Re: Ask HN: Where can I begin contributing to Node, MEAN stack, JavaScript projects?
#7Re: Ask HN: Where can I begin contributing to Node, MEAN stack, JavaScript projects?
#8I'm still convinced Assembly[0] is the greatest platform for budding developers to get experience, potentially earn some money, and network with other developers. Trying to commit to open source as a newbie is...well...hard. Most mature FOSS products feel like monstrosities and culturally are intimidating (omg dhh is gonna think I suck). If you're a noob and do wanna go the FOSS route, find libraries you use and are…