Feeds

Winners and losers in Sun's OpenDS spat

Not sticking it to the man

The essential guide to IT transformation

The brouhaha (here and here) surrounding Sun Microsystems and ex-employee Neil Wilson over governance of the OpenDS project - first reported in The Register - continued to bubble this week, not least among Reg Dev's readers.

Many of you took the harsh, but arguably fair, point of view that Sun was in the right as work done during the employer's time belongs to, guess who, the employer. Others adopted the slightly provocative stance that open source developers are "chumps" because what they are really doing is unpaid open source development for companies like Sun that have the money to pay.

"Open source and for-profit companies have got an irreconcilable conflict of interests - you just end up as an unpaid proxy working for The Man who makes a profit from your efforts," according to one reader.

So is everyone getting ripped off here? What is the legal position, and who wins?

The goal of OpenDS is to build a free, open-source directory service. Wilson, who helped found OpenDS, claimed he and four other laid-off Sun employees who were also project committers were threatened by Sun into relinquishing governance of the project.

Sun claimed a change in governance of OpenDS had been improperly made months earlier, and that if left in place, would leave Sun, the project sponsor, with no say.

Both sides are throwing around a lot of terms, like "owner" and "copyright." We ran this past a couple of experts to define terms.

Bruce Perens, one of the founders of the Open Source Initiative (OSI), primary author of the Open Source Definition and a project lead for the Debian GNU/Linux, told Reg Dev that an open-source project's "owners" are the copyright holders. "If the developers are applying another sense of the term to the project, they are probably confused.

"They don't teach very much about copyright and business law in engineering school, so a lot of programmers are confused about it. If the developers brought the project to Sun from outside - if they were hired after they were already working on it or if they initiated it on their own time - they own some portion of it, or the whole thing. If they initiated it at Sun, and did the work on Sun's time, it would belong to Sun.

Boost IT visibility and business value

More from The Register

next story
Intel's Raspberry Pi rival Galileo can now run Windows
Behold the Internet of Things. Wintel Things
The Return of BSOD: Does ANYONE trust Microsoft patches?
Sysadmins, you're either fighting fires or seen as incompetents now
Munich considers dumping Linux for ... GULP ... Windows!
Give a penguinista a hug, the Outlook's not good for open source's poster child
Microsoft cries UNINSTALL in the wake of Blue Screens of Death™
Cache crash causes contained choloric calamity
Eat up Martha! Microsoft slings handwriting recog into OneNote on Android
Freehand input on non-Windows kit for the first time
Linux kernel devs made to finger their dongles before contributing code
Two-factor auth enabled for Kernel.org repositories
prev story

Whitepapers

5 things you didn’t know about cloud backup
IT departments are embracing cloud backup, but there’s a lot you need to know before choosing a service provider. Learn all the critical things you need to know.
Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Build a business case: developing custom apps
Learn how to maximize the value of custom applications by accelerating and simplifying their development.
Rethinking backup and recovery in the modern data center
Combining intelligence, operational analytics, and automation to enable efficient, data-driven IT organizations using the HP ABR approach.
Next gen security for virtualised datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.