|Re: [equinox-dev] Merge of equinox committer groups|
I strongly agree. In fact, I'd go farther and merge in p2 as well. Fragmenting the permissions encourages developers to work around problems in the code they have commit rights to rather in the place where the fix really belongs, and makes it unnecessarily hard to do large changes such as rolling with deprecations.
> Am 01.03.2016 um 14:49 schrieb Thomas Watson <tjwatson@xxxxxxxxxx>:
> Right now the equinox project has the following sub-projects, each with their own committer groups
> rt.equinox - parent project, no real code here, but it does contain the website
> rt.equinox.framework - where the OSGi framework and Equinox native launcher lives
> rt.equinox.bundles - where everything else is, besides p2
> rt.equinox.p2 - where p2 is
> I plan to request the foundation fold rt.equinox.framework and rt.equinox.bundles into the parent project rt.equinox.Â I do not think there is a need to separate committers of the various equinox bundles from committers of the framework/launcher or the website.Â I do not plan to request p2 be folded into rt.equinox unless the existing p2 community of committers request that to happen.Â p2 is a fairly large codebase so it makes sense to keep it separate if the committers want that.Â But the rest of Equinox is not that large and maintaining 3 separate committer groups is not worth it in my opinion.
> Committers, please voice your concerns if you have them.
> equinox-dev mailing list
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
equinox-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit