Hi,

Here is a draft graduation checklist generated by Claude Code:
https://docs.google.com/document/d/1G7lyeAqgD2DdvAwdfwI_IXSmCmjOAuFkFonZ78-MjxY/edit?usp=sharing.
I think we can use this document to continue our graduation assessment
work. Welcome to leave your comments.

Best,
Dianjin Wang

On Wed, Nov 11, 2026 at 7:47 PM Dianjin Wang <[email protected]> wrote:
>
> Hi Ed,
>
> Thanks for starting this discussion.
>
> One correction to the team page first. Three people listed under HashData
> have left the company. I confirmed their current affiliations with them and
> opened a PR to update the page:
>
> https://github.com/apache/cloudberry-site/pull/420
>
> Reviews and approvals are welcome, so we can get the page updated.
>
> With that PR applied, the PPMC (25 members, mentors included) looks like
> this:
>
>   Organization       PPMC members   Share
>   HashData                 5                       20%
>   Yandex Cloud          4                       16%
>   Synx Data Labs       4                       16%
>   Individual                 4                       16%
>   Other (6 orgs)          8                       32%
>
> "Other" covers EDB, ByteDance, Microsoft, Ainekko, HighGo and Zilliz.
> Counting all 35 committers, HashData has 9 (about 26%) and Yandex Cloud
> has 6 (about 17%).
>
> So HashData is still the largest single group, but by a small margin, and
> no organization is close to a majority. The community is much more diverse
> than when we entered the Incubator.
>
> The roster is only part of the picture. When we form the PMC for
> graduation, its makeup will likely differ from today's PPMC. As usual, we
> would confirm with each PPMC member whether they want to continue, and the
> list should reflect participation during incubation, in code and in
> community work alike. That is a natural step, and a topic for a later
> thread.
>
> To make the discussion more concrete, could we write up our
> self-assessment against the Apache Project Maturity Model as a checklist,
> with evidence links for each item, and publish it on the wiki or the
> website? Then everyone can check it item by item. Apache Iggy has a good
> example:
>
> https://iggy.apache.org/community/graduation-checklist/
>
> My own view: we are close, and the checklist will show what is left.
>
> Best,
> Dianjin Wang
>
> On Wed, Nov 11, 2026 at 9:35 AM Ed Espino via dev
> <[email protected]> wrote:
> >
> > Hi,
> >
> > Apache Cloudberry (Incubating) files a short quarterly report with the
> > Incubator. That report goes to the ASF Board. The November one is filed. It
> > says a graduation discussion would start. This thread is that start, on dev@
> > only.
> > https://cwiki.apache.org/confluence/display/INCUBATOR/November2026
> >
> > The report named general@incubator as well. The Incubator graduation guide
> > suggests telling general@incubator when a community vote starts, and asks
> > that the vote itself not be copied there. So a note to general@incubator
> > comes later, if and when we start a community vote. It will point to this
> > thread. It will not carry the vote.
> > https://incubator.apache.org/guides/graduation.html
> >
> > The November report lists two unfinished items before graduating: grow the
> > contributor community, and publish a few more Apache releases.
> >
> > I ran the Incubator graduation self-assessment on 9 November 2026. It
> > compares those unfinished items to our releases and our roster. It assesses
> > the project as near ready. It does not say we are ready. The release item
> > is met. The community item is partly addressed, which is why this thread
> > asks whether any one company is still vital to the project.
> > https://github.com/apache/incubator/blob/master/tools/skills/graduation-self-assessment/skills/graduation-self-assessment/SKILL.md
> >
> > Here is what is behind each item, releases first.
> >
> > We have shipped 2.0.0, 2.1.0, and 2.2.0. The vote calls for the candidates
> > that passed were:
> >
> > 14 August 2025, Ed Espino, 2.0.0-rc3
> > 26 March 2026, Dianjin Wang, 2.1.0-rc2
> > 20 October 2026, Leonid Borchuk, 2.2.0-rc3
> >
> > 2.2.0 was announced on 6 November 2026.
> > https://cloudberry.apache.org/blog/announce-apache-cloudberry-2.2.0
> >
> > For the community item, the guide asks for a project that is not highly
> > dependent on any single contributor, with at least three legally
> > independent committers and no single company or entity that is vital to the
> > success of the project.
> > https://incubator.apache.org/guides/graduation.html#creating_an_open_and_diverse_community
> >
> > I checked our team page on 10 November 2026. It lists people at more than
> > one organization. On that page I am at Synx Data Labs, Dianjin is at
> > HashData, and Leonid is at Yandex Cloud, so those three vote calls came
> > from three organizations. Leonid also joined the PPMC during incubation.
> > The status page announces him as a new PPMC member on 7 April 2026.
> > https://cloudberry.apache.org/team/
> > https://incubator.apache.org/projects/cloudberry.html
> >
> > From that, I do not think a release depends on one company. That does not
> > settle whether any one company is vital to the project. HashData is still
> > the largest group on the team page. In the end that is the Incubator's
> > opinion to form, and I would like us to look at it here first. Is any one
> > company still vital to the project? If I have read the releases wrong,
> > please say that too.
> >
> > So I am asking everyone here, committer or not:
> >
> > Are we ready to graduate?
> > Is a top-level project the right destination?
> > What is still missing?
> >
> > Nothing is decided by this mail. I will leave this thread open long enough
> > for people outside any one organization to reply.
> >
> > -=e
> > --
> > Ed Espino
> > Apache Cloudberry (Incubating)

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

Reply via email to