Slashdot Mirror
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."
The most surprising thing in an article like this is the fact that it is getting written at all. It used to be that only MS would get this kind of rah-rah journalism, but the tide seems to be turning.
Now, stuff like this seems to be showing up all the time. I wonder what single thing tripped off this new trend.
Congratulations! Now we are the Evil Empire
DARPA supports BSD, and now big business buying Open source. Either sanity is breaking out everywhere or the apocolypse is coming soon to a planet near you.
Food not Bombs is a nice platitude but it breaks down when you notice that the Bombees are usually well fed
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.
Fleur de Sel
...has spawned a whole magazine already. That does certainly suggest Linux is ready for prime time.
Back in the 70's, IBM came out with their VM meta-OS. Its origins were in academia, not in IBM's shops, and in all the installations that I saw, it always came with full source. They actively encouraged customers to submit not just bug reports, but fixes, which were then sent out to other customers.
;-). I emailed the fix to the Amdahl support people, they thanked me, and it was in their next set of patches.
In one place that I worked around 1980, there was a big IMB mainframe, and one day we brought in some Amdahl people to demo their unix that ran on VM. One question was whether source was available. Their answer was "The source isn't an option; you get it whether you want it or not." Within a couple of weeks, I'd made a small fix to the kernel's clock routine (needed because the turkeys who ran our VM had screwed up their clock in a way that Amdahl's people hadn't conceived of
Closed source was to a great extent an invention of Microsoft. Before them, it was obvious to even the stupidest manager that it was a good idea to make source available to any programmers who could understand it. That way, you got bug fixes rather than bug reports.
It's actually a bit strange that we now have management that doesn't understand this. What are they teaching them in business schools these days?
Those who do study history are doomed to stand helplessly by while everyone else repeats it.
This got me wondering.
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. With the exception of major enhancements or improvements very few will be marketable, or generate any other revenue stream for the company.
"Goodwill" however, is a recognized asset for companies. An asset that can be appraised, and entered on the balance sheet raising the company's value.
I wonder whether the open source movement could benefit from this aspect of contribution to the community, encouraging companies to create a verifyable and appraisable track record of contributions, and supporting their efforts to create genuine bankable value based on goodwill.
Just a thought.
------
Believe me, I'm as surprised by my comment as you are.
the value of a MCSE drops another 20 G's a year.
I've been working with a lot of vendors on projects, IBM, BEA, ATG, TIBCO, etc.
You always find bugs in the products you use. Most of the time you have to develop a fix yourself, because the vendor's release schedule will not enable you to wait for the official fix. It's just good vendor relations to send the fix to the vendor.
I did that exactly for the same reason Merrill Lynch does that, to get better software.
Proletariat of the world, unite to kill bugs
In Soviet Russia, I ruled you
No. An attacker can already find out, (It is not hard usually.) and this way people can directly contribute to those projects in use in their area.
And they can also check to see if it would be making errors that would affect them. And fix them. This is an advantage.
'Sensible' is a curse word.
Tim O'Reilly had an interesting discussion with Adam Turoff on why Open Source communities do work so well.
http://www.oreillynet.com/pub/wlg/3017
Thanks,
Gerard
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.
I wish there was some there was some way that I could be outside playing basketball, in the rain, and not get wet.
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.
K
So businesses and govornments are going to use software that anyone can see the source code for. Does anyone else see this as a security risk?
Of course knowing exactly what software a government agency uses poses a potential security risk. At the same time this gives people who are monitoring security risks a list of the contacts that it makes a lot of sense to notify when a vulnerability in that code comes up.
As a comparison point, when code red, nimda, and slammer came out, was there any kind of list of agencies or businesses that should be notified of that fact? I suspect that well over 90% of the agencies and businesses were made aware of the existence of the problem by their own systems responding unusually.
-Rusty
You never know...
What is this supposed to mean? Open source is more compatible with communism? That sounds like a subtle insult to me.
There is absolutely nothing spectacular about corporations dealing with open source software.
I recently posted a short article on this subject on SYS-CON's SYS-CON's Linux Business and Technology (the publishers of Java Developer's Journal). I think an even better article on Corporate open source adoption is the one in the March 15th issue of CIO magazine.
...that just keeps gaining momentum. Linux/open source gets some press, some "hip" factor, PHBs start to look at the hip new thing (I can just hear some manager asking his newly minted MSCE, "Say, what would it take to switch to this Linux thing I read about in businessweek?"), the more the PHBs look at it, the more press it gets...
It's cool, but at the same time, a lot of the people writing about it clearly don't understand it -- the mutilated description of the GPL in the recent Businessweek article bears witness to that. Then at the same time (in that article, and elsewhere) there's the continued use of phrases like "a ragtag band of software geeks", which I don't consider pejorative or anything, but it begins to get a little old.
I think this will be a Good Thing. As long as the "trend" lasts long enough for people to figure out how to use it(Linux, etc); if they just abandon it the first time they're prompted to fsck their filesystem, it could stop rolling. But hopefully by that time the this-could-be-more-user-friendly-dept. will have worked some more magic...
philcrissman.com.
Companies like Microsoft are greatly overcharging for their products, perhaps not for the initial sale, but for the upgrades and on-going development. Or do you really think that the incremental improvements in your Office XP upgrade are really worth several hundred dollars to you compared to the version of Office you already paid for? And why would you want to pay for improvements that often are largely based on user feedback anyway, rather than representing actual R&D work by the software company?
Those are market inefficiencies with the commercial software model that open source software corrects. Sure, the open source model isn't perfect either, in that not everybody who benefits pays exactly for what they are getting, but it seems to all average out statistically well enough for open source software to be competitive.
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.
http://saveie6.com/
Anyone who has used the code licensed under
'viral' (read GPL) open-source licenses cannot
close their source code.
This is blatantly false. The GPL only requires
you to GPL your code if you distribute it. This
means that company X is allowed to take GPL'd
code, modify it for their own use and use it
internally for as long as they like without
ever releasing their changes to their competitors.
While it's true that they can't sell their
software without GPLing it, 99.9% of software
written isn't written to be sold as a product,
it's written to meet internal needs of an
organization. That's what "in-house" development
is.
*sigh* back to work...