Each pattern already has the "Known Instances" section, where organizations can list themselves when they are using a given pattern.
We could show this information a bit more prominently in our book.
Implementation ideas
Single Page
Maybe a single "Adopters" page at the top level, which would then list organizations, and they patterns they use e.g.
- Airbus
- InnerSource License
- Standard Base Documentation
- Maturity Model
- ...
- Europace
- Standard Base Documentation
- Communication Tooling
- ...
- Bosch
- InnerSource License
- Dedicated Community Leader
- ...
- Nike
Dedicated pages for each org
It could even be a dedicated page for each organization. Maybe that would be best?
so e.g. https://patterns.innersourcecommons.org/adopters/europace
On that pace we would only list the patterns used by Europace.
That would give the respective orgs a page that they can point to if they want to say "we use these InnerSource patterns".
And if adding themselves to the "Known Instances" of a pattern is the only way to do this, then that might motivate further contributions by other companies.
Each pattern already has the "Known Instances" section, where organizations can list themselves when they are using a given pattern.
We could show this information a bit more prominently in our book.
Implementation ideas
Single Page
Maybe a single "Adopters" page at the top level, which would then list organizations, and they patterns they use e.g.
Dedicated pages for each org
It could even be a dedicated page for each organization. Maybe that would be best?
so e.g.
https://patterns.innersourcecommons.org/adopters/europaceOn that pace we would only list the patterns used by Europace.
That would give the respective orgs a page that they can point to if they want to say "we use these InnerSource patterns".
And if adding themselves to the "Known Instances" of a pattern is the only way to do this, then that might motivate further contributions by other companies.