mirror of
https://github.com/vinta/awesome-python.git
synced 2026-11-20 06:40:51 +00:00
docs: apply CONTRIBUTING.md when rewording an entry
The instruction to apply CONTRIBUTING.md covered only adding or removing an entry, so agents rewording an existing description skipped its rules, including the description length soft cap. Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
parent
abf3019e8f
commit
13570f9c23
2 changed files with 2 additions and 2 deletions
|
|
@ -6,7 +6,7 @@ An opinionated guide to the best Python frameworks, libraries, and tools.
|
|||
|
||||
## Entry Rules
|
||||
|
||||
[CONTRIBUTING.md](CONTRIBUTING.md) holds the admission rules, quality requirements, rejection rules, entry format, and ordering. Apply it whenever adding or removing an entry — direct commits included, not only PR reviews.
|
||||
[CONTRIBUTING.md](CONTRIBUTING.md) holds the admission rules, quality requirements, rejection rules, entry format, and ordering. Apply it whenever adding, removing, or rewording an entry — direct commits included, not only PR reviews.
|
||||
|
||||
- Every keep/drop reason must be verified against current online data at decision time — download counts, repo activity and archived status, PyPI metadata, project docs. Judging tiers — obvious choice vs challenger — also requires WebSearch evidence (adoption trajectory, community sentiment), not download counts alone. Training-data recollections are not evidence; label anything unverifiable as a judgment call.
|
||||
- Checks stay read-only: judge whether a listed project installs or works from its PyPI metadata (`requires_python`, classifiers, wheel tags) and issue tracker, never by installing or running it, since that runs untrusted code.
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ An opinionated guide to the best Python frameworks, libraries, and tools.
|
|||
|
||||
## Entry Rules
|
||||
|
||||
[CONTRIBUTING.md](CONTRIBUTING.md) holds the admission rules, quality requirements, rejection rules, entry format, and ordering. Apply it whenever adding or removing an entry — direct commits included, not only PR reviews.
|
||||
[CONTRIBUTING.md](CONTRIBUTING.md) holds the admission rules, quality requirements, rejection rules, entry format, and ordering. Apply it whenever adding, removing, or rewording an entry — direct commits included, not only PR reviews.
|
||||
|
||||
- Every keep/drop reason must be verified against current online data at decision time — download counts, repo activity and archived status, PyPI metadata, project docs. Judging tiers — obvious choice vs challenger — also requires WebSearch evidence (adoption trajectory, community sentiment), not download counts alone. Training-data recollections are not evidence; label anything unverifiable as a judgment call.
|
||||
- Checks stay read-only: judge whether a listed project installs or works from its PyPI metadata (`requires_python`, classifiers, wheel tags) and issue tracker, never by installing or running it, since that runs untrusted code.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue