Built site for gh-pages

.nojekyll

@@ -1 +1 @@
-c6185961
+dd0799bf

index.html

@@ -7,7 +7,7 @@
 <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
 
 <meta name="author" content="NASA Openscapes Team">
-<meta name="dcterms.date" content="2024-06-19">
+<meta name="dcterms.date" content="2024-07-10">
 
 <title>EarthData Cloud Cookbook - NASA Earthdata Cloud Cookbook</title>
 <style>
@@ -589,7 +589,7 @@ <h1 class="title">NASA Earthdata Cloud Cookbook</h1>
     <div>
     <div class="quarto-title-meta-heading">Published</div>
     <div class="quarto-title-meta-contents">
-      <p class="date">June 19, 2024</p>
+      <p class="date">July 10, 2024</p>
     </div>
   </div>
 

policies-admin/add-folks-to-2i2c-github-teams.html

@@ -591,7 +591,8 @@
     <h2 id="toc-title">On this page</h2>
 
   <ul>
-  <li><a href="#individual-long-term-access" id="toc-individual-long-term-access" class="nav-link active" data-scroll-target="#individual-long-term-access">Individual long-term access</a>
+  <li><a href="#workshop-access-with-a-shared-password" id="toc-workshop-access-with-a-shared-password" class="nav-link active" data-scroll-target="#workshop-access-with-a-shared-password">Workshop access with a shared password</a></li>
+  <li><a href="#individual-long-term-access" id="toc-individual-long-term-access" class="nav-link" data-scroll-target="#individual-long-term-access">Individual long-term access</a>
   <ul class="collapse">
   <li><a href="#share-google-form-with-users-needing-long-term-access" id="toc-share-google-form-with-users-needing-long-term-access" class="nav-link" data-scroll-target="#share-google-form-with-users-needing-long-term-access">1. Share Google Form with users needing long-term access</a></li>
   <li><a href="#google-form-response-setup" id="toc-google-form-response-setup" class="nav-link" data-scroll-target="#google-form-response-setup">2. Google Form response setup</a></li>
@@ -644,10 +645,14 @@ <h1 class="title">How to Add Folks to the 2i2c Hub</h1>
 <ol type="1">
 <li><a href="#individual-long-term-access">Individually-managed long-term access for NASA-Openscapes mentors and others</a></li>
 <li>Access for participants in a NASA-Openscapes champions cohort</li>
-<li>Access for participants in a workshop</li>
+<li>Access for participants in a workshop using GitHub teams</li>
+<li><a href="../policies-admin/leading-workshops.html#workshop-hub-access-via-shared-password">Access for participants in a workshop using a shared password</a></li>
 </ol>
-<p>Access for for cohorts and workshop participants currently uses the <a href="#adding-workshop-participants-or-champions-cohorts-as-a-batch">same workflow</a>.</p>
-<p>We are also working on a method to give just-in-time access for specific workshops without using GitHub Teams or other managed access. Details of this process will be added as we finalize it.</p>
+<section id="workshop-access-with-a-shared-password" class="level3">
+<h3 class="anchored" data-anchor-id="workshop-access-with-a-shared-password">Workshop access with a shared password</h3>
+<p>If you are hosting a workshop that has a large number of particpants, especially if they are not all comfortable with GitHub and particpants do not require access to the Hub when the workshop is complete, use the <a href="../policies-admin/leading-workshops.html#workshop-hub-access-via-shared-password">“shared password” access method</a>. This access method allows instructors to share a single password with learners at the start of the workshop, which they can use to log on the the Hub, and eliminates the need to invite users to join the GitHub organization.</p>
+<p>Access for for cohorts and workshop participants using GitHub teams currently uses the <a href="#adding-workshop-participants-or-champions-cohorts-as-a-batch">same workflow</a>.</p>
+</section>
 <section id="individual-long-term-access" class="level2">
 <h2 class="anchored" data-anchor-id="individual-long-term-access">Individual long-term access</h2>
 <p>Individuals are given long-term access by adding them as members of the <a href="https://github.com/orgs/NASA-Openscapes/teams/longtermaccess-2i2c">LongtermAccess-2i2c team in the NASA-Openscapes organization</a>.</p>
@@ -767,7 +772,7 @@ <h2 class="anchored" data-anchor-id="adding-champions-cohorts-as-a-batch">Adding
 </div>
 </div>
 <div class="callout-body-container callout-body">
-<p>We have a newly developed process for giving people short-term access to the hub for workshops, with low overhead for instructors and particpants. This process removes the need to add people to a GitHub team, and gives participants “just in time” access to a special workshop hub with a username and shared workshop-specific password. Policies and instructions for this currently being developed.</p>
+<p>We have a newly developed process for giving people short-term access to the hub for workshops, with low overhead for instructors and particpants. This process removes the need to add people to a GitHub team, and gives participants “just in time” access to a special workshop hub with a username and shared workshop-specific password. Instructions for this simplified setup are <a href="../policies-admin/leading-workshops.html#workshop-hub-access-via-shared-password">here</a>.</p>
 </div>
 </div>
 <p>We use a dedicated GitHub Organization - <a href="https://github.com/nasa-openscapes-workshops">nasa-openscapes-workshops</a> - to manage access, with <a href="https://github.com/orgs/nasa-openscapes-workshops/teams">GitHub Teams</a> for Champions Cohorts and certain workshops.</p>

policies-admin/leading-workshops.html

@@ -559,7 +559,8 @@ <h2 id="toc-title">On this page</h2>
   <ul>
   <li><a href="#using-the-openscapes-2i2c-hub-in-a-workshop" id="toc-using-the-openscapes-2i2c-hub-in-a-workshop" class="nav-link active" data-scroll-target="#using-the-openscapes-2i2c-hub-in-a-workshop">Using the Openscapes 2i2c Hub in a workshop</a>
   <ul class="collapse">
-  <li><a href="#how-to-add-folks-to-the-2i2c-hub" id="toc-how-to-add-folks-to-the-2i2c-hub" class="nav-link" data-scroll-target="#how-to-add-folks-to-the-2i2c-hub">How to Add Folks to the 2i2c Hub</a></li>
+  <li><a href="#workshop-hub-access-via-github-teams" id="toc-workshop-hub-access-via-github-teams" class="nav-link" data-scroll-target="#workshop-hub-access-via-github-teams">Workshop Hub Access via GitHub Teams</a></li>
+  <li><a href="#workshop-hub-access-via-shared-password" id="toc-workshop-hub-access-via-shared-password" class="nav-link" data-scroll-target="#workshop-hub-access-via-shared-password">Workshop Hub Access via Shared Password</a></li>
   </ul></li>
   </ul>
 <div class="toc-actions"><div><i class="bi bi-github"></i></div><div class="action-links"><p><a href="https://github.com/nasa-openscapes/earthdata-cloud-cookbook/edit/main/policies-admin/leading-workshops.qmd" class="toc-action">Edit this page</a></p><p><a href="https://github.com/nasa-openscapes/earthdata-cloud-cookbook/blob/main/policies-admin/leading-workshops.qmd" class="toc-action">View source</a></p><p><a href="https://github.com/nasa-openscapes/earthdata-cloud-cookbook/issues/new" class="toc-action">Report an issue</a></p></div></div></nav>
@@ -588,19 +589,22 @@ <h1 class="title">Leading Workshops</h1>
 <hr>
 <section id="using-the-openscapes-2i2c-hub-in-a-workshop" class="level2">
 <h2 class="anchored" data-anchor-id="using-the-openscapes-2i2c-hub-in-a-workshop">Using the Openscapes 2i2c Hub in a workshop</h2>
-<!-- TODO: Add policies/instructions for setting up workshop with "just-in-time" access -->
 <ul>
 <li>Check with Luis that the Hub image has the packages you need</li>
-<li>Reach out to 2i2c a month in advance via email <code>support at 2i2c.freshdesk.com</code> (example below) to tell them about the workshop date, start and end times, # of participants, anticipated level of resources to be used.</li>
-<li><a href="../policies-admin/add-folks-to-2i2c-github-teams.html">Add participants to the 2i2c Hub</a> via a GitHub Team</li>
+<li>Reach out to 2i2c <em>a month in advance</em> via email <code>support at 2i2c.freshdesk.com</code> (examples below) to tell them about the workshop date, start and end times, # of participants, anticipated level of resources to be used, access method, and if appropriate, a desired password.</li>
 </ul>
+<p>We divide types of workshops into two different categories, with different access patterns:</p>
+<section id="workshop-hub-access-via-github-teams" class="level3">
+<h3 class="anchored" data-anchor-id="workshop-hub-access-via-github-teams">Workshop Hub Access via GitHub Teams</h3>
+<p>If you are hosting a smaller workshop with learners<br>
+with GitHub and who require longer-term access to the Hub after the workshop, follow the instructions to <a href="../policies-admin/add-folks-to-2i2c-github-teams.html">add participants to the 2i2c Hub</a> via a GitHub Team. Then send an email to <code>support at 2i2c.freshdesk.com</code>.</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-1-contents" aria-controls="callout-1" 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 email to 2i2c for a workshop
+Example email to 2i2c for a workshop with GitHub authentication
 </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>
@@ -611,14 +615,38 @@ <h2 class="anchored" data-anchor-id="using-the-openscapes-2i2c-hub-in-a-workshop
 <p>Title: Data Access Workshop for NASA’s SWOT Satellite<br>
 Date: February 13, 2024<br>
 Duration/Time: half day, 9:00 am-12:30 pm HST (Honolulu, HI).<br>
-Expected Usage: 3.7 GB per person (~50 people)</p>
+Expected Usage: 3.7 GB per person (~50 people) The URL of the hub that will be used for the event: https://openscapes.2i2c.cloud/ Access Method: GitHub Team</p>
 <p>Thank you!</p>
 <p>Cassie</p>
 </div>
 </div>
 </div>
-<section id="how-to-add-folks-to-the-2i2c-hub" class="level3">
-<h3 class="anchored" data-anchor-id="how-to-add-folks-to-the-2i2c-hub"><a href="../policies-admin/add-folks-to-2i2c-github-teams.html">How to Add Folks to the 2i2c Hub</a></h3>
+</section>
+<section id="workshop-hub-access-via-shared-password" class="level3">
+<h3 class="anchored" data-anchor-id="workshop-hub-access-via-shared-password">Workshop Hub Access via Shared Password</h3>
+<p>If you are hosting a workshop that has a large number of particpants, especially if they are not all comfortable with GitHub and particpants do not require access to the Hub when the workshop is complete, use the “shared password” access. This access method allows the instructors to share a single password with learners at the start of the workshop which they can use to log on the the Hub.</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 email to 2i2c for a workshop with shared password authentication
+</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">
+<p>Hello,</p>
+<p>The LP DAAC and Openscapes have an upcoming event where we are planning to use the Openscapes Hub. Here’s the main information:</p>
+<p>The GitHub handle or name of the community representative: [github username], [email protected] The date when the event will start: July 7, 2024 The date when the event will end: July ​7, 2024 What hours of the day will participants be active? 1:00pm - 5pm EEST (Athens, Greece). Number of attendees: ~40 Resources per user: 14.8GB RAM / up to 3.7 CPU The URL of the hub that will be used for the event: https://workshop.openscapes.2i2c.cloud/ Access method: shared password Password choice: [YouChooseAPassword]</p>
+<p>Thank you!</p>
+<p>Erik</p>
+</div>
+</div>
+</div>
+<p>Tell your learners that they will be able to access the Hub using the shared password for one week following the workshop, after which the password will be changed and the their home directories inside the Hub will be removed.</p>
+<p>One week after the workshop, send another email to <code>support at 2i2c.freshdesk.com</code> and request that the password be reset and users’ home directories from the workshop be removed.</p>
 
 
 </section>