Add wiki implementation of InnerSource portal pattern #637
Conversation
rrrutledge
requested review from
lenucksi,
NewMexicoKid,
cewilliams,
spier,
robtuley and
yuhattor
as code owners
There was a problem hiding this comment.
Great stuff @rrrutledge!
This makes me want to find orgs that are using Backstage for this purpose, we know they exist, so that we can add this to your new Implementations section :)
| * **Technology Pre-requisites**. You must use these technologies in order to on-board to the project. | ||
| * **Getting Started**. Link to instructions on how to start using the project. | ||
| * **Chat**. Link to a chat channel to ask questions about the project. | ||
| * **Sponsoring Team**. Seeing if a team is behind the project can help others to have the confidence to use it. |
There was a problem hiding this comment.
I have seen "Maintaining Team" and "Host Team" for this in the ISC.
Is there a particular reason why you like "Sponsoring" better here?
e.g. are you worried that the "maintaining" emphasizes a notice of mine vs yours, and with that goes somewhat counter to the core idea of InnerSource?
There was a problem hiding this comment.
Changed to Host team. Yes - maintainer has some connotation that goes against parts of InnerSource.
spier
added
2-structured
Co-authored-by: Sebastian Spier <[email protected]>
Co-authored-by: Sebastian Spier <[email protected]>
| * **Technology Pre-requisites**. You must use these technologies in order to on-board to the project. | ||
| * **Getting Started**. Link to instructions on how to start using the project. | ||
| * **Chat**. Link to a chat channel to ask questions about the project. | ||
| * **Sponsoring Team**. Seeing if a team is behind the project can help others to have the confidence to use it. |
There was a problem hiding this comment.
Changed to Host team. Yes - maintainer has some connotation that goes against parts of InnerSource.
|
Note: Will be interesting to see how this benefits our readers. Who knows, maybe other patterns could benefit as well from splitting out such "Implementation" information into a separate section in the pattern. |
spier
added
the
🐅 patterns-in-the-wild
|
@rrrutledge this is live now! https://patterns.innersourcecommons.org/p/innersource-portal#implementations The formatting of this new content in gitbook looks a bit strange. Apparently gitbook formats the h4 headers the same way as h3. Not a big deal though, let's just leave it as is for now. |
…mons#637) Add wiki implementation of InnerSource portal pattern. To structure the information more clearly, this adds a new "Implementation" section to this pattern, which complements the "Solution" and "Known Instances" section.
No description provided.