You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by David Radley <da...@uk.ibm.com> on 2025/10/10 16:21:58 UTC

Community Health Initiative update

Hi,
We are coming up for a year of the Community Health Initiative [1]. With goals of

  *   High level, remove the need for the workgroup and run as BAU
  *   Improve new contributor experience by getting prompt responses to issues and PRs, such that PRs are merged in a timely manner.
  *   Pragmatically address unmerged PR backlog considering
  *   Recent ones (to stay on top of incoming PRs and helping new contributors)
  *   High /critical blocking ones
  *   One that just should be merged.
  *   Pragmatically address issue backlog, especially criticals and blockers
  *   Assumption – all communications go through the dev list.

The main participants were @Tom Cooper<ma...@tomcooper.dev>, myself and @Robert Metzger<ma...@apache.org>. Tom is no longer working with Flink.

The achievements of the workgroup have been:

  *
 Tom and I have been reviewing Flink PRs, starting from the latest.
  *
Regular PR triaging in weekly meetings.
  *
Massively reducing the PR backlog by introducing the stale Github action. When we started last year, we had 1181 open PRs on the Flink repo, 1030 of them had not been reviewed. We now have 208 open PRs, 200 have not been reviewed and 8 are stale. We seemed to have reached a steady state around 200; which is much more manageable.
  *
To encourage and recognise more reviewing by non-committers we added the 2 community review labels.
  *
We added Github action to label PRs with the targeted branch, so it is easy to see back ports in the list of PRs.
  *
We produced list of the LGTM PRs and straightforward merges that Robert and other committers have merged.
  *
We discussed on going issues, potential ideas around improving the community health as detailed in the minutes.

I have very much enjoyed leading this workgroup and am happy to continue if there is support for it, as I am a big believer in the Apache way and community over code. If anyone would like to actively join this workgroup, please let me know, we have been meeting on Teams every week. If I do not hear anything within the next week,  then I will stop the weekly meetings and resurrect when the community has the appetite for it.

Either way I intend to continue reviewing PRs and be involved/support/own community health improvements; any feedback is welcome.

     Kind regards and thanks for your support over the past year, David.

[1] https://cwiki.apache.org/confluence/display/FLINK/Community+Health+Initiative+%28CHI%29+workgroup





Unless otherwise stated above:

IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: Building C, IBM Hursley Office, Hursley Park Road, Winchester, Hampshire SO21 2JN

Re: Community Health Initiative update

Posted by Xeno Amess <xe...@gmail.com>.
I don't know if it good to say it here but several sub-repos are actually
nearly archived..
For example https://github.com/apache/flink-connector-pulsar/ , it never
undate since last year, and we actually use
https://github.com/streamnative/flink-connector-pulsar/ as a usable fork,
or even a central repo.
For another example flink training is dead also.
https://github.com/apache/flink-training/pulls for about 2 years. nobody
review prs, nobody track latest flink 2.x versions...
Sigh. Hope things get well but...

Pedro Mázala <pe...@gmail.com> 于2025年10月16日周四 21:29写道:

> Just stating what we discussed IRL, this is a great effort and initiative,
> David!
>
>
>
> Att,
> Pedro Mázala
> Be awesome
>
>
> On Thu, 16 Oct 2025 at 08:52, Robert Metzger <rm...@apache.org> wrote:
>
> > Thank you for running this initiative!
> >
> > Let's try to collaborate async on the community health and do calls
> ad-hoc
> > as needed.
> >
> > On Fri, Oct 10, 2025 at 6:22 PM David Radley <da...@uk.ibm.com>
> > wrote:
> >
> > > Hi,
> > > We are coming up for a year of the Community Health Initiative [1].
> With
> > > goals of
> > >
> > >    - High level, remove the need for the workgroup and run as BAU
> > >    - Improve new contributor experience by getting prompt responses to
> > >    issues and PRs, such that PRs are merged in a timely manner.
> > >    - Pragmatically address unmerged PR backlog considering
> > >    - Recent ones (to stay on top of incoming PRs and helping new
> > >    contributors)
> > >    - High /critical blocking ones
> > >    - One that just should be merged.
> > >    - Pragmatically address issue backlog, especially criticals and
> > >    blockers
> > >    - Assumption – all communications go through the dev list.
> > >
> > >
> > > The main participants were @Tom Cooper <co...@tomcooper.dev>, myself
> and
> > @Robert
> > > Metzger <rm...@apache.org>. Tom is no longer working with Flink.
> > >
> > > The achievements of the workgroup have been:
> > >
> > >    -  Tom and I have been reviewing Flink PRs, starting from the
> latest.
> > >    - Regular PR triaging in weekly meetings.
> > >    - Massively reducing the PR backlog by introducing the stale Github
> > >    action. When we started last year, we had 1181 open PRs on the Flink
> > repo,
> > >    1030 of them had not been reviewed. We now have 208 open PRs, 200
> > have not
> > >    been reviewed and 8 are stale. We seemed to have reached a steady
> > state
> > >    around 200; which is much more manageable.
> > >    - To encourage and recognise more reviewing by non-committers we
> added
> > >    the 2 community review labels.
> > >    - We added Github action to label PRs with the targeted branch, so
> it
> > >    is easy to see back ports in the list of PRs.
> > >    - We produced list of the LGTM PRs and straightforward merges that
> > >    Robert and other committers have merged.
> > >    - We discussed on going issues, potential ideas around improving the
> > >    community health as detailed in the minutes.
> > >
> > > I have very much enjoyed leading this workgroup and am happy to
> continue
> > > if there is support for it, as I am a big believer in the Apache way
> and
> > > community over code. If anyone would like to actively join this
> > > workgroup, please let me know, we have been meeting on Teams every
> week.
> > If
> > > I do not hear anything within the next week,  then I will stop the
> weekly
> > > meetings and resurrect when the community has the appetite for it.
> > >
> > > Either way I intend to continue reviewing PRs and be
> involved/support/own
> > > community health improvements; any feedback is welcome.
> > >
> > >      Kind regards and thanks for your support over the past year,
> David.
> > >
> > > [1]
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/Community+Health+Initiative+%28CHI%29+workgroup
> > >
> > >
> > >
> > >
> > >
> > > Unless otherwise stated above:
> > >
> > > IBM United Kingdom Limited
> > > Registered in England and Wales with number 741598
> > > Registered office: Building C, IBM Hursley Office, Hursley Park Road,
> > > Winchester, Hampshire SO21 2JN
> > >
> >
>

Re: Community Health Initiative update

Posted by Pedro Mázala <pe...@gmail.com>.
Just stating what we discussed IRL, this is a great effort and initiative,
David!



Att,
Pedro Mázala
Be awesome


On Thu, 16 Oct 2025 at 08:52, Robert Metzger <rm...@apache.org> wrote:

> Thank you for running this initiative!
>
> Let's try to collaborate async on the community health and do calls ad-hoc
> as needed.
>
> On Fri, Oct 10, 2025 at 6:22 PM David Radley <da...@uk.ibm.com>
> wrote:
>
> > Hi,
> > We are coming up for a year of the Community Health Initiative [1]. With
> > goals of
> >
> >    - High level, remove the need for the workgroup and run as BAU
> >    - Improve new contributor experience by getting prompt responses to
> >    issues and PRs, such that PRs are merged in a timely manner.
> >    - Pragmatically address unmerged PR backlog considering
> >    - Recent ones (to stay on top of incoming PRs and helping new
> >    contributors)
> >    - High /critical blocking ones
> >    - One that just should be merged.
> >    - Pragmatically address issue backlog, especially criticals and
> >    blockers
> >    - Assumption – all communications go through the dev list.
> >
> >
> > The main participants were @Tom Cooper <co...@tomcooper.dev>, myself and
> @Robert
> > Metzger <rm...@apache.org>. Tom is no longer working with Flink.
> >
> > The achievements of the workgroup have been:
> >
> >    -  Tom and I have been reviewing Flink PRs, starting from the latest.
> >    - Regular PR triaging in weekly meetings.
> >    - Massively reducing the PR backlog by introducing the stale Github
> >    action. When we started last year, we had 1181 open PRs on the Flink
> repo,
> >    1030 of them had not been reviewed. We now have 208 open PRs, 200
> have not
> >    been reviewed and 8 are stale. We seemed to have reached a steady
> state
> >    around 200; which is much more manageable.
> >    - To encourage and recognise more reviewing by non-committers we added
> >    the 2 community review labels.
> >    - We added Github action to label PRs with the targeted branch, so it
> >    is easy to see back ports in the list of PRs.
> >    - We produced list of the LGTM PRs and straightforward merges that
> >    Robert and other committers have merged.
> >    - We discussed on going issues, potential ideas around improving the
> >    community health as detailed in the minutes.
> >
> > I have very much enjoyed leading this workgroup and am happy to continue
> > if there is support for it, as I am a big believer in the Apache way and
> > community over code. If anyone would like to actively join this
> > workgroup, please let me know, we have been meeting on Teams every week.
> If
> > I do not hear anything within the next week,  then I will stop the weekly
> > meetings and resurrect when the community has the appetite for it.
> >
> > Either way I intend to continue reviewing PRs and be involved/support/own
> > community health improvements; any feedback is welcome.
> >
> >      Kind regards and thanks for your support over the past year, David.
> >
> > [1]
> >
> https://cwiki.apache.org/confluence/display/FLINK/Community+Health+Initiative+%28CHI%29+workgroup
> >
> >
> >
> >
> >
> > Unless otherwise stated above:
> >
> > IBM United Kingdom Limited
> > Registered in England and Wales with number 741598
> > Registered office: Building C, IBM Hursley Office, Hursley Park Road,
> > Winchester, Hampshire SO21 2JN
> >
>

Re: Community Health Initiative update

Posted by Robert Metzger <rm...@apache.org>.
Thank you for running this initiative!

Let's try to collaborate async on the community health and do calls ad-hoc
as needed.

On Fri, Oct 10, 2025 at 6:22 PM David Radley <da...@uk.ibm.com>
wrote:

> Hi,
> We are coming up for a year of the Community Health Initiative [1]. With
> goals of
>
>    - High level, remove the need for the workgroup and run as BAU
>    - Improve new contributor experience by getting prompt responses to
>    issues and PRs, such that PRs are merged in a timely manner.
>    - Pragmatically address unmerged PR backlog considering
>    - Recent ones (to stay on top of incoming PRs and helping new
>    contributors)
>    - High /critical blocking ones
>    - One that just should be merged.
>    - Pragmatically address issue backlog, especially criticals and
>    blockers
>    - Assumption – all communications go through the dev list.
>
>
> The main participants were @Tom Cooper <co...@tomcooper.dev>, myself and @Robert
> Metzger <rm...@apache.org>. Tom is no longer working with Flink.
>
> The achievements of the workgroup have been:
>
>    -  Tom and I have been reviewing Flink PRs, starting from the latest.
>    - Regular PR triaging in weekly meetings.
>    - Massively reducing the PR backlog by introducing the stale Github
>    action. When we started last year, we had 1181 open PRs on the Flink repo,
>    1030 of them had not been reviewed. We now have 208 open PRs, 200 have not
>    been reviewed and 8 are stale. We seemed to have reached a steady state
>    around 200; which is much more manageable.
>    - To encourage and recognise more reviewing by non-committers we added
>    the 2 community review labels.
>    - We added Github action to label PRs with the targeted branch, so it
>    is easy to see back ports in the list of PRs.
>    - We produced list of the LGTM PRs and straightforward merges that
>    Robert and other committers have merged.
>    - We discussed on going issues, potential ideas around improving the
>    community health as detailed in the minutes.
>
> I have very much enjoyed leading this workgroup and am happy to continue
> if there is support for it, as I am a big believer in the Apache way and
> community over code. If anyone would like to actively join this
> workgroup, please let me know, we have been meeting on Teams every week. If
> I do not hear anything within the next week,  then I will stop the weekly
> meetings and resurrect when the community has the appetite for it.
>
> Either way I intend to continue reviewing PRs and be involved/support/own
> community health improvements; any feedback is welcome.
>
>      Kind regards and thanks for your support over the past year, David.
>
> [1]
> https://cwiki.apache.org/confluence/display/FLINK/Community+Health+Initiative+%28CHI%29+workgroup
>
>
>
>
>
> Unless otherwise stated above:
>
> IBM United Kingdom Limited
> Registered in England and Wales with number 741598
> Registered office: Building C, IBM Hursley Office, Hursley Park Road,
> Winchester, Hampshire SO21 2JN
>