Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Shared Libraries - Establish more standards for shared libraries and beyond

Ouverte
#49 0 commentaires 0 réactions 1 personne assignée Voir sur GitHub

@desi y travaille déjà.

Depuis le 13/10/2023.

Évaluation

Cette issue n'a pas encore été évaluée.

Description

Epic team-wallet-framework
2024/Q1/O2/KR1 Description:

See positive trend on contributor-docs NPS score. [boolean] (satisfaction)
We did a survey at the beginning of Q4 which resulted in 18 responses regarding contributor docs and a 22 Net Promoter Score. At the end of Q4 (while still collecting data) we had 19 responses but the Net Promoter Score decreased to -11. While the NPS decreased this could be a good sign as it indicates people have more thoroughly engaged with the content and have actual opinions now.

2023/Q4/O2/KR1 Description:

In a previous quarter, we outlined a list of topics in a Global Contributor Documentation MVP document that we felt would be sufficient for a new Shared Libraries engineer to be effective. We have already written documentation for some of these topics, and we will choose more topics that we feel would be beneficial for contributors to Shared Libraries repositories.

2023/Q4/O2/KR2 Description:

The more people contribute to the documentation — either author documents themselves or contribute to discussions — the more that the repository represents the opinions of the whole organization and not just any one team.

The Shared Libraries team will set an example by starting to refer to the docs in pull requests ourselves and also encouraging other teams (such as the extension or mobile teams) to share any code guidelines they might be keeping privately.

Langage dominant
JavaScript
Étoiles
86
Forks
42
Métriques de merge des PR
Aucune PR mergée en 30 j

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 MetaMask/contributor-docs

Toutes les issues de MetaMask/contributor-docs

Issues similaires

Plus d'issues JavaScript

Recevez les nouvelles issues par e-mail

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