Removing inaccessible pattern: What Before How or Services Documentation

[spier]

I was not able to reach the author of this pattern or access the Google Doc.
If really nobody has access to this any more, let's remove this pattern from the list.

Plea for help:

Does any of the ISC old-timers have access to this Google Doc?
https://docs.google.com/document/d/1_N1wsQeDusfIcNy-O2ZXenY3PL7ZbvkUDRZxGUuegZw/edit?usp=drive_web

Timer:

Let's give this until end of next week or so, but if I don't hear back by then I would merge this PR.

[NewMexicoKid]

Sorry, Sebasian--I have no access rights. It's probably okay for us to let this one go. On the other hand, we might want to start a place to collect ideas to explore for future patterns. The title even by itself is provocative -- What before How -- pertaining to Services Documentation. Not in the main README but just a sort of scratch pad for ideas.

…

On Sat, Jan 30, 2021 at 5:05 AM Sebastian Spier ***@***.***> wrote: I was not able to reach the author of this pattern or access the Google Doc. If really nobody has access to this any more, let's remove this pattern from the list. Plea for help: Does any of the ISC old-timers have access to this Google Doc? https://docs.google.com/document/d/1_N1wsQeDusfIcNy-O2ZXenY3PL7ZbvkUDRZxGUuegZw/edit?usp=drive_web Timer: Let's give this until end of next week or so, but if I don't hear back by then I would merge this PR. ------------------------------ You can view, comment on, or merge this pull request online at: #284 Commit Summary - Removing inaccessible pattern: What Before How or Services Documentation File Changes - *M* README.md <https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/284/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5> (1) Patch Links: - https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/284.patch - https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/284.diff — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub <#284>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AARUJ4G6QI5YKWWSMLB44OLS4PRZDANCNFSM4W2GSACA> .

-- Tim Yao - [email protected] <[email protected]> <[email protected]> aka NewMexicoKid at National Novel Writing Month, http://nanowrimo.org <http://www.nanowrimo.org> co-Municipal Liaison for the Illinois::Naperville region NaperWriMo - http://naperwrimo.org

[spier]

Thanks for the confirmation @NewMexicoKid.

As for another place to collect ideas, I think a very lightweight Donut pattern is already a pretty good way to collect a pattern idea.

Personally I wouldn't create another place to collect ideas for these reasons:

• just a title alone doesn't provide enough information for anybody else to expand the idea into a pattern.
• it doesn't seem like we have a good track-record of turning existing Donuts into real patterns. So maybe collecting ideas isn't actually as impactful as we would like it to be?

Of course if you are passionate about the scratch-pad approach and still want to try it out: Just go for it :)

[NewMexicoKid]

In the early days, we spent some time (at ISC Summits) brainstorming ideas for patterns by collecting one-line pattern titles. Some of these did indeed get expanded into donuts or even full patterns (e.g., Trusted Committer started out this way). Donuts are great for when someone has a full problem to solve or a partial solution to share; I'm just thinking that, especially with a new crowd of InnerSource practitioners interested in patterns, it might be useful to do another brainstorming exercise to quickly capture ideas in a single place, not requiring even the sketchy info that a donut would require. This list could then help seed and drive conversations either in slack or in live meetings to take the one-liners and flesh them out. Cheers, --Tim

…

On Sat, Jan 30, 2021 at 12:44 PM Sebastian Spier ***@***.***> wrote: Thanks for the confirmation @NewMexicoKid <https://github.com/NewMexicoKid>. As for another place to collect ideas, I think a very lightweight Donut pattern is already a pretty good way to collect a pattern idea. Personally I wouldn't create another place to collect ideas for these reasons: - just a title alone doesn't provide enough information for anybody else to expand the idea into a pattern. - it doesn't seem like we have a good track-record of turning existing Donuts into real patterns. So maybe collecting ideas isn't actually as impactful as we would like it to be? Of course if you are passionate about the scratch-pad approach and still want to try it out: Just go for it :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#284 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AARUJ4CLMYLX75NLOJVTKJ3S4RHRJANCNFSM4W2GSACA> .

-- Tim Yao - [email protected] <[email protected]> <[email protected]> aka NewMexicoKid at National Novel Writing Month, http://nanowrimo.org <http://www.nanowrimo.org> co-Municipal Liaison for the Illinois::Naperville region NaperWriMo - http://naperwrimo.org

[spier]

That is an interesting idea.

I have heard about these brainstorming sessions that the community used to have at the in-person summits before.

Finding ways to replace such brainstorming sessions in an online format certainly sounds like an interesting challenge, and maybe your scratch-pad approach can help with that. Feel free to try it out at the next virtual summit :)

[spier]

I was able to reach the original author of this pattern, and unfortunately the Google Doc linked in our README is no longer accessible. However he suggest that this here is an expanded version (not in the pattern format) https://www.adaptivechangedesign.com/post/business-service-facts-vital-change-insights

I will merge this PR to finish the clean-up.