[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Commiter rights request

For full transparency to the others on this mailing list, Krzysztof has been emailing Ian and I privately in the past couple months on how to become a committer. Because none of the p2 committers have much time to work on the project and the size of the changes planned by Krzysztof may  be non-trivial, early September Ian and I have agreed with Krzysztof that if he would setup a standalone build, and gerrit then we could more easily review the changes, and thus better assess his readiness to become a committer once he would have started his contributions for his new work.
In case you have not been following, the setup of a standalone build is now almost complete but the work on the new functionalities has not started.


Ian and I talked about your situation yesterday, and even though the objectives that we set out for you have not been completely met, we are going to proceed with making you a committer to make sure you can meet your corporate deadlines.

However before doing this, we  want to make it clear that with the rights of a committer also comes the responsibilities, and that we are hoping that you will follow through with your commits until they are in the I-build and equally important contribute to all the other aspects of the project (testing days, bugzilla inbox monitoring, forums, etc.).

Finally to ensure a better chance of success I would recommend you to adapt a more respectful tone.

Pascal and Ian

-----Original Message-----
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Krzysztof Daniel
Sent: October-14-13 5:57 AM
To: p2-dev
Subject: [p2-dev] Commiter rights request

Hello everyone,

I, Krzysztof Daniel, hereby request commit rights to rt.equinox.p2 repository.

* I want to integrate P2 with external installers (but specifically with RPM). This is what I have announced on 26 Jun 2013 [1]. 
* I've already took efforts to get commitership, like:
  * P2 standalone build [0]
  * enabling gerrit/CI for P2. I got penalized here for not being a commiter [2].
  * I'm working on getting P2 tests executed in a Tycho build. It has been a month now and I got no attention until last week.
  * I've provided a number of patches to P2, and got no single review.
  * CI requires configuration changes, which was indicated by me last week [5] and got no feedback.
  * P2 tests have been broken for a month by now [6].
* I really don't want to maintain a forked version of P2, but the time is running out, and it looks inevitable as I have to deliver with Luna.

Question and answers:
* Chris, what's your experience with P2.
  * I've been troubleshooting external installers that deployed Eclipse since the P2 release.
  * I'm currently responsible for packaging Eclipse in Red Hat products and Fedora. I do it using dropins - and I fix dropins every time they stop working for me (almost every rebuilt).
  * I build P2 in a single tycho build [0].
* Chris, do you expect any regressions while you'll be working?
  * It would be a lie to say I don't.

[0] https://bugs.eclipse.org/bugs/show_bug.cgi?id=416676
[1] http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05226.html
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=416593#c1
[3] https://git.eclipse.org/r/#/c/16356/
[5] http://dev.eclipse.org/mhonarc/lists/p2-dev/msg05340.html
[6] https://bugs.eclipse.org/bugs/show_bug.cgi?id=416565

Best regards,
Krzysztof Daniel <kdaniel@xxxxxxxxxx>
Red Hat

p2-dev mailing list