wehub-resource-sync
84 lines
3.3 KiB
Markdown
84 lines
3.3 KiB
Markdown
---
|
|
id: 'become_committer'
|
|
title: 'Become A Committer'
|
|
sidebar_position: 2
|
|
---
|
|
|
|
<!--
|
|
Licensed to the Apache Software Foundation (ASF) under one or more
|
|
contributor license agreements. See the NOTICE file distributed with
|
|
this work for additional information regarding copyright ownership.
|
|
The ASF licenses this file to You under the Apache License, Version 2.0
|
|
(the "License"); you may not use this file except in compliance with
|
|
the License. You may obtain a copy of the License at
|
|
|
|
https://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
Unless required by applicable law or agreed to in writing, software
|
|
distributed under the License is distributed on an "AS IS" BASIS,
|
|
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
See the License for the specific language governing permissions and
|
|
limitations under the License.
|
|
-->
|
|
|
|
## Become A Committer of Apache HertzBeat
|
|
|
|
Anyone being supportive of the community and working in any of the
|
|
CoPDoC areas can become an Apache HertzBeat™ committer. The CoPDoC is an
|
|
acronym from ASF to describe how we recognize your contributions not
|
|
only by code.
|
|
|
|
- **Community** - You can join us via our mailing list, issue
|
|
trackers, discussions page to interact with community members, and
|
|
share vision and knowledge
|
|
- **Project** - a clear vision and consensus are needed
|
|
- **Documentation** - without it, the stuff remains only in the minds
|
|
of the authors
|
|
- **Code** - discussion goes nowhere without code
|
|
|
|
Apache HertzBeat™ community strives to be meritocratic. Thus, once someone
|
|
has contributed sufficiently to any area of CoPDoC they can be a
|
|
candidate for committer-ship and at last voted in as a HertzBeat
|
|
committer. Being an Apache HertzBeat™ committer does not necessarily mean
|
|
you must commit code with your commit privilege to the codebase; it
|
|
means you are committed to the HertzBeat project and are productively
|
|
contributing to our community's success.
|
|
|
|
## Committer requirements
|
|
|
|
There are no strict rules for becoming a committer or new PMC member.
|
|
Candidates for new committers are typically people that are active
|
|
contributors and community members. Anyway, if the rules can be
|
|
clarified a little bit, it can somehow clear the doubts in the minds
|
|
of contributors and make the community more transparent, reasonable,
|
|
and fair.
|
|
|
|
### Continuous contributions
|
|
|
|
Committer candidates should have a decent amount of continuous
|
|
engagements and contributions (fixing bugs, adding new features,
|
|
writing documentation, maintaining issues boards, code review, or answering
|
|
community questions) to HertzBeat.
|
|
|
|
- 3+ months with activity and engagement.
|
|
- 20+ pr coding, document, test or other contributions.
|
|
|
|
### Quality of contributions
|
|
|
|
- A solid general understanding of the project
|
|
- Well tested, well-designed, following Apache HertzBeat™ coding
|
|
standards, and simple patches.
|
|
- Well-organized and detailed user-oriented documentation.
|
|
|
|
### Community involvement
|
|
|
|
- Be active, courteous, and respectful on the dev mailing list and
|
|
help mentor newer contributors
|
|
and users.
|
|
- Be active, courteous, and respectful on the issue tracker for
|
|
project maintenance
|
|
- Be active, courteous, and respectful for pull requests reviewing
|
|
- Be involved in the design road map discussions with a professional
|
|
and diplomatic approach even if there is a disagreement
|
|
- Promoting the project by writing articles or holding events
|