Update workshop issue template to reflect changes in NMFS

Author: ateucher

.github/ISSUE_TEMPLATE/01-nasa-openscapes-workshop-template-form.yml

@@ -9,8 +9,20 @@ projects:
 body:
   - type: markdown
     attributes:
-      value: |
-        Thank you for your interest in hosting a workshop using the NASA Openscapes Jupyter Hub! Please fill out the form below to request a reservation. We will get back to you as soon as possible to confirm your reservation.
+      value: >
+        Thank you for your interest in hosting a workshop using the NASA
+        Openscapes JupyterHub! Use this issue to reserve access to the hub.
+
+
+        Before submitting, please check the
+        [workshop spreadsheet](https://docs.google.com/spreadsheets/d/1Sg4fMDGxMLI0p5cgK5xyamFJpKC6NyNneqXLDReSKcg/edit?gid=695033382)
+        for any existing reservations around your dates. See also the
+        [documentation on openscapes.cloud](https://openscapes.cloud/password-access.html)
+        for detailed instructions.
+
+
+        Fill out the form below and we will get back to you as soon as possible
+        to confirm your reservation.
 
   - type: textarea
     id: workshop-description
@@ -89,7 +101,7 @@ body:
     id: compute-requirements
     attributes:
       label: Compute Requirements
-      description: |
+      description: >
         What size compute resources will participants be asked to select when they log in?
         2Gb (default), 4Gb, more? This is selected in the dropdown at the Hub login, and knowing what you
         will need helps us make sure the hub is adequately provisioned.
@@ -101,7 +113,7 @@ body:
     attributes:
       label: Image Requirements
       description: |
-        Will you be using the default Openscapes image, or a custom image?
+        Will you be using one of the default images, or a custom image?
         Confirm that the image you will be using is sufficient for your needs
         (i.e., has the packages and sufficient versions you need), or that you
         have created an image that can be used by participants.
@@ -126,27 +138,51 @@ body:
     attributes:
       label: Checklist for workshop organizer (person planning/leading the workshop) and hub point-of-contact (PoC; Openscapes team member helping with hub setup and logistics. Usually @ateucher).
       options:
-        - label: |
-            **Hub PoC**: Send confirmation to organizer that the request is received and the hub is available for the workshop (a comment in this issue thread is fine)
-        - label: |
-            **Organizer**: Add your event in the [workshop spreadsheet](https://docs.google.com/spreadsheets/d/1Sg4fMDGxMLI0p5cgK5xyamFJpKC6NyNneqXLDReSKcg/edit?gid=695033382)
-        - label: |
-            **Organizer**: Submit a ticket by email to 2i2c for the workshop [as per instructions](https://openscapes.cloud/password-access.html), cc'ing hub PoC.
-        - label: |
-            **Hub PoC**: Confirm `[Event]` or `[Support]` issue opened in [2i2c-org/infrastructure](https://github.com/2i2c-org/infrastructure/issues) in response to ticket ([example](https://github.com/2i2c-org/infrastructure/issues/5466))
-        - label: |
-            **Hub PoC**: Add new password and dates to [workshop password spreadsheet](https://docs.google.com/spreadsheets/d/1Y4qzqWLsKHTNzuQi-fOaHGud0Ld_q1GHAzhS9-grV7Q/edit?gid=1793413915).
-        - label: |
-            **Organizer**: Two weeks before event. I have tested the default hub images on the workshop hub or conferred with hub PoC on plan for a workshop specific image.
-        - label: |
-            **Organizer**: In the week before the event (or when PoC indicates password should be live). I tested that the workshop password works and images work.
-        - label: |
-            **Hub PoC**: After event, put in a 2i2c ticket to remove the participants directories, cleared shared-public, and reset password.
-        - label: |
-            **Organizer**: After the event, open an [issue](https://github.com/NASA-Openscapes/workshop-planning/issues/new?template=nasa-openscapes-workshop-reporting-template.md) in the Workshop Planning repo to report back.
-
-  - type: markdown
-    attributes:
-      value: |
-        ---
-        _Please click on the "Projects" button below and tick the "Main Planning" project if it is available to you_
+        - label: >
+            **Hub PoC**: Send confirmation to organizer that the request is 
+            received and the hub is available for the workshop (a comment in 
+            this issue thread is fine).
+        - label: >
+            **Organizer**: Add your event in the
+            [workshop spreadsheet](https://docs.google.com/spreadsheets/d/1Sg4fMDGxMLI0p5cgK5xyamFJpKC6NyNneqXLDReSKcg/edit?gid=695033382).
+            Please check if there are any other workshops scheduled around the
+            same time and if so, let the hub PoC know to make sure the hub can
+            support multiple workshops at the same time.
+        - label: >
+            **Organizer**: Submit a ticket by email to 2i2c for the workshop and
+            request a new password for the workshop, 
+            [as per instructions](https://openscapes.cloud/password-access.html), 
+            cc'ing hub PoC (@ateucher; andy [at] openscapes [dot] org). You will 
+            receive confirmation of the new password for the workshop from 2i2c 
+            once it is reset.
+        - label: >
+            **Hub PoC**: Confirm `[Event]` or `[Support]` issue opened in 
+            [2i2c-org/infrastructure](https://github.com/2i2c-org/infrastructure/issues) 
+            in response to ticket ([example](https://github.com/2i2c-org/infrastructure/issues/5466))
+        - label: >
+            **Hub PoC**: Add new password and dates to 
+            [workshop password spreadsheet](https://docs.google.com/spreadsheets/d/1Y4qzqWLsKHTNzuQi-fOaHGud0Ld_q1GHAzhS9-grV7Q/edit?gid=1793413915).
+        - label: >
+            **Organizer**: Two weeks before event. I have tested the default hub 
+            images on the workshop hub or conferred with hub PoC on plan for a 
+            workshop specific image.
+        - label: >
+            **Organizer**: In the week before the event (or when hub PoC 
+            indicates password should be live). I tested that the workshop 
+            password works and images work.
+        - label: >
+            **Organizer**: After the event, open an 
+            [issue](https://github.com/NASA-Openscapes/workshop-planning/issues/new?template=nasa-openscapes-workshop-reporting-template.md) 
+            in the Workshop Planning repo to report back.
+        - label: >
+            **Hub PoC**: After event, put in a 2i2c ticket to reset password.
+        - label: >
+            **Hub PoC**: After event, log in to the hub as admin, enumerate the 
+            participant directories and update the workshop spreadsheet with the 
+            actual number of participants.
+        - label: >
+            **Hub PoC**: After event, delete the participant directories.
+        - label: >
+            **Hub PoC**: Close the issue. If the workshop was completed, close 
+            as "completed". If the workshop was cancelled before being held, 
+            close as "Not Planned" and note in the comments that it was cancelled.