You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@answer.apache.org by fe...@apache.org on 2023/11/24 07:23:27 UTC
(incubator-answer-website) branch build-community updated (83a0947f -> 68347ca9)
This is an automated email from the ASF dual-hosted git repository.
fenbox pushed a change to branch build-community
in repository https://gitbox.apache.org/repos/asf/incubator-answer-website.git
from 83a0947f fix: use className replace classs
new 5e926236 docs: update issue labels
new 68347ca9 docs: add open source guides
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
community/about.md | 2 +-
community/contributing/contributing.md | 7 ++++++-
community/contributing/issues.md | 16 ++++++++++------
3 files changed, 17 insertions(+), 8 deletions(-)
(incubator-answer-website) 02/02: docs: add open source guides
Posted by fe...@apache.org.
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 68347ca9355138add02fb5f4fafd922684d78f38
Author: fen <f3...@gmail.com>
AuthorDate: Fri Nov 24 15:23:17 2023 +0800
docs: add open source guides
---
community/contributing/contributing.md | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/community/contributing/contributing.md b/community/contributing/contributing.md
index da31275c..1b48aaf0 100644
--- a/community/contributing/contributing.md
+++ b/community/contributing/contributing.md
@@ -4,7 +4,12 @@ slug: /contributing
# Contributing
-> Thanks for your interest in contributing to Answer!
+Thanks for your interest in contributing to Apache Answer, hopefully, this document makes the process for contributing clear.
+
+The [Open Source Guides](https://opensource.guide/) website has a collection of resources for individuals, communities, and companies who want to learn how to run and contribute to an open source project. Contributors and people new to open source alike will find the following guides especially useful:
+
+- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
+- [Building Welcoming Communities](https://opensource.guide/building-community/)
## Code of conduct
(incubator-answer-website) 01/02: docs: update issue labels
Posted by fe...@apache.org.
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 <f3...@gmail.com>
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.