In an effort to promote stability and improve governance of the Hudson open-source java continuous integration server, Oracle has proposed to donate Hudson to the Eclipse Foundation.
has donated the code from the open-source Hudson
to the Eclipse Foundation in a move the company hopes will reunite
the fractured set of developers supporting the Java continuous integration server
move amounts to an olive branch of sorts to the Jenkins
. Jenkins was originally the Hudson
project, but after disagreements with Oracle over the stewardship and control
of the project, leaders of the Hudson
community called for a vote to change the name of the project to Jenkins. The
name change passed in late January 2010 and as the newly named Jenkins project
launched, Oracle vowed to maintain its efforts with Hudson
and considered Jenkins a fork.
with this move donating Hudson to
Eclipse, Oracle is hoping to reunite the Hudson/Jenkins community.
back, we could have handled it better," said Ted Farrell, chief architect and
senior vice president of tools and middleware at Oracle, in an interview with
said Oracle was looking to focus on stability and governance for the Hudson
project. "Our focus has been on stability," he said. "Hudson
used to release every week; we stretched that out to a five-week development
cycle. We also wanted to have a governance plan."
the end, Oracle decided the best place for stability, governance and neutrality
for Hudson was at Eclipse.
post on the issue
, Mike Milinkovich, executive director of Eclipse said:
of the key issues that split the Hudson/Jenkins community was how to balance
the corporate and community aspects of the Hudson
project. Kudos to Oracle for continuing to work on these issues and make, what
I believe, is the right move for Oracle and for the Hudson
moving the Hudson project to the
Eclipse Foundation, Hudson will now
be operating in a vendor-neutral, transparent, and not-for-profit organization.
This means potential contributors will no longer be required to sign an Oracle
contribution license agreement to contribute code. In fact, Eclipse allows you
to keep the copyright to your code; the code you contribute remains yours,
licensed under the Eclipse Public License (EPL). Furthermore, the Hudson
trademark will now be owned by the Eclipse Foundation and held in trust for the
benefit of the entire community rather than any particular company. So if you've
been wary of participating in Hudson
because of "trust issues", the Eclipse model of collaborative development
should make things a lot easier. Hudson
will now be a truly community-based project.
Skerrett, director of marketing at Eclipse, told eWEEK, "By moving Hudson
to Eclipse, Oracle is sending a strong signal they want to dramatically expand
the Hudson community participation,
increase the transparency of the Hudson
project and ultimately gain wider adoption for Hudson.
At Eclipse, we believe we have a very good model for collaborative development
of open-source software so I think it is a good fit."
Kersten, CEO of Tasktop Technologies, which is supporting Oracle's move of Hudson
to Eclipse, told eWEEK, "Open-source tools and Hudson
in particular, are becoming a key component of the enterprise ALM [Application
Lifecycle Management] stack. They encapsulate the very effective
development practices hardened by top open-source projects. The challenge
for popular open-source projects has been in creating a governance model that
links the interests of the project's community with the corporate support
needed to grow. The projects that have become de facto standards are the
ones that manage this dichotomy well, including Spring, JBoss and Eclipse."
added that Eclipse's success is based on a governance model that creates a
vendor-neutral technology base and marries corporate interests with those of
Eclipse's industry-leading API conventions
and tools have been architected to support the massive ecosystem of vendors
collaborating around popular Eclipse frameworks such as the Platform, Web Tools,
Modeling and Mylyn," Kersten said. "The proposed move is a great
opportunity to accelerate the evolution of Hudson
in an enterprise-friendly and community-inclusive way."
in a blog
post about the move
, Kersten said:
Hudson/Jenkins fork has generated FUD around this very popular Continuous
Integration (CI) tool. Oracle has ownership of the Hudson IP that they
acquired via Sun's initial investment in the project. Jenkins exercised
the very important open-source community right to fork, but in the process
split the community. I in no way want to diminish what Kohsuke Kawaguchi
created, and I have a deep and personal appreciation for the labour of love
that open-source projects like this are. But from the point of view of
the large number of users and integrators of Hudson,
in handing over the IP and governance of Hudson
to Eclipse, Oracle has done the right thing for the long term success of the