InnerSourceCommons
InnerSource @ SoundCloud | RFC process
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!
@pcalcado as you are the author of one of the docs above, would you be able to help us find somebody at SoundCloud that can tell us more about their RFC approach? Hope you don't mind the direct approach :)
The description of the approach from 2018 actually mentions further orgs that use (or at least have used) an approach like this at some point it time:
It adds some color and background on the key points of this process based on my experience implementing it at ThoughtWorks, SoundCloud, DigitalOcean, and now Meetup.
Btw @tsadler1988 if you haven't seen the docs above yet, I am sure you will absolutely love them.
The description of the approach goes into a lot of detail and provides anecdotal evidence for why their RFC process is structured the way it is.
@GavinMBell I found this quote in an older article by @pcalcado:
The NABC format was introduced to SoundCloud by Gavin Bell, who has learned about it during his time on research labs. I was very skeptical of it at first, but nowadays it is my go-to format for proposals.
Would you like to add anything more about how the RFCs were applied at SoundCloud?
Why, you may ask. Good question! :) We are looking to improve our InnerSource pattern called Transparent Cross-Team Decision Making using RFCs. And the SoundCloud implementation of this pattern would be great evidence of this approach being applied in the wild.