New Pattern: Core Team

[rrrutledge]

Is your InnerSource project difficult for people to work with, yet no one is interested in improving it? Establish a core team to take care of the project's fundamental items so that contributors are enabled to add and use the features that provide value to their scenarios.

---

View the rendered markdown.

[spier]

Thanks for the PR @rrrutledge.

I added some commits to make fix things discovered by the automated CI checks.

Weill take a deeper look at the content of the pattern in the coming days.

[NewMexicoKid]

Neat pattern, Russ! I think some more details or examples around the level of commitment/resourcing that might be needed for a core team would be helpful.

[spier]

This pattern looks really interesting already.
Thanks for sharing this @rrrutledge!

My main question is about the preconditions for this pattern, and to some extent how the project got into the state that it is in.

It almost sounds like the project in question doesn't have any team maintaining it, and maybe also no TCs yet? I am not quite sure.

What is surprizing to me about this is that I would suspect that many organizations would subscribe to a statement along the lines of:

Every project in production should have at least 1 team maintaining it.

I might also just misunderstanding something in the current pattern description, I am not quite sure.

[rrrutledge]

Thanks, all for the great feedback! I will take a look this week.

[rrrutledge]

Thanks for the help! Have a look at the conversations and updates.

[NewMexicoKid]

Changes look good to me, Russ. Thanks.

[spier]

I have reviewed this again, and suggested some changes.

The main discussion is now how and how strongly we should state that the team doesn't have an owner/maintainer before the Solution of this pattern goes into place.

Looks like we are close to resolving this.

Further I have found a couple of spelling issues that I will be committing straight away as they are not controversial.

[rrrutledge]

Thanks for this review! Responded to all feedback.

[rrrutledge]

Incorporated this feedback. What do you think?

[rrrutledge]

In the Problem section the bullets are finishing the sentence that is started before the colon.

[rrrutledge]

I removed them from this list.

[spier]

Thank you for this new pattern! 🚀

[spier]

The Core Team is now live in our book:
https://patterns.innersourcecommons.org/p/core-team

Congrats and thanks @rrrutledge!

Two questions that I forgot to ask:

• where in the mindmap would the new pattern fit best? Maybe in Adoption => Organization Challenges?
• is there any visual that would support this pattern? (using any visuals/pictures/charts in the book makes it a lot prettier but of course we don't want to add a picture just for beauty-sake, it should also support the understandability of the pattern)

Thanks again!

[rrrutledge]

🎉 Thank you!

• I think it could be under Technical Challenges or Organizational Challenges
• I can't think of any visual that would make things easier to understand. There aren't a lot of relationships to visualize in the pattern.