InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
InnerSource @ Intuit
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 853
- Forks
- 206
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
Shagun Bose from Intuit gave a talk about "What's the deal with InnerSource" at the GHC 2022.
Summary in this twitter thread.
Some ideas for possible pattern connections:
tweet 1 sounds like a new pattern:
InnerSource Pattern by InnerSource Commons, a repeatable proven solution to an InnerSource constraints.
For recognition, @Intuit implements 2 tiers - InnerSource badge and automated system to add contributors into the repo's Readme
tweet 2 might be an addition to the Standard Base Documentation pattern. Possibly also related to the Good First Projects pattern.
For standard base documentation, they asked feedback from their devs to come up with a list of requirements. To remove the barriers to entry for InnerSource, they created an automated system to add missing docs and created a readiness report for all their repos
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 by reviewing the GHC 2022 summary and linked Twitter threads, then compare their ideas with the Standard Base Documentation and Good First Projects patterns. Determine whether the Intuit practices warrant a new pattern or additions to an existing one; done means the relevant pattern documentation and connections are clearly recorded.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100