Higress Community

This document is the authoritative inventory of official Higress project communication channels, including channels used by its subprojects. Official technical and governance decisions are recorded in public GitHub issues, discussions, pull requests, or published meeting notes.

Public channels

Channel	Scope and purpose
GitHub Issues	Bug reports, feature requests, and work tracking for the primary repository
GitHub Pull Requests	Public change proposals, reviews, and decision records
GitHub Discussions	User questions, ideas, announcements, and longer-form community discussion
Higress Community Meeting	Monthly public project updates, technical discussions, roadmap planning, and community questions; schedule and joining details are published with the recurring DingTalk calendar event in MEETINGS.md
Higress Community Knowledge Base	Public product, usage, and community materials, including source documents for community meetings; technical and governance decisions remain authoritative in the relevant public GitHub record
Discord	Public real-time user and contributor chat; decisions arising there must be recorded on GitHub
Chinese-language community group	Publicly advertised Chinese-language user and contributor chat
Higress WeChat Official Account	Chinese-language technical articles and project announcements; broadcast rather than a decision channel
Higress website and documentation	Published user and contributor documentation and project announcements

Each subproject uses its own public GitHub issues and pull requests for work specific to that repository:

Subproject	Issues	Pull requests
higress-console	Issues	Pull requests
higress-standalone	Issues	Pull requests
plugin-server	Issues	Pull requests
wasm-go	Issues	Pull requests

Cross-subproject and project-governance decisions are recorded in this community repository. Repository-specific technical decisions remain in the relevant code repository.

Non-public channels

Non-public channels are limited to reports whose confidentiality protects reporters or users:

Channel	Special purpose
GitHub Private Security Advisories	Required, vendor-neutral, and authoritative vulnerability-reporting channel; used for project triage, remediation, and disclosure coordination under the Higress security policy
Alibaba Security Response Center	Optional additional channel, for example when a report also affects an Alibaba Cloud service; an SRT member with access may correlate the case with the project record
CNCF Code of Conduct reporting	Confidential Code of Conduct incident reporting under CODE_OF_CONDUCT.md
CNCF TOC private mailing list	Confidential escalation when project leadership cannot resolve a security or governance conflict without conflicted participants

Personal messages, employer-internal systems, and informal maintainer chats are not official project decision channels. If they inform project work, the non-sensitive decision and rationale must be recorded publicly.

Community meetings

The Higress Community Meeting is held on the third Thursday of each month from 20:00 to 21:00 Asia/Shanghai (UTC+8). Its current schedule and public joining information are published with the recurring DingTalk calendar event in MEETINGS.md. The meeting document also defines the public agenda, notes, decisions, action items, recordings, and transcripts process.

Contributor activity and recruitment

Public, continuously updated evidence is available through:

• GitHub contributor activity
• Recent repository activity
• CNCF DevStats for Higress
• help wanted issues
• good first issue issues
• the contributor path in CONTRIBUTING_EN.md
• the active-maintainer evidence and annual roster review in MAINTAINERS.md

Contributors can start through an issue, discussion, documentation update, bug fix, test, plugin, or other pull request. Maintainers and code owners recruit and mentor contributors through the public channels above and identify approachable work with contribution labels.