Making Money Using Open Source Software? 540
GamblerZG asks: "As many of us probably know, convincing people to run Free Software can sometimes be a tedious task. However, there are a lot of factors that help us in that regard, and, perhaps, the biggest of them is a simple truth: Free Software is free. It's hard to argue with such statement. I know it, because I faced it today, trying to convince my fellow co-worker that it is possible to profit by writing GNU-licensed code. 'How company can make money, if its products are available for free?' That was a valid question indeed, and I could not find any simple answers to respond with. That makes me wonder, whether there are articles on the Internet, which explain and analyze how Open Source business models work? Do you know any ways to prove that such models can be profitable?" It can be done, you can check out a recent interview with an Open Source Entrepreneur on NewsForge for some hints. What other ideas and business plans do you think would be a good match for a business with an Open Source core?
is it true? (Score:5, Funny)
Re:is it true? (Score:2)
Step 2: ...
Step 3: Profit!
Re:is it true? (Score:2)
Step 1: Select already released open source software
Step 2: Package software as your own
Step 3: Profit!
Re:is it true? (Score:5, Funny)
I thought the second step was obvious - patent ellipses.
Second Step? (Score:3, Funny)
But I don't have a problem. I can quit any time I want to. I just don't want to right now.
Re:is it true? (Score:4, Interesting)
For example, where I work at a research hospital, the software I work on is used for analysis of MRI images. It's not GPLed, but it's open source, free, and pretty much anyone can get access. Our money comes from grants.
In my previous job, I worked at a major defense contractor. Software wasn't written for "sale" persay, there either. Instead, we were given a contract by a government agency to develop a piece of software for them. Of course, we couldn't open-source that software because it was sensitive, but I'm sure there are plenty of other cases of "software by contract" out there where the submitter or recipient of the contract has no financial interest in software sales - just in getting the contract filled.
No-brainer (Score:5, Informative)
Re: (Score:3, Insightful)
Re:No-brainer (Score:3, Insightful)
No one ever went broke underestimating the intelligence of the American public
Make something idiot proof and the world will make a better idiot
I checked with my company's IT guy - he's in full agreement. I must admit, it's fun listening to him teach the executives how to use e-mail.
Re:No-brainer (Score:5, Insightful)
Re:No-brainer (Score:3, Insightful)
Also keep in mind that no matter how readable your code is, you are going to know it better than anyone else. It just may be faster and cheaper to pay the main developer make the modification.
Ongoing maintenance is an issue too. Let's say that you internally added feature X. The main project does a new major release, and it doesn't contain your feature, s
Re:No-brainer (Score:3, Interesting)
Re:No-brainer (Score:3, Insightful)
Here, have a clue on the house. The people who run sendmail.com? It's CTO is the original author of sendmail [sendmail.com]. How's that for making money writing open source software?
As for redhat, are you saying that having someone who knows how to make 50 software packages work together across 2000 seats in an enterprise situation isn't worth the price of admission to Red Hat Enterprise? Do they need to have written all that software themselves in order to make money off of it? Apparently not, or they'd be out
Here is my question?? (Score:5, Interesting)
However, he also stressed "living the mission" where there mission is to essentially alievate pain, help people live longer better lives." And in his next breath he said that his company would sue anyone who copies their ideas to do remote patient check ups on pacemakers etc.
So I asked, doesn't this contradict the mission, how can you on one hand be for helping people but writing proprietary software that maximizes your revenue? Why don't you open source it all, wouldn't that be a better fulfillment of the mission? He responded by saying that it is essential that the company do this to ensure that it can be financially healthy to continue to provide these services and develop new ones.
It seemed pretty logical to me, but I want to hear what the
Re:Here is my question?? (Score:3, Insightful)
They should look at their costs, and their income. Does it take locking something up 15 years that was probably trivial to come up with? (I don't mean the programming just the basic concept that is patented). How much of their cost is on patenting everything? That cost needs to be looked at too.
I would imagine cutting pay at the top to something that is still plenty high (speculating, maybe the
Re:No-brainer (Score:3, Insightful)
The only open-source model I've been able to dream up which would actually be long-term sustainable and which would actually align business incentives with the humanitarian goal of producing better-quality free software is the "contract programming" model. In other words, you pay me to write some particular software you need, and when the "final" version is delivered to you per contract
Re:No-brainer (Score:2)
Re:No-brainer (Score:3, Insightful)
If GPL code directly calls your code, your license must be compatible with the GPL.
However there are millions of other open source licenses out there that doesn't have this problem, and if you've got a hardon for the GPL, you can write the "main" program using a modified GPL that states that proprietary plugins may be added to the code, then write proprietary plugins.
Re:No-brainer (Score:3, Interesting)
Beyond that, I wonder if companies like Red Hat have actually made a profit over their lifetime despite having 95% of their product developed by people they didn't have to pay. (Yes, I could research the answer, but I'm too lazy).
Oh come on. You're so full of it. (Score:3, Funny)
Re:No-brainer (Score:4, Interesting)
They created the QT library, and they are giving it away under GPL. They make a profit from companies that need the library for non-GPL products.
Re:No-brainer (Score:5, Interesting)
However, I would argue that the reason they make that money is because they have smartly found a niche that encourages it - writing libraries that everybody wants to use. And, of course, they do what I would suggest to would-be OSS developement companies -- dual licensing.
IMO, dual licensing is key to OSS. For non-commercial purposes, one is basically free to do what they want (or it's licensed under GPL, whatever). But for commercial purposes, the license becomes more restrictive and demanding of money.
TrollTech really is probably the model the OSS community should look towards...
Re:No-brainer (Score:3, Interesting)
Re:No-brainer (Score:4, Insightful)
Trolltech is an excellent example. They would not have nearly as many paying customers if it wasn't for the free version. Everyone in unixland knows KDE, and a good part of them use and like it. Enough of them are programers who have played around with the source enough to pass the qt learning curve and see how great it is. When the boss decides to start a new project they are not in position of either asking for qt, or evaluating all toolkits. The latter is hard to do, because by the time you know a toolkit isn't great you have half your application written already.
Trolltech in fact mentions kde to those who are considering their product. When you evaluate something new it is hard to know if it is any good. It is hard to get customers to act as a reference, and even when they will there is always a question if the reference is honest. KDE is there, they can point to it and say "See, they have several million lines of code built on qt". That is worth a lot.
In short, sell the GPL version as the demo, and the free software built around it as proof that your code is good. Doesn't work so well for non-libraries though.
Re:No-brainer (Score:5, Informative)
Are you kidding? Redhat contribute to a lot of high-profile open source projects [redhat.com]. They also provide hosting [redhat.com] to many projects.
For goodness sake. Who is rating this interesting? (Score:3, Insightful)
First of all Red Hat, or any other company for that matter, are not appropriated the work of others. That is a vulgar lie.
The people that have produced the software (Red Hat payed employees amongst them) have released it under licensing terms that allows companies like Red Hat to make bussiness. All the GPLed parts are freely available, and they not only make them available but are contributing to a completely free project like Fedora.
The product is free; support isn't (Score:5, Insightful)
Re:The product is free; support isn't (Score:2)
in oppposition to what Microsoft is trying to do, Commoditize Hardware.
Re:The product is free; support isn't (Score:3, Insightful)
A lot of times (at least in the beginning) the developer and support personnel are one and the same person. So typically someone will do an OSS project in their spare time and then once it's complete they do the customizations/support for extra cash.
Also, even if you charge the same, keep in mind that the difference is that the product is usually still available (GPL or whatever) for people to use. That means that people who don't
Re:The product is free; support isn't (Score:3, Interesting)
The company I worked for a couple years ago installed this retarded ERP system. It was badly documented, it didn't do what we needed it to do and the interface for customizing it left our IT people completely baffled. Talking to the company that produced it offered us one solution, spend another $100,000 for the upgrade to the version which *supposed
Re:The product is free; support isn't (Score:3, Insightful)
You don't.
Open Source software does not mean free software (not always, at least). You can still charge a fee for OS software. However, once you've sold it/given it away, the purchaser can do whatever they damn well please with it, including redistribution and providing support services.
If you want to make money on Open Source software, you can:
- charge for your software, but offer no support
- charge for your software, and offer free support
- charge for your software, a
Support! (Score:5, Interesting)
Re:Support! (Score:2)
A lower TCO for your customer means less money for you. And here's the big kicker, if you open source your code and expect to make money off of support, what is going to prevent other companies competing against you on support? Look at IBM and redhat, they make money off supporting OSS projects, but you can't say they are main developers of these OSS projects. Whats to stop redhat bundling your product and offering support fo
Re:Support! (Score:3, Informative)
-N
Re:Support! (Score:2, Insightful)
Re:Support! (Score:3, Insightful)
You mean like I make a decent penny now and again by supporting Windows, even though I didn't write it and MS doesn't get dime one of my fee?
Jeezum Crow, even Billy hasn't figured a way around that one yet, it keeps him up nights working on it, but he still hasn't found the answer.
Still, there are people who call MS for support instead of me, because it's an MS product, yes? And there are still people who call me because I give t
Re: (Score:3, Insightful)
One Possibility... (Score:5, Insightful)
Then, sell consulting to design, write, install, support, and maintain those extensions.
Again? (Score:5, Funny)
Okay, it's been 2 weeks guys, so we have another programmer who wants to make money programming, but has no idea how to create a solid business model, so let's all put in some work and tell this guy how to make money with FOSS instead of those of us who have figured it out running our own businesses.
It's possible. (Score:5, Insightful)
Just take a quick look at IBM announce today they're making 38.8 million off Open-Source-based services [blogspot.com] on a single location in the span of four years.
If that is not money, I dare not fathom what is.
Re:It's possible. (Score:5, Insightful)
No, IBM did not. They made that money off of support, not development.
.04 percent (Score:3, Interesting)
(with a b) in sales in 2004
what percent is that?
%.0402
or
less than 1 half of 1 tenth of one percent
oh, I'm sorry, that's over four years?
about 1 tenth of 1 tenth of one percent of sales
Is that fathomable? I laud IBM for it's participation in FOSS, but- it's not even a drop in IBM's revenues...
Well... (Score:5, Funny)
I have the perfect solution... (Score:2)
Openflows makes money supporting Open Source (Score:2, Informative)
Check out this other article about making money and open so [indicthreads.com]
Re:Openflows makes money supporting Open Source (Score:3, Interesting)
Cathedral and the bazzar (Score:2, Informative)
Honor system (Score:5, Funny)
The Cathedral and the Bazaar (Score:2)
Re:The Cathedral and the Bazaar (Score:2, Insightful)
Easy, sell the code (Score:2)
Open doesn't always mean free.
OSS piracy (Score:5, Funny)
As we have already seen today [slashdot.org], the GPL is under attack from evil forces known as "pirates." These shadowy folk silently steal source code and violate the GPL, infringing on the rights of GPL authors. They are nothing more than thieves getting a free ride off the work of others, and I for one am disgusted at the idea of it. As you can see in the previous article, clearly Slashdot is also sickened by the idea of copyright infringement and piracy.
Some have even called for a lawsuit against these pirate thieves. Suing individual infringers has always been a position that Slashdot and its readership has supported, so it's only fair that the original GPL authors protect their rights and safeguard their material from being stolen in the future. I think we should all support any lawsuits against these infringers to protect the rights of GPL authors everywhere.
I appluad Slashdot and its readers for always taking a proactive stance against piracy and copyright infringement in general, and I would like to join the cause against this "source code theft." Piracy is a major threat facing OSS today.
Re:OSS piracy (Score:2)
Unless it's industry-backed media or software written by EVIL corporations. Then it's called "going after grandma and 12-year-old girls".
Moodle does it right (Score:2)
I have never been one to believe that's it's criminal to make a living off F/OSS. I think you can have it both ways, and Martin does a great job at pro
This is easy (Score:5, Insightful)
Er (Score:5, Funny)
In Soviet Russia it's a valid question, my friend, but not in English.
Do not forget the Embedded market. (Score:2)
It really depends on the market. Odds are pretty good that you will not make money on a spreadsheet, database, or game You may make good money on a vertical or embedded system. How many people make good money using GCC?
As they say ... (Score:2, Insightful)
Open Source is only free if your time is free.
There's alot of truth in that statement. It also means you can make money by setting up opensource systems for other people (and perhaps you'll have to add a feature or provide support to make the sell)
You could also get paid for simply adding a feature. You could only sell this feature once, which is a big difference with the proprietary model. You can respond to this by simply asking more money off course.
Overall, it's true that Open Source forces you to
It's not the software that matters (Score:5, Insightful)
Re:It's not the software that matters (Score:3, Insightful)
Services (Score:2)
For example, if you developed an easy-to-use & maintain (think GUI for the receptionist) Asterisk PBX, you could probably sell that into a lot of small businesses. Sell some maintenance on top of it and after a while you have a nice recurring rev
Google (Score:2)
Same thing in Academia (Score:2, Interesting)
I recommended we endorse the AMP (Apache/MySQL/PHP) platform over ASP.NET (which is what he had in mind), and his main reason for not taking that route was that "Apache is open source, and you can't make money with free products. Here in the business college, we're only interested in products that can make money."
I promptly never spoke to the dumbfuck ever again.
The TrollTech approach (Score:4, Insightful)
Re:The TrollTech approach (Score:2)
Compare this to Red Hat, which has no closed-source stuff in their distributions, and is obviously making money hand over fist in comparison to TrollTech.
-Erwos
The Apple Model (Score:3, Informative)
I think we'll start to see this model adopted more and more.
Not all sell or support software they create. (Score:2)
Money with OSS (Score:3, Funny)
Wrong question (Score:5, Insightful)
Simple answer: it's extremely dificult to do so.
The question you should be asking is 'How can a company make money, if it gives away software for free?', and the answer should be more obvious - it can do so if its product is not the software it's giving away.
For instance, IBM's "product" is the tailor-made services and consultancy it provides. The software is merely a tool they use to provide it.
You might argue that keeping such tools to yourself is a commercial advantage over your competitors. That's true to an extent, but there are also downsides - e.g. if you provide your own proprietary operating system instead, you don't get benefits contributed by the community, and your competitors are more attractive because there is no lock-in.
I do this now (Score:4, Insightful)
Recent examples include things like displaytag library [sourceforge.net], Hibernate [hibernate.org] and HTML Area [dynarch.com].
Of course, this means I must take a wide berth around GPL'd code, but there is enough stuff under BSD/Apache/whatever to get the job done.
Another solution (Score:2)
A more evil solution might be to GPL your program but distribute the code in such a way that it's difficult to compile, or needs proprietary tools, etc., thus discouraging homegrown solutions. Don't do this though.
here are three ways that first come to mind (Score:2)
The traditional approach is to sell a service instead of a product. Typically, the service is packaging or integration. This is what Redhat does. Customization work is also an option. JBoss tried to go this route.
Another approach is to code a proprietary app that runs on Linux and sell the whole thing as a turn key network appliance. This is what Sun tried to do with their Cobolt server appliance.
Another approach is to give away the "basic" version of the program and sell the "advanced" version. This
Here's one example in Education (Score:4, Interesting)
In brief, the Sakai project was started by a few large institutions who were tired of buying into the licensing fees of other learning management system products like WebCT and Blackboard. They decided to create their own and make it open source - both free as in beer and speech. However, the support for Sakai comes at a price, albeit a much lower price than the aforementioned commercial products were offering.
In the end, you recieve a completely open learning managment system created and maintained by developers at these institutions and supported by commercial interests.
Longtail vs. Lessig (Score:3, Interesting)
"What's changed is the presumption that the primary rights-holder is the best at extracting the commercial potential of creative material. Instead, anyone can do it: the advertising company that remixes an old movie to sell a car; the Linux t-shirt done Warhol-style, or just plain old DJ magic. "
"Let them eat cake" Well now that cake is actually free and we all want to sell it. Now if you can put a custom birthday signature on that cake you might have a business. This is one of the reasons film school is starting to see a new wave of interest. Communication and creativity, not business processes, are going to be the only things left after the so called Web2.0 is done modernizing commerce.
Service instead of Product (Score:2)
I work in a small company, so we don't do any real training for new versions. For example, we were using version 2000 of AutoCAD until about November of last year. We we upgraded, the new changes in software were left up to us (mostly me) to discover and incorporate into making the job easier. Now this wasn't so hard, si
Some Resources (Score:5, Informative)
-101 Ways to Make Money off Open Source [manageability.org]
-How to make money with Open Source Software [lathi.net]
-Making an open source living [builderau.com.au]
-eWeek:How to Make Money Off Open Source [eweek.com]
I am not intending to be snitty in suggesting that you search Google; there were tons of other seemingly-good resources contained within it, and it might just be a case of different search terms. You might be able to team the information gained there with the advice of people here.
Also, if you can gain access to the class papers from the Boston Embedded Systems conference, particularly those from Bill Gatliff in 2003, there were tons of developers there who lectured on this very thing, citing examples and explaining the ins and outs of open-source licensing. I thought Bill Gatliff did an excellent job, and you may be able to contact him through his website for some resources.
OoGhiJ MIQtxxXA (Score:2)
Is your co-worker named Oog? If he is, tell him Frylock wants his computer back, ok?
OSS business models don't work.. (Score:3, Interesting)
The reason why OpenSource works for Redhat and SuSE is because they don't write much OpenSource, the community does, they just pick the whole work of other, package it nicly, write some installer programms, fix some remaining bugs and then sell it. If there wouldn't be a large community to actually write the software they wouldn't have much of a chance, since there wouldn't be much that they could package. Supporting their products is another source for there income, for which their OpenSource activity is of course a great way to advertise it.
So if you expect to write original OpenSource software and expect to get a large return from it, you can basically forget it. If everybody can download your software for free you won't stand much of a chance to sell it. If you however sell a service and not a piece of software there is a good chance that OpenSource won't hurt you, since people will still buy your service. There are also models which work by releasing older versions as OpenSource and selling the current version as close source.
Overall making money by writing OpenSource doesn't work, what works however is using OpenSource as advertisment to services you sell. However selling services doesn't work for all kinds of software, so if your software doesn't require much service around it, you are out of luck. If you want to make money with your software there are probally better ways then OpenSource, you should see OpenSource as a way to ensure the users freedom, not to ensure yourself a larger income.
Look guys, which would you rather buy? (Score:2)
(2) Some software that's free, but, uh, you can probably find someone to support it if you pay them, but, uh, they haven't quite sussed out their business model yet, so they don't really know how much to charge, or whether they'll still be in business towards the end of your planned eight year life for this system?
Now, let's see. Fixed price means software quality is as high as they can get it, because
Two ways to make money (Score:2)
Now, about making money.
1. Do like the Sveasoft guy: package some open source stuff together into a value-add. He ges paid for doing the integration work.
2. Offer services around open source. Get pai for helping people install and run their software.
not from, with (Score:2)
from OSS, I think a better question is "how can I make money with OSS".
In other words, if your goal is to make money, then perhaps the best question to make is, how can you use OSS as a way to supplement your business model.
Think of how OSS can be used to make a business operate more efficiently and at a lower cost.
If your main business isn't IT related, then just appy this to your own business.
If your job is IT, then think about how you can appy this to your clie
Is it so hard to grasp? (Score:4, Informative)
I pay plenty of bar tenders to make me "Open-source" drinks that I know damn well how to make on my own because I'm just no good at it or I don't want to take the time to go to the store or I'm too tired to make it etc. etc..
People pay for hamburgers at restaurants all the time, even though even little kids know what goes in them, because they don't want to go to the store and buy all the stuff and they don't have the tools to prepare it or the skill to do it well. They just want to eat. It's a matter of convenience and skill and action.
You just have to choose the right market. When a bar tender is behind the bar she doesn't pay another bar tender to make her a drink that they both know how to make, but after her shift is over and she's dead tired, relaxing on the other side of the bar she will. Likewise, you probably won't be able to sell your OSS products to people who make their own OSS products. You sell them to people who need solutions to problems that you can provide using tried and true OSS code. To sound really cliche, if you're selling OSS stuff you're a "solutions provider" and your solution just happens to involve free software, but businesses will still pay you to solve their problems because you are doing work, your tools are just free.
Open Source/Free Software Issues for Games (Score:2)
Co-development (Score:2)
The motivation of open software isn't profit, that's not to say it isnt possible to make good money packaging and support
Valid question? (Score:2)
Only if Yoda were the one asking the question.
Who Cares? (Score:2)
Open for Open (Score:2)
All other operating systems would require binary version to be purchased, and it would be against the license to compile the software for those operating systems. Yeah it's not totally open, and sets conditions, but in some ways I think not only could it help fund the developers, it could h
Simple (Score:2)
Ohwait...
Pay for development, not code (Score:3, Interesting)
This work fine when there is a limited number of users, which is the case for far the most software.
It actually also works for some software with more users. GCC developemnt is largely funded by people who hire one of the GCC development companies (there are several) to improve some aspact of GCC that is important to that customer.
How to earn money from OSS (Score:3, Interesting)
For example, Red Hat has Fedora as a free Linux OS. If someone wants tech support for Fedroa, they can pay Red Hat for it. If they want a more advanced server version, they can pay for it.
Some projects are based on OSS, but sold commercially, like Linspire, WineX, Crossover Office, etc. The OSS license can be released into a commercial license, in that the OSS developers make their money in selling licenses to release their OSS code into commercial products.
The fundamental economics of OSS is this... (Score:3, Insightful)
The blunt fact is that in IT, there are really 2 classes of people: users, and developers. This is fully analogous to any other industry, where you have a consumer (users) and a producer (developers).
The users -- everybody from sysadmins and netadmins, on down to the secretary using her Office apps -- do not write code. They do not contribute anything beyond bug reports to OSS. Hence, their personal stake in the price of software is simply to get the cheapest software that will do the job. Given that OSS is free as in beer, users will naturally gravitate towards it and promote it. Just as in college, where there is free beer, there are students lined up around the block to get a drink.
Then there are developers -- the software engineers and programmers. They *do* write code; that is their job. They contribute more than bug reports to OSS; they contribute the very code that is required to build the apps that the users use. The trouble for developers is that OSS, by not charging a fee for the time spent developing, makes the value of developers' time equal $0. Time = money, and if money = $, then time = $0 as well.
When applied as a business model, that is how OSS works; there is no escaping this fundamental economic analysis. You cannot very long sell a product at a non-zero monetary sum that which one can get at zero monetary cost to themselves.
Thus, the only way OSS can survive in the business environment is if the developers are working for a company which has some other revenue stream then -- be it support services for the code they write if they are a software company, be it some other service if it is a non-software service business (e.g. a marketing firm, law firm, etc.), or be it some tangible, physical good (e.g. in any hardware company, car manufacturer, grocer, etc.).
It's an opportunity for creativity in business models to try and incorporate OSS into their business functionality, but from the developer's perspective, it's important to recognize this fact: because you are writing software which is being given away for free, your work is not directly making money for the company. Because your work is not directly making money for the company, you will be seen as "dead weight" in the company. Because you are seen as dead weight, you will have a hard time justifying your employment with management unless you can determine, clearly, how your work saved time somebody else in the company, or how your work drew in more customers for the company, or how your work generated more service contracts, and so forth. If you cannot do that -- and this will be difficult (though not impossible), given that you don't work in those departments -- you face job loss.
Hence, it is generally in the best interest of developers not to write OSS. OSS coders are literally coding their way out of their own jobs.
But all of the above largely assumes software is normally otherwise a product sold to people on store shelves, when in fact, most people already write code for internal use only anyway. What about those people?
OSS is still a negative to developers in most companies, because, after all, if you are writing code that would normally be for use within your company, that is potentially a competitive advantage for your company. But if you're giving away that code, you're giving away that advantage for other companies - other competitors - to use. This is good neither for the developer, nor the company paying the developer who released the code as OSS. After all, if you employ developers who just spent 6 months writing control software for, say, a large manufacturing company, why should the company release that software to the public? So that their competitors can go out and buy the same hardware, leverage this software they did not develop (and have no intention of contributing back to), and produce the same or very simi
The support model sucks (Score:5, Interesting)
We've had this problem, so I'm not speaking theoretically. Most of our users bought support with the purchase of our commercial product, but after one year many of them didn't want to renew because they hadn't had any problems and didn't know what they were paying for.
A business plan that is based on support is at direct cross purposes with creating high-quality, easy-to-use software.
The case of LaTeX (Score:5, Interesting)
"GMZ: Was this always meant to be free software ? Did you ever try to "get rich" with it? Do you regret that you didn't?
LL: At the time, it never really occurred to me that people would pay money for software. I certainly didn't think that people would pay money for a book about software. Fortunately, Peter Gordon at Addison-Wesley convinced me to turn the LaTeX manual into a book. In retrospect, I think I made more money by giving the software away and selling the book than I would have by trying to sell the software. I don't think TeX and LaTeX would have become popular had they not been free. Indeed, I think most users would have been happier with Scribe. Had Scribe been free and had it continued to be supported, I suspect it would have won out over TeX. On the other hand, I think it would have been supplanted more quickly by Word than TeX has been." (From TUGboat 22 (2001) [tug.org]
Just a very succesful case of money made out of free/open source software that is often overlooked (and maybe one of the oldest cases as well!)
Support, installation, bounties (Score:5, Interesting)
1) Support. Provide support for the software. Fixing or adapting it to the customers requirements for money.
2) Installation. Really a subset of support. Will install and train in the usage of OSS for money.
3) Add/Create OSS for money. They customer wants something. You will code it.
Answer to the Question (Score:4, Funny)
Volume.
The Magic Cauldron (Score:3, Interesting)
http://www.catb.org/~esr/writings/magic-cauldro
I can't believe nobody mentioned it before. (Yes! I actually checked it, so if someone did mention it, then Slashdot search sucks!)
Making ca$h with O$$ (Score:3, Funny)
Re:I don't think it was a valid question: (Score:5, Informative)
Yeah, but can anybody spot the other problem?
"How can a company make money if its products were available for free?"
The if...were is a hypothetical subjunctive; the writer is making a statement contrary to fact. The company's products are not available for free; the case is being postulated where they are.
Lots more details in Wikipedia [wikipedia.org], of course.
(No, I'm not a card-carrying pedant. It's made out of plastic.)
Re:I don't think it was a valid question: (Score:3, Informative)
The question about making money is referring to the present - the same point at which the products are hypothetically available for free. English isn't a language where every 'if' clause takes a subjunctive. This sentence isn't expressing doubt or disbelief; it's a condition posed as a question.
Re:Free Software is free? (Score:2)
He (assuming it is a he) obviously means Free as in freedom, not as in price. He also made sure he capitalised the 'F' in that 'Free'.
For instance, the Free Software Foundation doesn't develop and distribute software at zero cost. On the contrary, they develop software and give their users certain freedoms when it comes to use and redistribution.
By saying 'Free software is free', what he means is that for most purposes, people don't pay anything for copies of Free software.
It is unfortunate that 'fre