-
Notifications
You must be signed in to change notification settings - Fork 984
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[improve] home add apache info (#1740)
Signed-off-by: tomsun28 <tomsun28@outlook.com> Co-authored-by: tomsun28 <tomsun28@outlook.com>
- Loading branch information
1 parent
c4d1512
commit bb55caf
Showing
47 changed files
with
5,822 additions
and
428 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,84 @@ | ||
| --- | ||
| 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 PPMC 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 either by contributing to the codebase | ||
| of the main website or HertzBeat's GitHub repositories. | ||
|
|
||
| - +3 months with light activity and engagement. | ||
| - +2 months of medium activity and engagement. | ||
| - +1 month with solid activity and engagement. | ||
|
|
||
| ### 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 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,84 @@ | ||
| --- | ||
| id: 'become_pmc_member' | ||
| title: 'Become A PMC member' | ||
| sidebar_position: 3 | ||
| --- | ||
|
|
||
| <!-- | ||
| 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 PMC member of Apache HertzBeat | ||
|
|
||
| Anyone being supportive of the community and working in any of the | ||
| CoPDoC areas can become an Apache HertzBeat PMC member. 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 PMC membership and at last voted in as a HertzBeat | ||
| PMC member. Being an Apache HertzBeat PMC member 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. | ||
|
|
||
| ## PMC member requirements: | ||
|
|
||
| There are no strict rules for becoming a committer or PPMC member. | ||
| Candidates for new PMC member 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 | ||
|
|
||
| PMC member 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 either by contributing to the codebase | ||
| of the main website or HertzBeat's GitHub repositories. | ||
|
|
||
| - +5 months with light activity and engagement. | ||
| - +4 months of medium activity and engagement. | ||
| - +3 month with solid activity and engagement. | ||
|
|
||
| ### 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 |
Oops, something went wrong.