3 ms·
This conversation has been up for over 2 hours, and nobody has noted that this fails the Open Source Definition at item 1? You can verify that at http://openso
by btilly 14y ago
This conversation has been up for over 2 hours, and nobody has noted that this fails the Open Source Definition at item 1? You can verify that at http://opensource.org/osd http://opensource.org/osd.
More generally, when you sign a contract, or release something under a license, you should understand what you are doing, why you're doing it. If the legal agreement doesn't accomplish what you want, then don't do it. That goes whether you're a hobbyist, a business, are releasing open source for free, or are selling incredibly expensive per CPU licenses. In general, releasing software for free is not the best way to get paid for the act of writing it. That's common sense, and if that is a problem for you, then you really shouldn't be releasing your software as open source. But you have no grounds to complain that other people choose to.
So why do people release software as open source?
- Fun. It can be nice to say, "Here, look what I did!" Why not give it away for free?
- Learning. Participating in open source software is a good way to get feedback from experienced developers you could never learn from otherwise.
- Marketing. At the worst, you wind up with software to show people that has your name on it. At its best, an individual will wind up with a network of connections who can get you jobs that you like. Then for companies you get into dual licensing business models, ease of attracting developers, etc.
- Gratitude. A lot of developers gained a tremendous amount from using and reading other people's open source software, and feel like they are paying that gift forward.
- License requirement. Some open source software is only available under licenses that say you cannot restrict redistribution of your changes. (The GPL is an example.) Thus you can find that you can get a lot of what you're looking for already done, and the cost is reciprocity. (Hey, if you don't like the license, don't use the software...)
- Maintenance costs. Many companies find that they need something "almost the same as" something out there. But maintaining a fork over time gets expensive as you have to track future improvements, security advisories, and so on. But if you contribute your changes back into the project, then you avoid this cost. (Supporters of the BSD license prefer motivating people this way.)
- Reducing the price of complements. Customers often want to buy a solution, and have a price they are willing to pay. That solution will include multiple pieces of software. If you make other pieces of software cost less, then your piece can cost more. As a concrete example, for many years Oracle pushed customers towards Linux, and then charged a higher price to run on Linux than to run on Solaris.
...and so on and so forth. There are many valid reasons to give away open source software for everyone from individual hobbyists to big companies. But the fact that there are lots of reasons that lots of other people want to do it doesn't mean that it makes sense for you. If it doesn't make sense for you, then don't do it. But don't try to tell everyone else that they shouldn't do what they want to do for their own reasons..
- capisce 14y agoDon't forget altruism, wanting as many as possible to benefit from a valuable project, making the world a better place in the process. Should it not be the considered the best reason?
- mseebach 14y agoNo, that's one of the great things about the FOSS community. There's very little value judgement - or rather, the sum of the movement is altruistic, even if the individual actions taken within it are egoistical. My software isn't "better" because I wrote it altruistically than if I wrote it for a million bucks and open sourced it so I could legally take advantage of other peoples code in it. Actually, the quintessential open source project is a developer scratching his own back. That's not particularly altruistic.
- capisce 14y ago> Actually, the quintessential open source project is a developer scratching his own back. That's not particularly altruistic. He wrote the software to scratch his own back, and now he needs a reason to release it as open source for others to use. My point was that altruism would be just a good (if not better) a reason to release it as any of the other reasons listed by btilly.
- mseebach 14y agoIn my book near-zero cost actions can't be meaningfully altruistic - in that case the term gets so watered down that it's essentially meaningless.
- capisce 14y agoAltruism can be part of the reasons for writing new open source code too. For example in a specific case the set of reasons can be that it's fun, it's a learning experience, it markets the coder's skills, _and_ it provides free value to others. It doesn't have to be the only reason, and I'm not necessarily talking about "pure" altruism here (if there is such a thing), but rather about a general concern for the welfare of others.