InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
InnerSource @ KPMG
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 853
- Forks
- 206
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
Interesting article on the KPMG InnerSource story covering:
- Best practices for launching an InnerSource program
- How you can use automation to make your InnerSource program more successful.
- How to use automation to productise your information security.
I would love to hear more about KPMG is approaching InnerSource, and the InnerSource patterns that they are using.
Possibly we could add some of those stories to our existing collection of patterns?
Sharing those experiences could come in different forms e.g.
- "these are existing patterns that KPMG is also using" e.g. InnerSource License or Base Documentation
- "here is a new pattern that KPMG discovered that solved an InnerSource challenge" e.g. the GHA that automatically suggests a license could be such a new pattern
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 linked KPMG InnerSource article and compare its practices with the existing patterns collection. Determine whether KPMG uses the listed patterns or has a distinct pattern to document, such as the GitHub Action that suggests a license; done means the relevant experience is captured as an agreed pattern or story.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100