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/

Inizia esaminando il pattern esistente del portale InnerSource e i due esempi di implementazione collegati. Chiarisci l’ambito e il nome del pattern proposto, quindi documenta come un sito InnerSource possa raccogliere policy, template, documentazione, eventi, informazioni sulla community e il portale stesso; il lavoro è completo quando il nuovo pattern è sufficientemente specifico da poter essere applicato.