Corporations Getting Into The Open Source Spirit

Anonymous writes "Some bastions of capitalism are getting into the open-source spirit -- not only using the software, but contributing code fixes and other mods, according to an article in today's Computerworld."

Comments

yea, but how?

[matt4077]

I run a moderately-sized software company.

We use a lot of open source software, so I'm always looking for good ways to contribute to the oss-movement, but the consequences are too difficult to judge.

We actually thought about making our source open for the benefit of non-profit organisations (it's a project-management software).
Has anybody made any experience with something like this? We are talking about enterprise-level software here, not your average free-for-students-ide.

Re:yea, but how?

[Ogerman]

We actually thought about making our source open for the benefit of non-profit organisations (it's a project-management software). Has anybody made any experience with something like this? We are talking about enterprise-level software here..

I think it depends on how much your revenue stream relies on this software. It also depends on how similar your software is to existing free solutions (there are dozens of OSS project management packages, for example..) I firmly believe that there is plenty of money in providing free software, but you can't just jump right into it blindly without first thinking about how you're actually going to make money. (assuming the software *itself* is currently a significant source of revenue.. if not, there's no excuse for it to be closed) In my experience, customers have two criteria when choosing software: 1.) a solution that works perfectly for their needs and 2.) software that is reliably supported in case something goes wrong or the sysadmin quits or whatever. Neither of those require proprietary licensing to find a market. It's all about TCO. If you don't charge money for licensing, you can afford to charge *more* for support / customization services as long as what you offer is still overall cheaper / better than your competitors' solutions.

It is true that some potential customers will choose to free-ride on the software if it is openly licensed. However, those who do this also tend to be the ones with enough technical experience to contribute back.. to fix your bugs, offer valuable suggestions, or even add features that paying customers will then enjoy. And if not, there's no reason to feel like you must support them in any way. They're using the software as-is and if they need help, they must pay for a support contract.

Choice of open source licenses is also important. Using the BSD license potentially helps your proprietary competitors and should be avoided. (it allows them to take your code, modify it, and then *sell* it as a different and closed-source product.) GPL and many others force modifications to be re-released to the community. So even if a competitor was to decide to base their business on software you originally developed, they can't claim any rights to modifications and improvements. All they can do is offer competing support services. In practice, this is unlikely because they will lack credibility, product image, and your own intimate knowledge of the code. There are, of course, other licensing choices. You can, for example, forbid forks of the code into new projects or require that the certain trademarks, product names, and credits remain intact. Technically, this makes the software less than free, but it's still better than closed source from a purist perspective.

And remember, you can always experiment.. try opening up some software and see how it goes. Good luck! (:

Re:Getting the corporate word out

[dtolton]

It's really nice to see an introductory article written on Open Source. Particularly one written in a positive light, and without reference to Geeks or Zealots.

I wonder how long it will take the M$ team to start churning out response articles alleging that Open Source is destroying capitalism.

Security Risk?

[BarryJacobsen]

We're now trying to set up [an online] repository of which state agencies are using open source and for what projects

So you're going to create a database telling people exactly what software government agencies use and give them the code. Does anyone else see this as a security risk?

Holy freaking crap!

[qwijibrumm]

You're trying to tell me that buisnessmen, with their buisness management degrees, in charge of big buisnesses, finally are figuring out the buisness model that is the opensource concept.

Seriously I'm acctually shocked to see this in the press presented in such a clear and logical manner. Usually when the press refers to any Free/Opensource project they place a little blurb about how anyone can make contributions to the code. Almost never do they drop names of companies/governments who do. I guess this just goes to show after a while people can unlearn the proprietary method of software development.

Phase 2- get them to realise the idea of Free Software. Let them know it should be their right to change, develop, and distribute code.

Motivated Self Interest

[defaulthtm]

The most interesting part of this is the reason Merril Lynch gave as to why they posted patches back. They wanted to have a seat at the development table and did not want to have to maintain a fork of the product forever. Certainly not a RMS view of OSS, but one that makes more sense (and dollars) in the long run.

Re:Motivated Self Interest

[jonadab]

> The most interesting part of this is the reason Merril Lynch gave
> as to why they posted patches back. They wanted to have a seat at
> the development table and did not want to have to maintain a fork
> of the product forever. Certainly not a RMS view of OSS, but one
> that makes more sense (and dollars) in the long run.

RMS, notwitstanding the undebatably significant contributions he
has made, is full of bologna in regard to this issue. Here's why...

It's called bitrot, and it's been a known phenomenon for a long time,
but the speed at which some OSS projects develop (the big ones, e.g.,
the Linux kernel and Mozilla) makes it a major issue. Keeping just
a small handful of patches for an active project current (even as
many as three or four patches in some cases) could just about be a
full-time job. So you Don't Do That. You create them one at a time
and get them committed to CVS, and once they're in (and don't break
the tree) they become to a large extent Somebody Else's Problem.
Everybody else who was working on their own patches now has to fix
their patches to work with *your* stuff, because *your* stuff is
in the tree. Your workload drops off, and you move on to the next
thing you want to get done. Think of it as a race: two people are
working on patches that touch the same code. Whoever commits first
doesn't have to deal with the other guy's changes. They guy who
gets his stuff in second has to merge the changes. More, the guy
who gets his stuff in tenth has to merge nine sets of changes, and
the guy who never commits his stuff has to spend the rest of his
career merging changes until he gives up in dispair and declares
that the company must standardise on one version of the software
for the rest of time. In the long run, the price of not committing
your changes is that you either never get upgrades, or you have to
give up your changes.

Now, this assumes that you make changes in the first place. People
who are content to use the software in its out-of-the-box state
derive less benefit from open source (though they still get the
improvements other people make, they don't get to put in their
own stuff for their own special needs). But if it's worth your
time to fix up the software to meet your needs better, then it's
worth contributing it back.

So, as I said, RMS is full of it. We don't need the GPL to get
people to contribute back their changes. If the software is of
sufficient usefulness that a lot of people are using it and
making improvements for their own use, bitrot will punish anyone
who doesn't contribute their changes back. The license lets us
also sic lawyers on them, but that's not necessary; if they have
enough resources to maintain a fork, they'll find a way to do
that anyway, or cruft up something from scratch. Most outfits
can't afford to maintain a fork of an active project.

Now, a small and relatively static project is another matter,
but I would argue that if it's not important to enough people
to attract very many improvements, then it doesn't matter very
much whether it's open or not.

The GPL has had some positive effects, but these can mainly be
measured in terms of the confidence that its terms give to people
who otherwise might have been afraid that their code will be
taken over and made proprietary by some third party. In practice,
this won't happen to an active project. When Apple based their
OS on existing components, they kept the open components open,
even though some of those components are licensed under a BSD
license which does not require it. Why? Those components are
actively developed, and Apple doesn't feel like spending ten or
fifteen full-time developers maintaining a bunch of forks. Duh.
(Yes, they also like having goodwill, but that additional
motivation is icing on the cake.) If your code is something
sufficiently useful to creat

Re:Goodwill as an asset?

[derF024]

Bug fixes and other contributions to open source software are in and of themselves valuable, but creating them will always be an expense to companies.

actually, the article talks about exactly this.

What's the payoff? It makes for better software. "If we find a bug or a problem, we're interested in fixing that problem. We're also interested in not fixing it again in the next version," explains Robert M. Lefkowitz, director of open-source strategy at Merrill Lynch & Co. in New York.

contributing to open source projects ends up costing these companies less, because they don't need to maintain an internal version of the software.

Re:Getting the corporate word out

[jdray]

The most surprising thing in an article like this is the fact that it is getting written at all.

Agreed. And it has been a long time coming. I work in the electric utility industry, and I've been trying to convince my management that embracing the open source model is the only thing we can do to make dramatic changes in our bottom line in these times. Unfortunately, they laid people off around here instead. Well, okay, that's a little unfair, but not too much.

Our industry, as I suspect is the case with a lot of industries, is bursting with opportunities for community-built standards-based software. Instead, we'd rather pay vendors and consultants millions of dollars for niche market software that we don't understand. Bah!

Sometimes it's hard to keep up the fight. It's a good thing I've got /. to keep my spirits high!

JD

Re:Goodwill as an asset?

[Beatbyte]

goodwill creates a REPEAT customerbase.

I would tend to trust and appreciate a company more that has spent its money to better the world of OSS and the world of computing with the interest in making a better product for everyone and not just its customers...

Alot of this is free advertisement

[Billly Gates]

IBM was shunned for many years by both the Unix and opensource communities.

However they are now looked upon as the good guys and their bussiness skyrocketed as a result. IBM is what most hackers have on their minds if their employer needs support and consulting for huge projects. They are not free or cheap but you get what you pay for.

I use to live in NewYork and the NYLUG is one of the best in the country. IBM for years has been generious in donating their rooms for the meetings and group gatherings. Alot of the locals in the meetings have consulting contracts with IBM as a result.

The more they help free software advocates the more advertising they get as well as improved software they can sell for their clients. We all win.

I believe JBoss is also an advertisement for a consulting firm who produces it. There bussiness has taken off thanks to free advertising from their product.

Opensource does work well in getting your name out. Alot of PHB do not trust salesmen because they do not know if their products are any good. With opensource software they can test them out.

Uselessness of comparing Capitalism & Open Sou

[NaugaHunter]

The main crux of this comparison, as far as I can tell, should be made in reference to other aspects of business. Consider a manufacturing plant of some kind. In this plant they have equipment that they built, equipment they bought on contract and have serviced, and equipment that they bought but maintain themselves. The equipment they build or maintain is directly related to their business, and the operators/engineers are sufficiently trained and experienced to cover the majority of their needs. Over the years they have filled each equipment need they've had with the solution that was best at the time, and presumably address their solutions over time when difficulties or cost concerns come up.

This is roughly analogous to in-house software, proprietary software, and open source software. A company is free to pick and choose which solutions work best to remain in business. The main difference is very few companies naturally have Software Engineers/Designers/What Have You in the course of their normal business developments. Whereas a small manufacturing company is likely to have been founded by people making the product by hand, rarely are office environments founded by programmers (Exception: software companies which by this analogy are manufacturers of software and would fit with them).

The important thing to remember is that software isn't the only third party products these offices, or even manufacturers, use. There aren't many advocates for Open Source Copiers, or Open Source Pens, or Open Source Coffee Makers, all calling for GPL'd blueprints. The significant difference with software is that the only real resources required are the source code (or blue prints) and the person capable of understanding and modifying them. Virtually everything else would require a parts supply chain which, if not part of the main business, usually isn't an economical path to follow.

In conclusion, the cost of maintaining anything utilized by an organization that isn't directly related to the organization should be compared with the costs of outside solutions, whether talking about software or coffee makers, and whether talking about businesses, governments, or even your own house.