InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
Pattern idea: InnerSource Site / InnerSource Handbook
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 853
- Forks
- 206
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
Summarizing from a slack conversation:
We have a pattern for an innersource portal, but no pattern for a developer portal to layer on top of it to act as a source of truth for all things innersource and developer at orgs.
By having information in one place with the innersource portal it drives more traffic to the innersource portal. So adding policies, templates, documentation, an events calendar, community information, etc to a website with an innersource portal being a page on that website instead of a stand alone item.
Summary/Essence of the pattern:
Have a thing that points to all your InnerSource things :)
Brainstorming names and alises for this pattern:
- InnerSource Site
- InnerSource Handbook
- InnerSource Landing page
- Source of Truth
Open online examples of implementations of this 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 by reviewing the existing InnerSource portal pattern and the two linked implementation examples. Clarify the proposed pattern's scope and name, then document how an InnerSource site can gather policies, templates, documentation, events, community information, and the portal itself; done means the new pattern is specific enough to apply.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100