People seem to be questioning the validity of having domain knowledge in node/heroku/mongodb and an approved pull request be a prerequisite for joining a site not obviously about node development, not to the idea of an open source site in and of itself. If people had to learn Arc and have a pull request approved just to join HN, there would be maybe two or three people here.
Well, I managed to get a local instance running, poke around then hack together something. I would by no means call it 'borderline facile' though, just a set of annoying dependencies to install and hoops to jump through. That said, getting it set up was easier than I anticipated. (though granted, nobody has to do any of that to submit a pull request...)
Comments
People seem to be questioning the validity of having domain knowledge in node/heroku/mongodb and an approved pull request be a prerequisite for joining a site not obviously about node development, not to the idea of an open source site in and of itself. If people had to learn Arc and have a pull request approved just to join HN, there would be maybe two or three people here.
Node, Arc, MongoDB, and Heroku are not difficult to learn at all. All are borderline facile.
I don't think it's an unreasonable boundary at all and I strongly dislike those specific technologies.
If you don't have the willpower or gumption to contribute to the community, then I don't really care to read what you have to say at all.
tl;dr lazybones need not apply
Well, I managed to get a local instance running, poke around then hack together something. I would by no means call it 'borderline facile' though, just a set of annoying dependencies to install and hoops to jump through. That said, getting it set up was easier than I anticipated. (though granted, nobody has to do any of that to submit a pull request...)
You could make design changes using github's web interface and submit a pull that way.
Ah, you're right.