4 ms·
Open sourcing does not imply future maintenance. That's why everyone should evaluate the state of a project before starting to use it.
by svisser 12y ago
Open sourcing does not imply future maintenance. That's why everyone should evaluate the state of a project before starting to use it.
- duskwuff 12y agoThere is one good point made, though: if you don't plan on maintaining a project, you might as well disable issues and pull requests on Github. Leaving them on gives the (false) impression that you'll respond to them.
- johncoltrane 12y agoPutting the site on a social site and setting up an issue tracker implies future maintenance. Making it clear in the README that no maintenance is guaranteed and disabling the issue tracker should be enough to send the message to would be users. If the OP doesn't do that he is actively implying future maintenance.
- dalke 12y agoIt does not imply future maintenance, any more than having an account on Facebook means that you'll reply to anyone else's comment, pokes, or app requests, or that you'll even log in again. Having an account on Twitter doesn't mean there's an obligation to respond to every tweet directed your way. In dating web sites there's no obligation to reply to every "hi, I'm interested in you" message. In fact, in no social site I know of has an obligation for future engagement. Why is code different? You also assume that "social" => "with the world." If I want to work on a project with friends in California and New Zealand, why not set it up as a public account on github? We're being social, just not social with you. Our obligations are towards each other, not some stranger on the internet.