bullet03 commented on a change in pull request #17136:
URL: https://github.com/apache/beam/pull/17136#discussion_r833468936
##########
File path: website/www/site/content/en/contribute/_index.md
##########
@@ -24,366 +24,177 @@ See the License for the specific language governing
permissions and
limitations under the License.
-->
-# Contribution guide
-
-<a class="arrow-list-header" data-toggle="collapse" href="#collapseOverview"
role="button" aria-expanded="false" aria-controls="collapseOverview">
- {{< figure src="/images/arrow-icon_list.svg">}}
-
-## Overview
-
-</a>
-
-<div class="collapse dont-collapse-sm" id="collapseOverview">
-
-There are lots of opportunities to contribute. You can for example:
-
-- ask or answer questions on [[email protected]](/community/contact-us/) or
-[stackoverflow](https://stackoverflow.com/questions/tagged/apache-beam)
- - review proposed design ideas on
[[email protected]](/community/contact-us/)
- - improve the documentation
- - file [bug reports](https://issues.apache.org/jira/projects/BEAM/issues)
- - test releases
- - review [changes](https://github.com/apache/beam/pulls)
- - write new examples
- - improve your favorite language SDK (Java, Python, Go, etc)
- - improve specific runners (Apache Flink, Apache Spark, Google
- Cloud Dataflow, etc)
- - improve or add IO connectors
- - add new transform libraries (statistics, ML, image processing, etc)
- - work on the core programming model (what is a Beam pipeline and how does it
- run?)
- - improve the developer experience (for example, Windows guides)
- - add answers to the [contribution FAQ](
- https://cwiki.apache.org/confluence/display/BEAM/Contributor+FAQ)
- - organize local meetups of users or contributors to Apache Beam
-
+# Contribute to Apache Beam
+
+Apache Beam is an open source project developed and maintained by a friendly
community of users, contributors, committers, and project management committee
(PMC) members.
+
+Everyone is welcome to join and contribute to the project in multiple ways,
not only with code contributions. Contributions like asking questions,
reporting bugs, proposing new features, improving documentation, adding to the
website, organizing events, or writing blog posts among other contributions,
are welcome and recognized.
+
+### What’s In It for You?
+ - Become a part of the world’s largest, most welcoming open source community
+ - Drive innovation for next-gen distributed data processing
+ - Make an impact by bringing advanced technology solutions into reality
+ - Empower your brand recognition and thought leadership in the data world
+
+### Ways You Can Contribute
+
+Here’s a list of things you can do to get started contributing:
+
+<table class="table table-bordered">
+ <tr>
+ <th>Contribution</th>
+ <th>How to do it</th>
+ </tr>
+ <tr>
+ <td>Participate and share ideas</td>
+ <td class="list-text-size-md">
+ <ol>
+ <li>Start by <a
href="https://beam.apache.org/contribute/#accounts-and-permissions";>getting an
Apache Beam Jira account</a>.</li>
+ <li>Subscribe to our <a
href="https://beam.apache.org/community/contact-us/";>mailing lists</a> (<a
href="mailto:[email protected]";>[email protected]</a> and <a
href="mailto:[email protected]";>[email protected]</a>).</li>
+ <li>Stay in the loop of our <a
href="https://issues.apache.org/jira/projects/BEAM/issues";>Jira product
backlog</a>, participate in discussions to brainstorm solutions, and help the
community solve their mailing list questions.</li>
+ </ol>
+ </td>
+ </tr>
+ <tr>
+ <td>File a bug</td>
+ <td class="list-text-size-md">
+ <ol class="no-bullet">
+ <li>Create a Jira ticket and mark it as a bug</li>
+ <br><span>OR</span><br><br>
+ <li>Send an email to <a
href="mailto:[email protected]";>[email protected]</a> with subject: [Bug]
<bug summary> and include as much detail as possible.</li>
+ </ol>
+ </td>
+ </tr>
+ <tr>
+ <td>Propose a feature</td>
+ <td class="list-text-size-md">
+ <ol class="no-bullet">
+ <li>Create a Jira ticket and mark it as a feature request</li>
+ <br><span>OR</span><br><br>
+ <li>Send an email to <a
href="mailto:[email protected]";>[email protected]</a> with subject:
[Feature Proposal] <your idea>.</li>
+ </ol>
+ </td>
+ </tr>
+ <tr>
+ <td>Improve documentation</td>
+ <td>
+ Click the edit icon in our documentation and it’ll take you to our <a
href="https://github.com/apache/beam/";>GitHub</a>, where you can automatically
make the change you want and send a Pull Request.
+ </td>
+ </tr>
+ <tr>
+ <td>Improve the website</td>
+ <td class="list-text-size-md">
+ <ul>
+ <li>Follow the website <a
href="https://beam.apache.org/contribute/";>Contribution Guide</a> to make
changes yourself.</li>
+ <li>Check our <a
href="https://issues.apache.org/jira/browse/BEAM-13229?jql=project%20%3D%20BEAM%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20%3D%20website%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC";>Website
Backlog</a> in Jira to find rooms for improvement areas, or propose one.</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td>Write a blogpost</td>
+ <td>
+ Tell a story about your custom use cases or share your recommendations
and best practices.
+ </td>
+ </tr>
+ <tr>
+ <td>Share your success story</td>
+ <td>
+ Visit our <a href="https://beam.apache.org/case-studies/";>Case
Studies</a> page and share your story or add your company’s logo.
+ </td>
+ </tr>
+ <tr>
+ <td>Produce a social media publication</td>
+ <td>
+ Share the use cases that Beam helps empower or the data processing
performance you achieved. Spread the word about the upcoming Beam Summits and
conferences.
+ </td>
+ </tr>
+ <tr>
+ <td>Organize an event</td>
+ <td>
+ Send an email to <a
href="mailto:[email protected]";>[email protected]</a> to share your idea
about the Beam event you want to organize.
+ </td>
+ </tr>
+ <tr>
+ <td>Build a new feature like a new IO connector or PTransform</td>
+ <td class="list-text-size-md">
+ <ul>
+ <li>Create and contribute a custom <a
href="https://beam.apache.org/documentation/programming-guide/#pipeline-io";>I/O
connector</a> for a specific data storage system you want to connect to, if it
is not on <a href="https://beam.apache.org/documentation/io/built-in/";>the I/O
list yet</a>.</li>
+ <li>Look at our project backlog to get some inspiration on what to
build.</li>
+ <li>Follow our <a href="https://beam.apache.org/contribute/";>Code
Contribution Guide</a>.</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td>Share a code sample or template</td>
+ <td class="list-text-size-md">
+ <ol>
+ <li>Read our <a href="https://beam.apache.org/contribute/";>Code
Contribution Guide</a>.</li>
+ <li>Create your code sample or template. </li>
+ <li><a
href="https://beam.apache.org/contribute/#make-your-change";>Make a Pull
Request</a> to add it to the Beam example folder.</li>
+ </ol>
+ </td>
+ </tr>
+ <tr>
+ <td>Test a release candidate</td>
+ <td>
+ Anybody can <a
href="https://beam.apache.org/contribute/release-guide/";>propose a release</a>
via the [email protected] mailing list. Try Apache Beam releases in your
projects, vote for release candidates, inform the community about the results
and any issues found via <a
href="mailto:[email protected]";>[email protected]</a>. Learn more about
how to validate a Beam release <a
href="https://beam.apache.org/blog/validate-beam-release/";>here</a>.
+ </td>
+ </tr>
+ <tr>
+ <td>Other ideas?</td>
+ <td>
+ If you want to contribute in another way and you’re not sure how to get
started, send a proposal to <a
href="mailto:[email protected]";>[email protected]</a>.
+ </td>
+ </tr>
+</table>
+
+
+## Become a Committer
+
+If you like contributing to Apache Beam, you are active in the Apache Beam
mailing lists, Slack channel, or you attend/organize events, then you are a
candidate to become a project committer.
+
+Committers are community members that have write access to the project’s
repositories (i.e., they can modify the code, documentation, and website by
themselves and also assist with code reviews and accept other contributions).
+
+Even though there is no strict protocol to become a committer, the most
important thing we look for is that you display the traits of an Apache Beam
committer and that you have been consistently contributing to the project and
community.
+
+Candidates for new committers are suggested by current committers or PMC
members, and voted upon by the PMC team. So if you would like to become a
committer, engage with the community and keep contributing to Apache Beam, you
might also want to talk to other committers and ask for their advice and
guidance. Feel free to email any committer directly and ask for their advice!
+
+## The Traits of an Apache Beam Committer
+
+{{< contributor/row_of_traits committer_traits >}}
+
+## Become a Project Management Committee (PMC) Member
+
+The PMC is the official managing body of the project as per the Apache
Software Foundation governance model: “The Apache Way”. PMC members vote to set
Apache Beam’s community and technical direction and are directly responsible
for overseeing releases and the healthy development of the community.
+
+PMC members are also responsible for ensuring their project follows certain
core requirements set by the board or other corporate officers of the ASF, like
following Legal, Branding, and Infrastructure related requirements, along with
ensuring their community operates within the [ASF Code of
Conduct](https://www.apache.org/foundation/policies/conduct#code-of-conduct).
+
+Since the PMC members are responsible for establishing the Apache Beam vision
and leading our community to work in harmony to achieve it, we look for
committed individuals who can perform the responsibilities of the PMC, as well
as lead our community to fulfill its vision. This is why we strive to build a
diverse PMC that complements skills and expertise sharing the same sets of
values.
+
+Ideally, we find candidates among active community members that have shown
initiative to shape the direction of Beam and have shown willingness to learn
the official processes, such as how to create or verify for releases, how to
ensure trademark compliance for events, among others. We also expect PMC
candidates to be level-headed, constructive, supportive, and willing to
“disagree and commit” at times.
+
+A PMC member is also a committer, so if they are not initiated already, they
will automatically become committers when joining the PMC. Therefore, the
traits of Apache Beam committers also apply to PMC members.
+
+## Hear from the Community
+
+“Knowledge sharing and collaboration is something that comes naturally in the
community. Together, we can work with the most complex problems and just solve
them.”
+<div class="contribute-quote-block">
+ <span>Matt Casters, Co-founder @ Apache Hop</span>
+ <img src="https://beam.apache.org/images/matt_casters_photo.png"; alt="Matt
Casters">
</div>
Review comment:
done
--
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]
![https://beam.apache.org/images/matt_casters_photo.png"](https://beam.apache.org/images/matt_casters_photo.png"){kind=link}