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
+65-1Lines changed: 65 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,9 +25,73 @@ The ModelPack project leadership embraces the following values:
25
25
26
26
-**Participation**: Responsibilities within the project are earned through participation, and there is a clear path up the contributor ladder into leadership positions.
27
27
28
+
## Membership and Contributor Ladders
29
+
30
+
The ModelPack project is a community-driven open source project. We welcome contributions from anyone who shares our values and wants to help us achieve our mission. Below we lay out the different contributor roles in the ModelPack project, detailing the responsibilities, qualifications, and perks that come with each one.
31
+
32
+
| Role | Responsibilities | Qualifications | Privileges |
|**Contributor**| Follow our Code of Conduct & Contribution Guide | Anyone who participates in the community | Can be assigned issues and request reviews |
35
+
|**Reviewer**| Review PRs in your area of expertise and maintain quality | A Contributor with a solid track record of high-quality reviews | Approve PRs in specific areas and recommend others for Reviewer status |
36
+
|**Maintainer**| Merge PRs, coordinate releases, and help shape the project's direction | Long-term contributions, leadership, and a deep understanding of the project | Merge code, represent the project publicly, and nominate new Maintainers |
37
+
38
+
### Contributor
39
+
40
+
A **Contributor** is anyone who adds value to the project. This can be through code, but it doesn't have to be! This role is often where new or occasional contributors start.
41
+
42
+
-**Responsibilities**:
43
+
44
+
- Follow the project's [Code of Conduct](code-of-conduct.md).
45
+
- Stick to the [Contribution Guide](CONTRIBUTING.md).
46
+
47
+
-**Qualifications**:
48
+
49
+
- Open to anyone who wants to be part of the community.
50
+
- Contributions can include things like:
51
+
- Joining in on community discussions.
52
+
- Reporting bugs or giving feedback.
53
+
- Testing new releases and sharing your thoughts.
54
+
- Helping out with documentation.
55
+
- Attending or speaking at community events.
56
+
- Submitting pull requests (PRs).
57
+
- Helping other users or answering questions.
58
+
- Spreading the word about the project.
59
+
60
+
-**Privileges**:
61
+
- You can be assigned to issues and ask for reviews on your contributions.
62
+
63
+
### Reviewer
64
+
65
+
A **Reviewer** is a Contributor who takes ownership of a specific part of the project (like code, docs, or tests). They play a key role in keeping our quality high by reviewing and approving changes in their area.
66
+
67
+
-**Responsibilities**:
68
+
69
+
- Regularly review PRs in your area of expertise.
70
+
- Make sure changes meet our coding standards, don't introduce bugs, and are good for the project.
71
+
- Help other contributors become Reviewers.
72
+
- Help triage issues.
73
+
74
+
-**Qualifications**:
75
+
76
+
- You must already be a Contributor.
77
+
- Proven track record of high-quality reviews and contributions.
78
+
- Deep understanding of your specific area.
79
+
- Commitment to maintaining responsibility for your designated area.
80
+
- Supportive of new and occasional contributors, helping refine PRs for merging.
81
+
82
+
-**Privileges**:
83
+
84
+
- You'll have GitHub permissions to approve PRs and manage labels in your specific areas.
85
+
- You can recommend and review other Contributors for the Reviewer role.
86
+
87
+
-**How to Become a Reviewer**:
88
+
89
+
1. Submit an issue to the community repository to request for becoming a reviewer, with a list of your contribution and specific area of expertise.
90
+
2. Get approval from at least two existing Maintainers.
91
+
28
92
## Maintainers
29
93
30
-
ModelPack maintainers have write access to the project repositories in [the ModelPack GitHub organization](https://github.com/modelpack/). They can merge patches and are expected to review large or critical patches personally. The current maintainers can be found in [MAINTAINERS.md](./MAINTAINERS.md). Maintainers collectively manage the project's resources and contributors. Additional supplementary repositories can include a separate list of maintainers (such as for tools etc) which are not part of the primary ModelPack project maintainers.
94
+
Maintainers have write access to the project repositories in [the ModelPack GitHub organization](https://github.com/modelpack/). They can merge patches and are expected to review large or critical patches personally. The current maintainers can be found in [MAINTAINERS.md](./MAINTAINERS.md). Maintainers collectively manage the project's resources and contributors. Additional supplementary repositories can include a separate list of maintainers (such as for tools etc) which are not part of the primary ModelPack project maintainers.
31
95
32
96
This privilege is granted with some expectation of responsibility: maintainers are people who care about the ModelPack project and want to help it grow and improve. A maintainer is not just someone who can make changes, but someone who has demonstrated good judgement and an ability to collaborate with the team, get the most knowledgeable people to review code and docs, contribute high-quality code, and follow through to fix issues (in code or tests).
0 commit comments