Showcase the organizations and the patterns they use in our book

[spier]

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
  • Core Team
  • ...

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.

[spier]

I believe we did discuss somewhere if we could link from our Stories page to the patterns used by a specific org.
Implementing this feature here would allow us to do that.

[spier]

@sicot-f curious to hear your thoughts on this feature idea.

Currently listing all patterns in use at an organization is only possible like this via a search like this:
https://patterns.innersourcecommons.org/p/innersource-license?q=airbus

Given how the search results are presented in our book (we use gitbook to render the book), it isn't super easy to see all patterns in use at the given org.

Therefore I am wondering if organizations (like "Airbus"), if they could quickly point to all InnerSource patterns that they have adopted, via a dedicated URL similar to https://patterns.innersourcecommons.org/adopters/airbus

[spier]

I implemented an example of this, to see how it might look & feel like:
https://innersourcecommons.gitbook.io/innersource-patterns-staging/v/adopters-test/adopters/airbus

[spier]

@dellagustin-sap and @michael-basil you recently included SAP to the Known Instance sections of various patterns. Therefore I am wondering what you think about this idea here?

[michael-basil]

I like the idea.

My mind first went to ...

This helps take the pattern library from an academic focus to another lens of the companies and ultimately people implementing the patterns.

[spier]

I like the idea.

My mind first went to ...

This helps take the pattern library from an academic focus to another lens of the companies and ultimately people implementing the patterns.

Thanks for the feedback @michael-basil!

If you had a page like this for SAP, would you want to customize it further?
e.g. add general description about InnerSource at SAP, or pattern usage at SAP, or a logo, or similar?

Maybe this could be a v2 of this idea :) v1 could just be a plain list as shown above.

[michael-basil]

Hi @spier,

Happy to provide feedback.

I am an InnerSource practitioner, advocate, ambassador and natural change agent. These claims can be backed well I believe. Much of this is informal, but it is the pattern and energy that matter. I seek fellowship opportunities in such movements. I advocate for the existence of such programs. When they exist I volunteer even or especially to be the first through the fire so to speak.

What I am not is an InnerSource Program Officer. That would be someone like @Michadelic or @dellagustin or Michael Picht from SAP side. I feel strongly that such pages should be code-owned by such people at these companies. Or at least this is my natural inclination. I say this because they have a fuller picture of All Things InnerSource than someone like me would have relative to my situational position in such a company.

So understanding the context I can say that with SAP or whatever company I work for or whatever organization I find myself joined with in employment, I personally would love to contribute to such a customization page OR to generally help people get oriented to their First Contribution experiences with the pattern library and such.

SAP lens smell test ... Thinking of InnerSource Dojo for SAP I would further suggest that people that go through the Red and Black level would be compelled to make contributions to such a page. This will help connect the patterns to the people already motivated and situated to introduce or raise awareness of them. Language helps us scale ideas. Even attaching common language can help immensely. The Dojo Method makes this a deep experience by compelling exploratory dialog and reflection to demonstrate Green/Red/Black Level competency ... passes the smell test in my mind, seems highly useful.

As a reflective aside ... I like how @dellagustin provided some back pressure on my desire to add SAP as a known instance and put an obstacle of creating a blog article to support the claim in a high quality way reflective of the brand credibility of SAP. That he does such reflex naturally is why he is one of our Dojo Sensei of course.

I would very much like to join and contribute to the InnerSource Patterns working group if I could understand the responsibility / expectations / condition to ensure it would be a helpful and healthy pursuit.

I have been searching for such a community like this for a long time. I thought it would be Dojo Consortium, which is a great community, but it lacks the rigor and drive of cross company collaboration that InnerSource Commons and especially the pattern library bring.

So, emphatically yes!
🌿

[michael-basil]

Hello @spier,

I realized that in my excitement I gave a rather lengthy response to your question. I have resolved most of the conflations in that previous comment.

Since I haven't heard back for some time, I will try an amended and more direct/concise response:

1. Would I want to customize such a page further? Theoretically yes. Practically, definitely when I am working for a company that can provide blog support of known instances of patterns and InnerSource movement in play.

2. Regarding V2, I would see such a page as necessary to be code-owned by OSPO or relevant party for quality and delegation purposes. Is code-ownership or delegation something that the IC pattern repository has considered?

3. Do you need any assistance with the InnerSource Patterns working group or generally to review pull requests?

Warmly.
🌿