Thread-topic: [iot-pmc] Election for Neil O'Toole as Committer on Eclipse ioFog
Hi Jens, Kilton,
I tend to agree with Jens in that the linked PRs so far seem to
demonstrate understanding of the tooling and build process for parts of ioFog.
Personally, I would probably not vote in a committer to a project
that I am involved in based on the current track record. But as pointed out by Jens already, it is up to the ioFog project's committers to establish the baseline for "substantial, high quality contributions" (by means of voting in the election).
@Jens, Ian FMPOV we should waive the election result and (try to) use this as a reference
for future committer elections in ioFog.
Mit freundlichen Grüßen / Best regards
Kai Hudalla
Software Developer
Open Source Advocate
Bosch.IO GmbH Ullsteinstraße 128 12109 Berlin
GERMANY
www.bosch.io
Registered Office: Berlin, Registration Court: Amtsgericht Charlottenburg; HRB 148411 B
Chairman of the Supervisory Board: Stefan Koss
Managing Directors: Dr. Andreas Nauerz
Von: iot-pmc <iot-pmc-bounces@xxxxxxxxxxx> im Auftrag von Jens Reimann <jreimann@xxxxxxxxxx> Gesendet: Donnerstag, 1. Dezember 2022 08:58 An: PMC list for IoT top level project <iot-pmc@xxxxxxxxxxx> Betreff: Re: [iot-pmc] Election for Neil O'Toole as Committer on Eclipse ioFog
Hi Kilton,
To be honest, these look like rather basic contributions to me. I am not saying this to discredit anyone, but I also have a hard time to align this with the requirements from the project handbook [1]:
> After an individual has made a small number of high quality contributions that demonstrate that they understand how the project works, understand the Eclipse Foundation Development Process and are prepared to implement the Eclipse Foundation Intellectual
Property Due Diligence Process, a committer will invite them to join the team and initiate the election.
I know, that it also says:
> What constitutes a sufficient demonstration of merit varies by project team.
If the list above is the project's definition of "sufficient merit", then that is fine with me. But this also means that anyone else can become a project committer based on this baseline. Which I would say isn't a typical baseline. Otherwise, I think Neil
isn't ready yet. And there should be no blocker for making additional contributions.
In any case, I would like to hear some additional thoughts from the other PMC members.
The PMC has the responsibility to verify and check. Providing all the information upfront, makes that a lot easier, and thus most likely faster. If we need to look up this information ourselves, this will take a good amount of time from our spare time
we invest in this, and probably lead to worse results than if you would do it.
> is there a record of Neil's contributions to the ioFog project, as PRs and/or issues?
For the PMC, that is currently not transparent.
Cheers
Jens
On Tue, Nov 29, 2022 at 5:52 AM Kilton Hopkins <kilton@xxxxxxxxxxx> wrote:
Hi, Ian.
I would like to pass this election around again for PMC approval. Neil O'Toole has been a significant contributor (via pull requests) to the Eclipse ioFog code base in the past months. He has fixed several issues in iofog-operator and prepared the code
base for upcoming enhancements.
yes, Neil should contribute a few substantial PRs first before being nominated as a committer so there is a record of work that can be referred to. This is so that all contributors are treated equally.
Thanks,
Ian
On 15/03/2022 23:42, Kilton Hopkins wrote:
Hi, Ian.
Neil has contributed in Eclipse ioFog architecture discussions thus far but has not begun submitting code contributions. He is ready to do that now. He is an employee of Edgeworx so he has been exposed to the process and the existing committers for over
one year now.
If the guidance is that he needs to contribute first via PRs before he can be elected as a committer, then I will guide him to take that path.
Jens Reimann
Principal Software Engineer / R&D Product Middleware
_____________________________________________________________________________
Red Hat GmbH, Registered seat:
Werner-von-Siemens-Ring 12, D-85630 Grasbrunn, Germany
Commercial register: Amtsgericht München/Munich, HRB 153243,
Managing Directors: Ryan Barnhart, Charles Cachera, Michael O'Neill, Amy Ross
Jens Reimann
Principal Software Engineer / R&D Product Middleware
_____________________________________________________________________________
Red Hat GmbH, Registered seat: Werner-von-Siemens-Ring 12, D-85630 Grasbrunn, Germany
Commercial register: Amtsgericht München/Munich, HRB 153243,
Managing Directors: Ryan Barnhart, Charles Cachera, Michael O'Neill, Amy Ross
Jens Reimann
Principal Software Engineer / R&D Product Middleware
_____________________________________________________________________________
Red Hat GmbH, Registered seat: Werner-von-Siemens-Ring 12, D-85630 Grasbrunn, Germany
Commercial register: Amtsgericht München/Munich, HRB 153243,
Managing Directors: Ryan Barnhart, Charles Cachera, Michael O'Neill, Amy Ross