[Tech Review]: Higress

[EndlessSeeker]

Project name

Higress

Project link

https://github.com/higress-group/higress

Due diligence link

Not opened yet. Higress is preparing its CNCF Incubation application and is requesting this Technical Review as a prerequisite.

Project contact information

• Yuanxiao Zhao: @EndlessSeeker
• Tianyi Zhang: @johnlanni
• Yiquan Dong: @CH3CHO

Additional information

Higress is a CNCF Sandbox project requesting verification of its project-maintained General Technical Review in preparation for an Incubation application.

• Project-wide community and governance repository: https://github.com/higress-group/community
• General Technical Review: https://github.com/higress-group/community/blob/main/docs/cncf/general-technical-review.md
• Incubation application working copy: https://github.com/higress-group/community/blob/main/docs/cncf/incubation-application.md
• Security Self-Assessment: https://github.com/higress-group/community/blob/main/docs/cncf/security-self-assessment.md
• Governance Review working copy: https://github.com/higress-group/community/blob/main/docs/cncf/governance-review.md
• Architecture documentation: https://github.com/higress-group/higress/blob/main/docs/architecture.md
• OpenSSF Best Practices Passing badge: https://www.bestpractices.dev/projects/12667
• Public adopters: https://github.com/higress-group/community/blob/main/ADOPTERS.md
• Sandbox application and successful vote: [Sandbox] Higress sandbox#445
• Completed Sandbox onboarding: [PROJECT ONBOARDING] Higress sandbox#481

The project-maintained GTR was approved in higress-group/higress#4177 and refreshed after the OpenSSF Passing milestone in higress-group/higress#4261. The project-wide materials were moved through higress-group/community#1, with compatibility pointers and active Higress links updated through higress-group/higress#4270. We request CNCF Project Reviews verification and coordination of the required dated snapshot at projects/higress/tech-review/YYYY-MM-DD.md.

[EndlessSeeker]

Hi @angellk and @brandtkeller, this Technical Review issue was created via the GitHub CLI, so the standard issue-form labels were not applied automatically. The author account does not have permission to add repository labels. Could a Project Reviews maintainer please add the standard labels needs-triage, kind/initiative, review/tech, and sub/project-reviews? Thank you.

[angellk]

@riaankleinhans may be able to look into automation to assign these labels programmatically, if he hasn't already!