[External] : RE: CFV: New JDK Committer: Arno Zeller

Langer, Christoph christoph.langer at sap.com
Thu Feb 25 07:40:28 UTC 2021


Hi Vladimir,

thanks, I respect that. We'll hopefully come back to this soon backed by some better stats ��

Cheers
Christoph

> -----Original Message-----
> From: Vladimir Kozlov <vladimir.kozlov at oracle.com>
> Sent: Donnerstag, 25. Februar 2021 02:47
> To: Langer, Christoph <christoph.langer at sap.com>; jdk-
> dev at openjdk.java.net; David Holmes <david.holmes at oracle.com>
> Cc: Zeller, Arno <arno.zeller at sap.com>
> Subject: Re: [External] : RE: CFV: New JDK Committer: Arno Zeller
> 
> Hi Christoph,
> 
> I believe you that Arno is excellent engineer but we have to follow rules
> (which are based on contribution records) to
> be fair to other nominees.
> 
> Regards,
> Vladimir K
> 
> On 2/24/21 3:14 PM, Langer, Christoph wrote:
> > Hi Vladimir, David,
> >
> > I see that you've vetoed Arno's Committer nomination. This is a fair thing to
> do.
> >
> > If it wasn't about Arno and his personal record within our team I would
> probably just take back the CFV and postpone it to a later point in time when
> more commits have accumulated. But in this case, I'd like to add some
> pleading before I do that.
> >
> > First of all, the OpenJDK guidelines say [0]:
> > "As a rough guide, a Contributor should make at least eight significant
> contributions to that Project before being nominated." This, of course,
> leaves some room for interpretation about what "significant" means. In
> Arno's case we can see 11 commits plus the one he co-authored lately. It is
> arguable that a lot of the commits look simple, however I guess it is not
> always easy to judge whether getting to a certain change was as easy as the
> commit looks tiny. E.g. in a complex testing environment, chasing down
> problems can be rather hard.
> >
> > Furthermore, as I said in my nomination statement, Arno is a long time
> member of SAP's JVM team (actually quite some time longer than my own
> stay with the team). He is our main Quality Engineer and he is very involved
> in the OpenJDK project, triaging our tests every day. Owing to his role this
> doesn't show up so much in commits compared to other developers in the
> team. But there have been various occasions where he has found bugs and
> initiated fixes that eventually other people from our team (including myself)
> have finally brought to review and commit in the OpenJDK. We sometimes
> did not credit Arno, e.g. with co-authorship, out of convenience which was
> our fault.
> >
> > Well, after all, I personally strongly believe that Arno has deserved to
> become an OpenJDK Committer at this time. But if you stick to your veto
> after spending a second thought, I'll of course withdraw the nomination.
> >
> > Best regards
> > Christoph
> >
> > [0] https://openjdk.java.net/projects/#project-committer
> >
> >
> >> -----Original Message-----
> >> From: jdk-dev <jdk-dev-retn at openjdk.java.net> On Behalf Of Vladimir
> >> Kozlov
> >> Sent: Mittwoch, 24. Februar 2021 18:43
> >> To: jdk-dev at openjdk.java.net
> >> Subject: Re: CFV: New JDK Committer: Arno Zeller
> >>
> >> Vote: veto
> >>
> >> I think it is too early for Arno.
> >>
> >> I would like to remind that Committer candidate have to contribute
> >> *significant* changes:
> >>
> >> "As a rough guide, a Contributor should make at least eight significant
> >> contributions to that Project before being
> >> nominated."
> >>
> >> Most of changes on provided list are not significant from my POV. Also
> based
> >> dates, he was not active for more then one
> >> year except latest co-authored change.
> >>
> >> Regards,
> >> Vladimir K
> >>
> >> On 2/24/21 2:40 AM, Langer, Christoph wrote:
> >>> Hello,
> >>>
> >>>
> >>>
> >>> I hereby nominate Arno Zeller (azeller) to JDK Committer.
> >>>
> >>>
> >>>
> >>> Arno is a long time member of the SapMachine team at SAP. Most of his
> >> focus is dedicated to quality engineering for the various JDK releases that
> the
> >> SAP team is maintaining.
> >>>
> >>> Over time he has cumulated 11 commits in OpenJDK [0] and recently co-
> >> authored another one [1]. Above that, he's constantly involved in
> reporting
> >> OpenJDK bugs, contributing to their root cause analysis and reviewing the
> >> fixes.
> >>>
> >>>
> >>>
> >>> Votes are due by 12:00 UTC, 10th March 2021.
> >>>
> >>>
> >>>
> >>> Only current JDK Committers [2] are eligible to vote on this nomination.
> >>>
> >>>     Votes must be cast in the open by replying to this mailing list.
> >>>
> >>>
> >>>
> >>> For Lazy Consensus voting instructions, see [3].
> >>>
> >>>
> >>>
> >>> Best regards
> >>>
> >>> Christoph
> >>>
> >>>
> >>>
> >>> [0]
> https://urldefense.com/v3/__https://github.com/openjdk/jdk/search?q=au
> thor-
> __;!!GqivPVa7Brio!LAaKw5oglZT5Qck9mIMzB7x10lZ7hwJkpJTuwu1Lfgk73vM
> LnPu_cHJs8G5FHA9OS2e-5Q$
> >> name%3A%22zeller%22&type=commits
> >>>
> >>> [1]
> https://urldefense.com/v3/__https://github.com/openjdk/jdk/search?q=co
> -authored-
> __;!!GqivPVa7Brio!LAaKw5oglZT5Qck9mIMzB7x10lZ7hwJkpJTuwu1Lfgk73vM
> LnPu_cHJs8G5FHA-aEtifFg$
> >> by%3A%22zeller%22&type=commits
> >>>
> >>> [2] https://openjdk.java.net/census
> >>> [3] https://openjdk.java.net/projects/#committer-vote
> >>>


More information about the jdk-dev mailing list