npm / npm/rfcs

[TODO] Retro and cleanup

Open
#113 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
777
Forks
267
PR merge metrics
No merged PRs in 30d

Description

Several RFCs are sitting in the "accepted" folder, but actually are not slated for implementation, changed implementation, or just no longer make sense.

Let's go through all of those and identify which accepted RFCs to move to the implemented folder, which should be removed/updated, and which should be left where they are. We need to identify a good process for removal. Eg, does it take a new ratified RFC? or can we just agree to un-ratify something? I'd prefer it not be too much make-work, but also don't want to make it seem like we're not making good on a commitment, as that reduces our credibility when we do ratify RFCs.

As part of the same process, we can revisit some very old PRs that aren't going to happen for whatever reason, and close those out as well.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the RFCs in the "accepted" and "implemented" folders and inventorying old pull requests that may no longer be relevant. Determine which RFCs should move, be updated, be removed, or remain, and document an agreed removal process. Done means the RFC statuses and obsolete pull requests have been addressed through that process.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.