3 ms·
Setting up teams for inner source work can be done and tends to earn itself back, but most teams aren’t set up for this. Typical solutions for the issues you me
by Joeri 5y ago
Setting up teams for inner source work can be done and tends to earn itself back, but most teams aren’t set up for this. Typical solutions for the issues you mention: trusted committers to review and merge work without having that role burden the whole team, contribution guidelines to set standards, 30 day warranty to avoid getting code dumped in their lap that’s broken but also avoid having too many owners of parts of the codebase.
Anyway, I would recommend going to the inner source commons website and reading a few of the success stories like paypal’s.
- sokoloff 5y agoInteresting and I’d love to hear more about this “30-day warranty” concept. How’s that work in practice and how do you use it to avoid having too many owners? (Does it revert to the original system owners after 30 days?)
- Joeri 5y agoThe full explanation is on the inner source patterns website: https://patterns.innersourcecommons.org/p/30-day-warranty https://patterns.innersourcecommons.org/p/30-day-warranty