I forgot to include p2-dev in this thread.  I leave it to the p2 devs to 
decide.  If it was only up to me I would merge.

Tom


----- Forwarded by Thomas Watson/Austin/IBM on 03/01/2016 09:38 AM -----

From:   Thomas Watson/Austin/IBM@IBMUS
To:     Equinox development mailing list <equinox-...@eclipse.org>
Date:   03/01/2016 09:32 AM
Subject:        Re: [equinox-dev] Merge of equinox committer groups
Sent by:        equinox-dev-boun...@eclipse.org



I have no objections to merging in p2.  But I would like Pascal and other 
p2 committers to agree first.

Tom





From:        Stefan Xenos <sxe...@google.com>
To:        Equinox development mailing list <equinox-...@eclipse.org>
Date:        03/01/2016 08:25 AM
Subject:        Re: [equinox-dev] Merge of equinox committer groups
Sent by:        equinox-dev-boun...@eclipse.org



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.
+1

On Tue, Mar 1, 2016, 5:51 AM Martin Lippert <mlipp...@gmail.com> wrote:
+1

Cheers,
-Martin


> Am 01.03.2016 um 14:49 schrieb Thomas Watson <tjwat...@us.ibm.com>:
>
> 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.
>
> Tom
>
>
> _______________________________________________
> equinox-dev mailing list
> equinox-...@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
> https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
equinox-dev mailing list
equinox-...@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-...@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-...@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
p2-dev mailing list
p2-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/p2-dev

Reply via email to