Improve developer experience and productivity

Ouverte
  • Quelque chose ne va pas ?
#1,032 12 commentaires 2 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
20/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
À l'abandon
Stack technique
azure, csharp
Domaine
ci-cd, cloud, developer-experience, security

Piste de recherche

Aucun fichier, test ou point d’entrée n’est indiqué. Commencez par examiner la configuration locale et les intégrations actuelles avec Azure, Vimeo et Discord, puis étudiez les workflows de CI/CD et de gestion des secrets. Le travail sera terminé lorsque la discussion générale se transformera en un ensemble concret et clairement délimité d’améliorations, avec des résultats explicites pour l’intégration et la productivité.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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

Langage dominant
C#
Étoiles
157
Forks
59
Merge moyen
3 h 12 min
PR mergées (30 j)
4

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de DevBetterCom/DevBetterWeb

Toutes les issues de DevBetterCom/DevBetterWeb

Issues similaires

Plus d'issues C#

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.