>From http://www.infoq.com/news/2011/05/eclipse-hudson:
-- Oracle proposed today that the Hudson project be transferred to the Eclipse Foundation, complete with code re-licensing under the Eclipse Public License as well as the domain and controversial trademark. Oracle will continue to lead the project, along with Sonatype who have been instrumental in migrating the Hudson plugin system towards a JSR 330/Dependency Injection style of representation. However, the move to the Eclipse Foundation has also interested others, such as VMware and Tasktop, who have been invited to participate as committers on the project. With the top-level Mylyn project providing application lifecycle management from within Eclipse (which already includes a Hudson/Jenkins connector), and the recent move of Tycho (which was released under the org.eclipse namespace this week), the Eclipse Foundation's story on interoperable build and management tools makes it a natural place to host the Hudson builds. It is also hoped that the migration of Hudson to be an open-source managed project may help with the split between Jenkins and Hudson, which primarily focussed around the issues associated with the trademark and governance model. Since the Eclipse Foundation will now own the trademark, and the governance model is well known and understood, hopefully this can act as a point of co-operation between the Hudson and Jenkins products. The Eclipse Foundation pays a significant amount of attention to IP cleanliness, so the creation of a project proposal is just the start of a long journey. In addition, the re-licensing of the existing codebase to move to the Eclipse Public License will be fine for code contributed via Eclipse company members (Sonatype, Oracle) but any outside additions to the core may need closer examination before the code can come through. Hudson will continue to encourage the plugins be available via Maven Central, although this isn't a prerequisite for creating and hosting a Hudson plugin. Many plugins are compatible with both the Hudson and Jenkins projects; hopefully, with a new plugin model being available for both, the move to Eclipse will help draw a line under the Hudson/Jenkins debate and a true open-source governance model will be possible under the Eclipse Foundation. -- Matthew. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
