This is an automated email from the ASF dual-hosted git repository.
chaokunyang pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-fury-site.git
The following commit(s) were added to refs/heads/main by this push:
new e847210 add community page (#133)
e847210 is described below
commit e8472103c6d2c1cbec1373c55041b9640c3a45c4
Author: Shawn Yang <[email protected]>
AuthorDate: Thu Jun 13 11:54:58 2024 +0800
add community page (#133)
Add community page:
The content is derived from apache kvrocks community page:
https://kvrocks.apache.org/community/
Closes #131
---
docs/community/community.md | 90 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 90 insertions(+)
diff --git a/docs/community/community.md b/docs/community/community.md
new file mode 100644
index 0000000..6d26c71
--- /dev/null
+++ b/docs/community/community.md
@@ -0,0 +1,90 @@
+---
+title: Community
+sidebar_position: 0
+id: community
+---
+
+
+Apache Fury is a volunteer project and it thrives on the contributions of its
community.
+We invite you to participate as much or as little as you wish. Here are
several ways to contribute:
+
+- Use our project and share feedback.
+- Provide use-cases for the project.
+- Report bugs and contribute fixes.
+- Contribute code and documentation improvements.
+
+## Mailing list
+
+| Name | Desc |
Subscribe | Unsubscribe
| Post |
Archive |
+|-------------------------|---------------------------------------------|-------------------------------------------------------|-----------------------------------------------------------|------------------------------------|-----------------------------------------------------------------------|
+| [email protected] | Development related discussions |
[Subscribe](mailto:[email protected]) |
[Unsubscribe](mailto:[email protected]) |
[Post](mailto:[email protected]) |
[Archive](https://lists.apache.org/[email protected]) |
+| [email protected] | All commits to our repositories |
[Subscribe](mailto:[email protected]) |
[Unsubscribe](mailto:[email protected]) | Read only list
|
[Archive](https://lists.apache.org/[email protected]) |
+
+Please make sure subscribe to any list before attempting to post.
+
+If you are not subscribed to the mailing list, your message will either be
rejected or you won't receive the response.
+
+### How to subscribe to a mailing list
+
+To post messages, subscribe first by:
+
+1. Sending an email to [email protected] with `listname`
replaced accordingly.
+2. Replying to the confirmation email you'll receive, keeping the subject line
intact.
+3. You'll then get a welcome email, and the subscription succeeds.
+
+When discussing code snippets in emails, ensure:
+
+* You do not link to files in external services, as such files can change, get
deleted or the link might break and thus
+ make an archived email thread useless.
+* You paste text instead of screenshots of text.
+* You keep formatting when pasting code in order to keep the code readable.
+* There are enough import statements to avoid ambiguities.
+
+## Slack
+
+You can join
+the [Apache Fury™ community on
Slack](https://join.slack.com/t/fury-project/shared_invite/zt-1u8soj4qc-ieYEu7ciHOqA2mo47llS8A).
+
+There are a couple of community rules:
+
+* Be respectful and nice.
+* All important decisions and conclusions must be reflected back to the
mailing lists. "If it didn't happen on a mailing
+ list, it didn't happen." - The [Apache
Mottos](https://theapacheway.com/on-list/).
+* Use Slack threads to keep parallel conversations from overwhelming a channel.
+* Please do not direct message people for troubleshooting, issue assigning and
PR review. These should be picked-up
+ voluntarily.
+
+## Issue tracker
+
+We use GitHub Issues to track all issues:
+- code related issues: https://github.com/apache/fury/issues
+- website related issues: https://github.com/apache/fury-site/issues
+
+You need to have a [GitHub account](https://github.com/signup) in order to
create issues.
+If you don't have a [GitHub account](https://github.com/signup), you can post
an email to [email protected].
+
+### Bug reports
+
+To report a bug:
+
+* Verify that the bug does in fact exist.
+* Search the [issue tracker](https://github.com/apache/fury/issues) to verify
there is no existing issue reporting the bug you've found.
+* Create a [bug
report](https://github.com/apache/incubator-fury/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml)
on issue tracker.
+* If possible, dive into the source code of fury, and submit a patch for the
bug you reported, this helps ensure the bug
+ will be fixed quickly.
+
+### Reporting a Vulnerability
+
+Apache Fury is a project of the [Apache Software
Foundation](https://apache.org/) and follows the [ASF vulnerability handling
process](https://apache.org/security/#vulnerability-handling).
+
+To report a new vulnerability you have discovered please follow the [ASF
vulnerability reporting
process](https://apache.org/security/#reporting-a-vulnerability), which
explains how to send us details privately.
+
+### Enhancement
+
+Enhancements or new feature proposals are also welcome. The more concrete and
rationale the proposal is, the greater the
+chance it will be incorporated into future releases.
+
+## Source code
+
+* fury core repository: https://github.com/apache/fury
+* fury website repository: https://github.com/apache/fury-site
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
