|Hudson becomes Jenkins|
|Monday, 31 January 2011|
The news the Jenkins has forked from the Hudson continuous integration tool project raises the issue of whether trademarks control free open source software. Is it really all in the name?
The short version of this story is that another open source project has forked from Oracle to achieve a level of freedom. In a recent vote the developers of Hudson polled 214 to 14 to rename the project and create a new fork called Jenkins. However, the real story is just a little below the surface and it involves trademarks and a cunning plan.
We have all been speculating for around a year now on what Oracle's intentions are towards the open source projects it inherited from Sun. It has been fairly obvious to most that Oracle intended to make money from its open sources assets but exactly how and exactly what this means has been unclear.
There also have been plenty of examples of dissatisfaction with Oracle - the OpenOffice fork to become LibreOffice, the loss of OpenSolaris, the walkout of Apache from the JCP and so on. But until now there has been little of Oracle actually moving to make money out of open source.
The situation with Hudson is quite different. It is the first, but probably not the last attempt, that Oracle has made to take commercial control of an open source project. Oracle has tried to present the situation as it if was all perfectly reasonable.
It doesn't really matter what the software does but in case you are interested it is a continuous integration tool used with source control systems like CVS, Git and so on. The key fact is that Hudson was started as a "hobby" project by Kohsuke Kawaguchi while at Sun which promptly sponsored it and trademarked the name. And it is the trademark which gives Oracle the extra power.
By controlling the trademark Oracle can dictate what happens under the Hudson name - down to specifying what can or cannot be called Hudson. Basically what Oracle said to the developers working on the project was that they could add to the Hudson core and still call the result Hudson but if they were to change the code in the core then they could not.
Notice that Oracle hasn't the power to stop anyone from reusing the open source code - just what they call the end result.
Notice that the lever being used in this situation is the trademark. The project founder Kawaguchi writes:
The central issue was that we couldn't convince Oracle to put the trademark under a neutral party's custody (such as the Software Freedom Conservancy), to level the playing field.
So the previous Hudson community walked away and created Jenkins (let's hope they don't neglect to trademark it). But notice that it's the trademark that defines what is happening - without the trademark the previous Hudson community could walk away with Hudson leaving Oracle to think up what to call its new open source project.
Will Jenkins succeed? Who knows but it is clear that Oracle has a substantial intellectual property in the Hudson name which is known and established. This is just an argument about branding and good branding usually wins.
|Last Updated ( Monday, 31 January 2011 )|