On Fri, Nov 27, 2009 at 2:47 PM, Felix Meschberger <[email protected]> wrote: > ...I would think some bundles belong to Sling (e.g. the compiler or prefs > bundles). Some bundles would rather belong to the Jackrabbit project. > But then I am not sure about some bundles ....
I haven't looked at the details yet, but some Apache projects (Cocoon and Forrest for example) give write access to some parts of their svn repository to committers of both projects. Committers are then just expected to ask or mention (depending on the importance of their changes) on the list of the project that "owns" the module when they commit changes, but technically they have full write access to those common modules. Maybe that would be a good solution for those bundles that do not clearly belong to one project or the other? We could also probably extend that to other OSGi-related projects where that makes sense. -Bertrand
