|Re: [tools-pmc] Fw: PMC approval needed for committer vote for ....|
I should add that “uploading code from time to time from an internal repo” also feels problematic in terms of the IP Due Diligence.
Being a Committer is not only about write access to the repository, it’s also about a signed agreement (Committer Questionnaire) where the committer agrees that he/she understands the IP Due Diligence Rules.
If your internal developers have been happily pushing to an internal repository (probably not understanding IP implications of what they do), Eclipse Processes would require a full IP Review Process before such code is uploaded to an Eclipse.org repository.
Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6
From: tools-pmc-bounces@xxxxxxxxxxx [mailto:tools-pmc-bounces@xxxxxxxxxxx]
On Behalf Of Doug Schaefer
On Wed, Mar 9, 2016 at 10:33 AM, Elemér Lelik <elemer.lelik@xxxxxxxxxxxx> wrote:
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.
Back to the top