[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Merge of equinox committer groups


BJ Hargrave
Senior Technical Staff Member, IBM // office: +1 386 848 1781
OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788
----- Original message -----
From: Thomas Watson/Austin/IBM@IBMUS
Sent by: equinox-dev-bounces@xxxxxxxxxxx
To: "Equinox development mailing list" <equinox-dev@xxxxxxxxxxx>, "P2 developer discussions" <p2-dev@xxxxxxxxxxx>
Subject: [equinox-dev] Merge of equinox committer groups
Date: Tue, Mar 1, 2016 8:50 AM
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