[Pattern Draft] Scoring Grid

[johnbeech]

Based on a conversation in the InnerSourceCommons slack, from the Sept/2021 community call:

Curious to know if we have a source code score/ranking format, which can tell us how much behind we are from being called InnerSource project?

I answered with a pattern I've been using titled "Software Project Scoring Grid" - and was prompted to write up this draft pattern based on my own knowledge and experience:

• Original Software Project Scoring Grid (Google Slides)
• Easy read branch link: patterns/1-initial/scoring-grid.md

See: #351 for more details.

Looking for feedback from the InnerSource Patterns working group, and anyone else who has chance to read this PR.

I'm happy to talk publicly about the pattern, as it is something I have developed outside of formal work, and use privately, but will decline to name specific companies for which I have shared my version of the grid with.

[spier]

@johnbeech I just let some automatic checks run over the markdown file, mostly just a linter, to check for markdown formatting issues. We use this to keep our markdown files somewhat consistent, but sometimes the linter gets ahead of itself and does a bit too much :)

Anyways, you will find some inline comments from the linter in here: https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/352/files

Hopefully those will be fairly simple to fix.

I hope to have time to review the content of the pattern in the coming days as well. Thanks for the work you put into it already!

[johnbeech]

Hopefully those [linting errors] will be fairly simple to fix.

Super easy, barely an inconvenience :)

Running these commands fixed all but one of them:

npm i -g markdownlint-cli
markdownlint --fix "**/*.md"

I hope to have time to review the content of the pattern in the coming days as well. Thanks for the work you put into it already!

Brilliant, and thank you for the writing prompts!

[spier]

Hi @johnbeech. I hope all the feedback here didn't discourage you from your pattern contribution? 😉

My ambition is to merge this pattern relatively soon, as it is still in an initial state anyways. That would allow us to share it within the ISC but also outside more widely. That way we can collect more feedback, and level up the pattern in the future.

Please let me know how we can best help you with the remaining bits.

Also I am curious about your thoughts about the questions below:

One general question I have about the proposed pattern:

How do you see the relationship and level of overlap of this Software Project Scoring Grid pattern with the "Maturity Matrix" and "Good First Project"? I know that this is asking a lot, given that both of those are pretty long reads. However I think that when we clarify this, we will have an easier time to focus this pattern on the unique ideas it contributions, in comparison to the other patterns.

[spier]

@NiallJoeMaher would be awesome to get your feedback on this PR.

If the approach that you are applying with your Score Cards is significantly different, it would be great to capture it in a new pattern instead.

For context for others: Niall shared his experience in the presentation Leveraging scorecards to scale InnerSource.