Pattern idea: InnerSource Site / InnerSource Handbook

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

• https://innersource.flutter.com
• https://devguide.trimble.com/innersource/introduction/

Comece revisando o padrão existente do portal InnerSource e os dois exemplos de implementação vinculados. Esclareça o escopo e o nome do padrão proposto e, em seguida, documente como um site InnerSource pode reunir políticas, templates, documentação, eventos, informações da comunidade e o próprio portal; considera-se concluído quando o novo padrão for específico o suficiente para ser aplicado.