Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[incubation] How do project committers vote on proposals which affect the projects community?

Hi everyone,

I'm a committer on the Eclipse OMR project [1]. The committers along with the community have discussed (with general agreement) reformatting the entire source code repository using clang-format automation. Given such a change will affect everyone working on the project it falls in the realm of adhering to an official committer vote. We are having trouble finding concrete information of how to properly conduct such a vote.

The Eclipse Project Handbook [2], along with the Eclipse Development Process section 4.7 are the relevant notes we were able to find which say:

> Committers are required to track, participate in, and vote on, relevant discussions in their associated Projects. There are three voting responses: +1 (yes), -1 (no, or veto), and 0 (abstain).

Voting on new committers via the Committer Election process is explicitly stated. However this formatting change we are going to propose is not a Committer Election, so we are not sure how to properly count the committer votes. Does votting on such a matter adhere to the same rules as a Comitter Election? Depending on votes on such a proposal are counted will influence the scope of the proposal itself as one may choose to propose smaller or larger scope changes which may have a higher chance of succeeding, depending on how votes are counted.

Some explicit questions:

1. Does anyone have a reference to some guidance or examples on how such votes should be conducted?
2. Do individual projects have the freedom of establishing a Project Charter which explicitly defines how such votes are to be conducted (similar to the Eclipse IDE Project Charter [3])?
- If so how is such a Charter initially established?


Filip Jeremic

Back to the top