Yes from looking on eclipse.org filesystem I see the platform.ui.tools 
repository is still owned by eclipse.e4 group, so all the same committers 
should still have access today.

However if this project has really moved to Platform UI that is not the 
right answer - it should be owned by Platform UI group and all active 
contributors should be elected as committers. This is what we have always 
done in the past when graduating components out of e4. For example see:

https://wiki.eclipse.org/E4/4.0/Release_Process

John




From:   Lars Vogel <[email protected]>
To:     E4 Project developer mailing list <[email protected]>
Date:   04/03/2015 03:28 PM
Subject:        Re: [e4-dev] e4 leadership
Sent by:        [email protected]



Hi Wim,
didn't you see my other answer? AFACS e4 committers can commit to 
platform.ui.tools.
Best regards, Lars
Am 03.04.2015 11:40 vorm. schrieb "Wim Jongman" <[email protected]>:
Hi Lars,

I assume that your question to my question has to be interpreted that you 
and Dani do not have plans to provide formal commit access to platform e4 
tools repo for e4 committers?

People are looking for e4 tools but can only find old builds [1]. The 
marketplace download breaks in Mars [1]. It is a remarkable situation that 
the tools code has moved and is now left unmaintained. 

I think that the e4 committers should have access to the new tools repo 
and should be able to work on the build.
 
Normally, if code moves to another project, the committers move along. I 
can understand the subtle difference that commit access to platform must 
not be given lightly. Is it not possible to fromally grant access to only 
the tools repo? 

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=459929

Cheers,

Wim

On Fri, Apr 3, 2015 at 10:26 AM, Lars Vogel <[email protected]> 
wrote:
Hi Wim,
Do you have something to contribute to the new repo? I do no see any open 
Gerrit reviews.
Best regards, Lars
Am 03.04.2015 9:39 vorm. schrieb "Wim Jongman" <[email protected]>:
Hi,

I call on the new e4 leaders to do something about the fact that the e4 
committers cannot touch the tooling code anymore. 

Cheers,

Wim

On Mon, Mar 16, 2015 at 5:46 PM, Sopot Çela <[email protected]> wrote:
+1

On Mon, Mar 9, 2015 at 2:34 PM, Mickael Istria <[email protected]> wrote:
+1 for Dani and Lars as project leads.

-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

_______________________________________________
e4-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/e4-dev


_______________________________________________
e4-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/e4-dev


_______________________________________________
e4-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/e4-dev

_______________________________________________
e4-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/e4-dev


_______________________________________________
e4-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________
e4-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________
e4-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/e4-dev

Reply via email to