Skip to content

Commit ee601b8

Browse files
committed
MAINTAINERS_GUIDE: rm chief maintainer role
Since Michael Crosby is stepping down, and we don't want to nominate someone else to be a chief maintainer, let's remove the position. Signed-off-by: Kir Kolyshkin <[email protected]>
1 parent d6563f6 commit ee601b8

File tree

1 file changed

+3
-20
lines changed

1 file changed

+3
-20
lines changed

MAINTAINERS_GUIDE.md

Lines changed: 3 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -70,19 +70,6 @@ Overall the maintainer system works because of mutual respect across the
7070
maintainers of the project. The maintainers trust one another to make decisions
7171
in the best interests of the project. Sometimes maintainers can disagree and
7272
this is part of a healthy project to represent the point of views of various people.
73-
In the case where maintainers cannot find agreement on a specific change the
74-
role of a Chief Maintainer comes into play.
75-
76-
The Chief Maintainer for the project is responsible for overall architecture
77-
of the project to maintain conceptual integrity. Large decisions and
78-
architecture changes should be reviewed by the chief maintainer.
79-
The current chief maintainer for the project is Michael Crosby (@crosbymichael).
80-
81-
Even though the maintainer system is built on trust, if there is a conflict
82-
with the chief maintainer on a decision, their decision can be challenged
83-
and brought to the technical oversight board if two-thirds of the
84-
maintainers vote for an appeal. It is expected that this would be a
85-
very exceptional event.
8673

8774

8875
### How are maintainers added?
@@ -97,9 +84,8 @@ Just contributing does not make you a maintainer, it is about building trust
9784
with the current maintainers of the project and being a person that they can
9885
depend on and trust to make decisions in the best interest of the project. The
9986
final vote to add a new maintainer should be approved by over 66% of the current
100-
maintainers with the chief maintainer having veto power. In case of a veto,
101-
conflict resolution rules expressed above apply. The voting period is
102-
five business days on the Pull Request to add the new maintainer.
87+
maintainers. The voting period is five business days on the Pull Request
88+
to add the new maintainer.
10389

10490

10591
### What is expected of maintainers?
@@ -111,10 +97,7 @@ issues where they are pinged. Being a maintainer is a time consuming commitment
11197
not be taken lightly.
11298

11399
When a maintainer is unable to perform the required duties they can be removed with
114-
a vote by 66% of the current maintainers with the chief maintainer having veto power.
100+
a vote by 66% of the current maintainers.
115101
The voting period is ten business days. Issues related to a maintainer's performance should
116102
be discussed with them among the other maintainers so that they are not surprised by
117103
a pull request removing them.
118-
119-
120-

0 commit comments

Comments
 (0)