Built site for gh-pages

.nojekyll

@@ -1 +1 @@
-7d55a180
+3d5eaad3

champions/leading-cohort-calls.html

@@ -309,7 +309,7 @@ <h2 id="toc-title">On this page</h2>
   </ul></li>
   <li><a href="#between-cohort-calls" id="toc-between-cohort-calls" class="nav-link" data-scroll-target="#between-cohort-calls">Between Cohort Calls</a>
   <ul class="collapse">
-  <li><a href="#field-notes" id="toc-field-notes" class="nav-link" data-scroll-target="#field-notes">Field Notes</a></li>
+  <li><a href="#field-notes-debriefs" id="toc-field-notes-debriefs" class="nav-link" data-scroll-target="#field-notes-debriefs">Field Notes / Debriefs</a></li>
   <li><a href="#digests" id="toc-digests" class="nav-link" data-scroll-target="#digests">Digests</a></li>
   <li><a href="#coworking" id="toc-coworking" class="nav-link" data-scroll-target="#coworking">Coworking</a></li>
   <li><a href="#seaside-chats" id="toc-seaside-chats" class="nav-link" data-scroll-target="#seaside-chats">Seaside Chats</a></li>
@@ -411,24 +411,147 @@ <h3 class="anchored" data-anchor-id="guest-teachers-presentations">Guest teacher
 <section id="between-cohort-calls" class="level2">
 <h2 class="anchored" data-anchor-id="between-cohort-calls">Between Cohort Calls</h2>
 <p>Between Calls there are tasks for the Openscapes team and for the Champions teams (that the Openscapes team helps support).</p>
-<section id="field-notes" class="level3">
-<h3 class="anchored" data-anchor-id="field-notes">Field Notes</h3>
+<section id="field-notes-debriefs" class="level3">
+<h3 class="anchored" data-anchor-id="field-notes-debriefs">Field Notes / Debriefs</h3>
 <p>We ask all co-leads and assistants to write down thoughts about how the cohort went - these are internal “field notes” that will help us improve between Cohort Calls and across Cohorts.</p>
 <p>Prompts to answer include:</p>
 <ul>
 <li>Top-of-mind i.e.&nbsp;what would you tell your roommate?</li>
 <li>Brief summary of how it went</li>
 <li>Rose / Bud / Thorn - something that was good, developing, or tricky</li>
 </ul>
-<p>Write field notes in the DebriefsDigests Google doc (as of Fall 2022), with one doc for all Cohort Calls. We draft Digests in this same doc.</p>
+<p>We write field notes in the OpenscapesCohortPlanning folder: DebriefsDigests Google doc (as of Fall 2022), with one doc for all Cohort Calls. We draft Digests in this same doc.</p>
 </section>
 <section id="digests" class="level3">
 <h3 class="anchored" data-anchor-id="digests">Digests</h3>
 <p>We send digests the week following each Cohort Call (early, on Monday or Tuesday). This gives people a touch point in the week between Calls. Digests include links to the Call’s agenda, the Call’s goals, slides, and some excerpts from the shared notes.</p>
 <p>Call 1 Digest is sent via email, and following the GitHub Clinic, the rest are sent via GitHub Issues as a way to continue practicing throughout the cohort. When posting as an issue, tag the cohort GitHub team like <code>@Openscapes/2022-noaa-sefsc-summer-cohort</code> so they get email notification.</p>
-<p>We develop these in a single “DigestsDrafts” Google Doc - with the AFSC Mentors we would co-work on this during a debrief Seaside Chat.</p>
-<p>See examples:</p>
+<p>We develop these in a single “DebriefsDigests” Google Doc along with our field notes (above). With the AFSC Mentors we would cowork on this during a debrief Seaside Chat immediately after each Cohort Call.</p>
+<div class="callout callout-style-default callout-tip callout-titled">
+<div class="callout-header d-flex align-content-center" data-bs-toggle="collapse" data-bs-target=".callout-2-contents" aria-controls="callout-2" aria-expanded="false" aria-label="Toggle callout">
+<div class="callout-icon-container">
+<i class="callout-icon"></i>
+</div>
+<div class="callout-title-container flex-fill">
+Example DebriefsDigests doc template
+</div>
+<div class="callout-btn-toggle d-inline-block border-0 py-1 ps-1 pe-0 float-end"><i class="callout-toggle"></i></div>
+</div>
+<div id="callout-2" class="callout-2-contents callout-collapse collapse">
+<div class="callout-body-container callout-body">
+<section id="pre-call-prep-15-mins-before-start" class="level3">
+<h3 class="anchored" data-anchor-id="pre-call-prep-15-mins-before-start">Pre-Call prep 15 mins before start</h3>
+<p>Julie last minute checks: good internet?</p>
+<p>Stef during call</p>
+<ul>
+<li>turn on live transcript</li>
+<li>Share this Debriefs doc link with team to add async notes</li>
+<li>Set co-hosts</li>
+<li>Paste in Zoom chat: Welcome! Here’s our shared Agenda where we can all take notes, please say hello in Roll Call as you join: LINK</li>
+<li>Add slides link to chat when relevant</li>
+<li>Hit record (local); stop during breakouts &amp; restart. Add red RECORD text in doc
 <ul>
+<li>PAUSE in between, not STOP (pause makes it one recording, stop makes separate recordings)</li>
+</ul></li>
+<li>Breakout rooms - - create them 5-10 mins before opening so you can manually move ppl before opening rooms, if desired e.g.&nbsp;distribute Mentors to different rooms
+<ul>
+<li>don’t make them too early</li>
+</ul></li>
+</ul>
+<p>Stef or Julie post-call</p>
+<ul>
+<li>Upload video to CohortFolder</li>
+</ul>
+<p>Tips when presenting</p>
+<ul>
+<li>At start of call, open all your slide decks at 1st slide, especially when you’re presenting twice in one day</li>
+<li>As you start to present a deck, put slide link into chat</li>
+<li>Ask guest teachers to screenshare so we can post video</li>
+</ul>
+</section>
+<section id="debriefs" class="level3">
+<h3 class="anchored" data-anchor-id="debriefs">Debriefs</h3>
+<p><em>These are internal “field notes” that will help us improve between Cohort Calls and across Cohorts. Described in <a href="https://openscapes.github.io/approach-guide/champions/leading-cohort-calls.html#field-notes">Approach Guide</a></em></p>
+<p><strong><em>Prompts to answer include:</em></strong></p>
+<ul>
+<li><em>Top-of-mind (what would you tell your roommate?)</em></li>
+<li><em>Brief summary of how it went</em></li>
+<li><em>Rose / Bud / Thorn - something that was good, developing, or tricky</em></li>
+</ul>
+<section id="call-1" class="level4">
+<h4 class="anchored" data-anchor-id="call-1">Call 1</h4>
+<p>Julie</p>
+<ul>
+<li>&nbsp;</li>
+<li>&nbsp;</li>
+</ul>
+<p>Stef</p>
+<ul>
+<li>&nbsp;</li>
+<li>&nbsp;</li>
+</ul>
+<p>Co-lead</p>
+<ul>
+<li>&nbsp;</li>
+<li>&nbsp;</li>
+</ul>
+<p>Co-lead</p>
+<ul>
+<li>&nbsp;</li>
+<li>&nbsp;</li>
+</ul>
+</section>
+</section>
+<section id="digests-1" class="level3">
+<h3 class="anchored" data-anchor-id="digests-1">Digests</h3>
+<p><em>Call 01 Digest is sent by email. Subsequent digests are posted as GitHub Issues, following the GitHub Clinic in Call 02. Stef recommends pasting the Digest content in RStudio Visual, then look at the Source, edit, copy-paste into GitHub issue. This has required fewer edits than using a Google doc to Markdown plugin.</em></p>
+<p><em>Structure is</em></p>
+<ul>
+<li><em>“yay this thing from the call”</em></li>
+<li><em>below is a short digest</em></li>
+<li><em>(Digest 1) we’ve invited you to private Cohort channel in Openscapes Slack. Link to <a href="https://openscapes.github.io/approach-guide/approach/tooling.html#slack">orientation</a></em></li>
+<li><em>(Digest 1) we’ve sent calendar invite to Coworking in weeks between Cohort Calls. These are optional. Can use the time for team Seaside Chats</em></li>
+<li><em>(Digest 1) add your GitHub username</em></li>
+<li><em>Sign off</em></li>
+<li><em>Structured Digest content</em></li>
+</ul>
+<section id="call-1-1" class="level4">
+<h4 class="anchored" data-anchor-id="call-1-1">Call 1</h4>
+<p>Hi All!</p>
+<p>It’s exciting to start our NAME Openscapes Champions Cohort and meet you all in Zoom! We introduced a lot of concepts; we will explore them more together in the next sessions. Below is a light digest of Call 01, including a reminder about your Seaside Chat to think through your Pathway trailhead.</p>
+<p>As a reminder of tasks for next time: have your first ‘seaside chat’ with your team and discuss where are you now?&nbsp;</p>
+<p>We’ll send each of you an invitation to Openscapes Slack. Here’s a short <a href="https://openscapes.github.io/approach-guide/approach/tooling.html#slack">Slack orientation</a> to help you get comfortable. The 2023-cohort-name channel is a private space to connect with each other, and other community channels are to engage with folks from previous cohorts and the broader Openscapes Community. Joining Slack is optional, another tool for you to experiment with.</p>
+<p>Have a good week,</p>
+<p>Stef, Julie, Co-lead, Co-lead</p>
+<p><strong>Digest: Cohort Call 01 [ year-cohort-name ]</strong></p>
+<p>Openscapes_CohortCalls [ year-cohort-name ] (TODO: add link) Google folder - contains agendas, recordings, pathways&nbsp;</p>
+<p>https://openscapes.github.io/year-cohort-name/ (TODO: add link) - cohort webpage</p>
+<p><strong>Goals</strong>: We started working towards a common understanding of the Openscapes mindset and what your pathway forward looks like for your team.</p>
+<p><strong>Task</strong>: please see the Agenda doc (under Closing) (TODO: add link) for more details</p>
+<ol type="1">
+<li>Have a Seaside Chat (meet with your team) &amp; reflect together on what you’ve learned so far&nbsp;</li>
+<li>(optional) Attend Coworking. We’ve&nbsp; sent a calendar invite for DATE, TIME. Come prepared to get your own work done, ask questions, or listen in to other conversations and screensharing.</li>
+</ol>
+<p><strong>Slide Decks:</strong></p>
+<ul>
+<li>Openscapes mindset (<a href="https://docs.google.com/presentation/d/1fXgrWU5AMrZwgvpjs2J0dRT9x1Tc-IZyQIn8yPZSGM8/">slides</a>)</li>
+<li>Better science for future us (<a href="https://docs.google.com/presentation/d/1tE3pQ2ObNU68iG4uTIlMuSN4dguvn-cOvwtoM-c9L-w/">slides</a>)</li>
+</ul>
+<p><strong>A few lines from shared notes in the Agenda doc</strong></p>
+<p><em>Note: no need to add agenda subheadings or group notes under them</em></p>
+<ul>
+<li></li>
+<li></li>
+<li></li>
+</ul>
+</section>
+</section>
+</div>
+</div>
+</div>
+<p>See Digest examples:</p>
+<ul>
+<li><a href="https://github.com/nmfs-openscapes/2022-noaa-nwfsc-fall/labels/digest">2023-noaa-nwfsc-fall</a></li>
 <li><a href="https://github.com/NASA-Openscapes/2022-nasa-champions/labels/digest">2022-nasa-champions</a></li>
 <li><a href="https://github.com/Openscapes/2022-noaa-afsc/labels/digest">2022-noaa-afsc</a></li>
 <li><a href="https://github.com/Openscapes/2021-fdd/labels/digest">2021-fdd</a></li>
@@ -438,9 +561,9 @@ <h3 class="anchored" data-anchor-id="digests">Digests</h3>
 <section id="coworking" class="level3">
 <h3 class="anchored" data-anchor-id="coworking">Coworking</h3>
 <p>We started coworking with Cohorts in fall 2021. It’s a nice practice that our team does together (to work on your own but have a buddy available over Zoom) and it’s nice to offer as a practice to the Champions too. Champions have said they appreciate this as a practice to take back to their research groups and it’s also a nice way to continue to build community and a learning culture and practice talking about data needs and screensharing.</p>
-<p>We set up an hour of Coworking in between weeks; these are optional times where folks can work on their own things but also share and ask questions. Here is an <a href="https://docs.google.com/document/d/1kaMqhEIpF5flepHLS2TD3z2gSvSY5rzGOgC7IXCi-Dg/edit#">example agenda</a>.</p>
+<p>We set up an hour of Coworking in the weeks between Cohort Calls. These are optional times where folks can work on their own things but also share and ask questions. Here is an agenda template <a href="https://docs.google.com/document/d/1dT4KHvlS18rGxXVLhtvsCOWT_5kmxKgBkVwnhMf3WN0/edit?usp=drive_link">OpenscapesCoworking [ year-cohort-name ]</a>.</p>
 <div class="callout callout-style-default callout-tip callout-titled">
-<div class="callout-header d-flex align-content-center" data-bs-toggle="collapse" data-bs-target=".callout-2-contents" aria-controls="callout-2" aria-expanded="false" aria-label="Toggle callout">
+<div class="callout-header d-flex align-content-center" data-bs-toggle="collapse" data-bs-target=".callout-3-contents" aria-controls="callout-3" aria-expanded="false" aria-label="Toggle callout">
 <div class="callout-icon-container">
 <i class="callout-icon"></i>
 </div>
@@ -449,7 +572,7 @@ <h3 class="anchored" data-anchor-id="coworking">Coworking</h3>
 </div>
 <div class="callout-btn-toggle d-inline-block border-0 py-1 ps-1 pe-0 float-end"><i class="callout-toggle"></i></div>
 </div>
-<div id="callout-2" class="callout-2-contents callout-collapse collapse">
+<div id="callout-3" class="callout-3-contents callout-collapse collapse">
 <div class="callout-body-container callout-body">
 <p>We share what we’re going to work on, and then work quietly and then check in at the end as well. We also make breakout rooms for Q&amp;A if folks want to screenshare and talk things out.</p>
 <ul>
@@ -491,7 +614,7 @@ <h3 class="anchored" data-anchor-id="git-github-drop-in-help">Git / GitHub drop-
 </ol>
 <p>In the Fall 2022 NMFS Cohorts we learned that many people needed help finding where Git was installed on their Windows machines, for example. Collaborative notes with screenshots were added in Google doc: OpenscapesCoworkingCross-Cohort [ 2022-nmfs-fall ]</p>
 <div class="callout callout-style-default callout-tip callout-titled">
-<div class="callout-header d-flex align-content-center" data-bs-toggle="collapse" data-bs-target=".callout-3-contents" aria-controls="callout-3" aria-expanded="false" aria-label="Toggle callout">
+<div class="callout-header d-flex align-content-center" data-bs-toggle="collapse" data-bs-target=".callout-4-contents" aria-controls="callout-4" aria-expanded="false" aria-label="Toggle callout">
 <div class="callout-icon-container">
 <i class="callout-icon"></i>
 </div>
@@ -500,7 +623,7 @@ <h3 class="anchored" data-anchor-id="git-github-drop-in-help">Git / GitHub drop-
 </div>
 <div class="callout-btn-toggle d-inline-block border-0 py-1 ps-1 pe-0 float-end"><i class="callout-toggle"></i></div>
 </div>
-<div id="callout-3" class="callout-3-contents callout-collapse collapse">
+<div id="callout-4" class="callout-4-contents callout-collapse collapse">
 <div class="callout-body-container callout-body">
 <p>We’ve scheduled 30-minute drop-in sessions for those who want to get their computer connected to Git and GitHub. Drop in and we’ll get you set up!</p>
 <p>What should I install beforehand? <a href="https://desktop.github.com/">GitHub Desktop</a>. This is a great option and is especially good if your GitHub repos have files from multiple programs (R, Python, Excel, Word, images, data files). If you install GitHub Desktop, you will have Git installed with that. If you don’t get GitHub Desktop, then you will need to have Git installed.</p>
@@ -529,7 +652,7 @@ <h2 class="anchored" data-anchor-id="first-cohort-call">First Cohort Call</h2>
 <h3 class="anchored" data-anchor-id="beforehand">Beforehand</h3>
 <p>Set up Slack Channel with all assistants</p>
 <div class="callout callout-style-default callout-tip callout-titled">
-<div class="callout-header d-flex align-content-center" data-bs-toggle="collapse" data-bs-target=".callout-4-contents" aria-controls="callout-4" aria-expanded="false" aria-label="Toggle callout">
+<div class="callout-header d-flex align-content-center" data-bs-toggle="collapse" data-bs-target=".callout-5-contents" aria-controls="callout-5" aria-expanded="false" aria-label="Toggle callout">
 <div class="callout-icon-container">
 <i class="callout-icon"></i>
 </div>
@@ -538,7 +661,7 @@ <h3 class="anchored" data-anchor-id="beforehand">Beforehand</h3>
 </div>
 <div class="callout-btn-toggle d-inline-block border-0 py-1 ps-1 pe-0 float-end"><i class="callout-toggle"></i></div>
 </div>
-<div id="callout-4" class="callout-4-contents callout-collapse collapse">
+<div id="callout-5" class="callout-5-contents callout-collapse collapse">
 <div class="callout-body-container callout-body">
 <p>Hi All, Excited for today! We’ll share the [ Agenda ] in chat, and expect that some folks will still need to request access. We’ll ask them to share their emails in chat so that we can add them quickly - to the folder if possible. If you add access for someone, would you also add their email to [ OpenscapesParticipants ] and I’ll revisit afterwards. Thanks!</p>
 </div>