Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tools-pmc] Fw: PMC approval needed for committer vote for ....

On Wed, Mar 9, 2016 at 10:33 AM, Elemér Lelik <elemer.lelik@xxxxxxxxxxxx> wrote:

Hi David,



I understand your confusion and I ‘m the guilty one for creating such a confusing situation.


Let me explain:   the development of  Eclipse Titan  is ongoing in Ericsson,  and there’s a developer team taking care of that. Up until recently,  the workflow was to update from time to time the public github repositories

from our internal git repositories ( which  usually was proxied by me) , but Wayne pointed out that this is not in accordance with the transparency and openness required by the Eclipse development model.  

Which we understood and now we are preparing to move all our development in the open; but for this the whole team needs committer rights so  they can continue working in github (and Bugzilla etc.)    under the same conditions they did before


So the new committer  rights requested are for developers who are de facto developing Titan  currently. Once committer rights attributed , we  can cut over to the tools provided  by Eclipse.


I hope this is will be favorably  acknowledged by the PMC.

I have to admit that the kick off of Titan has been very problematic. You have essentially admitted violating the spirit of working in the open. We as the PMC and EMO really need to provide a better test to ensure you understand what your responsibilities are as an Eclipse project. We're not just a github repo where you dump things whenever you feel like it. You are supposed to be building a community of external contributors. That's why committer elections are supposed to show the external community that these committers are worthy of being added and to build trust.

In my opinion, this seems like you are asking to reboot the project and reset the initial set of committers with these people on it. If you are not willing to allow them to work as contributors without commit rights until they earn the trust of the community, or show us what they have worked on up to this point, then we need to see what the proper procedure to reboot is.



Thank you for your understanding and best regards




















From: tools-pmc-bounces@xxxxxxxxxxx [mailto:tools-pmc-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Tuesday, March 08, 2016 10:36 PM
To: titan-dev@xxxxxxxxxxx
Cc: Tools PMC mailing list
Subject: [tools-pmc] Fw: PMC approval needed for committer vote for ....


Titan Committers,

We, the Tools PMC were asked to approve 6 new committer elections similar to the attached one. Normally that is a wonderful thing. But, in this case, there was no evidence given of Eclipse commits or history, which is typically required to become a new committer. That is how Eclipse ensures "merit" and not simply that someone, say, works for a certain employer.

Normally, if a project has "just started" we do not mind bending the rules a little, but Titan has been at Eclipse for one year now, so I would think that is time enough to learn the Eclipse rules and process, and also time enough for new committers to develop some history with the project.

So can Elemer or someone explain to the PMC a little more what this is about? Did the nominations just fail to mention the commits and history at Eclipse? Was there some special new contribution of code? Or is there a misunderstanding of what it takes to become a new committer?

I don't mean to slow things down, and certainly don't want to discourage new committers -- I am sure they are all worthy. But, I do feel an obligation to "enforce the rules" that everyone must follow since every exception makes the next one easier, until there are no rules at all! Especially for 6 committers at once! Makes me think something is going on that is not well understood or documented?


----- Forwarded by David M Williams/Raleigh/IBM on 03/08/2016 04:19 PM -----

From:        portal-noreply@xxxxxxxxxxx (portal on behalf of emo)
To:        tools-pmc@xxxxxxxxxxx
Date:        03/08/2016 04:49 AM
Subject:        [tools-pmc] PMC approval needed for committer vote for Arpad Lovassy
Sent by:        tools-pmc-bounces@xxxxxxxxxxx

tools PMC Members,
This automatically generated message marks the completion of voting for
Arpad Lovassy's Committer status on the tools.titan project. As a PMC
member, you can approve or disapprove this vote through your My Foundation
portal page:

Arpad Lovassy was nominated by Elemer Lelik as follows:
member of Titan developer team

Vote summary: 4/0/0 with 0 not voting
 +1  Elemer Lelik
 +1  Gyorgy Rethy
 +1  Kristof Szabados
 +1  Gabor Szalai

tools-pmc mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

tools-pmc mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top