InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
InnerSource @ DAZN | "Building A DX Team: Lessons Learned"
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 853
- Forks
- 206
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
This post from DAZN Engineering contains various stories that could be cross-referenced with existing patterns:
https://medium.com/dazn-tech/building-a-dx-team-lessons-learned-4a66446088bc
There are other posts from DAZN as well that may be related e.g.
https://medium.com/dazn-tech/developer-experience-dx-at-dazn-e6de9a0208d2
https://medium.com/@nodefortytwo/what-is-platform-engineering-a6e8bff1d9c6
https://medium.com/dazn-tech/integrating-backstage-at-dazn-b8ef5268b347
Who knows, maybe even some new patterns could be extracted?
What I spotted in the article:
- DAZN InnerSource Marketplace => InnerSource Portal, maybe also Gig Marketplace (also an example of using Backstage for these)
- RFC process => Transparent Cross-Team Decision Making using RFCs
- likely more ...
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 DAZN Engineering article and compare its examples with the cited InnerSource patterns and related DAZN posts. Identify practices that are already covered versus genuinely distinct, then document any accepted new patterns or cross-references; completion requires a decided set of contributions rather than an open-ended list of possibilities.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100