Defining / documenting a process for Requests For Help (RFH) #372

Overview

In seeing a couple teams reaching out directly to this group for assistance and guidance

• Axios: Axios Outreach #322 / [axios] support opportunity analysis #239
• node-fetch: node-fetch is looking for help #360

As well as similar request happening on twitter

• Lodash: https://twitter.com/jdalton/status/1272230153200885762
• (React) Testing Library: https://twitter.com/kentcdodds/status/1272233319573254144

It might good to define and document a standard operating procedure, or some sort of expectation of what this group can provide. For example, looking at the main README.md as one might expect for a package, there is no equivalent "Getting Started" or "Usage" section that might indicate to a reader there are docs, tools, developers, inside and related to this repo.

This way, in situations like this someone could link to this section as a one stop shop, so to speak.

Proposal

Add a section to the README, that would be ongoing and growing as this team continues to make more documentation, tools, etc available as resources for package authors. This section could be called "Resources"? I am not too picky about the name, tbh.

It should / could contain

1. Any specific policies, expectations of the team, etc
2. Link to docs table of contents (recently added in Issue/309 docs table of contents #333 )
3. Other things that are ready?