Improve developer experience and productivity

Abierto
  • ¿Algo no está bien?
#1,032 12 comentarios 2 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
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
azure, csharp
Área
ci-cd, cloud, developer-experience, security

Línea de trabajo

No se mencionan archivos, pruebas ni puntos de entrada. Comienza revisando la configuración local y las integraciones actuales con Azure, Vimeo y Discord; después, examina los flujos de trabajo de CI/CD y de gestión de secretos. El trabajo estará terminado cuando la discusión general se convierta en un conjunto concreto y delimitado de mejoras con resultados claros para la incorporación y la productividad.

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

Descripción

  • DevBetter as a project provides value to its community and to its owner, but one can imagine that that value is not counted in the billions of dollars (not yet 😜). At the moment, for DevBetter community members and its owner (and agents), time spent working on the project provides limited ROI.
  • DevBetter does not really have a pool of dedicated maintainers for which DevBetter work is a high priority. Which is normal when taking into consideration the previous point.
  • The DevBetter project, though not very large in size, does rely on a number of third party services (Azure, Vimeo, Discord...).
  • At the moment the repo is open source and we have to be very careful about secrets and credentials leaking out.
  • Getting DevBetter up and running locally is not the most complicated thing in the world but is also not exactly trivial.
  • Given all of the above, individual development efforts by community members and the owner is probably not as efficient as it could be.

If we want the DevBetter project to be maintained and developed to a certain level of quality by community members, which is no doubt one of the main benefits of having it be open source, getting up and running should be as easy and as fast as possible. My personal experience so far is that it isn't, for a number of reasons.

I've created this issue so that we can all come up with some ideas, hopefully some low-hanging fruits, that could potentially improve developer experience, speed up onboarding and generally increase development ROI.

One of my personal pain point has been working with features that integrate with 3rd party services, but I believe there is room for improvement in the CI/CD process and other areas as well.

Lenguaje dominante
C#
Estrellas
157
Forks
59
Merge medio
3 h 12 min
PR fusionados (30 d)
4

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 DevBetterCom/DevBetterWeb

Todos los issues de DevBetterCom/DevBetterWeb

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.