The idea of a common process and rules but separate owners for the components sounds good. We would have to discuss / agree on the details of course. This would then of course also imply that the camel community would not officially support the marketplace components. So rather each component would be supported by an individual group.
Christian On 20.02.2013 10:04, Maruan Sahyoun wrote: > a discussion/decision how to handle components is independent of a stable and > thin core. I mentioned it only to have the 'layers' complete. The points you > are making are very valid and as has been proven by others they can be > addressed. What I wanted to introduce is the idea of not being responsible > for all components themselves. Providing the 'marketplace' and procedures > associated with it on the other hand should be handled by the project. This > way Apache Camel will provide the foundation from a coding as well as > infrastructure/terms and procedures perspective. > > I think jQuery is a good example of how that could be done > http://plugins.jquery.com/ . Take a look at the submenus > • Naming Your Plugin > • Publishing Your Plugin > • Package Manifest > > Kind regards > > Maruan Sahyoun > > -- Christian Schneider http://www.liquid-reality.de Open Source Architect http://www.talend.com
