Slashdot Mirror
Sun Says, "Compensate OSS Developers"
krelian writes "Talking at Netbeans Day, Rich Green, Sun executive vice president for software, expressed doubts about the current open source model in which developers create free intellectual property only to have others scoop it up and generate huge amounts of revenue. Green said, 'I think in the long term that this is a worrisome scenario [and] not sustainable. We are looking very closely at compensating people for the work that they do.'" Green didn't provide any details about how payments from Sun or others might work.
From the FTA
Meanwhile, author Tim O'Reilly said at CommunityOne that the days in which developer salaries differ based on the nation where the developer is located were numbered. Developers overseas now are asking why they should get paid less than others, he said. "We're actually coming to the end of cheap outsourcing," O'Reilly said.
When these numbered days are over, a great wave of levelling will start if our friend TOR is proved correct.
i remember debian compensated some people to get 4.0 out quickly... this complicated things; some unpaid contributers to the debian project protested by working very slow. the compensation policy had the opposite effect of what was intended.
i also think that a large part of the reason for FLOSS to be of high(er) quality (than proprietary software) is that it is written from for fun and from passion. people dont like to produce low quality stuff for fun and from passion. nope, that kind of stuff is produced for money, e.g. compensations!
so: sun, please dont pay us, but make some anonymous donations to some projects without letting know why you did it. this will keep us healthy.
Businesspeople use greed to motivate--it works, is easily understood, easily harnessed, and reproducible on demand. Offer money, and people will show up to work. But since that's the only tool they have, it's the only one they trust.
I think businesses would love it if it was a service that was free, and if they needed an extra gear they can throw in some cash. Unfortunately, like the Debian incident putting money in doesn't always make it progress faster. Cash is concrete and transferable. You can't give a person who's lost the spark to program a new spark plug. In fact, there's been cases where a company has become heavy users of something and the developers go tired of acting like their support desk. And they don't want to become tech support just because you're willing to pay them. "Hippy visionary volunteers" are a fickle bunch, even if they produce brilliant software. The trouble is that if they aren't looking for what you have to offer, you have no leverage at all. It just becomes some sort of unmanagable software that's going whereever they want to go, and you can either tag along or fall off. You don't know how to prod or poke it make it suit your business needs without breaking it apart. In that sense, I can understand why they don't like it.
Live today, because you never know what tomorrow brings
Back in The Day when a lot of us were contributing to Public Domain (which was the term for a loose, undocumented, unlegalized form of Open Source back then) .. we always heard the whines, "Well, what happens if someone takes this Public Domain code and sells it?"
.. well, we ALL take advantage of that in our own ways.
.. the thieves and cheats are going to take advantage. That's life.
:-) I'll bet there are pieces of that really great code buried even in the Microsoft "compressed file" functions added around WinXP time as I recall.
.. incorporated parts of our code, and probably with not a hint of credit either. (Wouldn't want anyone's lawyers worried, eh?)
.zip archiver (for every kind of system from Commodore C-64's to Crays (really!)); and we all learned a lot. So what if none of us made a bloody penny?
Well, they sell it, that's what happens. If they were clever enough to find a buyer (to pay money for what would otherwise be free), more power to them. Hell, you're so smart, YOU go sell it! Feel free!
Add services, support, a fancy front end, user customization, whatever it takes. It's free, like beer! Do what you want!
Contribute to Public Domain if you want; we all do it for our own reasons (usually to share what we've learned, and to encourage more PD code so we can learn some more). If you're concerned about someone taking advantage of that
That was then. Some great stuff came out, and still does. Public Domain, Open Source, GPL, whatever
One great example, of which I was most proud to be a very small part, was the Info-Zip Project (or Workgroup). Google it; that was a project
And I'm sure lots and lots of commercial archiving programs stol... errr
But we were all in the Info-Zip Project for our own reasons (mostly to share and learn); we produced a great