Rob Tuley

> One proposal from me: > > merge this branch as is but keep all review comments in this PR open. Add a link from the pattern to this PR,...

Updates for this pattern are now continued in #489

> Look for another org that can confirm a Known Instance on this (in preparation for leveling this pattern up to "Validated") If you're still looking for another which is...

If it helps I think the conflict isn't actually as bad as GitHub UI is suggesting... ``` InnerSourcePatterns git:(book-ja) git merge main ... ... CONFLICT (content): Merge conflict in book/README.md...

> Possibly because I did "rebase and merge" to update the branch the last time in #445 Yeah maybe -- I think using a merge commit is needed and will...

Crap, I'm now wondering whether `book-ja-with-main-merged` was a terrible temporary branch name choice given it matches `book-*`, erm.. hopefully that doesn't do anything I didn't intend.

Hi @Trueblueaddie -- Thanks for the contribution! I think I understand the main thrust of the pattern here -- use continuous improvement, a series of small rather than 1 big...