Hi Vaughn,

+1 (non-binding).

Thanks for organizing and clearly laying out the checklist. The completed items 
look solid, especially the progress on license compliance and release readiness.

The pending tasks you outlined are reasonable and aligned with the standard TLP 
graduation requirements. I don’t see any obvious blockers missing from the list 
at this point.

Looking forward to the next steps.

Best regards,
Wang Jing

On 2025/12/10 14:10:33 vaughn wrote:
> Hi everyone,
> 
> As we move closer to graduating as a Top-Level Project (TLP), I have
> organized a checklist of action items to ensure we meet all Apache
> requirements and to track our current status.
> 
> The purpose of this email is to align on the remaining tasks. Please
> review the checklist below and let me know if I have missed any
> critical blockers or if the plan looks reasonable.
> 
> ✅ Completed / Resolved Items
> 
> License Compliance: Replaced python-igraph (GPL dependency) to ensure
> full compliance; re-verified dependencies.
> 
> Release Readiness: Verified that the recent releases (including 1.7.0)
> were led by PPMC members independent of mentors.
> 
> IP Clearance: Confirmed pycgraph licensing and SGA/CCLA status.
> 
> Documentation Compliance: Added LICENSE/NOTICE/DISCLAIMER to
> incubator-hugegraph-doc (PR submitted) and fixed binary distribution
> artifacts.
> 
> Legacy Modules: incubator-hugegraph-tools is considered deprecated, so
> we will focus compliance efforts on active repositories.
> 
> 🚧 Pending Items (To-Do List)
> 
> I have identified the following key tasks that need to be addressed
> before we start the formal voting process:
> 
> 1. Whimsy & SVN Status Update
> 
> Update HugeGraph.xml in the ASF SVN repository to reflect the complete
> release history, SGA, and Copyright dates.
> 
> 2. Comprehensive License Check (Apache RAT)
> 
> Run Apache RAT / License header checks across all active repositories
> (including hugegraph-ai, toolchain, computer, commons).
> 
> Fix any missing headers or incorrect binary exclusions, and update
> NOTICE files where necessary.
> 
> 3. Maturity Model Assessment
> 
> Update and finalize the "Apache Project Maturity Model" assessment
> (covering Code, License, Releases, Community, Consensus,
> Independence).
> 
> Publish the updated report to our website or Wiki for community review.
> 
> 4. Community Diversity Data
> 
> Collect data for the graduation proposal, including the ratio of
> active contributors by company and the growth of new committers/PPMC
> members during incubation.
> 
> Next Steps: If there are no objections to this list, we will proceed
> with these items. Once they are marked as "Done", we will initiate the
> formal graduation discussion on the general@incubator list.
> 
> Your feedback on this roadmap is appreciated.
> 
> Best regards
> 
> Vaughn zhang
> 

Reply via email to