Re: [che4z-dev] Committer Elections

[Lukas Zima <lukas.zima@xxxxxxxxxxxx>]

Hi Wayne,

thank you for your valid comments.

We have reviewed the nominee process and had a team discussion about our further nominations. For the future, we will nominate only significant contributors so that we can provide a sufficient demonstration of the merit.

We will be happy for any additional feedback.

Lukas Zima

Product Owner  | Eclipse plug-ins | Eclipse Che

Broadcom

 

CA CZ, s.r.o. | V Parku 2316/12 | Prague 4 Chodov, 148 00 | Czech Republic
Office: +420226221317 | Mobile: +420723433205 | Lukas.Zima@xxxxxxxxxxxx

On Mon, Mar 23, 2020 at 9:59 PM Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx> wrote:

Greetings Eclipse Che4z project team.

I've observed a handful of recent committer elections have been started with insufficient demonstrations of merit.

According to the Eclipse Development Process, a person may be appointed as a committer following a demonstration of merit. Typically a demonstration of merit takes the form of a handful of high quality contributions to the project. Whatever form they take, there must be a public record.

Additionally, employment status is irrelevant. It doesn't matter if your company has hired or reassigned somebody to fill the role, what matters is their contribution record. Don't cite the company that they work for or the vendor product that they've been assigned to (you don't need to hide this information, it's not not relevant).

Further, whether or not somebody is needed is also irrelevant in a committer election. If they're needed, then they can make a small number of pull requests to demonstrate that they also know the process.

Finally, "I like this person" is not a sufficient merit statement. You may know the person and your colleagues within your organization may now the person, but the community as a whole does not.

As part of being an open source project, you also need to be transparent and open about how people become committers. The playing field must, as they say, be level: anybody else who shows up to participate in the project will need to demonstrate to the team that they deserve to be a committer in a public manner, so should your colleagues.

You don't need to be a committer to contribute. If you need for somebody to become a committer, get them to make contributions (pull requests) to the project to demonstrate--both to the team and to the community--that they understand the project code, the Eclipse Development Process, and the Eclipse IP Due Diligence process. All committers must be familiar with all of those things.

There is more information in the handbook (and here).

I have removed the committer elections for Anton Grigorev and Vit Gottwald. Restart those elections when you can cite contributions to the Eclipse Che4z project.

Stating that Adam Šmelko and Marcel Hruška are original authors should likely be sufficient, but I'll leave that to the discretion of the PMC.

Thanks,

Wayne

--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

_______________________________________________
che4z-dev mailing list
che4z-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/che4z-dev