InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
Pattern idea: Move to cross-team shared ownership
@MaineC is already working on this.
Since Jun 14, 2022.
- Dominant language
- HTML
- Stars
- 853
- Forks
- 206
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
In the Governance Levels we have defined "shared ownership" as a governance level where members of different teams have write access to the InnerSource project.
In organisations that traditionally have been very team- as opposed to product-/InnerSource project focused, moving to this level of ownership can cause trouble as existing information pathways are very team focused. There may be chat channels to get in touch with specific teams - but not with everyone involved with the InnerSource project. Planning may happen locally at the team level - but co-ordination across teams lacking which causes issues for those people trying to work together on the InnerSource project.
The idea of the pattern is to describe the need to integrate the cross team InnerSource project into the existing local teams.
Likely related: The pattern we have on communication infrastructure for InnerSource projects.
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.
Assessment
This issue has not been assessed yet.