vrr/qwen-code
2
0
Fork 0
mirror of https://github.com/QwenLM/qwen-code.git synced 2026-07-09 17:19:02 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 12

docs: add provider preset governance policy to CONTRIBUTING.md (#5631)

Browse source 
Define Tier 1 qualification criteria (affiliation disclosure, operational
maturity, organic user demand, data/security transparency, maintenance
commitment) and the custom-provider default path for providers that don't
qualify. Also document the technical checklist for approved preset PRs.

This formalizes the governance stance applied to recent third-party gateway
PRs (#5060 TrustedRouter, #5625 PleumRouter).
This commit is contained in:
pomelo 2026-06-27 22:44:21 +08:00 • committed by GitHub
parent a93ec674e9
commit 8b5cb01a33
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 16 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

16
CONTRIBUTING.md
View file

@ -66,6 +66,22 @@ Your PR should have a clear, descriptive title and a detailed description of the
In the PR description, explain the "why" behind your changes and link to the relevant issue (e.g., `Fixes #123`).
### Adding a Provider Preset
A built-in preset is an **endorsement**, not just a convenience. Users route API keys and full prompt data through these endpoints, so the bar is high.
**Tier 1 — Built-in Preset** requires all of the following:
- **Affiliation Disclosure** — PR author must disclose any relationship with the provider.
- **Operational Maturity** — publicly operational with demonstrated uptime; public SLA or status page preferred.
- **Organic User Demand** — evidence of community demand (issues, discussions), not just a self-listing.
- **Data and Security Transparency** — provider's data handling practices must be publicly documented.
- **Maintenance Commitment** — provider team commits to tracking Qwen Code protocol changes.
**Default Path — Custom Provider**: for providers that don't meet Tier 1, users connect via the built-in custom-provider flow (`/auth` or `/model` → Custom Provider). No code change or project endorsement needed.
**If a Tier 1 preset is approved**, the PR should follow the existing `openrouter.ts` / `requesty.ts` pattern: use `customHeaders` for attribution, implement `ownsModel` with a dual-gate (env key + hostname), and add the env key to `SECRET_ENV_VARS` in `packages/cli/src/serve/envSnapshot.ts` with corresponding test assertions in `auth.test.ts` and `provider-config.test.ts`.
## Development Setup and Workflow
This section guides contributors on how to build, modify, and understand the development setup of this project.