micropython / micropython/micropython-lib

The number of open PRs is... kinda concerning.

Abierto
#474 5 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Lenguaje dominante
Python
Estrellas
2.9k
Forks
1.1k
Merge medio
7 d 6 h
PR fusionados (30 d)
3

Descripción

On the one hand, I reluctantly get it. This is open-source volunteerism. We're all eternally thankful for the continual oversight by @jimmo and @dpgeorge. They deserve all our thunderous applause for their many years of die-hard service to the cause of a usable MicroPython stack.

On the other hand... the last repository commit was over a month-and-a-half ago and there are 80 outstanding PRs (as of this writing) – most of which haven't even received a single comment. I'm concerned about the health of this repository and the subprojects housed under it – especially aioble, @jimmo's blessed API that makes Bluetooth viable under MicroPython.

aioble has a plethora of open issues, many with known resolutions and working open PRs. Moreover, aioble alone has 10 open uncommented PRs by community stalwart @andrewleech. Like, I feel for this guy! That's enthusiastic commitment right there. And... we're squandering all of that enthusiastic commitment and community goodwill. You know?

Merging PRs in a (reasonably) timely manner is absolutely the most critical facet of open-source project management. We can drop everything else – even testing. But when we drop PR merging, that's really the final death knell.

If we don't have even the spare manpower to review and accept work that others are freely submitting of their own accord and scarce time, the road ahead to 2022 and beyond is clouded with uncertainty. Let's part by the clouds by either:

  • Closing obsolete and broken PRs with merge conflicts.
  • Merging recent and working PRs with no merge conflicts that pass rudimentary scrutinity. Bonus points for PRs with one or more working tests.

Thanks again for all the h0t libs, @jimmo and @dpgeorge. Happy New Year! 🎆

Guía de contribución

Abrir la guía de contribución

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.

Línea de trabajo

Comienza revisando las 80 pull requests pendientes del repositorio, prestando especial atención a las 10 PRs de aioble sin comentarios mencionadas en este issue. Comprueba si hay cambios obsoletos, conflictos de merge, resultados de pruebas rudimentarios y contribuciones funcionales; se considerará terminado cuando las PRs relevantes estén cerradas o fusionadas después de la revisión.

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

Evaluación

Stack tecnológico
python
Área
developer-experience
Tipo de issue
Refactorización
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
15/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.