Hacker News new | ask | show | jobs
by tomjen3 5213 days ago
> You have an obligation to release code that is tested. Automated spec is preferrable. You have an obligation to document your code and build process, most especially — your contribution and pull request policy

No I don't. Unless I signed a document saying otherwise you should consider yourself damn lucky that you get to access my source code.
1 comments
edwardhotchkiss 5213 days ago
Correct. You don't, unless you'd like other developers to contribute to your project.

You also owe it to yourself. But hey: if you want to post sloppy seconds untested code on GitHub - consider yourself lucky that they let anyone in.

link
city41 5213 days ago
I'm honestly not sure if I want other developers to contribute. All of my github repos are personal projects. I have no problem with them being open source (and they are all rather tidy and well tested btw) and no problem at all with patches, pull requests, bug reports and such from other people. But if one took off then suddenly my little baby project becomes a second full time job. Popular open source projects are a lot of work for the maintainers. I'd only want that to happen if it was a project I was particularly passionate about.
link