Hi all, (Apologize for the wrong mail format↑:) Apache HugeGraph joined the Incubator in January 2022[1]. Since then, under the guidance of our mentors, we have continuously learned and embraced the Apache Way. We have practiced the spirit of "Community Over Code," successfully building a friendly and diverse community while attracting a growing number of participants.
After recent discussions[2a] and a successful community vote[2b], we believe HugeGraph is ready for graduation. We have placed a strong emphasis on license compliance and verified our releases strictly following ASF policies. We have also confirmed the initial PMC membership and selected a chair/VP on our private list[3a][3b]. We are now bringing this to the Incubator PMC for discussion and welcome any feedback. ## Community Growth & Diversity Since entering incubation, we have elected 10 new committers and 2 new PPMC members[4]. Our community has reached 210+ total contributors. Notably, our Committer and PPMC group is merit-based and represents more than 8 different companies, organizations, and universities, with a relatively even distribution of members across these entities. This structure ensures the project's independence, vendor-neutrality, and satisfies the ASF requirement for a diverse contributor base. Throughout incubation, we have submitted regular board reports documenting our progress[5]. ## Project Highlights - Community: 22 committers (including mentors[6]) across 4 core repositories (hugegraph, hugegraph-computer, hugegraph-ai, hugegraph-toolchain). - Growth: Gained 1,000+ new GitHub stars during incubation, reflecting significant community interest. - Security: Established a robust security process. We have proactively managed and resolved 10+ security-related issues, successfully publishing 5 CVEs with transparent disclosure[16]. - Releases: 5 Apache releases (1.0 -> 1.2 -> 1.3 -> 1.5 -> 1.7), managed by 5 different release managers, demonstrating the community's ability to execute the release process independently. - Issues & PRs: 1,642 issues opened with 1,325 resolved; 1,165 PRs created with 1,129 merged[7][8]. - Adoption: HugeGraph is used in production by diverse organizations worldwide across finance, e-commerce, and telecommunications[9]. ## Release Cadence The project maintains a stable and high-quality release rhythm. Given the complexity of a multi-component graph database/system, we focused on refactoring the legacy codebase to align with the new architecture after joining the incubator. We coordinate synchronized releases across all components (Server/Core, Toolchain, Computer, AI) to ensure ecosystem-wide compatibility and stability. ## Community Engagement We have actively participated in open-source programs to cultivate new talent: - Google Summer of Code (GSoC)[10]: 2024, 2025 - Open Source Promotion Plan (OSPP & GLCC)[11]: 2023 ~ 2025 We have also presented at ApacheCon/CommunityOverCode for three consecutive years (2023 ~ 2025), with 6 sessions in total. ## Cross-Community Collaboration We actively collaborate with the broader open-source ecosystem, fostering "bidirectional contribution": - Within ASF: HugeGraph has been integrated as a connector in Apache SeaTunnel & Apache TinkerPop, adopted Apache Fury for off-heap memory management, and is working on supporting Apache GraphAR for standardized data exchange. - Beyond ASF: We maintain deep technical cooperation with projects like ToplingDB (storage optimization), CGraph (graph computing), and JRaft (consensus). We not only use these technologies but also actively contribute back via PRs and feedback. ## Trademark Status We have completed the preparation and submission of all necessary materials for the trademark transfer to ASF. As per the internal approval from the donor company and the coordination with the ASF trademark team, we are proceeding with graduation while the formal transfer completes in parallel. The status is tracked in[12a] and discussed in[12b]. ## Maturity Assessment We have completed a self-assessment and believe we meet all maturity criteria outlined by the ASF[13][14]. All branding-related items have been addressed[15]. We extend our sincere thanks to our mentors and the incubator community for their invaluable guidance throughout our incubation journey. ------------------------------------------------------------------- Refer Links [1] https://lists.apache.org/thread/j7glr7dryhszq42v2qwymd85jb28gmnr (Incubator VOTE for HugeGraph) [2a] https://lists.apache.org/thread/spvoytpqh1fq496hj26s19j6s1t0hg74 (Graduation discussion) [2b] https://lists.apache.org/thread/mb77pmhft4bhrmmypcwl94dg9fcfgp2y (Result of dev VOTE) [3a] https://lists.apache.org/thread/f96bk0mpkcf3l7rrp75roy94zwm84qn6 (PMC Chair confirmation - Part 1) [3b] https://lists.apache.org/thread/fkfxom9ycsnr5h077rknky8x63dbdg2n (PMC Chair confirmation - Part 2) [4] https://incubator.apache.org/projects/hugegraph.html (HugeGraph incubation status) [5] https://whimsy.apache.org/board/minutes/hugegraph.html (Board report history) [6] https://whimsy.apache.org/roster/ppmc/hugegraph [7] https://github.com/apache/incubator-hugegraph/issues [8] https://github.com/apache/incubator-hugegraph/pulls [9] https://github.com/apache/incubator-hugegraph/issues/1651 (User cases collection) [10] https://community.apache.org/gsoc.html (ASF GSoC page) [11] https://summer-ospp.ac.cn/ (OSPP official site) [12a] https://github.com/apache/incubator-hugegraph/issues/2855 (Trademark donation tracking) [12b] https://lists.apache.org/thread/18cbgvpskrbkovr18j8n2lmyghwmgq41 (Trademark status on the private list) [13] https://hugegraph.apache.org/community/maturity/ (HugeGraph maturity self-assessment) [14] https://community.apache.org/apache-way/apache-project-maturity-model.html (ASF maturity model) [15] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-244 (Branding issue resolved) [16] https://hugegraph.apache.org/docs/guides/security/ (HugeGraph Security Page) Best regards Imba Jin - Behalf of the HugeGraph PPMC On 2025/12/26 16:07:57 Imba Jin wrote: > Hi all, Apache HugeGraph joined the Incubator in January 2022[1]. Since > then, under the guidance of our mentors, we have continuously learned and > embraced the Apache Way. We have practiced the spirit of "Community Over > Code," successfully building a friendly and diverse community while > attracting a growing number of participants. After recent discussions[2a] > and a successful community vote[2b], we believe HugeGraph is ready for > graduation. We have placed a strong emphasis on license compliance and > verified our releases strictly following ASF policies. We have also > confirmed the initial PMC membership and selected a chair/VP on our private > list[3a][3b]. We are now bringing this to the Incubator PMC for discussion > and welcome any feedback. Community Growth & Diversity Since entering > incubation, we have elected 10 new committers and 2 new PPMC members[4]. > Our community has reached 210+ total contributors. Notably, our Committer > and PPMC group is merit-based and represents more than 8 different > companies, organizations, and universities, with a relatively even > distribution of members across these entities. This structure ensures the > project's independence, vendor-neutrality, and satisfies the ASF > requirement for a diverse contributor base. Throughout incubation, we have > submitted regular board reports documenting our progress[5]. Project > Highlights - Community: 22 committers (including mentors[6]) across 4 core > repositories (hugegraph, hugegraph-computer, hugegraph-ai, > hugegraph-toolchain). - Growth: Gained 1,000+ new GitHub stars during > incubation, reflecting significant community interest. - Security: > Established a robust security process. We have proactively managed and > resolved 10+ security-related issues, successfully publishing 5 CVEs with > transparent disclosure[16]. - Releases: 5 Apache releases (1.0 -> 1.2 -> > 1.3 -> 1.5 -> 1.7), managed by 5 different release managers, demonstrating > the community's ability to execute the release process independently. - > Issues & PRs: 1,642 issues opened with 1,325 resolved; 1,165 PRs created > with 1,129 merged[7][8]. - Adoption: HugeGraph is used in production by > diverse organizations worldwide across finance, e-commerce, and > telecommunications[9]. Release Cadence The project maintains a stable and > high-quality release rhythm. Given the complexity of a multi-component > graph database/system, we focused on refactoring the legacy codebase to > align with the new architecture after joining the incubator. We coordinate > synchronized releases across all components (Server/Core, Toolchain, > Computer, AI) to ensure ecosystem-wide compatibility and stability. > Community Engagement We have actively participated in open-source programs > to cultivate new talent: - Google Summer of Code (GSoC)[10]: 2024, 2025 - > Open Source Promotion Plan (OSPP & GLCC)[11]: 2023 ~ 2025 We have also > presented at ApacheCon/CommunityOverCode for three consecutive years (2023 > ~ 2025), with 6 sessions in total. Cross-Community Collaboration We > actively collaborate with the broader open-source ecosystem, fostering > "bidirectional contribution": - Within ASF: HugeGraph has been integrated > as a connector in Apache SeaTunnel & Apache TinkerPop, adopted Apache Fury > for off-heap memory management, and is working on supporting Apache GraphAR > for standardized data exchange. - Beyond ASF: We maintain deep technical > cooperation with projects like ToplingDB (storage optimization), CGraph > (graph computing), and JRaft (consensus). We not only use these > technologies but also actively contribute back via PRs and feedback. > Trademark Status We have completed the preparation and submission of all > necessary materials for the trademark transfer to ASF. As per the internal > approval from the donor company and the coordination with the ASF trademark > team, we are proceeding with graduation while the formal transfer completes > in parallel. The status is tracked in[12a] and discussed in[12b]. Maturity > Assessment We have completed a self-assessment and believe we meet all > maturity criteria outlined by the ASF[13][14]. All branding-related items > have been addressed[15]. We extend our sincere thanks to our mentors and > the incubator community for their invaluable guidance throughout our > incubation journey. ------------------------------ > ------------------------------------- > Refer Links: > [1] https://lists.apache.org/thread/j7glr7dryhszq42v2qwymd85jb28gmnr > (Incubator VOTE for HugeGraph) [2a] > https://lists.apache.org/thread/spvoytpqh1fq496hj26s19j6s1t0hg74 > (Graduation discussion) [2b] > https://lists.apache.org/thread/mb77pmhft4bhrmmypcwl94dg9fcfgp2y (Result of > dev VOTE) [3a] > https://lists.apache.org/thread/f96bk0mpkcf3l7rrp75roy94zwm84qn6 (PMC Chair > - Part1) [3b] > https://lists.apache.org/thread/fkfxom9ycsnr5h077rknky8x63dbdg2n (PMC Chair > - Part2) [4] https://incubator.apache.org/projects/hugegraph.html > (HugeGraph incubation status) [5] > https://whimsy.apache.org/board/minutes/hugegraph.html (Board report > history) [6] https://whimsy.apache.org/roster/ppmc/hugegraph [7] > https://github.com/apache/incubator-hugegraph/issues [8] > https://github.com/apache/incubator-hugegraph/pulls [9] > https://github.com/apache/incubator-hugegraph/issues/1651 (User cases > collection) [10] https://community.apache.org/gsoc.html (ASF GSoC page) > [11] https://summer-ospp.ac.cn/ (OSPP official site) [12a] > https://github.com/apache/incubator-hugegraph/issues/2855 (Trademark > donation tracking) [12b] > https://lists.apache.org/thread/18cbgvpskrbkovr18j8n2lmyghwmgq41 (Trademark > status on the private list) [13] > https://hugegraph.apache.org/community/maturity/ (HugeGraph maturity > self-assessment) [14] > https://community.apache.org/apache-way/apache-project-maturity-model.html > (ASF maturity model) [15] > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-244 (Branding issue > resolved) [16] https://hugegraph.apache.org/docs/guides/security/ > (HugeGraph Security Page) Best regards, Imba Jin - Behalf of the HugeGraph > PPMC > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
