Skip to content

Commit

Permalink
Restore "attributes of a Beam committer" to prior accuracy
Browse files Browse the repository at this point in the history
  • Loading branch information
kennknowles committed Jan 30, 2025
1 parent 4a09fc4 commit 9a9f338
Show file tree
Hide file tree
Showing 2 changed files with 28 additions and 23 deletions.
44 changes: 24 additions & 20 deletions website/www/site/content/en/contribute/attributes.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: "Attributes of a Beam community member"
title: "Attributes of a Beam committer"
layout: "arrow_template"
---

Expand All @@ -17,29 +17,16 @@ See the License for the specific language governing permissions and
limitations under the License.
-->

# Attributes of a Beam community member
# Attributes of a Beam committer

{{< figure src="/images/community/beam-logo-icon.svg" >}}

## Knows, upholds, and reinforces the Beam community’s practices

- They have a proven commitment to the project
- They share their intentions with the community
- They accept and integrate community feedback in their plans, designs, code, etc.
- They earnestly try to make Beam better with their contributions

In particular, if a code contributor:

- They earnestly try to make Beam better with their own code
- They earnestly try to make Beam better with code review
- They accept and integrate feedback on their code
- They know, follow, and enforce Beam’s practices while reviewing/merging code - style, documentation, testing, backward compatibility, etc.
These are the Beam PMC's expectations for all current and potential committers,
and encouraged for all community members.

{{< figure src="/images/community/messages-icon.svg" >}}

## Knows, upholds, and reinforces the Apache Software Foundation code of conduct

In particular, we manifestly strive to:
In particular, a Beam committer strives to:

- Be open
- Be empathetic
Expand All @@ -50,7 +37,7 @@ In particular, we manifestly strive to:
- Be inquisitive
- Be careful in the words that they choose

[To learn more see the ASF documentation.](https://httpd.apache.org/docs/)
[See the entire Code of Conduct](https://www.apache.org/foundation/policies/conduct)

{{< figure src="/images/community/diamond-icon.svg" >}}

Expand All @@ -63,4 +50,21 @@ In particular, we manifestly strive to:
- They can be trusted to decide when code is ready for release, or when to ask someone else to make the judgment
- They can be trusted to decide when to merge code (if a code contributor) or when to ask someone else to make the judgment

[To learn more see the ASF documentation.](https://httpd.apache.org/docs/)
[To learn more see the ASF documentation.]((https://www.apache.org/dev/committers.html#committer-responsibilities)

{{< figure src="/images/community/beam-logo-icon.svg" >}}

## Knows, upholds, and reinforces the Beam community’s practices

- They have a proven commitment to the project
- They share their intentions with the community
- They accept and integrate community feedback in their plans, designs, code, etc.
- They earnestly try to make Beam better with their contributions

In particular, if a code contributor:

- They earnestly try to make Beam better with their own code
- They earnestly try to make Beam better with code review
- They accept and integrate feedback on their code
- They know, follow, and enforce Beam’s practices while reviewing/merging code - style, documentation, testing, backward compatibility, etc.

7 changes: 4 additions & 3 deletions website/www/site/content/en/contribute/become-a-committer.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,15 +29,16 @@ Everyone is welcome to join and contribute to the project in many ways, not only

{{< contributor/list_with_icons ways_of_contribution >}}

### What are the traits of an Apache Beam committer?
### What are the expectations of an Apache Beam committer?

{{< contributor/row_of_traits committer_traits >}}

### Process
The [PMC](https://www.apache.org/foundation/how-it-works.html#pmc-members)
makes someone a committer via nomination, discussion, and then majority vote.
We use data from as many sources as possible to inform our reasoning. Here are
some examples:
We use data from as many sources as possible to inform our reasoning and
evaluate potential committers against the expectations above. Here are some
examples:

- [dev@ archives](https://lists.apache.org/[email protected])
- [user@ archives](https://lists.apache.org/[email protected])
Expand Down

0 comments on commit 9a9f338

Please sign in to comment.