Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Organization-level policy source for operator configuration

Abierto
  • ¿Algo no está bien?
#503 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
tooling

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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).

Lenguaje dominante
Python
Estrellas
22
Forks
27
Merge medio
2 d 28 min
PR fusionados (30 d)
40

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de darnitdevorg/darnit

Todos los issues de darnitdevorg/darnit

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.