InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
Identify adopters of the RFC pattern
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 853
- Forks
- 206
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
I found the repo jakobo/rfc that contains an RFC template. as well as a description of how to run an RFC process internally in an organization.
I suggest we link to this repo from our pattern:
https://patterns.innersourcecommons.org/p/transparent-cross-team-decision-making-using-rfcs
We could also check the forks list of the repo, to see if we can identify further adopters of this company-internal RFC approach. Adding those adopters to our pattern would likely require us to contact them and ask if they want to be mentioned publicly.
See related conversation in here.
So the changes could be in two parts (or more):
- add the reference to jakobo/rfc to pattern
- add further adopters of the RFC approach - based on adopters that we can find via jakobo/rfc
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
Review the transparent cross-team decision-making using RFCs pattern and the jakobo/rfc forks list, then read the related conversation in jakobo/rfc issue #3. Identify relevant adopters, contact them before public attribution, and update the pattern only with adopters who agree to be mentioned.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100