[Bug]: No Mention of RFCs (or ANY Way to Provide Feedback) on Site
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
Summary
The React team (seems to?) prefer that new React suggestions be submitted through https://github.com/reactjs/rfcs/, rather than through GitHub issues.
That's totally reasonable, given the massive firehose of feedback you must get ... but can't you at least tell users? I had to find that link in a Reddit post 😢
I think it would make a lot more sense to link to it on https://react.dev/community ... not to mention on the GitHub Issue template (https://github.com/facebook/react/issues/new/choose), and probably a few other places too.
Page
Details
This doesn't need a ton of documentation; just something like:
To submit suggestions on React itself, first search the existing issues (link). If you can't find your suggestion there, submit it as a formal RFC (Request For Comment)(link).
Contributor guide
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.
Research direction
Start with the react.dev/community page and the GitHub issue template linked in the report. Add clear links to the React RFC process and relevant issue-search or feedback guidance in the mentioned locations, then verify that users can find where to submit suggestions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100