4 ms·
Ethical responsibilities? None. But that doesn't mean that you shouldn't open source any of your code. Spending time on things which are not your core functi
by cperciva 17y ago
Ethical responsibilities? None.
But that doesn't mean that you shouldn't open source any of your code. Spending time on things which are not your core functionality is bad -- this is why services like AWS are so popular. All of those open source libraries which you're using? They're not your core functionality -- so it's better for you to contribute your changes/improvements back so that someone else can maintain them rather than spending time on that yourself.
Tarsnap is built around the excellent bsdtar tar archiver and libarchive archive-handling library written by Tim Kientzle; whenever I write code for tarsnap which could conceivably be useful in bsdtar or libarchive (bug fixes, SIGINFO handling, reworking of internal buffering, etc) I contribute it back because it reduces the amount of work I need to do merging changes when I update to a new
version of libarchive in the future.
Of course, this argument doesn't apply if the open source code you're using is your core functionality -- but at that point, you've got bigger problems to tackle than figuring out whether you should contribute code back.
- tsally 17y agoIn this post, whenever I use GPL I am using it to refer to the class of licenses (AGPL, LGPL, and GPL proper), not the specific license. Remember that Colin is FreeBSD's security officer, so it's probably pretty obvious which camp of open source thinking he falls into. :-) I'll do my best to present the other way of thinking within the open source community. I recognize the FreeBSD school of thought and don't have a problem with it, I just think there is a better way. Let's use Colin's example and say you find and fix a bug in an open source library you are using. It is at that point I believe you have an ethical responsibility to contribute back. You found a bug and you should share the fix with everyone. Hell, the library probably wouldn't even be in a usable state if people didn't contribute patches. Patching back is what keeps the open source ecosystem flowing, and if you can encourage it though a license it's probably a good idea Now, people of the FreeBSD camp believe that people will usually contribute patches on their own accord. This might be true for open source hackers, but I can tell you that it is not true at large companies (not sure about the startup scene). The GPL camp believes it is better to have stronger language to encourage people to contribute back. Even with the GPL, if you are modifiying code for your own use, you can do whatever you want. It is only when you use GPLed code to run a service or to provide a product that you have to make your patches availible under the GPL. It's simple really. If you attempt to profit or use the code in any way other than for personal reasons, the GPL kicks in. Let's examin a running theory in the OpenBSD community. Theo thinks that the GPL is a poor choice because companies are scared of it. They are afraid to get involved with the GPL because it is a viral license, and thus will not contribute code back. He contends that to achieve their main goal of security, they need a more permissive license so companies will patch back. Theo may be right, but it is my personal belief that in practice this theory does not hold. I contend that any company with a useful patch will want to hold on to it, no matter what. Useful patches for OpenSSH represent a competitive advantage that other companies do not have. If I ran a company purely for profit, I would keep all my patches under wraps, regardless of license. It is for that reason that I believe the GPL style licenses are a better choice.
- davidw 17y agoYou sum up two points of view: * Make them share stuff (GPL) * Be permissive, and aim for a bigger community - companies can participate and still use the stuff for proprietary code of their own. (BSD/Apache). > it is my personal belief that in practice this theory does not hold. Do you have any evidence either way? Both are valid points and have been show to 'work' in some way. Apache has lots of companies that participate, which is a counterpoint to your theory. On the other hand, maybe individuals are less likely to participate in efforts seen to benefit Big Companies? I suspect there are no certain answers.
- tsally 17y agoYou're right, there are no certain answers. In fact, sometimes it seems that community and company participation is kind of arbitrary. It is because of that uncertainty that I believe in the GPL. The GPL licsenses provide legal incentive and wont stop any altruistic individuals from contributing as well. As for companies, you'll see from my example below that license may not actually matter at all. If you look at some of the more prominant examples, getting companies to contribute actually doesn't have anything to do with the license, and everything to do with popularity. nVidia provides both 32 bit and 64 bit blobs for Linux, but only a 32 bit blob for FreeBSD. This is only because Linux is widespread, and the blobs are neither GPLed or under a BSD license.
- davidw 17y agoI'm talking more about "library" style code. BSD means companies can integrate it, and potentially contribute back. And this does happen. GPL may mean they simply do not use it, and thus the project loses out on potential contributions.
- prodigal_erik 17y agoDespite BSD's large head start, Linux has received substantially more contributed work. This is evidence that "this is useful, let's follow the license" tends to outweigh "this is scary, let's avoid the project".