Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Generalize the maturity model pattern #536

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

Open
spier wants to merge 8 commits into main
base: main
Choose a base branch
Loading
from generalize-maturity-model

Conversation

@spier
Copy link
Member

@spier spier commented Mar 23, 2023
edited
Loading

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

  • rewrite Patlet into the 2 sentence form (1 problem + 1 solution)
  • Generalize the Solution section. Separate the definition of the maturity model from the self-assessment of the teams.
  • Formatting Forces, Context, and Resulting Context as list, to allow for easier checking

@spier spier added 2-structured Patterns with existing instances (Please see our contribution handbook for details) 📖 Type - Content Work Working on contents is the main focus of this issue / PR labels Mar 23, 2023
Copy link
Contributor

@rrrutledge rrrutledge left a 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).
Copy link
Contributor

@rrrutledge rrrutledge Mar 23, 2023

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.

Copy link
Member Author

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 :)

Copy link
Contributor

@rrrutledge rrrutledge Mar 23, 2023

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 <rrrutledge@users.noreply.github.com>
Copy link
Member Author

spier commented Mar 24, 2023

@dicortazar I would love to get your input on the changes to this pattern, given that you were one of the original authors.

@lenucksi lenucksi changed the title (削除) Generalize the marity model pattern (削除ここまで) (追記) Generalize the maturity model pattern (追記ここまで) Apr 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@rrrutledge rrrutledge rrrutledge left review comments

@lenucksi lenucksi Awaiting requested review from lenucksi lenucksi is a code owner

@NewMexicoKid NewMexicoKid Awaiting requested review from NewMexicoKid NewMexicoKid is a code owner

@cewilliams cewilliams Awaiting requested review from cewilliams cewilliams is a code owner

@robtuley robtuley Awaiting requested review from robtuley robtuley is a code owner

Assignees

No one assigned

Labels

2-structured Patterns with existing instances (Please see our contribution handbook for details) 📖 Type - Content Work Working on contents is the main focus of this issue / PR

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /