Direction: goals for 0.1

Abierto
#27 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
django, python

Línea de trabajo

Read the linked roadmap issues #9–#15, #23, and #24, plus ADRs 0007, 0015, 0017, 0018, and 0019 to understand the stated milestones and design decisions. The body says this issue is updated as direction changes; check its latest updates against the Roadmap view. Done means the 0.1 goals and current direction are accurately reflected here.

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

Descripción

roadmap

Long-term goal (0.1, target late January 2027)

  • A Django app runs attached (in-process) or detached (HTTP) behind the same contract, with no code change, proven by two example apps (#15).
  • A published specification with a conformance suite (#13), so other implementations can be checked against it.
  • Released on PyPI from the public repository (#23, #24).

Short-term (this week)

  • Step 2 (#9) is done: contracts, actions, implementation checks and typed errors are merged.
  • The records step 3 needed are Accepted: ADR 0007, 0017 and 0019. Step 3 (#10), the in-process transport, has started with its first PR (wire encodings); the duration type is under a design debate.
  • Step 4's plan is on #11.

How we get there

  • Spec first (ADR 0015, 0018). Design calls are settled by a recorded debate, code passes a red-team pass before review, and every change gets external review.
  • Each step's dates live in the Roadmap view. This issue is updated whenever the direction changes.
Lenguaje dominante
Python
Estrellas
1
Forks
0
Merge medio
5 h 30 min
PR fusionados (30 d)
85

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 stack314/django-neolith

Todos los issues de stack314/django-neolith

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.