InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
InnerSource @ SoundCloud | RFC process
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 853
- Forks
- 206
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
SoundCloud mentions their RFC process in here:
This article from 2022 mentions the RFC approach, and points back to a description of the approach from 2018.
It should be possible to add this as Known Instance to our existing pattern, as SoundCloud are already talking about it publicly:
https://patterns.innersourcecommons.org/p/transparent-cross-team-decision-making-using-rfcs#known-instances
They seem to have extensive experience with it, if somebody from SoundCloud would review and extend our pattern that would be a great improvement too!
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
Open the existing “Transparent cross-team decision-making using RFCs” pattern and its Known Instances section, then review the linked SoundCloud article and RFC description. Add SoundCloud as a documented known instance with the relevant links; done means the pattern accurately reflects the public source material and the links work.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100