You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: GOVERNANCE.md
+58-14Lines changed: 58 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,17 +7,18 @@ and are approved through consensus by the existing maintainers.
7
7
8
8
### Nomination Protocol
9
9
10
-
#### Submit Nomination
10
+
#### Submit Nomination for a New Maintainer or Role
11
11
12
-
The candidate or an existing maintainer creates
13
-
a [maintainer nomination issue](.github/ISSUE_TEMPLATE/maintainer_nominate.yaml)
14
-
and submits a pull request (PR) to modify the `MAINTAINERS.md`
15
-
or `ADVISORS.md` file to add the nominee.
12
+
The candidate or an existing maintainer creates a [maintainer nomination issue](.github/ISSUE_TEMPLATE/maintainer_nominate.yaml) and submits a pull request (PR) to update the `MAINTAINERS.md`
13
+
or `ADVISORS.md` file by adding the nominee or reflecting the new role.
16
14
17
15
#### Voting
18
16
19
-
The PR requires approval from **at least three maintainers**,
20
-
including the nominator if they are not self-nominating.
17
+
The PR requires approval from **at least three maintainers**.
18
+
19
+
For self-nominations, all three approvals must come from other maintainers.
20
+
21
+
For nominations by existing maintainers, the nominator's approval counts toward the three required.
21
22
Maintainers indicate their approval by approving on the PR.
22
23
23
24
#### Approval and Merge
@@ -28,6 +29,48 @@ If the nominee is not yet added as a maintainer to the repository,
28
29
they should be added at this point,
29
30
officially confirming their maintainer status.
30
31
32
+
### Active Maintainer Definition
33
+
34
+
An **active maintainer** is a contributor who demonstrates ongoing commitment
35
+
to the Kepler project through regular participation and meaningful contributions.
36
+
Active maintainers are listed in the [`MAINTAINERS.md`](https://github.com/sustainable-computing-io/kepler/blob/main/MAINTAINERS.md)
37
+
file to provide users with a reliable point of contact for project-related questions,
38
+
support, and collaboration.
39
+
40
+
Active maintainer will be reviewed on a 6-month cycle.
|**Fall**| October 1 – March 31 | August 1 – September 30 |
45
+
|**Spring**| April 1 – September 30 | February 1 – March 31 |
46
+
47
+
- Active maintainers are expected to maintain engagement during each cycle by providing tangible contributions in accordance with the [Active Engagement Expectations](#active-engagement-expectations).
48
+
- A designated person responsible for maintaining the maintainer list will create an issue during each review period to propose changes based on observed activity. This issue will remain open throughout the window, giving maintainers the opportunity to review and confirm their status.
49
+
- Maintainers who are not included in the proposed active list may respond or rebut (i.e., provide justification or recent contributions) to remain on the list.
50
+
- Maintainers who do not confirm their active status during the review period will be moved to the **Emeritus** list.
51
+
-**Emeritus maintainers** can return to active status in a future cycle by reaffirming their commitment to active participation.
52
+
53
+
This lightweight process helps streamline contributor engagement while maintaining an up-to-date and representative list of active maintainers.
54
+
55
+
#### Active Engagement Expectations
56
+
57
+
To help maintain a healthy and transparent governance process, the following example metrics can be used to demonstrate active involvement over a 6-month cycle. These are **guidelines**, not strict requirements:
58
+
59
+
- Volunteering for specific operational tasks such as:
60
+
- Hosting community meetings
61
+
- Triage and issue management
62
+
- Release coordination or management
63
+
- Triage and response to community questions in Slack channels
64
+
- Attending **more than 25% of community meetings** (e.g., at least 4 out of 12 calls within a cycle)
65
+
- Actively participating in **more than 3 triaged issues** (e.g., raising, commenting on, or resolving issues)
66
+
- Completing **more than 3 pull request reviews**
67
+
- Actively promoting the Kepler project in the community, such as:
68
+
- Organizing a meetup
69
+
- Writing a blog post
70
+
- Giving a talk or presentation at an event
71
+
72
+
These metrics support transparency in participation and help ensure that active maintainers remain engaged and accountable to the community.
73
+
31
74
## Maintainers
32
75
33
76
Maintainers are responsible for the overall health and progress of the project.
@@ -47,13 +90,13 @@ Their roles and responsibilities are organized into functional areas:
47
90
48
91
### 2. Technical Committee
49
92
50
-
- Oversee the overall direction of the Kepler project.
93
+
- Oversee the overall direction of the Kepler project
51
94
- Provide guidance for the project maintainers and the onboarding process for
52
-
new maintainers.
53
-
- Actively engage in the technical committee meetings.
95
+
new maintainers
96
+
- Actively engage in the technical committee meetings
54
97
- Participate in design and technical discussions
55
-
- Review and approve pull requests,
56
-
especially those involving significant technical changes or core areas
98
+
- Review and approve pull requests involving significant technical changes,
0 commit comments