This FAQ answers some of the questions you may have in relation to the proposed transfer of the Hudson project to the Eclipse Foundation.
What is happening?
Oracle has submitted a proposal to the Eclipse Foundation to create a Hudson project in Eclipse and contribute all of the Hudson core code and IP to that project.
What is Oracle's ongoing investment in Hudson?
Oracle remains fully committed to the Hudson project and will continue to invest in the project both in terms of leading the project at Eclipse and continuing to staff full-time employees in the areas of development, QA, documentation and product management.
Does Oracle still view Hudson important for their customers?
Absolutely. As application software development evolves to become ever more complex, the core tasks of managing the development processes around it can quickly exceed the capacity of manual systems. We believe that a continuous integration solution such as Hudson is key to all enterprise development efforts, including, but not restricted to, those undertaken by Oracle itself and its customer base.
Will Oracle have commercial products or support for Hudson?
Oracle intends to offer commercial support for Hudson.
What happens to the Hudson trademark?
The Hudson trademark will be transferred to the Eclipse Foundation.
Who owns the IP?
The IP for the Hudson project will be licensed under the Eclipse Public License (EPL). In addition, Oracle will transfer ownership of the trademark and appropriate namespace to the Eclipse Foundation. The project will be covered by the standard Eclipse IP Management rules [http://www.eclipse.org/org/#IP Management].
The license for Hudson is being changed to EPL. What are the implications for Hudson plugin developers?
This contribution to the Eclipse Foundation consists purely of the Hudson core. It does not imply that all Hudson plugins will have to transfer to Eclipse as well. Plugin writers will still be free to host their code with the main Husdon project or elsewhere and still be published in the Husdon update center. Hudson plugins that are currently hosted on the existing repositories will be automatically transferred into the Eclipse Infrastructure provided that:
Contributing a code base as big and complex as Hudson involves a lot of work to check out the IP and ensure that the code is clean and of high quality. Fortunately this has already been a major focus of the Hudson team for the last few months and many of the problems are understood (see the Eclipse proposal, legal issues section). Of course it's hard to predict with any certainty but we anticipate the issues should be resolved within a couple of months.
Who else is supporting and participating in the Hudson community?
Oracle will be leading the project along with an initial pool of contributors from Sonatype, Tasktop, and VMware. IBM and Intuit are also listed as project supporters.
Why now? Why not do it to avoid the Jenkins split?
Moving Hudson to Eclipse, or even to an Eclipse-like structure was proposed to the core Hudson community before the fork. At that time, it was deemed as “too heavyweight”. In evaluating our options post-fork, we still were lead back to the Eclipse submission as the best course of action for the continued success of the Hudson project.
Why is Oracle making this change to move this project to the Eclipse Foundation and why is it good for the Hudson community.
Oracle has been looking for ways to improve the insight, predictability and openness of the Hudson project and we believe having it part of the Eclipse community was the best way to achieve that.