Skip to main content

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​

NameDescSubscribeUnsubscribePostArchive
dev@fury.apache.orgDevelopment related discussionsSubscribeUnsubscribePostArchive
commits@fury.apache.orgAll commits to our repositoriesSubscribeUnsubscribeRead only listArchive

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 listname-subscribe@fury.apache.org 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.

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.
  • 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:

You need to have a GitHub account in order to create issues. If you don't have a GitHub account, you can post an email to dev@fury.apache.org.

Bug reports​

To report a bug:

  • Verify that the bug does in fact exist.
  • Search the issue tracker to verify there is no existing issue reporting the bug you've found.
  • Create a bug report 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 and follows the ASF vulnerability handling process.

To report a new vulnerability you have discovered please follow the ASF vulnerability reporting process, 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​