This is an automated email from the ASF dual-hosted git repository. fenbox pushed a commit to branch build-community in repository https://gitbox.apache.org/repos/asf/incubator-answer-website.git
commit 5e926236dc61b6988ca5b932121988312fb630ea Author: fen <[email protected]> AuthorDate: Fri Nov 24 15:17:16 2023 +0800 docs: update issue labels --- community/about.md | 2 +- community/contributing/issues.md | 16 ++++++++++------ 2 files changed, 11 insertions(+), 7 deletions(-) diff --git a/community/about.md b/community/about.md index 43647f07..55418540 100644 --- a/community/about.md +++ b/community/about.md @@ -19,7 +19,7 @@ Becoming a contributor means you are interested in and contribute to the project ### Committer -Committers have read-write access to the code repository, have signed the Contributor License Agreement (CLA), and have an email address at `@apache.org`. They can directly patch the code or documentation, and the Project Management Committee (PMC) will generally approve these changes by default, or reject them. Of course, the final decision is made by the PMC, not the committer individually. +Committers have read-write access to the code repository, have signed the Contributor License Agreement (CLA), and have an `@apache.org` email address. They can directly patch the code or documentation, and the Project Management Committee (PMC) will generally approve these changes by default, or reject them. Of course, the final decision is made by the PMC, not the committer individually. There's no set timeline or specific code contribution requirement to become a committer, long-term active contributors are typically considered strong candidates. The Apache Software Foundation embraces diverse contributions, so anyone who supports the community and is following the CoPDoC (Contributing to Apache Projects by Doing the Right Thing) is a potential candidate for committership. diff --git a/community/contributing/issues.md b/community/contributing/issues.md index 1fb78ef3..1e1def81 100644 --- a/community/contributing/issues.md +++ b/community/contributing/issues.md @@ -45,9 +45,13 @@ If we think the feature request is a good idea, we'll add it to the roadmap and We use labels to categorize issues. -- `bug`: Issues that are bugs. -- `enhancement`: Issues that are feature requests. -- `good first issue`: Issues that are good for beginners. -- `help wanted`: Issues that are open to help from the community. -- `invalid`: Issues that are invalid. -- `duplicate`: Issues that are duplicates of other issues. +- `bug`: Something isn't working. +- `enhancement`: New feature or request. +- `good first issue`: Good for newcomers. +- `help wanted`: Extra attention is needed, open to help from the community. +- `invalid`: This doesn't seem right. +- `duplicate`: This issue or pull request already exists. +- `security`: This is a security issue. +- `wontfix`: This will not be worked on. +- `question`: Further information is requested. +- `documentation`: Improvements or additions to documentation.
