Maintainers
This file lists project roles for Q+ Language. Names and public handles are placeholders until the Maintainer confirms the publication identity; do not treat any placeholder as a public commitment.
Maintainer
| Role | Name / entity | Contact |
|---|---|---|
| Maintainer (final authority) | 如东星瀚科技有限公司 (Rudong Xinghan Technology Co., Ltd.), brand 星瀚 / Xinghan | TBD (Maintainer decision before publication) |
The Maintainer makes final decisions on licensing, publication, repository hosting, branding, commercial support, and anything that creates a public commitment.
Maintainer roles
| Area | Role | Placeholder | Responsibilities |
|---|---|---|---|
| Whole project | Lead maintainer | TBD | Cross-area review, release candidates, governance, release notes |
| Compiler / VM / AOT | Language maintainer | TBD | src/compiler, src/runtime, AOT backend, spec conformance |
| Standard library / modules | Stdlib maintainer | TBD | stdlib/std, tools/module_map.py, qbc package metadata |
| Tests / CI / robustness | Quality maintainer | TBD | tools/test.sh, tools/robustness_test.sh, CI workflow, fixtures |
| Documentation / site | Docs maintainer | TBD | English docs, site/, docs/, release notes, examples |
| Editor components (LSP/VS Code) | Editor maintainer | TBD | editors/vscode, optional/dev LSP components (outside the release tar) |
| Security | Security responder | TBD | Private vulnerability intake, coordination, advisories |
| OS SDK prototype | Prototype maintainer | TBD | External OS SDK prototype docs and coordination (not a release runtime) |
One person may hold several roles. All maintainers are expected to follow CODE_OF_CONDUCT.md and the DCO requirement in CONTRIBUTING.en.md.
Becoming a maintainer
- Sustained, high-quality contributions in a project area (code, tests, docs, or release engineering).
- Demonstrated review quality and adherence to the Code of Conduct.
- Nomination by an existing maintainer and approval by the Maintainer in consultation with maintainers.
- Onboarding: read
GOVERNANCE.md,RELEASING.md, andSECURITY.md; get repository permissions appropriate to the role.
Removing a maintainer
A maintainer may step down at any time. The Maintainer may revoke maintainer status for inactivity, Code of Conduct violations, or security/release-process violations, after maintainer consultation where practical. Access is revoked on removal.
Release authority
Only the Maintainer may authorize a public release. The release manager prepares candidates and evidence, but tag/upload/announce actions require explicit Maintainer approval and are performed only by authorized maintainers. See RELEASING.md. v1.4.8-dev is currently NOT PUBLISHED.
Public contact
Public maintainer handles, e-mail addresses, and repository URLs are TBD (Maintainer decision). Security and conduct contacts are placeholders in SECURITY.md and CODE_OF_CONDUCT.md and must be filled before the first public publication.