10 ms·
"The problem with it is the same problem with messianic religions in general; for people who are not flipped into true-believer mode by any given one, it will c
by jgrahamc 14y ago
"The problem with it is the same problem with messianic religions in general; for people who are not flipped into true-believer mode by any given one, it will come off as at best creepy and insular, at worst nutty and potentially dangerous (and this remains true even for people attached to a different messianic religion)."
I fit into neither of the caricatures of either a 'true believer' or someone scared of RMS. I see him as someone who truly believes in something and has stood by it no matter what. His 'fanatical' language of evil etc. is because he truly believes those things to be evil. I've always used the GPL for licensing my open source code specifically because it ensures that it stays open and that improvements are given back. On one occasion I've been persuaded to use another license so that $CORP could use the code (http://gmsl.sf.net/ http://gmsl.sf.net/) internally and I see that the non-fanatical position helped $CORP but I'm not sure it helped the greater cause of open source.
- Karunamon 14y ago>His 'fanatical' language of evil etc. is because he truly believes those things to be evil. Any fanatic truly believes themselves to be right. That said, I'm a free software advocate. I see where the guy is coming from. I agree on most points. The one that I absolutely cannot get behind is that not releasing the source is evil.
- marquis 14y ago>not releasing the source is evil I believe it's a cultural necessity given how we make money as software developers. Hardware developers have a buffer in terms of actual production, which requires significant investment. You can reverse engineer any hardware you have in your hands but it's unlikely given 2012 technology that you can mass-produce it and steal revenue from the copied source (patents notwithstanding). I can't imagine a global business environment environment in which open source software is the norm, but I would really to hear some theories - can you imagine how wonderful it would be to be able to explore the source code of say, SpaceX?
- einhverfr 14y agoSome areas where open source software is the norm: 1) Web servers 2) compilers for UNIX and embedded application development 3) ISP infrastructure I am sure there are plenty of others. My business is trying to bring LedgerSMB to this area regarding mid-range accounting and ERP. Open source can be effectively monatized in more ways than proprietary software. As LedgerSMB 1.4 comes along we'll be shifting from consulting company to start-up offering subscription services to do things that open source economics doesn't pay for very well. The software will still be open source but it will be monatized through subscriptions (think RHEL) which come with value added components updated in a timely manner. However the fact that it is open source also allows for me to off-set some of the development costs via consulting services (those aren't going away, but they are being de-emphasized a bit). No I don't mind sharing the plans here. There are reasons why the revenue for these solutions, even if people know what the problems and solutions are, cannot be stolen from me. Open source is just a different game and you have to figure out what the rules are. For the record the major areas we are going to focus on will be payroll and electronic submission to government agencies. These areas are frequently updated and the issue is that you don';t want to be the first one to ask for the feature and thus pay for everyone else's use. A subscription model lets us spread the cost around. People could try to jump in but I have a head start and a place of great privilege in the market. It would take a long time for someone to be able to challenge me. In open source the way you get to a point where you can monetize the user base is by maximizing your downstream market (that's those who use your services and your customers' services). The closer you are to the center, the larger that base is. If anyone here says "oh that's a great idea" and tries to do this in LedgerSMB, you'll be starting near the outside, while I have the entire community as a potential user base. And if you go out and find lots of new customers, those are also potential customers for me. I win there too. The real reason for proprietary software is that it is one way of spreading around the cost of development. You have to do it differently in open source software, but there are actually a larger number of ways of doing it than are possible in the standard COTS world.
- dpark 14y agoNot coincidentally, those are also areas where there's basically no longer any profit to be made. No one makes money selling web servers or compilers for Unix, because it's not possible to compete on price with "free". The businesses that make money from open source typically do so by selling something else on top. Google doesn't sell open source. They sell services. Red Hat doesn't sell open source. They sell support to large businesses. ISPs sell bandwidth. Etc.
- tytr 14y agoBut then you have a corporation like Google adopting "Don't be evil" as its value statement. It's obvious that software nerds do have some concept of "evil" as it applies to software, and they like to label things as "evil" or not. Nerds believe the potential for "evil" exists through software. Even if they are not fanatics.
- cheatercheater 14y agoI agree with RMS on many points, but I think you're misguided: > I've always used the GPL for licensing my open source code ITYM "free software" > specifically because it ensures that it stays open and that improvements are given back. No, it does not. Any software not being redistributed does not have to publish its improvements. And even if it does publish the improvements, they don't have to be made accessible in any useful way (for example, just a source dump, rather than a version control repo). And even if it is made accessible in some useful way, often the projects don't end up contributing back upstream (Hello Ubuntu!) > On one occasion I've been persuaded to use another license so that $CORP could use the code (http://gmsl.sf.net/ http://gmsl.sf.net/) internally and I see that the non-fanatical position helped $CORP but I'm not sure it helped the greater cause of open source They still can. You're confused about licensing and what GPL does. HOWEVER, I do resonate with your concerns. I think the world needs to start making programs which are NOT "free" according to RMS, in that if someone uses the program, and he improves it, he has to give back to the general population. How to execute this properly is another question, but I really want to be able to release code which is a public good, rather than something everyone can take, without ever giving back.
- luser001 14y agoUbuntu doesn't contribute to upstream? What do you mean? The limitations you point out on publishing changes are nits imho. It's far better than nothing, and social pressure has been successfully used in many cases to make sure proper SCM logs are sent.
- cheatercheater 14y agoI'd upvote for humour.
- dpark 14y agoThe Affero license sounds closer to what you want. It doesn't stop someone from using the code internally without releasing improvements, but it does stop a company from building a network-based product on top of your code without releasing their improvements. http://www.gnu.org/licenses/agpl-3.0.html http://www.gnu.org/licenses/agpl-3.0.html Beyond that, though, it sounds like what you want is actually a bunch of mandatory process bureaucracy. You seem to want everyone to be required to contribute to the original repository, but that's a maintenance nightmare. This would pretty much prohibit forks (pushing changes upstream from a heavily modified fork is non-trivial), and add senseless work to lots of derivatives (e.g. some project B uses a tiny piece from A, but now has to attempt to send all changes upstream, no matter how irrelevant).
- smsm42 14y ago"it ensures that it stays open and that improvements are given back" Actually, this phrase can be understood in two ways: 1. I want to ensure that the software is improved and the improvements are shared. 2. I want to ensure that the if the software is improved, then improvements are given back. If it's not happening, I prefer it not to be improved or used. The difference between these two are the difference between OSS and FSF. I think the latter doesn't have better moral claim at improving the world than the former, since it bundles positive environmental change (making better code available for more people) with control over other people's behavior (I won't allow you to benefit from the change unless you act as I like). It's like one person giving to charities with no preconditions and another giving only to charities that support his political views. Both approaches are valid, but the latter doesn't have a base to feel morally superior to the former.
- jcbrand 14y ago> 2. I want to ensure that the if the software is improved, then improvements are given back. If it's not happening, I prefer it not to be improved or used. This is false. You are free to use and improve it, even if you don't want to give your improvements back. But then you are just not allowed to distribute the software with your changes as closed source. > It's like one person giving to charities with no preconditions and another giving only to charities that support his political views. That is a crap analogy. The people who don't want to open source their improvements to GPL'd code aren't charities, they are businesses who want to make money of other people's work. The GPL provides a kind of compensation to these people for their work. Which is the guarantee that all (distributed) improvements will be GPL'd as well. That's one of the main reasons why I like the GPL. I know I will in some form be compensated for my labour (as opposed to BSD), in the sense that any improvements to it will come back to me.
- smsm42 14y agoYou seem to be confusing political stance with GPL legal language. GPL legal language, due to the way copyright works, may not allow the author to control usage - even though Affero GPL comes close. But mere fact that the ASP scenario is called a "loophole" and mere fact that Affero GPL exists suggests that the use of improved software without distribution of the improvements is considered something that needs to be discouraged. You missed the point of the analogy. The point was that if somebody gives away his work for charitable reasons without any strings attached, and somebody else demands that whoever uses that work behaves in certain way that is politically approved by the giver - the latter has little base for claims of moral high-ground over the former. It is an empirical fact that restrictive licenses like GPL lead to more friction in integrating various software projects, often making it impossible to use existing code and requiring to reimplement existing functionality from scratch. Again, this is fine if the goal is certain political action and not just improving the world of software available. You of course are entitled for compensation for your work, and entitled to choose in which form it comes. However I do not see a base for claiming that your requirement of compensation somehow morally superior to both people that prefer monetary compensation and people that do not require any compensation at all and allow their work to be used freely by anybody.