Re: [equinox-dev] Merge of equinox committer groups

2016-04-06 Thread Thomas Watson 
I am moving forward with merging the equinox committer groups.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=488579

Tom


- Forwarded by Thomas Watson/Austin/IBM on 04/06/2016 07:57 AM -

From:   Thomas Watson/Austin/IBM
To: Equinox development mailing list <equinox-dev@eclipse.org>
Date:   03/25/2016 08:06 AM
Subject:    Re: [equinox-dev] Merge of equinox committer groups


OK, to be clear Pascal and Ian.  You are fine moving forward with a single 
committer group for all of Equinox including p2?

Personally I don't see any issues here with merging.  We should be using 
gerrit reviews, especially if a committer is touching code they are not 
familiar with.

Tom





From:   Pascal Rapicault <pas...@rapicault.net>
To: Equinox development mailing list <equinox-dev@eclipse.org>
Date:   03/24/2016 10:10 PM
Subject:        Re: [equinox-dev] Merge of equinox committer groups
Sent by:equinox-dev-boun...@eclipse.org



Well, why not.

On 16-03-22 09:50 PM, Ian Bull wrote:
+1 

Cheers,
Ian

On Tue, Mar 1, 2016 at 8:46 AM, Raymond Auge <raymond.a...@liferay.com> 
wrote:
+1

- Ray

On Tue, Mar 1, 2016 at 10:31 AM, Thomas Watson <tjwat...@us.ibm.com> 
wrote:
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-dev@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-dev@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-dev@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-dev@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-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev



-- 
Raymond Augé (@rotty3000) 
Senior Software Architect Liferay, Inc. (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance (@OSGiAlliance)

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



-- 
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource


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

Re: [equinox-dev] Merge of equinox committer groups

2016-03-25 Thread Thomas Watson 
OK, to be clear Pascal and Ian.  You are fine moving forward with a single 
committer group for all of Equinox including p2?

Personally I don't see any issues here with merging.  We should be using 
gerrit reviews, especially if a committer is touching code they are not 
familiar with.

Tom





From:   Pascal Rapicault <pas...@rapicault.net>
To: Equinox development mailing list <equinox-dev@eclipse.org>
Date:   03/24/2016 10:10 PM
Subject:    Re: [equinox-dev] Merge of equinox committer groups
Sent by:equinox-dev-boun...@eclipse.org



Well, why not.

On 16-03-22 09:50 PM, Ian Bull wrote:
+1 

Cheers,
Ian

On Tue, Mar 1, 2016 at 8:46 AM, Raymond Auge <raymond.a...@liferay.com> 
wrote:
+1

- Ray

On Tue, Mar 1, 2016 at 10:31 AM, Thomas Watson <tjwat...@us.ibm.com> 
wrote:
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-dev@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-dev@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-dev@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-dev@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-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev



-- 
Raymond Augé (@rotty3000) 
Senior Software Architect Liferay, Inc. (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance (@OSGiAlliance)

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



-- 
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource


___
equinox-dev mailing list
equinox-dev@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-dev@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-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Re: [equinox-dev] Merge of equinox committer groups

2016-03-01 Thread Raymond Auge 
+1

- Ray

On Tue, Mar 1, 2016 at 10:31 AM, Thomas Watson <tjwat...@us.ibm.com> wrote:

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



-- 
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
___
equinox-dev mailing list
equinox-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Re: [equinox-dev] Merge of equinox committer groups

2016-03-01 Thread Thomas Watson 
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-dev@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-dev@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-dev@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-dev@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-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Re: [equinox-dev] Merge of equinox committer groups

2016-03-01 Thread Dr. Pavlin Dobrev 

+1.

Mit freundlichen Grüßen / Best regards

*Dr. Pavlin Dobrev*

ProSyst Software GmbH
Research and Development Manager
Aachener Str. 222
50931 Cologne
Germany

_www.prosyst.com_ 

 
 



Tel. (+359 2) 954 91 62
Fax. (+359 2) 953 26 17
_p.dobrev@prosyst.com_ 

Registered office: Köln, Register court: Amtsgericht Köln HRB 54586
Executives: Dr. Rainer Kallenbach, Thomas Hott, Daniel Schellhoss, Dr. 
Dimitar Valtchev


On 3/1/2016 3:49 PM, Thomas Watson wrote:
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-dev@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-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Re: [equinox-dev] Merge of equinox committer groups

2016-03-01 Thread BJ Hargrave 
+1
 
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
 
 
- Original message -From: Thomas Watson/Austin/IBM@IBMUSSent by: equinox-dev-boun...@eclipse.orgTo: "Equinox development mailing list" , "P2 developer discussions" Cc:Subject: [equinox-dev] Merge of equinox committer groupsDate: Tue, Mar 1, 2016 8:50 AM Right now the equinox project has the following sub-projects, each with their own committer groupsrt.equinox - parent project, no real code here, but it does contain the websitert.equinox.framework - where the OSGi framework and Equinox native launcher livesrt.equinox.bundles - where everything else is, besides p2rt.equinox.p2 - where p2 isI 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 listequinox-dev@eclipse.orgTo change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://dev.eclipse.org/mailman/listinfo/equinox-dev

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

Re: [equinox-dev] Merge of equinox committer groups

2016-03-01 Thread Pascal Rapicault 

Makes sense to me
On 3/1/2016 8:49 AM, Thomas Watson wrote:
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-dev@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-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Re: [equinox-dev] Merge of equinox committer groups

2016-03-01 Thread Stefan Xenos 
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  wrote:

> +1
>
> Cheers,
> -Martin
>
>
> > Am 01.03.2016 um 14:49 schrieb Thomas Watson :
> >
> > 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-dev@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-dev@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-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Re: [equinox-dev] Merge of equinox committer groups

2016-03-01 Thread Martin Lippert 
+1

Cheers,
-Martin


> Am 01.03.2016 um 14:49 schrieb Thomas Watson :
> 
> 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-dev@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-dev@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] Merge of equinox committer groups

2016-03-01 Thread Thomas Watson 
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-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev