This is an automated email from the ASF dual-hosted git repository.
alamb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/arrow-site.git
The following commit(s) were added to refs/heads/master by this push:
new 5099cf063f4 [Website] Committer expectations and process (#306)
5099cf063f4 is described below
commit 5099cf063f44b1493f0965f0dba826976fe062d3
Author: Andrew Lamb <[email protected]>
AuthorDate: Wed Feb 15 21:50:37 2023 +0100
[Website] Committer expectations and process (#306)
**NOTE** This is a work in progress and does not necessarily represent
the PMC stance yet.
# Rationale
It has come to my attention recently that it may not be clear what
criteria we use to determine if we should invite someone new to be a
committer.
I would like to add some clarity that our project is open to new
contributors, and that if you want to become more deeply involved with
the project, here are the kinds of activities that maintainers do.
Also, I of course want to encourage more people to contribute to our
project, and I hope this will inspire some to do so
# Changes
Add a "Becoming a committer" section to
https://arrow.apache.org/committers/
The content partially came from a discussion on the PMC mailing list,
and I would like to thank @nealrichardson @westonpace and @kou for their
help so far. I also took inspiration from the "Becoming a committer" on
the Spark website: https://spark.apache.org/committers.html
---------
Co-authored-by: Neal Richardson <[email protected]>
Co-authored-by: Sutou Kouhei <[email protected]>
---
committers.md | 51 ++++++++++++++++++++++++++++++++++++++++++++++-----
1 file changed, 46 insertions(+), 5 deletions(-)
diff --git a/committers.md b/committers.md
index cf4b21da998..f2378255d54 100644
--- a/committers.md
+++ b/committers.md
@@ -63,12 +63,12 @@ on important decisions, including releases and inviting
committers to join the P
### Committers
-Contributors who have demonstrated a sustained commitment to the project, not
-only authoring code but also reviewing others' patches and exercising good
-judgment, may be invited by the PMC to become
+Contributors who have demonstrated a sustained commitment to the
+project may be invited by the PMC to become
[committers](https://www.apache.org/foundation/how-it-works.html#committers).
-Committers are authorized to merge code patches to the project and serve as
-non-voting project maintainers.
+Committers are authorized to merge code patches to the project's
+repositories and serve as non-voting project maintainers. See the
+"Becoming a committer" section below for more details.
<table class="table table-striped"><thead>
<tr>
@@ -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 `[email protected]`
+mailing list.
+
+
+[documented here]:
https://cwiki.apache.org/confluence/display/ARROW/Inviting+New+Committers+and+PMC+Members
+[Code of Conduct]: https://www.apache.org/foundation/policies/conduct.html
+[the Apache Way]: https://www.apache.org/theapacheway
