PEP 1: Replace/Update the "How to teach this" with "Documentation Updates"
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- reStructuredText
- Estrellas
- 5k
- Forks
- 1.8k
- Merge medio
- 2 d 4 h
- PR fusionados (30 d)
- 25
Descripción
I would like to suggest an update to the "How to teach this" section in PEPs to "Documentation Updates".
As part of proposing new features or changes, it would be great if PEP authors also take into consideration of what docs need to be produced/updated.
For example, would the PEP require changes to the how-to doc? Will there be new tutorial section written? What other areas of Python docs need to be updated to accommodate this new change? Are there existing docs that will become outdated and need changing? I think all of these should be taken into consideration when proposing changes so that we can have up to date documentation alongside the changes.
I think the "How to teach this" section meant to address this, but in practise I find the use of this section has been inconsistent, so I recommend making the section be more explicit about documentation artifacts to accompany the feature/change.
I also find some of the "How to teach this" in current PEPs sometimes are sounding can sound hypothetical. I'm seeing phrases like "Teachers could say so and so to students".
Instead of imagining what teachers could say, I think it would be more helpful to come up with concrete plan of what documentation can be produced to assist users in learning and adopting the feature/change.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Comienza localizando la plantilla o las directrices del PEP que definen la sección «How to teach this». Actualízala para que utilice «Documentation Updates» y proporciona indicaciones concretas para documentar funcionalidades o cambios; después, comprueba el uso actual de los PEP para garantizar la coherencia.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- python
- Área
- documentation
- Tipo de issue
- Documentación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 50/100