Adopt the AI-native SDLC and repository policies

Aperta
  • Qualcosa non va?
#634 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@goanpeca ci sta già lavorando.

Dal 28/10/2026.

  • #635 di @goanpeca — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
python
Ambito
developer-experience, devops, documentation

Direzione di ricerca

Review the proposed files and workflow in the issue, especially intent/review-process/intent.md, README.release.md, and the existing nox sessions and towncrier checks. The issue spans repository policy, contributor guidance, release documentation, CI decisions, and a maintainer review proposal; first read the linked pull request and confirm with maintainers which parts remain in scope. Done means the agreed policies and workflows are documented and any admin decisions are recorded.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

Problem

More and more b2-sdk-python PRs are written with coding agents, and nothing in the repo tells an agent (or a new contributor) how this codebase works or what reviewers keep asking for. The rules live in reviewers' heads and in past review threads: towncrier fragments in changelog.d/ with the right name and type, changes made in b2sdk/_internal and exported through the right b2sdk/vN apiver layer without breaking older layers, raw_simulator.py kept in step with raw_api.py, tests that fail when the fix is reverted, retry and Retry-After parity, and the .sdkharness contract checks that CI does not run. The release steps are a single line in README.release.md.

The repo also lacks the standard policy files: no AGENTS.md/CLAUDE.md, REVIEW.md, SECURITY.md, CODE_OF_CONDUCT.md, PR template or issue forms.

Proposed outcome

  • Agents and contributors read the recurring review lessons before they write code (AGENTS.md, CLAUDE.md, docs/review-lessons.md), and reviewers follow one written process (REVIEW.md).
  • Keep towncrier and the existing CI changelog check; document them where agents look, and make the local check easy to run.
  • A documented release process (RELEASE.md, replacing README.release.md), security policy, code of conduct, PR template and issue forms.
  • One documented local command sequence that mirrors CI (nox -s lint, unit, build, doc, towncrier_check).
  • Larger changes start from intent/<slug>/intent.md → spec.md → plan.md, following the AI-native SDLC playbook, with the playbook skills in .claude/skills/.
  • A proposal, for the maintainers to decide, on scaling human review by risk (tiers, re-approval on new commits, required conversation resolution, automated AI and security review, merge queue, reviewer evals, metrics).

Settings that need a repo admin

  • Enable private vulnerability reporting (needed by SECURITY.md and the issue form's security link).
  • Decide whether the changelog validation step should become a required check on master.
  • Confirm which branch protection is applied to master.
  • Review intent/review-process/intent.md and accept, reshape or close it.
Lingua principale
Python
Stelle
214
Fork
68
Merge medio
51m
PR unite (30g)
6

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Backblaze/b2-sdk-python

Tutte le issue di Backblaze/b2-sdk-python

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.