Seven Open Source Business Strategies 97
Openstandards.net writes "One of /. posters' favorite discussions is the value of open source as a business model. OSDN has an article on IT Manager's Journal that highlights seven business strategies for open source. " Slashdot and ITMJ are both owned by OSDN.
One interesting thing (Score:5, Interesting)
Re:One interesting thing (Score:5, Interesting)
Re:One interesting thing (Score:5, Insightful)
Open source shouldn't have to count on people "playing nice" - it's about enlightened self interest: sharing your patches decreases your costs in the long run, because you can apply other people's patches more easily.
Convincing MBA weilding bosses of this is more than half the fight.
Re:One interesting thing (Score:2, Insightful)
The good news is that business people ARE starting to hear about F/L/OSS. Within my own classes, I tried to inject presentations about it whenever possible. In my last class, a business strategy class, my prof allowed me to deviate from the normal "find a way to help a business" project to doing one on "what every manager needs to know about OSS".
It will take some time, but the word is getting out!
It's not the MBA that makes people stupid. Stupid p
Re:One interesting thing (Score:1)
I, for one, am overjoyed to hear this!
Business people with things stuck between their teeth are the scourge of the Earth!
Re:One interesting thing (Score:2)
Re:One interesting thing (Score:1)
In other words, stupid people made dumber by arrogance.
Re:One interesting thing (Score:1)
A wise manager once said: "Obviously you want smart, productive people on your project. Note that dumb, unproductive people are relatively harmless, because they are not productive enough to cause much damage. What you need to watch out for are dumb, productive people."
Re:One interesting thing (Score:5, Insightful)
I think the problem is that its so difficult for 'accountants' and 'evaluators' to really put a value on any open source which a company may end up contributing to with
With software, there are a number of different approaches for 'valuating' a company codebase and sticking that figure in a spreadsheet along with all the company's other assets, such as account balances, etc.
With OSS though, how does that valuation occur? Its a public trust sort of scenario - as if the tax which all employees paid the government each year was 'also valuable' to the company, whose cash it was originally before payroll was paid.
OSS 'contributions' are a strange beast to an accountant, and unfortunately, many companies these days rely on valuations and assessments from 'traditional bankers' for things (such as getting loans to cover payroll, or new inventory for sales seasons, etc).
I know that EFF donations and all those 'tax-free writeoffs' are also valuable too, but these don't get thought of as 'investment return', generally. So if you put your main codebase development out into OSS, and your accountant wants to write all your primary code off as 'donations and contributions, non-return expected', then it gets a bit weird...
I think groklaw really ought to spend some time on this sort of thing; the more boring side of supporting linux/OSS on the legal fronts may well lead to a solution to this accounting dilemna, and that would surely be nice for a lot of companies that want to get into OSS
Re:One interesting thing (Score:2)
Over the last year to eighteen months, i've seen the words "open source" become more buzzy around here, but no real understanding of what they mean. Like i like to say: "i
Re:One interesting thing (Score:1)
heh heh, thats a good one. i'm gonna start using that, too. nice!
Re:One interesting thing (Score:2)
Re:One interesting thing (Score:1)
Succinct. It is 'language', after all, maybe it belongs in the 'language' department
Re:One interesting thing (Score:4, Interesting)
Re:One interesting thing (Score:4, Informative)
Optimization - give away good, sell better code.
Dual license - give away good code, sell same code to anyone not wanting to GPL their modifications.
Consulting - give away code so people will hire you to customize it.
Subscription - give away code, but get people to pay for more convenient distribution of it.
Patronage - find someone else to pay you to give away code.
Hosted - (this is the one) write code based on free software that only you use.
Embedded - Give away code tailored to hardware you sell.
Re:One interesting thing (Score:2)
Re:One interesting thing (Score:2)
Optimization: Align your proprietary software with someone else's open source software to make the total package less expensive for your customer without giving out any code yourself.
Dual license: Subsidize open source development with licensed version.
Subscription: Subsidise open source develo
Re:One interesting thing (Score:1)
Well, yeah. That's the whole point. You don't make money by giving away stuff for free. Ever. These business models are ones where it is to a company's advantage (usually indirect) to develop and distribute open source software. Of course you can be a consultant without writing open source software. I would think that point is so obvious, no one would misconstrue the article as suggesting anything else.
It isn't hard
Re:One interesting thing (Score:1)
P2 should begin "It isn't hard to try to find reasons for..."
Re:One interesting thing (Score:1)
Translation: (Score:2)
You know what this means, though: you write the code, and somebody else gets the profit. Is it any wonder Open Source is so popular? It lets everyone live off the geeks for free. Most geeks are just interested in writing code (and good code, mind you, not some boring database screens for those customization scenarios) and are not likely to actively pursue any of the mentioned strategies. They don't even have enough time to try
Reply: One interesting thing, maybe missed .... (Score:2)
However, the examples only show ways that businesses can exploit OS "software products" for ROI. Businesses using these SOS BS will outlast/outperform other business making the proprietary "stovepipe" (one choice, no options) mistake.
The big businesses of the future will discover ways to use/exploit the real international value of Open Source which are the methods, values, processes,
Give back code or money (Score:1)
Data Strategy? (Score:5, Interesting)
Re:Data Strategy? (Score:2, Interesting)
The problem with any strategy that involves giving away code and making money on something else is that there's a first-mover disadvantage. You're better off waiting for someone else to give away a game engine and then building games based on it. (Although I could be wrong, considering how little I know about business.)
Re:Data Strategy? (Score:1, Insightful)
Do not release engine code, since that will remove the option of licensing it to other companies.
Release game specific code, so that your paying customers can modify game play elements as they see fit, and by doing so increase the number of people who will by your game (continues flow of customers by continuously updated content, with minimal time and money investment from the game developer).
All this has proven to work, and there's absolutely no s
Re:Data Strategy? (Score:2)
The question is whether the credibility and knowledge gains outweigh the cost of the original development - and that varies from product to product. In games software, it probably doesn't- but in monitoring systems, it may.
Re:Data Strategy? (Score:5, Funny)
Let's take a look at gaming development under the GLP. It offers an excellant case-study of how GNUlatic-ism will destory America.
1. NetHack: This game promises to connect your computer to a "net"work and expose it to "hack"ers. This is not a good model for a law-abiding company
2. Frozen Bubble: I'm not up on the street-lingo these days, but I'm 101% sure this is a drug reference; perhaps to "crystal methane" or "the acid". Do you want drug users working for your firm? Is that a way to be profitable? Also, I believe it comes from France, that notorious hangout for Maoists and ne'er-do-wells.
3. Klotski: Like many pinko names, it begins with a "K-" and ends with a "-ski". It's also affiliated with a sinister group of known East German "hackers" [kde.org] whose avowed goal is to "conqer" the American workplace.
I could proffer further examples, but any healthy-minded citizen will clearly see that GLP games encourage roguery of the worst kind and are unsuitable for emulation by the large, dependable corporations upon which our Constitution is based.
Re:Data Strategy? (Score:2)
Re:Data Strategy? (Score:1)
Re:Data Strategy? (Score:1)
See here [thekompany.com]
Re:Obligitory Profit Scheme (Score:2)
Re:Obligitory Profit Scheme (Score:3, Funny)
2. Help Microsoft consolidate 100% of the software industry
3. Microsoft outsources your job to India
4. Beg for food since there's nobody other than Microsoft to work for in the software industry!
Re:Obligitory Profit Scheme - More likely with OSS (Score:1, Funny)
1. Write an Open Source program for free
2. See the guy in India maintaining it for money
Re:Obligitory Profit Scheme (Score:1, Funny)
But what are they doing with them? Is this like collecting action figures and leaving them in the package? Does Bill have a roomful of never-opened developers?
Re:Obligitory Profit Scheme (Score:1)
This is Slashdot, you have a good probability the answer is Yes.
VA's strategy (Score:1, Funny)
Adapt... (Score:5, Insightful)
I found this article quite insightfull. One of the paradigms of modern business is the outsourcing model, and that is due to a recurrent need to reduce overhead in any kind of business (overhead always looks like bad news for stock investors). And software aquisition and maintenance IS a major overhead in any IT oriented enterprise.
The obvious solution is to get the resources as they are needed. And that business frame fits perfectly on the OS business model. That, and not Open Source fundamentalism, is what may make or mars OS.
Therefore OS must continue to focus on enhanced flexibility and customization, not offered by other non-OS platforms, as a way to thrive. Then, let us consultants do the rest of the dirty work :)
Missing option: consumer desktop business models? (Score:5, Insightful)
Any thoughts?
Re:Missing option: consumer desktop business model (Score:5, Interesting)
1. IBM dumps tons of money into marketing Linux (any distro..)
2. IBM upgrades OO..
3. IBM allows blatant pirating of OS, and offer's free (or next to free) training. Pirates = Free training..
4. IBM reduces price of x desktop model that comes with Linux.
5. IBM sell's business licenses because now it's desktop version is well known to market/consumers/PHB's..
6. Profit!
Re:Missing option: consumer desktop business model (Score:4, Informative)
I would imagine that in order to successfully do this you need be a hardware company. If you can provide commodity hardware with commodity software that presents a viable consumer alternative (read marketable to average joes as the best thing since a toaster for this new sliced bread stuff) then you might be able to make it. This is really a marketing problem rather than anything else. Generate a kick ass device by intergrating open source solutions with commodity hardware and your product development is much cheaper.
For example the L600 [neoseeker.com].
In the end, to be successful with this strategy you have to be a kick ass marketer to deal with the big guns at the top of the food chain.
Re:Missing option: consumer desktop business model (Score:1)
Re:Missing option: consumer desktop business model (Score:4, Interesting)
In other words, not having a viable business model for the home desktop is not important, because it will ride on the coat-tails of the business desktop.
Re:Missing option: consumer desktop business model (Score:2)
Sleepycat license question (Score:4, Interesting)
Like if I submit a fix/enchancement to MySQL in the GPL version, can they as the 'owners' put that in their commercial license which their customers can release without the source code?
Re:Sleepycat license question (Score:3, Informative)
Quick answer: No (Score:4, Informative)
Assuming your fixes are GPL, they cannot put your changes in the commercial version without first negotiating a separate license from you.
Re:Sleepycat license question (Score:5, Informative)
If you (foolishly) assign the copyright on your code to them, then they can do whatever they want. If you keep copyright to your patch, they can only use it under the license you have chosen.
Re:Sleepycat license question (Score:1)
Re:Sleepycat license question (Score:1)
Question is, do you think many developers would allow their code to be dual-licensed?
In other words, if I made a piece of software that was quite useful, but dual licensed it, do you think a lot of people would be happy to have their GPL code dual-licensed (for reasonable payment).
Personally, if I were selling a dual-licensed product, I'd probably rather just pay people for their fixes and assignment o
Re:Sleepycat license question (Score:1)
I would not want to be involved in surviving legal due diligence for a company that was careless about re-using contributions without managing the copyright issues.
Re:MySQL license question (Score:3, Insightful)
If you (foolishly) assign the copyright on your code to them, then they can do whatever they want. If you keep copyright to your patch, they can only use it under the license you have chosen.
I don't see what is foolish per se about allowing them to use their license on my code, considering the huge benefit I got from gettin
Re:Sleepycat license question (Score:2)
Re:Sleepycat license question (Score:1)
Sounds complicated, and a pity as I can see dual-license as a really good option from all perspectives.
How is parent flamebait? (Score:1)
Example. You develop software, license under GPL. It is an excellent product that fills a niche in enterprise level applications. You go out to sell it and guess what, nobody even acknowledges your existence.
Forward a few months. IBM have noticed your GPL'ed application. They download the source, modify it and offer it as one of their enterprise solutions. They make millions off it, still nobody will acknowledge your existence.
And guess what, IBM do not have to pay you a ce
D'oh! (Score:1, Funny)
Cygnus (Score:5, Informative)
Cygnus primarily provided support, but I think they also did some development. Maybe someone can elaborate?
In my mind, Cygnus is a good example of how a small company can survive on just dealing in Free Software. Many people need support, or perhaps need custom-made changes to Free Software.
AFAIK, Cygnus is now part of Red Hat, and Michael Tiemann is CTO of Red Hat.
Re:Cygnus (Score:2)
Re:Cygnus (Score:3, Informative)
One of the problems that they always had was that they were "customer driven", and tried to evolve the GNU compilers in the direction that favored their customers. This put them in direct conflict with the "official maintainer" of the GNU compiler suite, and, from time to time,
Re:Cygnus (Score:1)
Judging from this changelog [gnu.org] there have been various people from cygnus who have contributed.
Re:Cygnus (Score:2)
Eighth Open Source Business Strategies (Score:4, Funny)
Aren't They Forgetting.... (Score:5, Funny)
Of course, that strategy has yet to be proven, and it seems to have a few holes in it....
Or... (Score:1)
2. Steal somebody elses code
3. Ridicule company code was stolen from
4. Profit!
software dumping (Score:2, Interesting)
very very interesting. recently i just ran Microsoft Office under Crossover-Office (Wine with codeweavers improvements) and on a pentium 400 with 128mb of RAM it took 5 seconds to load a word document.
the SAME document took OVER A MINUTE to load with OpenOffice.
open source software does not automatically mean better.
as a community we are almost entirely dependent on the goodwill o
Re:software dumping (Score:1)
OSS Support company (Score:1, Interesting)
Mozilla is a failure? (Score:3, Insightful)
The Mozilla project continued to deliver buggy, late releases
That can be said of most successful software projects. Why is the article picking on Mozilla especially? Because a superficial look at their Bugzilla database makes it seem like Mozilla has lots of problems? IE is worse.
Re:Mozilla is a failure? (Score:1, Interesting)
Thank you (Score:2)
Linux on the Desktop - NOT (Score:2)
Re: (Score:2)
Out of curiousity... (Score:2)
Re:Out of curiousity... (Score:3, Informative)
It's common practice in journalism, so that the reader is aware of any potential bias caused by the relationship. So, I'm not sure why slashdot does it.