3 ms·
Companies producing open-source need to make money too -- that's not anything new. This is the reason why open-source is a commons resource for software develo
by bad_user 16y ago
Companies producing open-source need to make money too -- that's not anything new.
This is the reason why open-source is a commons resource for software developers, but it cannot overtake commercial software for consumers, and rational people could see this coming.
You can also think of it as the commoditization of the software industry, much like Rentacoder. Companies that sell packaged software are against it, companies that don't (i.e. IBM, Oracle, Google) are pro.
The open source community has tried
to fight back. For example, the new
Affero GPL license (AGPL) ...
IMHO, AGPL is the product of sower grapes, and the realization that Free Software needs a business model to survive, which isn't easy when your first customer can redistribute your software freely.
What AGPL truly allows is for dual-licensing to work for server-side products. But what it also boils down to is that such a company isn't in any danger of having any kind of commercial competition from forks (i.e. the perfect natural monopoly over something that should be public commons), which is something Free Software was supposed to solve in the first place.
AGPL is not open anymore and I don't know how it could pass the open-source definition -- because AGPL is an EULA that restrict what users can do with said software, usage rights that don't have anything to do with redistribution by the normal copyright definition.
AGPL is only Free depending on which side of the dick you're standing.
- JoachimSchipper 16y agoCertain groups[1] have always tried to eradicate commercial software. AGPL is just the logical adaption to the current environment. Also, given that BSD and GPL advocates can debate about which is "more free" for hours, I don't think "free" is a very useful word in this kind of discussion. [1] "It's called GNU/crazy!"
- bad_user 16y agoYes, but by going by the definition of both Open Source and Free Software, I don't think AGPL qualifies; that was my point. Going by the Free Software definition, which is a lot more relaxed about terms and simpler: (0) freedom to run the program, for any purpose (1) change it to make it do what you wish How about changing it into something that has an output for which I own copyright / redistribution rights, such that I can sell it? If the output of a program can be considered derived work of that program, than freedom (0) is bitch-slapped. And if redistribution is not involved, then freedoms (2) and (3) don't enter the picture; which is why AGPL is trying to redefine what redistribution means. It's a word-play and I don't know how this was Open Source certified, which makes me think that the process itself is broken (bias towards FSF maybe?).
- wladimir 16y agobut it cannot overtake commercial software for consumers This follows from the definition of "consumer". Consumption, in our society, means buying (and subsequent ownership). If you only use free software, you're not a consumer of software. You're simply using what people are choosing to share with you.
- ChuckMcM 16y ago"Companies producing open-source need to make money too -- that's not anything new." I find this statement ironic. My understanding of 'free software' movement is that only the creation (or modification) of software incurs economic debt, use and distribution do not. In that model of the world company A is writing software because they need that software to make money. They subtract the cost of making the software from the total dollars they receive and that is their margin. They 'gift' their economic output to the community on the hopes that they will see a return gift in the form of changes that improves their ability to exploit the software to make money. If you "need" to make money, then you really shouldn't be participating in a gift economy should you? If you gift me with MySQL and I make a crap-ton of money by creating a web service that allows me to convert some customer pain to dollars, I don't owe you anything in exchange for your gift. I may, if I want the gifts to keep coming throw you a bone now and then. But at the end of the day if you 'need' to make money, gifting is a very uncertain way to go about it.
- tzs 16y ago> AGPL is not open anymore and I don't know how it could pass the open-source definition -- because AGPL is an EULA that restrict what users can do with said software, usage rights that don't have anything to do with redistribution by the normal copyright definition. Stallman on SAAS: I came up to the mike again because I wanted to address the topic that Tim O'Reilly raised....a proprietary program on a web server that somebody else is running limits his freedom perhaps, but it doesn't limit your freedom or my freedom. We don't have that program on our computers at all, and in fact the issue of free software versus proprietary [only] arises for software that we're going to have on our computers and run on our computers. We're gonna have copies and the question is, what are we allowed to do with those copies? Are we just allowed to run them or are we allowed to do the other useful things that you can do with a program? If the program is running on somebody else's computer, the issue doesn't arise. Am I allowed to copy the program that Amazon has on it's computer? Well, I can't, I don't have that program at all, so it doesn't put me in a morally compromised position. http://radar.oreilly.com/archives/2006/08/open-source-licenses-are-obsol.html http://radar.oreilly.com/archives/2006/08/open-source-licens... Given that, and AGPL's clear incompatibility with Freedom 0 (it restricts your freedom to run the program for any purpose), and it how it is triggered by something other than an act of distribution, it was very surprising to see the FSF approve it. Your characterization of AGPL as a EULA is spot on. Unlike Free Software licenses, which relax things that are exclusive rights of the copyright owner, AGPL restricts things that aren't otherwise prohibited under copyright. That is exactly the criticism the FSF and many other Free Software advocates have of EULAs.