-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generalize the maturity model pattern #536
base: main
Are you sure you want to change the base?
Conversation
…ity model from the self-assessment of the teams.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great! We need a way to have this idea of the pattern and then specific instances of implementations of the pattern that people can lift and reuse for themselves.
Teams sharing InnerSource learnings run into misunderstandings as they are not | ||
aware of their respective level of InnerSource adoption. | ||
* Teams sharing InnerSource learnings run into misunderstandings as they are not aware of their respective level of InnerSource adoption. | ||
* Teams believe that "it's all about migrating to a shared software development [forge](https://en.wikipedia.org/wiki/Forge_%28software%29)" (GitLab, GitHub, or Bitbucket being well known examples of such forges). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just remove this line. It's too specific.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean just the line 30, right?
Interestingly the fits the discussion around what qualifies "ThinnerSource" in slack :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, line 30 🙂
Co-authored-by: rrrutledge <[email protected]>
@dicortazar I would love to get your input on the changes to this pattern, given that you were one of the original authors. |
By generalizing the marity model pattern we hope to allow for other orgs to list themselves as adopters of this pattern, even if they may be using a maturity model that is different from the one proposed in this pattern.
At the same time we think that providing a maturity model as part of this pattern has its merits, as it allows readers to understand in greater depth what this goals of this pattern are.
Key changes