Hi Justin,

Thanks for the follow-up.

Before evaluating individuals in the PPMC thread, I sent a note to
align the PPMC on the criteria for Fluss PMC membership [1]. We
followed the Incubator guidance [2] and highlighted two points in
particular:

1. PMC membership is about governance, not just technical contribution.
2. Incubation-era contributions count most.

We then evaluated each nomination against those agreed criteria.

According to the first point, we declined the nomination of Hongshun
Wang. He is our top 4 contributor, but his work so far is concentrated
on technical contribution, and we felt he needs more time to grow on
the governance side.

According to the second point, we specifically discussed the
less-active members [3]. Taking into account that they did make
incubation-era contributions [4], including promoting the project in
the industry and driving Fluss adoption at multiple companies during
incubation. Besides, following the mentors' guidance given earlier in
this thread [5]: Rather than preemptively removing members whose
foundational contributions were the basis for Fluss entering the
Incubator, we gave them the opportunity to explicitly state their
willingness to take on active PMC governance going forward, treating
sustained commitment as a forward-looking signal for retention, and
non-response as grounds for the PPMC to draw its own conclusions.

They each explicitly confirmed that willingness in the PPMC thread,
and proactively committed to concrete post-graduation roles —
including mentoring, growing the project's visibility globally, and
driving deeper integration across Fluss and other open-source projects
— which we consider important for the community after graduation. We
have also seen recent, concrete governance engagement from them, such
as handling CVE issues and proposing new members. After weighing all
of this, the PPMC considered that they should be included in the
proposed roster.

I hope this additional background helps address your concern, and if
there is anything we have not done well, we genuinely welcome more
specific suggestions for improvement.

Thanks again for the guidance.

Best regards,
Jark

[1] https://lists.apache.org/thread/pls4boxokgjhy1rjww3q9whnlmo4h393
[2] 
https://cwiki.apache.org/confluence/display/INCUBATOR/Selecting+the+Initial+PMC+at+Graduation
[3] https://lists.apache.org/thread/p6ys5wkxd9bsf877g4k6jtzpg8v9y7ny
[4] https://lists.apache.org/thread/svzdw670073qhl8m9pz4oywp941705vb
[5] https://lists.apache.org/thread/hwv94806rc45o4lo8yy0bs358f6qmpgs

On Fri, 12 Jun 2026 at 23:34, Jean-Baptiste Onofré <[email protected]> wrote:
>
> Hi All,
>
> Please excuse my delayed response; I am traveling this week and have been
> slower to reply.
>
> The podling currently has its committer criteria documented here:
> https://fluss.apache.org/community/become-a-committer/
>
> To move forward, I suggest that the podling proposes a more concise PMC
> roster consisting specifically of active contributors. Based on meritocracy
> and ongoing contributions, I am confident that other qualified members can
> be added to the PMC in the future.
>
> I believe this approach aligns well with the Apache Way and directly
> addresses Justin's concerns. I will share this suggestion with the PPMC on
> the private mailing list to help us finalize the next steps.
>
> Regards,
> JB
>
>
> On Fri, Jun 12, 2026 at 3:28 PM Justin Mclean <[email protected]>
> wrote:
>
> > Hi,
> >
> > Thanks for the detailed update. The community has clearly put significant
> > effort into addressing the feedback.
> >
> > I do still have the same concern. The revised process correctly adopted a
> > nomination-with-evidence standard, which is good to see. However, I'd ask
> > the community to confirm that all proposed PMC members have been evaluated
> > against the agreed criteria, and in particular that the contributions being
> > relied on occurred during the incubation period rather than prior to the
> > ASF donation. Looking at the proposed roster, I don't believe this has been
> > done for everyone, and the initial issue that concerned me has not been
> > fully addressed.
> >
> > Kind Regards,
> >
> > Justin

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to