InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
Pattern Idea: InnerSource Program Office
Personne n'a encore pris cette issue.
- Langage dominant
- HTML
- Étoiles
- 853
- Forks
- 206
- Merge moyen
- 1 j 23 h
- PR mergées (30 j)
- 2
Description
In our Slack this conversation happened:
Q: Is there a place where I can find a charter for an InnerSource program office?
A: The “charter for InnerSource Program Office” depends on the situation your company is in and where it wants to go — there are as many designs as there are members in the InnerSource Commons. Do you have an effort with top-level management support or more a grassroots movement? Are you trying to improve transparency, cross collaboration, communication, reuse, time to market, reduced defects, or something else? Do you have a picture of the current barriers and what capabilities need to be developed for your next low hanging fruits?
We have some patterns that either mention an InnerSource Program Office (ISPO), or are written from the perspective of an ISPO. Of particular interest could be the Explicit InnerSource Principles pattern that has a section on "Why does the organisation want to adopt InnerSource?".
However we don't have a pattern describing what an ISPO is, how to establish one, and what problems can be addressed through it.
We recognize that there may be different reasons for establishing an ISPO, as well as different charters that an ISPO may follow. However we think that it is possible to describe the main building blocks for establishing an ISPO in the form of a pattern.
Things that could support the creation of such a pattern
- list the patterns that mention an ISPO already (or similar concepts) => allows us to understand whether we even mean the same thing when talking about an ISPO in the existing patterns
- review content from the TODO Group on how to create an OSPO. That might be similar to the creation of an ISPO.
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Commencez par examiner le pattern Explicit InnerSource Principles et les guides de TODO Group OSPO liés dans l’issue. Répertoriez les patterns existants qui mentionnent un ISPO ou un concept similaire, puis utilisez cette recherche pour définir les principaux éléments constitutifs du pattern. La tâche est terminée lorsqu’un pattern explique ce qu’est un ISPO, comment en établir un et quels problèmes il peut résoudre.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Domaine
- documentation
- Type d'issue
- Documentation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 25/100