Hi Ed, Thanks for starting the discussion.
What the upstream commit history shows (origin/main, after stripping PostgreSQL/Greenplum backports. Please correct me if something wrong): - Activity is steady. 180–200 Cloudberry commits per half-year from 27–38 author emails. 2025H1 reached 429 because of the PG16 port. - Few people merge. At most 9 distinct people per half-year landed code, against 27–56 authors. Best regards, Max Yang 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) >
