Open Source trumps InnerSource - Is the title backwards?

[dokuhebi]

The titles of the patterns in the project speak using a positive voice, i.e. "here are things you should do." If I'm understanding it correctly, the "Open Source Trumps InnerSource" seems to be backwards, with the title being an anti-pattern, and the content of the pattern showing ways to counter that anti-pattern.

From the Patlet

Developers disregard InnerSource projects because they consider open source projects to be superior. Introducing a required evaluation of InnerSource projects before choosing an open source project increases the likelihood of the InnerSource projects to be adopted.

Should the title of this pattern be reversed, as "InnerSource Trumps Open Source", reflecting the change the pattern is looking to make?

[welcome]

🎉 Welcome to The InnerSource Commons community, and in particular to our patterns! 🎉 We're really excited to have your input into the project! 💖

If you haven't done so already, please check out our Contributing Guidelines. If you need to connect more synchronously with members of The InnerSource Commons community, come chat with us in our Slack workspace.

[lenucksi]

The titles of the patterns in the project speak using a positive voice, i.e. "here are things you should do." If I'm understanding it correctly, the "Open Source Trumps InnerSource" seems to be backwards, with the title being an anti-pattern, and the content of the pattern showing ways to counter that anti-pattern.

I would not call that an anti-pattern, just an observation of reality. The reality may, depending on the circumstances, be anti-pattern-ish.

From the Patlet

Developers disregard InnerSource projects because they consider open source projects to be superior. Introducing a required evaluation of InnerSource projects before choosing an open source project increases the likelihood of the InnerSource projects to be adopted.

Should the title of this pattern be reversed, as "InnerSource Trumps Open Source", reflecting the change the pattern is looking to make?

I would not say so. The title aptly describes the issue as it happens. It proposes a few approaches towards resolving the perceived problem in the lower sections.
Given that people might look for issues they encountered and then look for possible approaches to deal with them (or not) the title looks helpful & appropriate to me.

[spier]

Hello @dokuhebi, great that you found our repo and thank you for helping by sharing your observation.

Naming things is hard, naming patterns is even harder :)

I did a quick scan of all pattern names in this list. Most of the time we seem to use the solution as the title, sometimes just the topic that the pattern deals with.

In the case of "Open Source trumps InnerSource" it indeed sound like we rather used the problem as the title.

This pattern is around for a while, and has not matured enough to be published in our online book at https://patterns.innersourcecommons.org/ yet. The key element missing for this are 1-2 orgs that confirm that they are using this pattern.

We can certainly take another stab at finding a better name for this pattern, when we try to get it published to the online book. We can even provide multiple aliases, to make the pattern discoverable by different names.

Is your org using an approach similar to this pattern? If you are interested in pushing this forward, I could share more information about how to improve this pattern to get it published to our online book (and possibly rename it) :)

Cheers

[dokuhebi]

Is your org using an approach similar to this pattern? If you are interested in pushing this forward, I could share more information about how to improve this pattern to get it published to our online book (and possibly rename it) :)

Going through the patterns that didn't make the book, this was one that jumped out at me as novel and we want to consider within in our org in some form. It might not be a hard-and-fast "thou must choose an InnerSource project", but more along the lines of "Check to see if there's an InnerSource project before you create your own solution".

Since the work we do has traditionally been very siloed, we have multiple identical projects limping along at various levels of maturity. One of my tasks is to help implement the above, but first, we need to give users the ability to do that search.

Thanks for the response, and I'll keep an eye on this as we're moving forward. I might help tweak the wording to match closer with what we're doing.

[spier]

Thanks for the extended feedback @dokuhebi.

Great to hear that your org is on an InnerSource journey.

If you start using any of these patterns, we would appreciate any input that you have about how to implemented it in your org, and what tweaks made sense for you given your specific context. You can always add this type of information in the "Known Instances" section of each pattern. This helps us tremendously to improve the quality of our patterns, and increase trust of the readers as they see that more and more orgs start to adopt these patterns. Thanks so much, for any time that you can spend on this!

As for this GitHub issue here, I will close it for the time being. But if you end up using and improving this pattern, we would love a pull request with your improvements. ❤️

Cheers