Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Organization-level policy source for operator configuration

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

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
tooling

Direzione di ricerca

Start by reading RFC-0001 September 2026 revision (#499) and RFC-0002 organization question inbox (#500), which this issue identifies as related. Work through the listed design questions: policy location and trust, precedence, allowed settings, and how org-scoped answers interact with policy. Done means those choices are specified, while user-level operator configuration remains out of scope.

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

Descrizione

module-core

Summary

darnit is moving tool configuration (which checks and commands run, which plugins and MCP servers are trusted, storage backends, LLM budgets, policy for how project assertions are treated) out of the audited repository and into operator configuration: configuration owned by whoever runs darnit, starting at the user level.

This issue tracks the follow-on: an organization-level policy source that an operator can choose to trust, so an org can set shared policy once for every repository it audits.

Scope to design

  • Where org policy lives (for example the org-level .project repository) and how an operator declares that they trust it, including pinning to a reviewed revision.
  • Precedence: built-in defaults, then user-level operator configuration, then trusted org policy, then per-run flags. Nothing from an audited repository enters this chain.
  • Which settings org policy may set (policy such as frameworks, levels, confirmation expiry, treatment of project assertions) versus settings that stay with the individual operator (credentials, local execution, budgets).
  • How org-scoped answers (for example an org security contact) relate to org policy, so a question answered once applies across repositories.

Out of scope

User-level operator configuration itself, which is being specified first.

Related: RFC-0001 September 2026 revision (#499), RFC-0002 organization question inbox (#500).

Lingua principale
Python
Stelle
22
Fork
27
Merge medio
1g 20h
PR unite (30g)
39

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 darnitdevorg/darnit

Tutte le issue di darnitdevorg/darnit

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.