Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: new process documentation #682

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: new process documentation #682

wants to merge 1 commit into from

Conversation

nlf
Copy link
Contributor

@nlf nlf commented Mar 8, 2023

This is an attempt at defining a new, lighter, RFC process for the npm CLI.

Major changes from the old process include:

  • RFCs are now submitted via issues rather than pull requests
  • the RRFC is no longer a thing
  • we have defined an initial response time of 2 weeks
  • possible reasons for rejecting an RFC have been expanded for clarity
  • clarified that this repository is not how the npm CLI team prioritizes work or defines a roadmap

and the biggest change, humans who open an RFC are also expected to handle implementation of that RFC themselves. the npm CLI team is available through several different channels for guidance and assistance, but in order to prevent this repository from becoming the place good ideas come to die we absolutely must ask our community for help in implementing them.

@nlf nlf requested a review from a team as a code owner March 8, 2023 18:42
@nlf nlf requested review from lukekarrys and removed request for a team March 8, 2023 18:42
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@nlf nlf marked this pull request as draft March 9, 2023 16:28
@nlf
Copy link
Contributor Author

nlf commented Mar 9, 2023

i've changed this pull request to a draft while i work on revising some things and greatly reducing the scope of this process

@nlf nlf marked this pull request as ready for review March 20, 2023 17:09
@thescientist13
Copy link

thescientist13 commented Mar 22, 2023

Would it be possible to get a quick high level call out in the description of what (if anything) is fundamentally changing with the new process proposal compared to the current process? Or maybe this is just making institutional knowledge of the process more formal and explicitly written out?

@nlf
Copy link
Contributor Author

nlf commented Mar 22, 2023

Would it be possible to get a quick high level call out in the description of what (if anything) is fundamentally changing with the new process proposal compared to the current process? Or maybe this is just making institutional knowledge of the process more formal and explicitly written out?

of course, thank you for the reminder! i've updated the pull request description to do just that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants