Re:Ask HN: If you open source some code, are you responsible...
by jrochkind1 on Saturday December 06, 2014 @05:51PM
(#8710506)
I disagree. It's certainly still 'open sourcing' if it's released under an open source license.
But some people (like you) will assume by default that it is supported. So be clear in your README that it ain't. I think we should start popularizing the term 'abandonware' here -- some code starts out as abandonware, but other code becomes so when the authors lose interest. We all know that using abandonware is 'riskier' to your project long-term than using supported open source, and many of us find ourselves depending on abandonware that used to be supported, and looking for alternatives. So it goes.
And especially for 'abandonware', I think it's actually much better to put it in a github repo than as a .tar.gz. One of the main uses for born-abandoned open source would be to look at the source code as an example and copy-paste from it, and a github repo makes those sorts of uses a lot easier in several ways than a .tar.gz.
But some people (like you) will assume by default that it is supported. So be clear in your README that it ain't. I think we should start popularizing the term 'abandonware' here -- some code starts out as abandonware, but other code becomes so when the authors lose interest. We all know that using abandonware is 'riskier' to your project long-term than using supported open source, and many of us find ourselves depending on abandonware that used to be supported, and looking for alternatives. So it goes.
And especially for 'abandonware', I think it's actually much better to put it in a github repo than as a .tar.gz. One of the main uses for born-abandoned open source would be to look at the source code as an example and copy-paste from it, and a github repo makes those sorts of uses a lot easier in several ways than a .tar.gz.