kou commented on code in PR #306:
URL: https://github.com/apache/arrow-site/pull/306#discussion_r1103737824
##########
committers.md:
##########
@@ -86,3 +86,44 @@ non-voting project maintainers.
{% endif %}
{% endfor %}
</tbody></table>
+
+### **Becoming a committer**
+
+There are many ways to
[contribute](https://arrow.apache.org/docs/developers/contributing.html)
+to the Apache Arrow project, including issue reports,
+documentation, tests, and code. Contributors with sustained, high-quality
activity
+may be invited to become committers by the PMC
+as a recognition of their sustained
+contribution to the project. A committer can commit
+changes directly in all Arrow github repositories, and have the significant
responsibility
Review Comment:
```suggestion
changes directly in all Arrow GitHub repositories, and have the significant
responsibility
```
##########
committers.md:
##########
@@ -86,3 +86,44 @@ non-voting project maintainers.
{% endif %}
{% endfor %}
</tbody></table>
+
+### **Becoming a committer**
+
+There are many ways to
[contribute](https://arrow.apache.org/docs/developers/contributing.html)
+to the Apache Arrow project, including issue reports,
+documentation, tests, and code. Contributors with sustained, high-quality
activity
+may be invited to become committers by the PMC
+as a recognition of their sustained
+contribution to the project. A committer can commit
+changes directly in all Arrow github repositories, and have the significant
responsibility
+of using their status and access to improve the Arrow project
+for the entire community.
+
+When considering to invite someone to be a committer, the PMC looks for
+contributors who are doing the work and exercising the judgment expected
+of a committer already. After all, any contributor can do all of the things a
+committer does except for merge a PR. While there is no set list of
+requirements, nor a checklist that entitles one to commit privileges,
+typical behaviors include:
+
+* Contributions beyond pull requests, such as reviewing other pull requests,
+ fixing bugs and documentation, triaging issues, answering community
+ questions, improving usability, reducing technical debt, helping
+ with CI, verifying releases, debugging in strange environments, etc.
+
+* These contributions to the project should be consistent in quality
+ and sustained over time, typically on the order of 6 months or more.
+
+* Assistance growing the size and health of the community via
+ constructive, respectful, and consensus driven interactions, as
+ described in our [Code of Conduct] and [the Apache Way].
+
+The mechanics of how the process works is [documented here]. If you
+feel you should be offered committer privileges, but have not been,
+you can reach out to one of the PMC members or the private at arrow
+dot apache dot org mailing list.
Review Comment:
I think that we don't need to care about spam for `[email protected]`
because the e-mail address is public.
```suggestion
you can reach out to one of the PMC members or the `[email protected]`
mailing list.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
