InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
Pattern idea: Move to cross-team shared ownership
@MaineC ya está trabajando en esto.
Desde el 14/6/2022.
- Lenguaje dominante
- HTML
- Estrellas
- 853
- Forks
- 206
- Merge medio
- 1 d 23 h
- PR fusionados (30 d)
- 2
Descripción
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.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Evaluación
Este issue todavía no se ha evaluado.