InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
Call-out on website to collect Known Instances
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 853
- Forks
- 206
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
How to motivate orgs to contribute their experiences with our patterns back to the community?
A small contribution would be to list themselves as a Known Instance on the pattern, possibly with a couple of sentences about how they have used the given pattern.
A great example of such a Known Instance description from the 30 Day Warranty pattern:
Microsoft recommends this pattern as a principle - teams set their own specific time target matching their needs and confidence.
Possible Solution
backstage.io has this need call-out at the side of their website, to motivate early adopters to share publicly that they are using backstage. See screenshot.
Could we do something similar on https://innersourcecommons.org?
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 innersourcecommons.org and the existing Known Instance content, then compare the requested call-out with the Backstage example at backstage.io. Done means the website has a clear way to invite organizations to share their pattern experiences and Known Instance descriptions, matching the proposed purpose.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- content, design, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100