[Team Process Documentation] Taking ideas from proposal to "implemented"

[Emuentes]

As we create tools, what steps do we need to make sure we follow to get the most out of our contributions.

This issue began as part of the discussion of this issue:
#161

The issue has been addressed by @Eomm by creating the tool that the issue described as proposed by @ljharb.

@ljharb suggested that we should open PRs to implement the tool in the projects that would benefit most and as use of the tool increases across the ecosystem we can consider moving it from @Eomm's repo to the Node or NPM ecosystems as desired or needed by the teams.

This thread is to discuss the above approach and any alternatives or missing pieces in our strategy for evolving our contributions from the proposal phase to an implemented solution that brings value to the community.

[Emuentes]

The first example of this process evolving is here:
#192

As that process is completed we can validate the practical steps to consider from tool to tool.

[Emuentes]

So far the process for on-boarding a new tool appears to be:

1. Propose the tool here in the Package Maintenance Team repo by adding an issue describing your idea

2. Put your proposal on the agenda for the next meeting

3. Discuss with the group during our team meeting so we can plan next steps. (See Calendar for date/time)

4. Build the tool as a public GitHub repo that follows Package Maintenance Team standards

• https://github.com/nodejs/package-maintenance/blob/master/docs/drafts/Baseline%20practice%20-%20Document%20support%20levels.md

5. Release your tool as a public NPM module (following our documented steps for publishing modules)

6. As Needed: Follow the steps for transferring you repo into the org.

@Eomm @ljharb As folks who thumbs-upped this issue:

Do y'all feel it would be beneficial to build out a documentation section for this?
I created a PR for an example document: #202

I know the process wasn't particularly clear, before we gave it our first attempt, what the appropriate steps would be. I think it would bring value to have a documented example case of our process in action!

[mhdawson]

PR to land merged, close.