Shall README include a link to "Frequently requested changes"?
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Shall "Before creating an RFC" section of the README (and corresponding site section) include a link to "Frequently requested changes", so that authors can avoid creating unnecessary pre-RFCs for things that are highly unlikely to be seriously considered?
Ideally it should also link to some place where valid, but tricky, nontrivial requests that have multiple prior discussions across previous years (examples include refined types, namespaced cargo crates, delegation) are collected. It is not easy to find those discussions, especially if you don't know the terminology and that should decrease the number of iRLO pre-RFC threads where the main post is a list of previous threads.
Contributor guide
No contributing guide indexed for this repository
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 README's "Before creating an RFC" section and the corresponding site section linked in the issue. Check how those sections are generated or maintained, then add the "Frequently requested changes" link and determine whether an existing location can collect valid but tricky recurring requests; done means both sections provide the intended guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100