Skip to content
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

Board Report 2022-11 #486

Merged
merged 18 commits into from
Nov 23, 2022
Merged

Board Report 2022-11 #486

merged 18 commits into from
Nov 23, 2022

Conversation

robtuley
Copy link
Collaborator

@robtuley robtuley commented Nov 21, 2022

Content for Nov 2022 board report:

2022-11.md

@robtuley robtuley self-assigned this Nov 21, 2022
@robtuley robtuley added the ⚙️ Type - Meta Improving how we collaborate in this repo is the main focus of this issue / PR label Nov 21, 2022
@spier
Copy link
Member

spier commented Nov 22, 2022

Great stuff @robtuley! Already see a couple of angles in your report that are new, which is great!

I already got the traffic numbers and will add them in the evening, together with some other feedback.

Copy link
Member

@spier spier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great stuff @robtuley!

I left some input with further details as suggestions to your PR.
Will merge 1-2 minor ones myself, that don't require further discussion.

The points under "Next Goals" are probably most interesting for us as TCs to discuss further.

meta/boardreports/2022-11.md Show resolved Hide resolved
meta/boardreports/2022-11.md Outdated Show resolved Hide resolved
meta/boardreports/2022-11.md Outdated Show resolved Hide resolved
meta/boardreports/2022-11.md Outdated Show resolved Hide resolved
## Next Goals

* Clear down pending PRs?
* Expand the content in the book to include more existing but less mature patterns?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer to keep the "included in the booK" as a gatekeeper for a minimum level of quality/maturity.

Currently that gate is: "has at least 1 Known Instance"

An alternative or additional goal could be:

  • level up more patterns from Initial to Mature (to get them published in the book).
  • maybe even list the patterns here where we see the best opportunities to do so

Copy link
Collaborator Author

@robtuley robtuley Nov 22, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer to keep the "included in the booK" as a gatekeeper for a minimum level of quality/maturity.

Very much agree.

level up more patterns from Initial to Mature (to get them published in the book).

Yes this is a better goal.

These goals as drafted where a rather vague stub tbh, looking back at the goals from last report:

help the Japanese InnerSource Community to channel new patterns into our repo (in English + Japanese)
reduce the time that PRs stay in review
reduce the time it takes from posting a pattern idea to opening a first PR (lower the barrier for entry)
actively reaching out to orgs that already talk about their InnerSource work publicly. Help them to contribute their patterns. => see Patterns in the Wild
hardening the patterns further, by finding 3 known instances for some of the patterns in the book (improves quality and increases trustworthiness of the patterns) => see Known Instances Collection
level-up more patterns from the GitHub repo to the book (i.e. from Level 1 to Level 2). The patterns in the book seem to get more exposure.
trying out other ways to make the patterns easier to discover (e.g. different pattern categories; index pages at the end of the book or similar)
try out other forms of engagement around patterns (office hours, "pattern of the month", etc)

That's quite a lot of goals 😄 . Broadly I read that as a funnel-ish...

  1. increase number of people viewing patterns ("easier to discover", pattern of month, categories)
  2. increase number & quality of patterns
    • increase number of people thinking to contribute ("patterns in wild", "known instances")
    • increase probability of successful contribution ("reduce review time", "lower barrier of entry")
    • optimise the existing content (level-up more patterns, known instances again)

If you were to pick one...? I tend to be an optimiser sort of person rather than a sociable sort of person so its not that surprising optimise content would be my instinct ha.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great list of patterns that are "close to make it to level 2".
The low-hanging fruits here should be the ones that have a Known Instance already, as that info is often hard to get.

That might reduce the list to:

  • extensions-to-manage-contributions-at-scale.md - should be quite easy. I recall that we mostly kept this one in Initial to give the community time to review/harden this pattern before it goes into the book
  • governance-levels.md - should also be easy, given that we have somebody here who can drive this ;)
  • release-process.md - I don't quite remember why we left this in Initial when we merge it's PR back then. would have to check.
  • contained-innersource.md - this has been around for a long time. best chance might be to activate the two authors again and see if they want to bring it over the finish line.
  • Disclaimer: I did not check if there are any other Initial patterns that have a Known Instance

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you were to pick one...? I tend to be an optimiser sort of person rather than a sociable sort of person so its not that surprising optimise content would be my instinct ha.

My own instinct is also to optimize. However I feel like I have invested too much time into that area already, and too little in getting more people involved. Therefore I am spending more time on the "sociable" bits these days. This is work in progress though, as I don't feel I/we have found a good way yet to engage more people in this project yet.

meta/boardreports/2022-11.md Outdated Show resolved Hide resolved
spier and others added 7 commits November 22, 2022 14:46
Co-authored-by: Yuki Hattori <15963767+yuhattor@users.noreply.github.com>
Co-authored-by: Sebastian Spier <github@spier.hu>
Co-authored-by: Sebastian Spier <github@spier.hu>
Co-authored-by: Sebastian Spier <github@spier.hu>
Co-authored-by: Sebastian Spier <github@spier.hu>
@robtuley robtuley marked this pull request as ready for review November 22, 2022 20:33
meta/boardreports/2022-11.md Outdated Show resolved Hide resolved
meta/boardreports/2022-11.md Outdated Show resolved Hide resolved
meta/boardreports/2022-11.md Outdated Show resolved Hide resolved
@robtuley
Copy link
Collaborator Author

@spier -- its very polite leaving suggestions but by all means just commit direct to branch to correct/add I will look at diffs etc and rasie comment if disagree.

Copy link
Member

@spier spier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for all your work on this Rob!

@robtuley robtuley merged commit cb5b50d into main Nov 23, 2022
@robtuley robtuley deleted the board-report-nov-2022 branch November 23, 2022 19:47
@yuhattor
Copy link
Member

@robtuley and @spier,
Thank you for such a wonderful report!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⚙️ Type - Meta Improving how we collaborate in this repo is the main focus of this issue / PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants