docs: judge stability by the project, not its PyPI classifier

CONTRIBUTING's Stable requirement read as "not alpha/beta", so about 40 production-used entries (fastapi, uvicorn, keras, statsmodels, numba, and others) failed it on their PyPI Development Status classifier alone, and each needed an audit-log exception.

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Vinta Chen
2026-10-02 12:36:53 +08:00
co-authored by Claude
parent b44cdc1d4c
commit 0b75c7806d
+1 -1
View File
@@ -8,7 +8,7 @@ All submissions must satisfy **ALL** of these:
1. **Serves Python Developers**: Python developers use it in their Python work. Implementation language and packaging are irrelevant — uv and ty are written in Rust, and agent skill packs are markdown, yet all belong; a pure-Python project nobody uses in Python work does not.
2. **Active**: Commits within the last 12 months
3. **Stable**: Production-ready, not alpha/beta/experimental
3. **Stable**: Production-ready, not alpha/beta/experimental. A PyPI "Development Status" classifier alone does not decide this; judge by releases, documentation, and production use.
4. **Documented**: Clear README with examples and use cases
5. **Established**: Repository at least 1 month old