[news.eclipse.technology.kepler] Kepler and Buckminster

[Thomas Hallgren <thomas@xxxxxxx>]

Reading and talking about the Kepler creation review, I've come to 
realize that the objectives of our two projects are 80+% similar. We 
both want to establish a common model of the component world. This is a 
great opportunity to join forces.

Kepler and Buckminster both have a common model that is:
- agnostic to the type of component (Maven, OSGi, Eclipse Feature, etc.)
- agnostic to the type of build system (Ant, PDE-build, Maven plugins, etc.)
- extendable through extension points.

The Kepler and Buckminster platforms want an API that allows you to:
- add new types of components
- add new types of repositories
- integrate tightly with Eclipse team providers such as CVS, SVN, and P4

Kepler and Buckminster objectives include:
- consume the new p2 model
- consume other component models
- include community information
- integrate with build server management

The Kepler team has additional good ideas, such as the "facets" concept. 
A facet is something that extends the model in some respect so that it 
can be extended with information from component models that goes beyond 
what the cspec can describe today. This is a good idea and, as far as I 
can see, the only real difference between the two projects.

So rather than duplicating each other's work, let's join forces in a 
single project and take advantage of the purpose of Eclipse: to reduce 
the cost of the common infrastructure through multiple contributors. 
Then we can each focus more of our efforts on our profit making 
extensions and services.

Kind Regards,
Thomas Hallgren