silverstripe / silverstripe/developer-docs
Delete docs about RFC process - or start following the process again
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7
- Forks
- 74
- Avg merge
- 1d 14m
- Merged PRs (30d)
- 6
Description
There are some docs about an RFC process that we haven't followed for a long time - especially the "what next" section which talks about a monthly catchup that just doesn't happen.
We should either delete these misleading docs, or start following an RFC process again.
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 RFC process documentation at docs.silverstripe.org/en/5/project_governance/request_for_comment/ and check whether a current RFC process exists elsewhere in the developer documentation. The work is done when the misleading guidance is either removed or updated to accurately describe a process that the project can support.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100