Shared Libraries - Establish more standards for shared libraries and beyond
@desi is already working on this.
Since Oct 13, 2023.
Assessment
This issue has not been assessed yet.
Description
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.
- Dominant language
- JavaScript
- Stars
- 86
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MetaMask/contributor-docs
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
MetaMask/contributor-docs#164 ·
-
category-documentation github-migration-triaged team-wallet-framework wf-documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MetaMask/contributor-docs#115 · 1 comment ·
-
issueOpen
Difficulty 5/5 Over a week Newbie friendliness 10/100
MetaMask/contributor-docs#169 ·
-
team-core-platform
Difficulty 4/5 3-5 days Newbie friendliness 45/100
MetaMask/contributor-docs#157 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
MetaMask/contributor-docs#142 ·
All issues in MetaMask/contributor-docs
Similar issues
-
factory-active factory-automatic harness/codex task-bug-reproduction-success task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
vercel/ai#21582 · 3 comments ·
Maintainers usually reply within 1 day
-
ux
Difficulty 1/5 Under an hour Newbie friendliness 90/100
rr-djk/rr-djuikoo.com#53 ·
Maintainers usually reply within 1 day
-
new spec review
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
w3c/browser-specs#2666 · 1 comment ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
thim81/openapi-format#238 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
decentespresso/dye2#13 ·