Community & Project Info | Apache Flink
Community & Project Info
How do I get help from Apache Flink?
There are many ways to get help from the Apache Flink community. The
mailing lists
are the primary place where all Flink committers are present. For user support and questions use the
user mailing list
. You can also join the community on
Slack
. Some committers are also monitoring
Stack Overflow
. Please remember to tag your questions with the
apache-flink
tag. Bugs and feature requests can either be discussed on the
dev mailing list
or on
Jira
. Those interested in contributing to Flink should check out the
contribution guide
Mailing Lists
Name
Digest
Unsubscribe
Post
Archive
news
@flink.apache.org
News and announcements from the Flink community
Unsubscribe
Read only list
Archives
community
@flink.apache.org
Broader community discussions related to meetups, conferences, blog posts and job offers
Unsubscribe
Post
Archives
user
@flink.apache.org
User support and questions mailing list
Unsubscribe
Post
Archives
user-zh
@flink.apache.org
User support and questions mailing list
Unsubscribe
Post
Archives
dev
@flink.apache.org
Development related discussions
Unsubscribe
Post
Archives
builds
@flink.apache.org
Build notifications of Flink main repository
Unsubscribe
Read only list
Archives
issues
@flink.apache.org
Mirror of all Jira activity
Unsubscribe
Read only list
Archives
commits
@flink.apache.org
All commits to our repositories
Unsubscribe
Read only list
Archives
Please make sure you are subscribed to the mailing list you are posting to!
If you are not subscribed to the mailing list, your message will either be rejected (dev@ list) or you won't receive the response (user@ list).
How to subscribe to a mailing list
Before you can post a message to a mailing list, you need to subscribe to the list first.
Send an email without any contents or subject to *
listname*-subscribe@flink.apache.org
. (replace
listname
with dev, user, user-zh, ..)
Wait till you receive an email with the subject “confirm subscribe to *
listname*@flink.apache.org
”. Reply to that email, without editing the subject or including any contents
Wait till you receive an email with the subject “WELCOME to *
listname*@flink.apache.org
”.
If you send us an email with a code snippet, make sure that:
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 Flink community on Slack.
After creating an account in Slack, don’t forget to introduce yourself in #introductions.
Due to Slack limitations the invite link expires after 100 invites. If it is expired, please reach out to the
Dev mailing list
Any existing Slack member can also invite anyone else to join.
There are a couple of community rules:
Be respectful
- This is the most important rule!
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.
Use either
#pyflink
(for all Python Flink questions) or
#troubleshooting
(for all other Flink questions).
Please
do not direct message
people for troubleshooting, Jira assigning and PR review. Doing this can result in removal from Slack.
Note
: All messages from public channels in our Slack are
permanently stored and published
in the
Apache Flink Slack archive on linen.dev
. The purpose of this archive is to allow search engines to find past discussions in the Flink Slack.
Stack Overflow
Committers are watching
Stack Overflow
for the
apache-flink
tag.
Make sure to tag your questions there accordingly to get answers from the Flink community.
Issue Tracker
We use Jira to track all code related issues:
You must have a JIRA account in order to log cases and issues.
If you don’t have an ASF JIRA account, you can request one at the
ASF Self-serve portal
All issue activity is also mirrored to the issues mailing list.
Reporting Security Issues
If you wish to report a security vulnerability, please contact
security@apache.org
. Apache Flink follows the typical
Apache vulnerability handling process
for reporting vulnerabilities. Note that vulnerabilities should not be publicly disclosed until the project has responded.
Meetups
There are plenty of meetups on
meetup.com
featuring Flink.
Source Code
Main Repositories
Flink Core Repository
ASF repository:
GitHub mirror:
Flink Docker Repository
ASF repository:
GitHub mirror:
Flink Kubernetes Operator Repository
ASF repository:
GitHub mirror:
Flink CDC Repository
ASF repository:
GitHub mirror:
Flink ML Repository
ASF repository:
GitHub mirror:
Flink Stateful Functions Repository
ASF repository:
GitHub mirror:
Flink Stateful Functions Docker Repository
ASF repository:
GitHub mirror:
Flink Website Repository
ASF repository:
GitHub mirror:
Complete List of Repositories
The complete list of repositories of Apache Flink can be found under
Training
Ververica
currently maintains free Apache Flink training. Their
training website
has slides and exercises with solutions. The slides are also available on
SlideShare
Project Wiki
The Apache Flink
project wiki
contains a range of relevant resources for Flink users. However, some content on the wiki might be out-of-date. When in doubt, please refer to the
Flink documentation
Flink Forward
Flink Forward is a conference happening yearly in different locations around the world. Up to date information about the conference is available on
Flink-Forward.org
People
Please find the most up-to-date list
here
Materials / Apache Flink Logos
The
materials page
offers assets such as the Apache Flink logo in different image formats, or the Flink color scheme.
Want to contribute translation?
Edit This Page