Is It Good For Business To Subsidize OSS Developers? 124
ruphus13 writes "A lot of developers for open source software have full-time day jobs too. As economist Milton Friedman said, 'The business of business is business.' So, does it make sense for companies to encourage their developers to contribute to the open source community? OStatic discusses a blog post by Alfresco exec Matt Asay, who makes the case for why they should. '"Companies like IBM, Intel, SGI, MIPS, Freescale, HP, etc. are all working to ensure that Linux runs well on their hardware. That, in turn, makes their offerings more attractive to Linux users, resulting in increased sales." While I don't think we'll ever see companies everywhere subsidizing employee development of open source tools, many tech and non-tech companies alike could benefit from subsidizing open source development from employees with talent. If more companies woke up to this idea, we'd see more purpose-driven, mission-critical open source software shared by firms in the same industries. That, ultimately, would benefit the companies providing the subsidies.' Should your employer pay you for time spent on open source development?"
snydeq points out an Infoworld story suggesting that there's something to learn from the way French companies are promoting open-source development.
Define "Good" (Score:5, Insightful)
Is it "good" to maintain and expand the upstream rain forest that provides your raw materials?
It's not good for this week's balance sheet, but it's good if you think about it for five minutes.
Re: (Score:2)
Who wants to think?
Re: (Score:2)
Um, business owners who wish not to be competed out of existence by other business owners who think
Undermining Opponents, Complements, Corp Warfare (Score:2)
Open Source is now used as a weapon in corporate competition.
Why does IBM spend money to release Eclipse? To hurt Sun. (What does an Eclipse do to a Sun?) To make it more difficult for Sun to earn money off of Java. (You can commoditize something to prevent it from becoming your rival's money making product.) At the same time, the software is an economic complement [answers.com] to things that IBM sells. (All manner of middleware and corporate consulting, mostly the latter. A great IDE and other tools encourages m
The French seems to be leading the US these days (Score:3, Interesting)
Yes. (Score:4, Insightful)
Re:Yes. (Score:4, Insightful)
Free Software has the convenient side effect for these businesses that it makes software not just a commodity, but a very cheap commodity. For businesses in the first category, that means people have more money to spend on their products. For businesses in the second category it means that they reduce their operating costs.
This is exactly why Microsoft has tried to encourage something like a Free Software ecosystem around their products. MS Office is not Free Software, but it has a set of developer tools that allow your company to hire someone else to extend it in ways specific to your business needs. You then aren't locked in to a single supplier for these modifications (assuming you are sensible, and use a work-for-hire contract so you own the rights to them). You can do it in-house, or contract it out to one of a great many small companies. Free Software just broadens this idea. The more of your stack is Free Software, the less you rely on a single source, and the safer your business is.
Re: (Score:1)
Compared to professional labor working in an office environment, Vista+Office is already a cheap commodity.
Free Software is doomed if it tries to compete on price (widespread perception is that MS Office is the best office software; Microsoft is making enormous profits and could still operate while charging much less); Free Software needs to compete on quality.
Linux on servers, Apache, etc., back up this assertion.
Re: (Score:2)
Compared to professional labor working in an office environment, Vista+Office is already a cheap commodity.
Wrong. A decent computer running Vista costs about $400 for a desktop and about $600 for a laptop. You can easily get the same or better performance out of a $250-300 desktop or a $400 laptop with Linux. Office Small Business costs $269 (http://www.bestbuy.com/site/olspage.jsp?skuId=8182593&st=2007+office&type=product&id=1164154035835) for a license. So that leaves you with $669 for a desktop and $869 for a laptop. Are there some jobs that need Office? Yes. But for most businesses Open Offi
Re: (Score:2, Insightful)
A desktop+Vista+Office is going to last for about 3 years. So over 3 years, you save, say, $1,000 with Linux (this amount is preposterous). Over those same 3 years, if you are lucky, you will have paid the professional office worker about $150,000 in salary (with at least another $50,000 in overhead directly related to employing that person, and probably another $50,000 of overhead that is less directly related).
So the computer costs, maybe, $2,000 over 3 years, and the person costs at least $250,000 over 3
Re: (Score:2)
But how much does a bug in MS Office cost you in lost productivity? Last time I used MS Office in a corporate environment there was a bug that caused it to crash and lose data that was triggered regularly by the in-house templating system. Every time I encountered it, I tended to lose around half a page of text. Possibly other people in the organisation were more used to it, so saved more often and only lost the time spent relaunching Office.
What options did they have? They could try to work around the
Re: (Score:1, Insightful)
Paying an OSS developer to fix a bug or add a feature seems like it would be simple, but unfortunately it's not.
First, most OSS projects work on a charity model. "You give us money, we work on whatever we feel like." You can ask for whatever feature or bugfix you want, but the devs won't work on it unless they want to. There's nothing wrong with that -- as I implied, most charities work in exactly this way -- but it means that there is literally no way, other than hiring the dev into your company directl
Re: (Score:2)
Paying an OSS developer to fix a bug or add a feature seems like it would be simple, but unfortunately it's not. First, most OSS projects work on a charity model. "You give us money, we work on whatever we feel like." You can ask for whatever feature or bugfix you want, but the devs won't work on it unless they want to. There's nothing wrong with that -- as I implied, most charities work in exactly this way -- but it means that there is literally no way, other than hiring the dev into your company directly, to get a specific feature or bugfix added to most OSS projects.
Developer != project. Any programmer with a bit of knowledge of the sourcecode and how the program works should be able to do a simple bugfix on an OSS project. Just because you e-mailed RMS about a bugfix on Emacs and he declined the offer doesn't mean that Joe Programmer can't fix the bug.
There are, of course, companies which form around OSS software specifically to do work-for-hire. The problem there is that the work they do for you typically ends up back in the OSS project. Logical enough: that is the way OSS is supposed to work, after all. But it removes any competitive advantage you have, and it's contrary to the way software contracting has traditionally worked (where the company to whom the programmers are contracted will usually have the rights for the software).
Unless you make software, software should not give you any more of an advantage. The product you sell and the employees you hire should give you the advantage, yes, upgrading your desktops will give you a possible pr
Re: (Score:1)
Unless you make software, software should not give you any more of an advantage. The product you sell and the employees you hire should give you the advantage, yes, upgrading your desktops will give you a possible productivity boost, but for most businesses technology should stay in the background.
I couldn't agree more. Bringing technology into the foreground enables innovation and [potentially] massive improvements in efficiency and methods. I go to lots of IT conferences where speakers say over and over that IT is now a commodity - they're just wrong. Through IT companies can do allot to help their competitiveness - but not if they keep technology in the background.
If I am at a restaurant, I am going to go to wherever has fast service, and cheap and decent food. If having a new cash register helps them do that fine. If having a new server helps them do that, fine. But the main object for them is to sell the most food to make the most money, that is what gives them a competitive advantage, not a new server.
This isn't a realistic example. Most businesses, and certainly that businesses that sell products or services to other businesses,
Re: (Score:2)
Collective action problem (Score:5, Insightful)
Why would a business pay for software that benefits everybody else? Why not just wait for someone else to do it?
There are answers to this question - e.g. IBM or Google is big enough and uses Linux enough that it needs to make the fixes just for its own benefit; pushing them upstream is not much extra work. Or, companies in long-term relationships - e.g. in the Silicon Valley ecosystem - can encourage each other to contribute to public goods like OSS via a "reputation mechanism" - contributors get respect and this translates into better relationships.
But the CAP is the fundamental issue.
Re:Collective action problem (Score:5, Insightful)
This attitude that business is being charitable to open source when they push changes upstream is just, well, ignorant.
They push their changes upstream because they don't want to have to keep merging them in every time a new version comes out. If they didn't push them upstream they'd either have to weigh down their development team with annoying merging duties or they'd have to stick with outdated versions of the software.
The fact that they can push stuff that possibly is completely useless to everyone else upstream and have it accepted as part of the build is one of the wonders of open source.. and, if anything, it's the upstream developers who are being charitable.
Re:Collective action problem (Score:4, Insightful)
Well, yes and no. Simple bugfixes are obviously best to push upstream, the bigger question is added/customized functionality which really adds value. At some point the value of having exclusive functionality exceeds the merge costs, depending on a boatload of factors ranging from interface complexity and stability, business value, use by competitors, specificness of the issue solved and so on. Very many companies are afraid to give away anything of value or just don't rationally calculate what it costs them to maintain it themselves, so they'd rather keep it inhouse instead even if they rationally should have open source it. But it's too drastic to go to the other extreme and say that open sourcing code isn't being charitable.
Re: (Score:2)
At some point the value of having exclusive functionality exceeds the merge costs, depending on a boatload of factors ranging from interface complexity and stability, business value, use by competitors, specificness of the issue solved and so on.
In the short term, that can certainly be true. However, what happens when you merge it for the fourth, tenth, etc. time? Especially as the merge tends to get more difficult over time. Also, note that the more work it is to add the functionality, then the more work it is to merge the functionality.
Another issue is that if the functionality is actually useful to someone else, someone will probably eventually upload it to the project in some form. If your company does this, then your upgrade path is usuall
Re: (Score:3, Insightful)
One thing you left out (or, at least, under-emphasized): if you push your changes back upstream, then you're no longer the sole maintainer of your fork, and others likely (almost certainly) can and will help maintain and enhance and fix the bugs. That's always a big win.
The flip side of this (something I've actually encountered) is when your add-ons are so specific to your particular company that upstream isn't interested in accepting your patches.
I've gotten paid, here-and-there, to send patches upstream
Re: (Score:1)
I think my reasons all help my company.
The part of my contribution that doesn't is pissing off our larger software partners, like Oracle, by making and promoting free products that are in competi
Re:Collective action problem (Score:4, Interesting)
Why would a business pay for software that benefits everybody else? Why not just wait for someone else to do it?
To scratch an itch. My company needed a fast way to convert FoxPro files to PostgreSQL [honeypot.net], so I wrote one. Now, we're not in the database format conversion business, so this isn't something our competitors would be waiting to pounce on. Why on Earth would we want to keep it locked up? I've already gotten bug reports and feature requests that made it work better for us, so we actually came out ahead by giving it away.
Honestly, especially for projects outside a company's direct business plan, I can't think of a single reason not to subsidize FOSS. You needed it and were going to write it anyway, right?
Re: (Score:1)
To scratch an itch. My company needed a fast way to convert FoxPro files to PostgreSQL [honeypot.net], so I wrote one. Now, we're not in the database format conversion business, so this isn't something our competitors would be waiting to pounce on. Why on Earth would we want to keep it locked up? I've already gotten bug reports and feature requests that made it work better for us, so we actually came out ahead by giving it away.
Honestly, especially for projects outside a company's direct business plan, I can't think of a single reason not to subsidize FOSS. You needed it and were going to write it anyway, right?
Exactly. I contribute patches to a couple of Open Source projects. My primary employer uses those packages but they don't relate to our line of business - they are general purpose. Improvements in those packages just allow us to build on more functionality that does relate the primary line of business. Hiding them doesn't have value, it is even bad. A project with new and better features will attract more users who will potentially contribute to the project.... and we'll probably consome those featur
Re: (Score:1)
An analogy is industry lobbying. When (to take an unpopular example) oil companies lobby for subsidies and tax breaks, the resulting legislation not only benefits them, but also all of their industry competitors. Often in practice the Exxon-Mobils of the world pull the laboring oars while the smaller companies get to freeload. But a more common scenario is the establishment of industry associations, supported by a wide number of players,
Re: (Score:3, Insightful)
In at least one case I can think of, no one else will do it. My soon-to-be-former hardware-based employer is a great example (I got a better offer, and went for it). The folks I'm about to leave behind uses Linux very, very heavily. Their entire software backend to the product is written with (and for) Linux.
Linux made perfect sense for them since they're selling hardware, Linux/FOSS means it won't cost a mint to license out, and it means a HUGE amount of flexibility for the programmers.
Re: (Score:3, Insightful)
> Why would a business pay for software that benefits everybody else?
If they do that, they will
a) They will look better in the eyes of open source community. And trust me, you want this, because we are usually those who tell others what they should buy.
b) They become more attractive employer to those who are most talented. Like me ;) . I would love to work for an open source project and I'm not alone.
c) They usually benefit from it directly also. For example if it is a text editor they decide to support,
Re: (Score:1)
Re: (Score:2)
Depends on the product.
For silicon manufacturers (Intel, Marvell, Freescale, TI, etc), there is a benefit to investing in OSS development - it helps them sell more chips. Some manufacturesrs, Marvell and Freescale in particular, require NDAs in order to develop software. (For Marvell, this is particularly funny, since the PXA25x, PXA27x CPU manuals used to be available freely via Intel's site, but
Depends on the needs . . . (Score:2)
It comes down to the companies controlling officers opinion of the companies' needs.
On one hand, I see no motivation for small to midsized businesses to contribute to open source applications, especially those that don't relate to the business' operating needs. Each business' business model and methods are distinct enough that most software is completely proprietary, or a proprietary implementation of a base package.
On the other hand, public relations is sometimes given more consideration. Contributing t
evidence free (Score:4, Insightful)
Wow, that article on the French is an evidence-free zone. The only actual French OSS project they mention is some middleware doodah that I've never even heard of. Trying to think of some myself... um:
1. Mandrake ...er ... ... that's it.
2.
3.
I'm sure there are others but none springs to mind.
Re: (Score:3, Interesting)
Re: (Score:1)
Re: (Score:2)
http://glpi-project.org/ [glpi-project.org]
Re: (Score:3, Informative)
Re: (Score:3, Interesting)
Re: (Score:2, Interesting)
Free.fr actually ships you a minimalistic linux box as modem; it streams the VOD through vlc, can record shows on it's hdd, and they even encourage you to hack it. I'd say that's pretty awesome, even without comparing prices or snooping practices with US ISPs...
Re: (Score:1, Informative)
Well it's certainly being talked about:
here [techworld.com]
here [infoworld.com]
here [linux.com]
and here [edemocracy-forum.com]
Re: (Score:1)
Actually it's Mandriva. Using Mandrake is no more allowed, because of Mandrake the magician ( http://en.wikipedia.org/wiki/Mandriva_Linux#Name_changes [wikipedia.org] )
Well Mandriva is just an example of software tagged "Fre
Re: (Score:2)
Wow, now I'm persuaded. You should have written the original article!
Re: (Score:1)
Re: (Score:2)
I wonder what they thought of KDE 4.0 :-)
DARPA? (Score:1)
It's silly to put basic research and (more generally) the development and maintenance of public goods in the hands of public companies because their motivations are not even vaguely in that ballpark. "The market" isn't good at providing the things that make markets possible, as the years since Reagan took office have shown. Markets are powerful tools for optimizing certain kinds of behavior, but they are not self-hosting.
If we as a society don't spend that money on basic research and other public goods li
Most FOSS projects need subsidies of some kind (Score:2)
It's inherent in successful FOSS projects that they work with their users, and when these users are businesses, it's usually win-win for the businesses to invest something in the projects they depend on.
* they pay anyhow, and it's better to pay as partners than clients.
* their engineers get to learn the insides of the product and so are able to reduce the risks of using it.
* they can get their business needs incorporated into the product.
* they give their engineers a way to enjoy their work more.
* they get
lost opportunity (Score:1, Insightful)
The path that budding developers take is infinitely more accessible (and far less expensive) via open source. If you lose the foresight of funding that community you risk intellectual hoarding and corporate driven (read "heavily manipulated") R&D that is self serving and beleaguered with protection, IP, DRM, and general monetary ballast that ultimately imprisons creativity.
Because reinventing the wheel is really expensive. (Score:5, Insightful)
F/OSS means that you don't have to buy or write an operating system just to run a single program on a single device, or write an OS for a new piece of equipment from scratch. It means you don't have to come up with a proprietary database when you're not sure the bigger project will pan out. It means that you can support standards and undermine format monopolies, allowing you to bring your product to market despite an 800lb gorilla.
"The business of business is business" doesn't mean that short-term gain trumps long-term. It means that business, in a market economy, seeks advantages where it can find them. Having a large base of reliable free software is a big enough advantage for some companies that they happily underwrite its development.
Re: (Score:2)
Having a large base of reliable free software is a big enough advantage for some companies that they happily underwrite its development.
It is only an advantage if you can keep your competitors from using it too; othewrise it is just a cost of doing business.
Re: (Score:3, Funny)
Re: (Score:1)
It may not be an advantage compared to your direct competitors, but it may well grow your market overall.
Yes, but ... GPL (Score:2, Insightful)
The company I work for would love to subsidize open source development. We'd all love to use and extend existing projects instead of writing code from scratch. But recently I spent a couple of weeks writing a proprietary communications package when there's already perfectly good code on SourceForge.
Why? The OSS project uses the GPL. This means if the company donates two weeks of my time to subsidize this OSS project, it ends up losing ownership of the rest or our application. That would cost the company *a
Re: (Score:1, Troll)
Mods on crack. (Score:2)
How is the parent a troll? That is the whole point of the GPL.
Re: (Score:3, Insightful)
Re: (Score:3, Insightful)
Free Software isn't a religion, but it's not a charity either.
Re: (Score:1)
Re:Yes, but ... GPL (Score:5, Insightful)
Why? The OSS project uses the GPL. This means if the company donates two weeks of my time to subsidize this OSS project, it ends up losing ownership of the rest or our application. That would cost the company *a lot* more than wasting time rewriting existing code.
First, you still own your application. It's copyrighted to you. You own it. Second, is the app one your plan on distributing? If not, then the GPL is moot.
It's just to damn bad there's so much GPL. Let's get the religion out of software development.
The GPL keeps you from taking my code and locking it up in some proprietary application where I won't get to use it. You seem to be under the unsupported belief that I should let you.
Re: (Score:2)
How exactly can you lock up code? The code will still be distributable no matter how many proprietary projects use it. The real question is, "should we allow companies (or anyone) to profit from code without giving something back?"
Re: (Score:2)
We were actually talking about code that was previously free, but somehow is now not. You can't copyright free code again to stop it circulating, and you can hardly call it a trade secret when it has been circulating the net for some time (not to mention the copyright belongs to someone else).
Maybe that might tell you that I'm not actually posting a flamebait? No? I guess my name means that all my posts are automatic attempts at flamebait, huh. As for you, your o
Re: (Score:2)
The GPL keeps you from taking my code and locking it up in some proprietary application where I won't get to use it.
So the existence of these proprietary postgres-derived databases [postgresql.org] means that you don't get to use postgres because its code is now "locked up"?
Re: (Score:2)
So the existence of these proprietary postgres-derived databases means that you don't get to use postgres because its code is now "locked up"?
No. It means that I don't get to use the modified, enhanced derivatives that are tucked away where no one can get at them. Still, that's the choice of the PostgreSQL developers. They chose a license that explicitly allowed that, as is their right. The post I replied to was complaining that GPL-using authors did not make the same choice.
Re: (Score:2)
Let me turn it around a bit to see if it makes it easier to understand why developers choose the GPL over other, less restrictive licenses.
I have recently started writing a free software game. It will have a 3d isometric view. I will spend several weeks writing a free software graphics engine where there is already perfectly good code in proprietary programs. (Well, actually, there is probably already a free software one I can use, but let's say there isn't)
Why? The proprietary programs use their own lic
Re: (Score:2)
This is why I prefer MIT or BSD licenses for my own work. I
Re:Yes, but ... GPL (Score:4, Informative)
This means if the company donates two weeks of my time to subsidize this OSS project, it ends up losing ownership of the rest or our application.
No it doesn't. You (or your company) seem to be confusing copyright ownership with source code distribution. You don't relinquish copyright ownership of code you wrote by incorporating GPL'd code into your application, you're just required to make your source available if you're distributing it with the stuff you didn't write. Don't like it? Sorry, that's what the author of the code you got for and investment of $0 decided upon when they chose to distribute what they wrote --and own.
Re: (Score:1)
You're right. The company still keeps full copyright ownership of the proprietary code. What I should have said is that the company also loses control over millions of dollars worth of R&D that went into developing the rest of the application, and, by publishing it, loses any competitive advantage it may have had.
That, of course, is th
Re: (Score:2)
You're right. The company still keeps full copyright ownership of the proprietary code. What I should have said is that the company also loses control over millions of dollars worth of R&D that went into developing the rest of the application, and, by publishing it, loses any competitive advantage it may have had.
That's entirely dependent upon the business model. If you're looking at a traditional "we make money by selling a license and a pre-compiled binary with mysterious voodoo code contained there
Seems to me the most important reason to.... (Score:2)
...support open source development is that of helping to advance the technology of the human race and benefits of in all the ways it can.
And at the rate that open source can do above and beyond the false constraints of proprietary software.
See more info [mit.edu]
The above contents at url has broken links and some outdated info but the general scope is still valid.
The paper only report "hirts_report1.0.pdf" address the failure, of autocoding to identify incompatibility inspired by closed source profit motives. Softwar
More work, more practice (Score:2, Insightful)
I'm surprised nobody has yet pointed out that contributing to OSS is likely to lead to a direct increase in developer skillset.
It definitely is ! (Score:2)
and in open source, you dont want to supply a constant subsidy either, there are other sources also donating to that project. so its like an installment plan.
you basically encourage and contribute to the development of a software you need or you probably will need.
its democracy at its finest - open contribution from all. how much a software is needed by people, market
No surprises (Score:2, Insightful)
A company whose livelihood is open source proposes that other businesses should subsidize open source... That's kinda like asking the RIAA and MPAA to sponsor a study on piracy.
It's not a subsidy. (Score:1)
Government is just a big user, LL IS big in France (Score:5, Insightful)
Open source is really about users taken responsibility and control for mission critical applications. Government is just a big user, like a big bank, an insurance company, or film production company. They have internal needs. All organizations need to look at their internal needs and skills and contribute effectively, where it is of direct benefit to them. When the benefit is big enough, they pay someone to work on a project directly, if not, they don't. Sometimes it is only part time, and the level of expertise is only for QA, patches, and the like. That's fine!
The major Apache contributors at the outset were all firms whose survival depended on having an effective web server. The business case for working on apache was compelling for all involved. Other contributions should be similarly compelling.
The flip side of yesterday's story on Quebec sole sourcing (avoiding all responsibility of any kind, and just following 'the market'), is national funding of software distributions (taking total responsibility to the point of re-inventing the wheel) Neither approach is going to work best in the long run. Large organizations funding what they need, is just the corporate analogy of individuals scratching their itch.
blog post about that: http://csptrn.blogspot.com/2007/03/national-use-of-open-source.html [blogspot.com]
Logiciel Libre is Big in France.
In France, that's what they do, on a massive scale. Example: the French Fisc (like the US. Internal Revenue Service) replaced their almost all Oracle all the time solutions by making an RFP (Request for Proposal) with specific performance tests for a J2EE platform. All the biggies were invited (Oracle, IBM, BEA, etc...) but the fastest implementation was by a small local firm using open source tools.
reference:
http://www.cllap.qc.ca/2006/modules/wfdownloads/singlefile.php?lid=48 [cllap.qc.ca] duh... it's in French...
They don't care if you can't read it, their in it for their own good.
The fisc saved a ton of money by doing a competitive procurement. The winning company is local, and developing expertise among people who pay taxes, and drive the economy.
Another useful initiative in France with OSS is
http://adullact.org/ [adullact.org] where people from a bunch of different local governments work together and fund and adopt common integrations of OSS technologies for specific vertical uses. Each local government reduces their costs by partially funding the common solution. Each gets a say in requirements and functionality delivered. None is stuck shouldering the whole burden.
It is not about creating new software projects. There are thousands of those, and almost all needs can be met by integration/consultation of existing software, because, frankly, not a lot of government needs are that complicated. People just have to have a mind set that they are responsible for the technological choices they make, and get educated about long term implications.
On a given government procurement, the traditional decision is 'buy vs. build' that is an obsolete decision, it is more like 'buy vs. assemble' or 'buy vs. contribute' or 'buy vs. cultivate (local talent)' today. The costs are looked at on over the duration of a procurement, not on a life cycle basis.
For example, if you take open office, and you say it will cost 4 years to make the transition, that's true. the requirement for the functionality is not going away, so in five years, assuming the transition was taken care of, when you have to renew your MS license, ooo is going to cost close to zilch. That's when they pay back starts.
Government needs to look at things rationally over the long term. the only thing on the side of the traditional vendors is perceived level of risk and market share. As the number of adopters increases, both of those aspects are declining.
Not my decision to make... (Score:2)
Should your employer pay you for time spent on open source development?
Thats not my decision to make, my employer can do whatever they wish with what I produce as a coder (or designer, or....) as I'm producing it for them. They tell me what to do, and so long as its within my ethics ranges, I do it - if they wish to then put my work out into the wild through some open source scheme, thats entirely up to them.
Re: (Score:2)
I feel a little sorry for you actually. It sounds like you've pretty much accepted that you have no say in your workplace at all. You say that "they tell me what to do, and so long as its within my ethics ranges, I do it". I myself am just a "lowly programmer", but I get invited to every meeting to discuss the future of our projects, get to give my input, and am often listened to. If I suggest we go with an open source approach on a project, there's a good chance it'll happen (unless there's a compellin
Re: (Score:2)
But its still not my place to decide what my employer does with my output, so the question the summary presented is one I refuse to answer because it is not my decision to make.
Re: (Score:2)
Without knowing the specifics of your industry, I can't tell you the answer to this, but from what you've said your company is paying you to answer it for them.
It is. (Score:1)
Yes - but give an incentive (Score:2, Interesting)
Re: (Score:2)
You can do whatever you want. There's no copyright on the GPL, and you may modify it however you want. However, I would be careful about losing the concept of "free" software to some anti-corporatist ideology.
Re: (Score:2)
There's no copyright on the GPL, and you may modify it however you want.
Not true. The text of the GPL is copyrighted, and owned by the Free Software Foundation. Derived works are expressly not allowed by the copyright notice on the license (v2 has an identical notice with a different year):
Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
I've stopped being surprised by people who comment on the GPL without having the slightest clue what it says in the license, but not even knowing the conditions for using the license is a new low even by Slashdot standards.
Re: (Score:2)
Oh. Good to know, thanks. :)
Still, you should be able to come up with similar concepts, even if the GPL is copyright.
different people: different motivations & rewa (Score:2)
Normally, companies can't meet these different needs: and extra money doesn't help retain the kind of staff who would want to work on OSS projects. So as a cheap and efficient way of retaining people they value, why not let them work on their own projects - so long as it doesn't interfere with the business of business?
Better Question (Score:2, Insightful)
Easy call in my mind.
Community (Score:1)
In my experience, the support works both ways. What I want, and enjoy, is the community of development.
When I need help with a particular project, say printing barcodes, the OSS community allows me to incorporate features into my code that I'd otherwise have to spend a lot of $ to get. The ability to extract source code to streamline the process for my users makes for an easier to use system.
Any code changes that I make that improve functionality or fixes bugs, I return to the project. (I guess that 2/3
Why I hire OSS devlopers (Score:5, Insightful)
On a number of occasions I have hired people who actively participate in OSS projects. Here's why:
And they get bonus points if they have done the work in some area that relates to the work I'm paying them to do, even if we don't use their package. Why? Because it means they've been thinking very hard about the problem.
Yes: case study from Google / ZXing (Score:4, Informative)
I am from Google and co-operate the "zxing" open-source barcode reader project. (http://code.google.com/p/zxing) Two of us were allowed to devote most of our time for 6 months to this open project, because it made strategic sense for the business.
Why? To be brief, 2D barcodes open up new possibilities for advertising services in print. Our Print Ads business wanted to build services around them. However the market is still developing and while there are some dominant open standards evolving, there are several proprietary formats emerging. We thought it best -- both for the ecosystem but also for our business -- if the open standards won. So we explicitly set out to promote them, and one way of doing that is to release free, open, quality software that uses the open standards.
Contributing to open source can definitely be strategically valuable.
What goes around comes around. (Score:2)
Sure they should: you reap what you sow.
Re:Why (Score:4, Insightful)
Re:Why (Score:5, Insightful)
OSS developers get funding because companies think their free software benefit them
I may be overly cynical, but I would suspect that the only time a company contributes to an OSS project is when it wants some form of control over it: benevolence doesn't really come into it, nor does a subscription to Free Software ideals.
Take Apple: as closed and proprietary as Microsoft, if not more so, yet they contribute to OSS. In fact, take Microsoft, who now sponsor the Apache Software Foundation [arstechnica.com].
I suppose my point is that perhaps instead of asking whether companies should subsidise OSS, we should be asking whether OSS should want companies to subsidise it.
Re: (Score:3, Insightful)
I may be overly cynical, but I would suspect that the only time a company contributes to an OSS project is when it wants some form of control over it: benevolence doesn't really come into it, nor does a subscription to Free Software ideals.
I don't think you are over cynical, but I do think you are missing something. Companies contribute to OSS projects when it gives them a return on their investment. Sometime that's control. Most of the time, though, they realize that they can benefit from cooperation if the software is not part of the core service/business that they are selling.
To really understand how free and open source software works in this circumstance, you merely have to look at consortiums. These were popular with businesses long
Re: (Score:1)
A really good example of this is the OpenNETCF project. It's an implementation of the .Net framework libraries with a MIT style (I think -- it's been a while since I used it) license. Back when I was doing mobile work with .Net it was indispensable. Microsoft's own implementation just plain didn't work and my company needed code that would operate the same on both desktop and mobile platforms. So we used OpenNETCF. And we fixed bugs in a few places and submitted patches.
In fact, OpenNETCF is released under a "shared source" licence [opennetcf.com], the first condition of which explicitly prohibits distribution or combination with other free (both senses) software.
Actually, the whole thing reeks of Microsoft sponsorship.
To be fair, a lot of their other projects (little helper apps, debugging tools etc.) _are_ MIT licensed (they call [opennetcf.com] it "true Open Source").
Re: (Score:2)
Very interesting... I swear it was MIT licensed about 3 years ago (when I was using it). I wish I had saved a copy... In fact, I vaguely remember when 1.3 came out there was a division between OpenNETCF and OpenNETCF.com. And I also seem to remember that there were two different licenses at the time.
But if this is what happened, then it is indeed scuzzy beyond words...
Re: (Score:3, Informative)
True, but I can think of a reason why companies would want to subsidise OSS for their own selfish needs.
Currently I use some OSS software in my company, dragging my boss kicking and screaming and recently, begrudgingly agreeing that it was a better solution!. Now, there are features I'd like to add, improvements I'd like to make, additions I'd like to implement, but I don't really have the time at work or at home to do it. Persuade my boss that we could improve the OSS software and we would have a better sy
Re: (Score:2)
If you keep your code internal, you have to maintain a branch and handle any conflicts introduced whenever anyone else touches the same bit of code as you. If you send it upstream, merging conflicts becomes someone's problem and doesn't cost you anything.
Whether letting other people use your changes will cost more or less than keeping them secret depends on your individual case.
Re: (Score:2)
Apache is an excellent example because it gained enough ground that to recreate it would cost any company too much money. It's far better to let the experts handle it and chip them a little money to put the system on your hardware too.
I think that OSS lends itself to the consulting business, but it's not quite there yet. Companies that get paid for results and not for software directly, like web hosts. I think that ERP systems and business software could be the next frontier if companies changed over.
Re: (Score:1)
I know, I know, to some extent that's exactly what Apple does with webkit. But my feeling is that, sadly, they cannot concede because of the looming threat of lunix, as in: "first, it was the browser, then, the whole desktop". So no concessions at all are made.
Re: (Score:2)
Because colossal missed opportunities arising from beneficial externalities that are not getting incorporated into the development funding.
Example: almost *everyone who has a website benefits from some part of the LAMP stack, though they pay nothing for it. This isn't a problem, as the marginal cost of the LAMP stack is zero.
But if all those beneficiaries would pool a fair price -- or 5% of a fair price -- for that code, and put it into more development .. well, I can barely imagine how fast the stack would
Re: (Score:2)
Well, according to the Free Software Foundation:
'Freedom is a matter of liberty, not price. Think of free as in "free speech" not "free beer".'
Re:Why (Score:4, Insightful)
"The Open Road" article annoys me because it incorrectly implies that free/open source software has some sort of problem and needs subsidizing. Honestly, it's quite insulting to the free/open source software movement. IMHO, the author has hugely underestimated the strength of the free/open source software movement. It's not free/open source software that's in trouble - it's companies that rely on selling proprietary software that are in trouble.
Re: (Score:2)
Why would a person who doesn't know what a homograph [wikipedia.org] is post absurd rhetorical questions on Slashdot?
Of course, almost any other question would have been better, so it's not like I had to jump very high to clear the bar.
Re:Sounds like 'la la land' (Score:5, Insightful)
Let's say I'm running Company A, and I compete with Companies B and C. If I subsidize an OSS project (rather than paying external or internal devs for a private custom solution that might give me a competitive advantage), what's to stop Companies B and C from using the OSS code that I funded, for free?
Maybe they don't know about it, maybe they're not set up properly to use it effectively, maybe they've already bought in to a competing solution.
Or the reverse: If Companies B and/or C are willing to subsidize an OSS project, why should I subsidize when I can mooch that code for free myself? I'd be more than happy to let my competitors fund code that I then can use for free.
Maybe you want faster development, or maybe you want slightly different features than what your competitors are going for.
As time goes on, more and more companies would wise up and realize that funding OSS code let's their competitors mooch that code for free, and more and more companies will stop subsidizing since they're being played as suckers.
You're not automatically a "sucker" just because you happen to be creating positive externalities. I doubt that a lumber mill would much care who else used benefited from the software they helped fund for their HR department to use, unless the wider use actually benefited them by, say, getting bugs found/fixed quicker.
When's that last time OSS folk actually invented something? IBM or Google tweaking Linux or Apache and giving those tweaks back to the community is baby shit. Let's see Google release their search algorithm code so that Yahoo, MS, Ask, etc can use it for free, then I'll be convinced that subisdizing OSS is worthwhile.
A lot of the work on distributed/decentralized source control (Darcs patch theory, (deterministic) mark-merge, etc). FastCGI. Anything described in the RFCs. Plan 9 and Inferno. Package management. etc...
Re: (Score:1)
I wish some people, especially business people, would study more game theory. They would realize that in most situations corporation is more advantageous than confrontation. In the case that you describe if there are several competitors it is better for them to work together on those solutions than to keep them closed. I doubt that leaching is really that advantageous either because you have absolutely no influence on the code so you probably still have to adjust some of it to your needs.