3 ms·
I think it's strange to say that a project with source code published under an open source license isn't open source because it isn't developed in a collaborati
by schoen 12y ago
I think it's strange to say that a project with source code published under an open source license isn't open source because it isn't developed in a collaborative way with public input. We need different terminology to distinguish these things.
There are a number of closely-held and opaque projects that practice software development in a not-particularly-transparent way and don't solicit or welcome input from the general public. Their output can still be open source, though! It's just not what people have grown to expect.
Historically, a lot of the Free Software Foundation's projects were like this. They didn't offer public access to their version control systems, the development was primarily done by officially FSF-approved developers, and they made (sometimes relatively infrequent) periodic official source releases with lots of big changes. Some people called these intermittent releases "throwing code over the transom". They didn't always specifically invite the public to take an ongoing active role (though of course outside developers did contribute patches).
Another interesting example is NetHack (whose official Dev Team is famously secretive and slow to make official releases), and, until recently (except for the licensing problems) TrueCrypt. And, so I've heard, the Android Open Source Project.
The article says
The original idea behind “the commons” was that by everyone putting in a little bit we could build software better and more sustainably.
I find this a little historically suspect. It depends on whose notion of the commons and at what point in software history. Some notions of nonproprietary software with rather long historical pedigrees include: it's culturally weird to restrict who can use software or for what; it's too much bother to try to restrict the use or distribution of software; end users deserve control and freedom when they use software; making software available for unrestricted use helps it become part of infrastructure that its developers and other people value; getting open source software out there helps commoditize complementary goods.
And there are some rather concrete reasons that someone would want open source software instead of proprietary software even if it's not developed in a collaborative way at all.
* Transparency about what the software does
* The ability to do audits for backdoors, bugs, and malware
* The right to fork the code if one's interests or judgments diverge sharply from the upstream developers' over the long run
* Avoiding the risk of abandonware if the upstream developer goes out of business or decides to stop developing the software
- 650REDHAIR 12y ago>* Transparency about what the software does >* The ability to do audits for backdoors, bugs, and malware >* The right to fork the code if one's interests or judgments diverge sharply from the upstream developers' over the long run >* Avoiding the risk of abandonware if the upstream developer goes out of business or decides to stop developing the software This is the boat that we're in. Our libraries, transports, and server code are open-sourced to provide more transparency and make it an easier decision to build on or migrate to us. As much as I'd love more community involvement- we just aren't there yet and I hope that we aren't faced with similar criticism in the future.
- saraid216 12y ago> The article says You lost a bunch of text at this point. Seems like it might be important.
- schoen 12y agoJust not indented properly. :-) The paragraph that followed that is quoted from the article.
- leccine 12y agoWell you can do audits for backdoors and malware without having the source code. It is a common misconception in open source communities that you cannot do these without the source. If you check the pro security guys, they do not care about source code too much, it makes exploitation a bit easier but that is it. On the top of that, having the source code does not guarantee that you will find the security bugs either. See OpenBSD weakened crypto.
- schoen 12y agoI think this is something of a continuum from actively hostile to external audit (proprietary EULAs and legal threats; binary code obfuscation) to actively welcoming of it (an open source project like Tor that will give advice to researchers who are studying or reviewing it, or other projects that try to encourage audits in other ways). I agree that it's much more feasible to read binaries than we tend to think, and that they're intelligible artifacts that many people do make a habit of studying.