
On the heels of the announcement that Oracle will begin the process of moving the Hudson CI project to Eclipse, Koshuke Kawaguchi, the creator of Hudson, posted on his blog that he was 'surprised' by the announcement. Instead of saying it's a good idea or bad idea, he emphasized he tried speaking to Oracle about such a move in the past but was rebuffed. Then, on the thread that emerged, Ian Skerritt of the Eclipse Foundation admitted a "communication oversight" but said the move to Eclipse would be a good thing. Oracle's Ted Farrell also weighed in, saying the company proposed the move to Eclipse in December but was rebuffed by the Jenkins. There's a lot of bruised feelings and jockeying for moral high ground going on, so I posed this question on Kawaguchi's blog: "So let me ask point-blank.. will the Hudson and Jenkins sides be able to put aside their differences over project leadership and work together, bringing the forks together again? Are talks happening beyond the exchange about poor communication on this blog? That’s what people want to know!" Of course, there was no direct response; instead, there was much back-and-forth about licensing issues, and the rights under the various licenses involved. It's clear the Jenkins crew believes it is the rightful heir to the project, as its creator is on their side. Yet Oracle owns the Hudson name from its acquisition of Sun. The initial squabble was a difference over rapid releases (Jenkins side) vs. stability (Hudson side). By bringing Hudson into Eclipse, which has a great record of building community around open-source projects (rapid releases) that are then productized (stability), both sides should be satisfied. Oracle's announcement is but a first step, but one that should properly be explored, and ultimately chosen. Let the two sides check their egos at the door and work for the betterment of the community by bringing the forks together and creating something that both keeps pace with changes in the field and provides the stability enterprises require to deploy such software.

