Hi Ted,
This is a great question. There are usually bi-weekly sync meetings to
discuss plans and progress for the next Flink release. For example, there
was a regular one for the Flink 1.15 release [1]
I do see some things that we could improve on as a Flink community. For
example, there are quite a large number of open PRs. PRs don't always get a
review or get merged. I'm hearing from other contributors that they need to
ping people in order to get attention for their PR. Some PRs are of poor
quality, because they don't adhere to the code contribution guide. I can
imagine that newly interested contributors don't know exactly where to
start.
I see other open source projects who indeed run a public Slack channel,
like Apache Airflow [2]. Kubernetes actually has a triage team and
processes documented [3].
I'm curious what other Users and Dev'ers think. What are some of the
problems that you're currently experiencing and how do you think we could
improve/solve those?
Best regards,
Martijn Visser
https://twitter.com/MartijnVisser82
https://github.com/MartijnVisser
[1] https://cwiki.apache.org/confluence/display/FLINK/1.15+Release
[2] https://airflow.apache.org/community/ (Under "Ask a question")
[3]
https://github.com/kubernetes/community/blob/master/sig-contributor-experience/triage-team/triage.md
On Thu, 31 Mar 2022 at 23:44, Hao t Chang wrote:
> Hi,
>
>
>
> I have been looking into Flink and joined the mailing lists recently. I am
> trying to figure out how the community members collaborate. For example, is
> there Slack channels or Weekly sync up calls where the community members
> can participate and talk with each other to brainstorm, design, and make
> decisions?
>
>
>
> Ted
>
