Skip to content

Commit

Permalink
Built site for gh-pages
Browse files Browse the repository at this point in the history
  • Loading branch information
Quarto GHA Workflow Runner committed Jan 29, 2025
1 parent 3cd73cf commit e29e83d
Show file tree
Hide file tree
Showing 4 changed files with 11 additions and 10 deletions.
2 changes: 1 addition & 1 deletion .nojekyll
Original file line number Diff line number Diff line change
@@ -1 +1 @@
05f5cd4d
ab6b3f34
3 changes: 2 additions & 1 deletion github-access.html
Original file line number Diff line number Diff line change
Expand Up @@ -341,7 +341,8 @@ <h3 class="anchored" data-anchor-id="email-confirmation">6. Email confirmation</
<div class="callout-body-container callout-body">
<p>Subject: [NASA/NMFS] Openscapes Access to 2i2c Hub</p>
<p>Hi [FIRST NAME],</p>
<p>I have added you to the [NASA/NMFS] Openscapes 2i2c Jupyter Hub. Here is the link to the hub: <a href="https://openscapes.cloud/" class="uri">https://openscapes.cloud/</a></p>
<p>I have added you to the [NASA/NMFS] Openscapes 2i2c Jupyter Hub with the GitHub name you provided. You will have received an invitation from GitHub via email that you will need to accept.</p>
<p>Here is the link to the hub: <a href="https://openscapes.cloud/" class="uri">https://openscapes.cloud/</a></p>
<p>There is a getting started guide in the NASA Earthdata Cloud Cookbook here: <a href="https://nasa-openscapes.github.io/earthdata-cloud-cookbook/" class="uri">https://nasa-openscapes.github.io/earthdata-cloud-cookbook/</a>. You can see policies for hub use here: <a href="https://openscapes.cloud/access-policies.html" class="uri">https://openscapes.cloud/access-policies.html</a>, and policies and best practices for data storage here <a href="https://openscapes.cloud/data-storage.html" class="uri">https://openscapes.cloud/data-storage.html</a></p>
<p>We’d love to know about the kind of work you are doing on the hub. Please add a brief description of your progress as you go at <a href="https://github.com/NASA-Openscapes/2i2cAccessPolicies/discussions/2" class="uri">https://github.com/NASA-Openscapes/2i2cAccessPolicies/discussions/2</a>. We will follow up in the next few months.&nbsp;</p>
<p>Best,</p>
Expand Down
2 changes: 1 addition & 1 deletion search.json
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@
"href": "github-access.html#individual-long-term-access-through-github-teams",
"title": "GitHub-based Access",
"section": "Individual long-term access through GitHub Teams",
"text": "Individual long-term access through GitHub Teams\n\n1. Share Google Form with users needing access\nAsk users: Please fill out the Google form for Openscapes JupyterHub Access. Users must have a GitHub username to fill out the form, as this is how they will be given access to the Hub. If they are requesting long-term access they should be sure to list their affiliation and who referred them, so administrators know that their request is within scope for the Hub.\n\nNASA-Openscapes form\nNMFS-Openscapes form\n\n\n\n2. Google Form response setup\nSet the form responses to notify you by email when there are responses: Click on Responses &gt; click three vertical dots and then check “email notification.”\n\n\n\n\n\n\n\n\n\n\n\n\n3. Email alert of new signup\nWhen you get an email click ‘view response’ (not view summary)\n\n\n\n\n\n\n\n\n\n\n\nNote\n\n\n\nIf you are not sure if the access request is valid (i.e., the requestor does not appear to be an Openscapes mentor, staff member or close collaborator etc.), ask the mentor community in Slack to verify if the person requesting access is affiliated with any mentors’ work. If not, then send the requestor the following email, and do not add them to the GitHub team:\n\nDear XXX,\nThank you for your interest in our JupyterHub. Currently we provide access to people who participate in workshops taught by NASA Data Center (DAAC) staff through the NASA Openscapes community. We will be adding upcoming events you can sign up for here: https://nasa-openscapes.github.io/news.\nBest,\n\nNote in the “Notes” column in the Google form response sheet that this email was sent denying access, and the date.\n\nNASA-Openscapes responses sheet\nNMFS-Openscapes responses sheet\n\n\n\n\n\n4. Copy GitHub username\nOn the response page, copy the Github Username\n\n\n\n\n\n\n\n5. Add GitHub username to the GitHub Team\n\n\n\n\n\n\nTip\n\n\n\nIf you are adding many new mentors to the long-term access team, you can use the same steps as for adding workshop participants\n\n\nGo to the appropriate team in GitHub &gt; Click Add member &gt; Paste GitHub username.\n\nNASA-Openscapes GitHub Teams\nNASA-Openscapes-workshops GitHub Teams\nNMFS-Openscapes GitHub Teams\n\n\n\n\n\n\nGitHub may ask you for 2-factor authentication for the first one you add in a batch, not after that.\nPeople may see invitation notifications in two ways; in GitHub itself, and/or via email. They must accept the invitation to be able to access the Hub. This is what it looks like in their email inbox:\n\n\n\n\n\nThis is what the invitation looks like in the GitHub website interface - clicking the yellow banner notification leads to the invitation:\n\n\n\n\n\n\n\n\n\n\n\n\n6. Email confirmation\nGo back to the Google form response and grab their email address. Send the following email to the person:\n\n\n\n\n\n\nEmail for General requests: \n\n\n\n\n\nSubject: [NASA/NMFS] Openscapes Access to 2i2c Hub\nHi [FIRST NAME],\nI have added you to the [NASA/NMFS] Openscapes 2i2c Jupyter Hub. Here is the link to the hub: https://openscapes.cloud/\nThere is a getting started guide in the NASA Earthdata Cloud Cookbook here: https://nasa-openscapes.github.io/earthdata-cloud-cookbook/. You can see policies for hub use here: https://openscapes.cloud/access-policies.html, and policies and best practices for data storage here https://openscapes.cloud/data-storage.html\nWe’d love to know about the kind of work you are doing on the hub. Please add a brief description of your progress as you go at https://github.com/NASA-Openscapes/2i2cAccessPolicies/discussions/2. We will follow up in the next few months. \nBest,\n\n\n\n\n\n\n7. Register date in Form Response Sheet\nIn the Form Response Sheet (NASA/ NOAA), in column Added to 2i2c hub add the date they were added to the Hub, or if the request came via email add a new row - in part so that we as admins knew if someone had already fulfilled the request. Check Column A for the date of the form request.\n\n\nDirections for invitees\n\nPlease go to:\n\n\nNASA (workshops/champions): https://github.com/nasa-openscapes-workshops\nNASA (longterm access): https://github.com/nasa-openscapes-workshops\nNMFS: https://github.com/nmfs-openscapes\n\n\nClick the big yellow bar that says “you’ve been invited” \nNot seeing that bar? \n\nAre you logged into GitHub.com?\nHave you shared your GitHub username via the Google Form (NASA/NOAA)?\nYou can also check your email that you use for GitHub and look for an invitation from GitHub and Openscapes"
"text": "Individual long-term access through GitHub Teams\n\n1. Share Google Form with users needing access\nAsk users: Please fill out the Google form for Openscapes JupyterHub Access. Users must have a GitHub username to fill out the form, as this is how they will be given access to the Hub. If they are requesting long-term access they should be sure to list their affiliation and who referred them, so administrators know that their request is within scope for the Hub.\n\nNASA-Openscapes form\nNMFS-Openscapes form\n\n\n\n2. Google Form response setup\nSet the form responses to notify you by email when there are responses: Click on Responses &gt; click three vertical dots and then check “email notification.”\n\n\n\n\n\n\n\n\n\n\n\n\n3. Email alert of new signup\nWhen you get an email click ‘view response’ (not view summary)\n\n\n\n\n\n\n\n\n\n\n\nNote\n\n\n\nIf you are not sure if the access request is valid (i.e., the requestor does not appear to be an Openscapes mentor, staff member or close collaborator etc.), ask the mentor community in Slack to verify if the person requesting access is affiliated with any mentors’ work. If not, then send the requestor the following email, and do not add them to the GitHub team:\n\nDear XXX,\nThank you for your interest in our JupyterHub. Currently we provide access to people who participate in workshops taught by NASA Data Center (DAAC) staff through the NASA Openscapes community. We will be adding upcoming events you can sign up for here: https://nasa-openscapes.github.io/news.\nBest,\n\nNote in the “Notes” column in the Google form response sheet that this email was sent denying access, and the date.\n\nNASA-Openscapes responses sheet\nNMFS-Openscapes responses sheet\n\n\n\n\n\n4. Copy GitHub username\nOn the response page, copy the Github Username\n\n\n\n\n\n\n\n5. Add GitHub username to the GitHub Team\n\n\n\n\n\n\nTip\n\n\n\nIf you are adding many new mentors to the long-term access team, you can use the same steps as for adding workshop participants\n\n\nGo to the appropriate team in GitHub &gt; Click Add member &gt; Paste GitHub username.\n\nNASA-Openscapes GitHub Teams\nNASA-Openscapes-workshops GitHub Teams\nNMFS-Openscapes GitHub Teams\n\n\n\n\n\n\nGitHub may ask you for 2-factor authentication for the first one you add in a batch, not after that.\nPeople may see invitation notifications in two ways; in GitHub itself, and/or via email. They must accept the invitation to be able to access the Hub. This is what it looks like in their email inbox:\n\n\n\n\n\nThis is what the invitation looks like in the GitHub website interface - clicking the yellow banner notification leads to the invitation:\n\n\n\n\n\n\n\n\n\n\n\n\n6. Email confirmation\nGo back to the Google form response and grab their email address. Send the following email to the person:\n\n\n\n\n\n\nEmail for General requests: \n\n\n\n\n\nSubject: [NASA/NMFS] Openscapes Access to 2i2c Hub\nHi [FIRST NAME],\nI have added you to the [NASA/NMFS] Openscapes 2i2c Jupyter Hub with the GitHub name you provided. You will have received an invitation from GitHub via email that you will need to accept.\nHere is the link to the hub: https://openscapes.cloud/\nThere is a getting started guide in the NASA Earthdata Cloud Cookbook here: https://nasa-openscapes.github.io/earthdata-cloud-cookbook/. You can see policies for hub use here: https://openscapes.cloud/access-policies.html, and policies and best practices for data storage here https://openscapes.cloud/data-storage.html\nWe’d love to know about the kind of work you are doing on the hub. Please add a brief description of your progress as you go at https://github.com/NASA-Openscapes/2i2cAccessPolicies/discussions/2. We will follow up in the next few months. \nBest,\n\n\n\n\n\n\n7. Register date in Form Response Sheet\nIn the Form Response Sheet (NASA/ NOAA), in column Added to 2i2c hub add the date they were added to the Hub, or if the request came via email add a new row - in part so that we as admins knew if someone had already fulfilled the request. Check Column A for the date of the form request.\n\n\nDirections for invitees\n\nPlease go to:\n\n\nNASA (workshops/champions): https://github.com/nasa-openscapes-workshops\nNASA (longterm access): https://github.com/nasa-openscapes-workshops\nNMFS: https://github.com/nmfs-openscapes\n\n\nClick the big yellow bar that says “you’ve been invited” \nNot seeing that bar? \n\nAre you logged into GitHub.com?\nHave you shared your GitHub username via the Google Form (NASA/NOAA)?\nYou can also check your email that you use for GitHub and look for an invitation from GitHub and Openscapes"
},
{
"objectID": "github-access.html#adding-champions-or-workshop-participants-to-the-hub-as-a-batch",
Expand Down
14 changes: 7 additions & 7 deletions sitemap.xml
Original file line number Diff line number Diff line change
Expand Up @@ -2,30 +2,30 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://openscapes.cloud/password-access.html</loc>
<lastmod>2025-01-22T19:22:13.364Z</lastmod>
<lastmod>2025-01-29T20:47:36.956Z</lastmod>
</url>
<url>
<loc>https://openscapes.cloud/index.html</loc>
<lastmod>2025-01-22T19:22:13.363Z</lastmod>
<lastmod>2025-01-29T20:47:36.956Z</lastmod>
</url>
<url>
<loc>https://openscapes.cloud/access-policies.html</loc>
<lastmod>2025-01-22T19:22:13.348Z</lastmod>
<lastmod>2025-01-29T20:47:36.940Z</lastmod>
</url>
<url>
<loc>https://openscapes.cloud/github-access.html</loc>
<lastmod>2025-01-22T19:22:13.348Z</lastmod>
<lastmod>2025-01-29T20:47:36.941Z</lastmod>
</url>
<url>
<loc>https://openscapes.cloud/fledging.html</loc>
<lastmod>2025-01-22T19:22:13.348Z</lastmod>
<lastmod>2025-01-29T20:47:36.941Z</lastmod>
</url>
<url>
<loc>https://openscapes.cloud/about.html</loc>
<lastmod>2025-01-22T19:22:13.348Z</lastmod>
<lastmod>2025-01-29T20:47:36.940Z</lastmod>
</url>
<url>
<loc>https://openscapes.cloud/data-storage.html</loc>
<lastmod>2025-01-22T19:22:13.348Z</lastmod>
<lastmod>2025-01-29T20:47:36.941Z</lastmod>
</url>
</urlset>

0 comments on commit e29e83d

Please sign in to comment.