Hudson: Trouble at the mill?
Looks like Oracle and the Hudson developers aren’t getting along.
The project hosting that Oracle provide (inherited from Sun) has been a
bumpy ride for the developers, who are suggesting GitHub as a less bumpy
and more functional way to develop. Oracle seem reluctant to let them
go. Which you can understand, in a way.
Excerpt from Hudson-Labs blog:
The Monday morning prior to the planned switchover to GitHub, Oracle Senior VP of Tools and Middleware Ted Farrell sent a message to the users list expressing concerns he had regarding the migration of the Hudson codebase from Java.net to GitHub:
Oracle's goal is to grow the community and make hudson stronger. You all might not be aware of this, but the actual hudson user base is very large. Much bigger than what you see on the mailing lists or in the forums. The unfortunate part of that is how many of these users do not contribute to the core, and do not participate in these discussions. They want to do that, but don't feel like they can be heard. We want them to be heard. We need to make the hudson community a place that will welcome all the hudson users and encourage its growth and longevity. We will be announcing some changes in the upcoming weeks that we believe will foster that.
For now, however, we are going to stay on the java.net infrastructure. We believe it is important for hudson to stay connected with the rest of the the java community, as well as take advantage of some of the cool changes we will have coming to java.net. Moving to GIT can be done while staying on java.net. It is not a requirement to move to github.
Because it is open source, we can't stop anybody from forking it. We do however own the trademark to the name so you cannot use the name outside of the core community. We acquired that as part of Sun. We hope that everyone working on hudson today will do as they claim to want, and work with us to make hudson stronger.
And here's an excerpt from Hudson creator Kohsuke Kawaguchi's blog:
Monday morning I came into work and discovered that I cannot commit to the Hudson Subversion repository. Initially I wasn’t worried — I thought it was just another java.net outage that will resolve itself in a few hours — but a little research a bit later revealed that Hudson was locked down and being migrated to new java.net infrastructure.I and the whole community was quite surprised by this, as we are supposed to be “notified as soon as we assign a date for [our] projects to move.”
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)