diff --git a/.nojekyll b/.nojekyll index 091ab91..04ad80f 100644 --- a/.nojekyll +++ b/.nojekyll @@ -1 +1 @@ -cd72fd6d \ No newline at end of file +3959f0cc \ No newline at end of file diff --git a/mentors-framework/onboarding.html b/mentors-framework/onboarding.html index c490253..b9d8200 100644 --- a/mentors-framework/onboarding.html +++ b/mentors-framework/onboarding.html @@ -301,10 +301,13 @@

On this page

@@ -338,20 +341,50 @@

Cre

We create a spreadsheet called OpenscapesParticipantsList [ nasa-mentors ]

Headers (comma separated list): cohort, first, last, email, email-2 for Google Folder access, institution, GitHub username, Twitter - not using Twitter as of 2023, New Mentor Welcome email - sent, Calendars - added, Folders - added, Google Group - added, 2i2c - added using GitHub username via https://openscapes.2i2c.cloud/hub/admin#/ then add them to Openscapes_JupyterHubAccess (Responses) sheet, GitHub - added to Team, Slack - added, Coiled - added, Carpentries - Y3 code shared, Carpentries Certified Instructor, Bio text - for https://nasa-openscapes.github.io/mentors.html. Please Share details that we’ll add; you can also make a GitHub Pull Request if you’d prefer.

-
-

Create a Google Group with Mentors

-

For NASA, we created a Google Group so we could easily add mentors to Google Folders and Calendars.

-

This hasn’t worked perfectly because not everyone can use their work address to access Google things. We collect a second email address in the ParticipantsList spreadsheet, but if we use Google Groups we need to make sure that everyone’s Google-access emails are included in the Google Group.

-
-
-

Create a GitHub Team with Mentors

-

Create a GitHub Team in GitHub org Openscapes, NASA-Openscapes, or NMFS-Openscapes, that includes new and past Mentors. Team name: YYYY-mentors-community.

+
+

Welcome Email

+
+ +
+
+

Subject: Welcome to the NASA Openscapes Mentor Community!

+

Hi Rhys et al,

+

Welcome, we’re excited you’ll be joining the NASA Openscapes Mentor community!

+

This cross-DAAC mentor community is creating & teaching resources to help researchers migrate workflows to the cloud. We learn and develop common materials and teaching approaches together, working with alignment on common needs for researchers using NASA Earthdata. We meet regularly via video and collaborate asynchronously - details follow.

+

We are currently gearing up for workshops and presentations at the Fall AGU Conference - will you be attending?

+

Here are the first few steps for onboarding to this community:

+
    +
  1. Read the NASA Mentors Onboarding section of the Earthdata Cloud Cookbook. There are links to further information and work by the NASA Mentors, including slides, reading, and setup for what to expect.
  2. +
  3. Provide your GitHub username via our JupyterHub request form.
  4. +
  5. Look out for and accept invitations to our Calendar, Google Drive, Slack, and GitHub. Note that to access our 2i2c JupyterHub, you’ll need to provide your GitHub username and accept the GitHub Teams invitation.
  6. +
  7. Carpentries Instructor Training - We partner with The Carpentries, a nonprofit that teaches introductory coding skills around the world. This remote training is not coding-specific, but it is a pedagogical approach to teaching technical topics, and has grown a common teaching approach for NASA Openscapes Mentors. Please sign up following the 2-step process below.
  8. +
+ +
    +
  1. Register for the event of your choice on our Instructor Training event calendar with the code: OUR-CODE-HERE. New events are added to this calendar in December, March, June, and September.
  2. +
  3. Complete Carpentries profile-creation form using the same code. Please note: Registration secures their seat; profile creation enables us to record their attendance and track their progress toward certification.
  4. +
+

If you have any questions, please reach out via email or Slack. We are also available to book 1:1 intro calls before Thanksgiving.

+

We’re really looking forward to working with you!

+

Cheers,

+

Julie Lowndes, Erin Robinson, Stefanie Butland, NASA Openscapes

+
+
+
-

## 1:1 Mentor intro calls

+

1:1 Mentor intro calls

We have intro calls with each mentor pair or trio prior to our kickoff call with the whole Mentor community.

- -
+

SEDAC – Openscapes 1:1 meetings

Zoom:

@@ -448,7 +481,7 @@

Post 1:1 Follow
- -
+

Hi V,

It was great to meet you; your colleagues said you’re able to join the NASA Openscapes Mentors from PO.DAAC – we’re super excited, welcome! We’re preparing for a Sept 20 kickoff to onboard new mentors, and have a light outline of plans here: https://nasa-openscapes.github.io/mentors.html#current-activities.

@@ -468,7 +501,7 @@

Post 1:1 Follow

- -
+

Subject: Welcome to the NASA Openscapes Mentor Community!

Hi Sean, Alicia, Guoqing,

@@ -491,7 +524,7 @@

Post 1:1 Follow

- -
+

Subject: Welcome to the NASA Openscapes Mentor Community!

Hi Kytt and Juan,

@@ -515,8 +548,18 @@

Post 1:1 Follow

+

+
+

Create a way to email Mentor group

+

This is evolving.

+

For NASA, we started off by creating a Google Group so we could easily add mentors to Google Folders and Calendars. This hasn’t worked perfectly because not everyone can use their work address to access Google things. We collect a second email address in the ParticipantsList spreadsheet, but if we use Google Groups we need to make sure that everyone’s Google-access emails are included in the Google Group.

+

We’re also using GitHub Teams more, for 2i2c access and coordinating. Rather than a Google Group that is difficult to hand off in terms of managing, a GitHub Team might be the way to go. This will raise challenges for any private info (e.g. Carpentries code), but that could be handled in Slack.

+
+

Create a GitHub Team with Mentors

+

Create a GitHub Team in GitHub org Openscapes, NASA-Openscapes, or NMFS-Openscapes, that includes new and past Mentors. Team name: nasa-mentors-community.

+
diff --git a/search.json b/search.json index 231b108..69de7ea 100644 --- a/search.json +++ b/search.json @@ -889,25 +889,18 @@ "text": "We create a spreadsheet called OpenscapesParticipantsList [ nasa-mentors ]\nHeaders (comma separated list): cohort, first, last, email, email-2 for Google Folder access, institution, GitHub username, Twitter - not using Twitter as of 2023, New Mentor Welcome email - sent, Calendars - added, Folders - added, Google Group - added, 2i2c - added using GitHub username via https://openscapes.2i2c.cloud/hub/admin#/ then add them to Openscapes_JupyterHubAccess (Responses) sheet, GitHub - added to Team, Slack - added, Coiled - added, Carpentries - Y3 code shared, Carpentries Certified Instructor, Bio text - for https://nasa-openscapes.github.io/mentors.html. Please Share details that we’ll add; you can also make a GitHub Pull Request if you’d prefer." }, { - "objectID": "mentors-framework/onboarding.html#create-a-google-group-with-mentors", - "href": "mentors-framework/onboarding.html#create-a-google-group-with-mentors", + "objectID": "mentors-framework/onboarding.html#welcome-email", + "href": "mentors-framework/onboarding.html#welcome-email", "title": "Onboarding Mentors", - "section": "Create a Google Group with Mentors", - "text": "Create a Google Group with Mentors\nFor NASA, we created a Google Group so we could easily add mentors to Google Folders and Calendars.\nThis hasn’t worked perfectly because not everyone can use their work address to access Google things. We collect a second email address in the ParticipantsList spreadsheet, but if we use Google Groups we need to make sure that everyone’s Google-access emails are included in the Google Group." - }, - { - "objectID": "mentors-framework/onboarding.html#create-a-github-team-with-mentors", - "href": "mentors-framework/onboarding.html#create-a-github-team-with-mentors", - "title": "Onboarding Mentors", - "section": "Create a GitHub Team with Mentors", - "text": "Create a GitHub Team with Mentors\nCreate a GitHub Team in GitHub org Openscapes, NASA-Openscapes, or NMFS-Openscapes, that includes new and past Mentors. Team name: YYYY-mentors-community." + "section": "Welcome Email", + "text": "Welcome Email\n\n\n\n\n\n\nNote\n\n\n\n\n\nSubject: Welcome to the NASA Openscapes Mentor Community!\nHi Rhys et al,\nWelcome, we’re excited you’ll be joining the NASA Openscapes Mentor community!\nThis cross-DAAC mentor community is creating & teaching resources to help researchers migrate workflows to the cloud. We learn and develop common materials and teaching approaches together, working with alignment on common needs for researchers using NASA Earthdata. We meet regularly via video and collaborate asynchronously - details follow.\nWe are currently gearing up for workshops and presentations at the Fall AGU Conference - will you be attending?\nHere are the first few steps for onboarding to this community:\n\nRead the NASA Mentors Onboarding section of the Earthdata Cloud Cookbook. There are links to further information and work by the NASA Mentors, including slides, reading, and setup for what to expect.\nProvide your GitHub username via our JupyterHub request form.\nLook out for and accept invitations to our Calendar, Google Drive, Slack, and GitHub. Note that to access our 2i2c JupyterHub, you’ll need to provide your GitHub username and accept the GitHub Teams invitation.\nCarpentries Instructor Training - We partner with The Carpentries, a nonprofit that teaches introductory coding skills around the world. This remote training is not coding-specific, but it is a pedagogical approach to teaching technical topics, and has grown a common teaching approach for NASA Openscapes Mentors. Please sign up following the 2-step process below.\n\n\n\nRegister for the event of your choice on our Instructor Training event calendar with the code: OUR-CODE-HERE. New events are added to this calendar in December, March, June, and September.\nComplete Carpentries profile-creation form using the same code. Please note: Registration secures their seat; profile creation enables us to record their attendance and track their progress toward certification.\n\nIf you have any questions, please reach out via email or Slack. We are also available to book 1:1 intro calls before Thanksgiving.\nWe’re really looking forward to working with you!\nCheers,\nJulie Lowndes, Erin Robinson, Stefanie Butland, NASA Openscapes" }, { "objectID": "mentors-framework/onboarding.html#mentor-intro-calls", "href": "mentors-framework/onboarding.html#mentor-intro-calls", "title": "Onboarding Mentors", - "section": "## 1:1 Mentor intro calls", - "text": "## 1:1 Mentor intro calls\nWe have intro calls with each mentor pair or trio prior to our kickoff call with the whole Mentor community.\n\n\n\n\n\n\n1:1 agenda example\n\n\n\n\n\nSEDAC – Openscapes 1:1 meetings\nZoom:\nAug 24, 2023\nName, Julie Lowndes\n30 minutes\nPurpose: Openscapes overview and getting to know each other\nAgenda\nIntroductions - what brings you to NASA Openscapes?\n\n\nJulie marine ecologist turned open science person, NASA Openscapes with Erin Robinson\n\nNASA-Openscapes Overview\n\nhttps://nasa-openscapes.github.io (recent presentations) \nESIP Session at Winter 2023 - 3 Approaches for the Year of Open Science\nNASA OSS Working Group Talk \nOur goal: to support the work you are already doing. Using Openscapes model, iterating and growing and evolving with Mentors\n“Not in addition to our jobs” - and connects to other DAACs\nProfessional dev, relationships with other DAAC mentors, and ability to work with “early adopter” scientists\n\nBroader background about Openscapes: https://openscapes.org \nDAAC activities, skills & software (help us plan clinics/co-working/what do you all collectively want to do?)\n\nGitHub Usernames:\n\n \n\nNASA activities\n\nAre you working with ARSET, DEVELOP, TOPS, SERVIR?\n\n\n\nAre you doing anything cross-DAAC?\n\n\n\n\nAre there hurdles that we should be aware of?\n\n\n\n\nNext steps\n\n \n \n\nDraft Calendar (in progress)\n\nNew mentors onboarded in late Summer 2023 \n\n\nDiscussion / Questions" + "section": "1:1 Mentor intro calls", + "text": "1:1 Mentor intro calls\nWe have intro calls with each mentor pair or trio prior to our kickoff call with the whole Mentor community.\n\n\n\n\n\n\n1:1 agenda example\n\n\n\n\n\nSEDAC – Openscapes 1:1 meetings\nZoom:\nAug 24, 2023\nName, Julie Lowndes\n30 minutes\nPurpose: Openscapes overview and getting to know each other\nAgenda\nIntroductions - what brings you to NASA Openscapes?\n\n\nJulie marine ecologist turned open science person, NASA Openscapes with Erin Robinson\n\nNASA-Openscapes Overview\n\nhttps://nasa-openscapes.github.io (recent presentations) \nESIP Session at Winter 2023 - 3 Approaches for the Year of Open Science\nNASA OSS Working Group Talk \nOur goal: to support the work you are already doing. Using Openscapes model, iterating and growing and evolving with Mentors\n“Not in addition to our jobs” - and connects to other DAACs\nProfessional dev, relationships with other DAAC mentors, and ability to work with “early adopter” scientists\n\nBroader background about Openscapes: https://openscapes.org \nDAAC activities, skills & software (help us plan clinics/co-working/what do you all collectively want to do?)\n\nGitHub Usernames:\n\n \n\nNASA activities\n\nAre you working with ARSET, DEVELOP, TOPS, SERVIR?\n\n\n\nAre you doing anything cross-DAAC?\n\n\n\n\nAre there hurdles that we should be aware of?\n\n\n\n\nNext steps\n\n \n \n\nDraft Calendar (in progress)\n\nNew mentors onboarded in late Summer 2023 \n\n\nDiscussion / Questions" }, { "objectID": "mentors-framework/onboarding.html#post-11-followup-checklist", @@ -916,6 +909,13 @@ "section": "Post 1:1 Followup Checklist", "text": "Post 1:1 Followup Checklist\n\nSend Welcome email (examples below)\n\nAsk for: GitHub Username, email-2\n\nAdd to calendar invites for Mentor Calls and Coworking\nAdd to Google Folder\nAdd to Google Group\nAdd to GitHub Mentors Team in Org\nAdd to Slack\nAdd Bio to Mentors page, or name if bio not available\nFor NASA-Openscapes\n\nAdd to 2i2c as member via https://openscapes.2i2c.cloud/admin\nAdd to Openscapes_JupyterHubAccess (Responses) sheet of 2i2c members\nAdd to Coiled\nInvite to Carpentries Instructor Training\n\n\n\n\n\n\n\n\nIntro email example\n\n\n\n\n\nHi V,\nIt was great to meet you; your colleagues said you’re able to join the NASA Openscapes Mentors from PO.DAAC – we’re super excited, welcome! We’re preparing for a Sept 20 kickoff to onboard new mentors, and have a light outline of plans here: https://nasa-openscapes.github.io/mentors.html#current-activities.\nThis cross-DAAC mentor community is creating & teaching resources to help researchers migrate workflows to the cloud. The expected time commitment is 3 days/month per year (and this ebbs and flows with your deadlines). This accounts for ~6 hours/month of synchronous calls with the rest of the time being self-directed towards improving support approaches for specific DAACs. You’ll be collaborating with others at your DAAC as well as across DAACs and the broader open science community. Please talk with your supervisor to make sure you are supported in alignment with your job; we will share with EOSDIS and HQ as well.\nWe’ll soon add you to calendar invites. If you’d have time for a 1:1 intro in the next few weeks, that would be super – we can share more and answer any questions you have ahead of our Sept 20 kickoff. The week of Sept 5 I’m available most days between 11-2pm PT if you’d have 30 minutes to chat.\nCheers, Julie\n\n\n\n\n\n\n\n\n\nFollowup email example\n\n\n\n\n\nSubject: Welcome to the NASA Openscapes Mentor Community!\nHi Sean, Alicia, Guoqing,\nIt was great to meet you and we’re really excited Guoqing will be joining the NASA Openscapes Mentor community from OBDAAC! I’ve cc’d co-lead Erin Robinson and our colleague Stefanie Butland here as well.\nPlease look out for invitations to our Calendar and Slack. Guoqing, could you please share your GitHub username and an email address for Google Drive (if not this one)?. We’ll then give you access to our 2i2c JupyterHub and other things listed in our how we onboard documentation – this is part of the Earthdata Cloud Cookbook that is the main place for all cloud resources the Mentors are developing. As one professional development opportunity, we partner with The Carpentries, a nonprofit that teaches introductory coding skills around the world. They will announce new dates for Instructor Training next month and we will share information for how to sign up.\nWe’ll have our first Fall kickoff meeting September 20, but you’re welcome to join sessions anytime before then. Please also let us know if there are additional colleagues who are able to join.\nWe’re really looking forward to working with you!\nCheers,\nJulie\n\n\n\n\n\n\n\n\n\nFollowup email example with Carpentries\n\n\n\n\n\nSubject: Welcome to the NASA Openscapes Mentor Community!\nHi Kytt and Juan,\nIt was great to meet you and we’re really excited you’ll be joining the NASA Openscapes Mentor community from SEDAC!\nPlease look out for invitations to our Calendar and Slack. Could you please share your GitHub username and an email address for Google Drive (if not this one)?. We’ll have our first Fall kickoff meeting September 20, but you’re welcome to join sessions anytime before then. You can also familiarize yourself with how we onboard — this is part of the Mentors’ Earthdata Cloud Cookbook.\nCarpentries Instructor Training - As part of our NASA grant, we partner with The Carpentries, a nonprofit that teaches introductory coding skills around the world. This remote training is not coding-specific, but it is a pedagogical approach to teaching technical topics. If you would like to sign up, please follow the 2-step process below. Our membership renews Sept 14; if you have trouble signing up using our code please let me know and I can help get it sorted.\n\nRegister for the event of your choice on our Instructor Training event calendar with the code: OUR-CODE-HERE. New events are added to this calendar in December, March, June, and September.\nComplete Carpentries profile-creation form using the same code. Please note: Registration secures their seat; profile creation enables us to record their attendance and track their progress toward certification.\n\nWe’re really looking forward to working with you! Cheers, Julie" }, + { + "objectID": "mentors-framework/onboarding.html#create-a-way-to-email-mentor-group", + "href": "mentors-framework/onboarding.html#create-a-way-to-email-mentor-group", + "title": "Onboarding Mentors", + "section": "Create a way to email Mentor group", + "text": "Create a way to email Mentor group\nThis is evolving.\nFor NASA, we started off by creating a Google Group so we could easily add mentors to Google Folders and Calendars. This hasn’t worked perfectly because not everyone can use their work address to access Google things. We collect a second email address in the ParticipantsList spreadsheet, but if we use Google Groups we need to make sure that everyone’s Google-access emails are included in the Google Group.\nWe’re also using GitHub Teams more, for 2i2c access and coordinating. Rather than a Google Group that is difficult to hand off in terms of managing, a GitHub Team might be the way to go. This will raise challenges for any private info (e.g. Carpentries code), but that could be handled in Slack.\n\nCreate a GitHub Team with Mentors\nCreate a GitHub Team in GitHub org Openscapes, NASA-Openscapes, or NMFS-Openscapes, that includes new and past Mentors. Team name: nasa-mentors-community." + }, { "objectID": "index.html#welcome", "href": "index.html#welcome", diff --git a/sitemap.xml b/sitemap.xml index dce3da5..d1ff0be 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -2,118 +2,118 @@ https://openscapes.github.io/approach-guide/contributing/inspiration.html - 2023-11-07T00:19:57.424Z + 2023-11-11T22:56:15.779Z https://openscapes.github.io/approach-guide/contributing/index.html - 2023-11-07T00:19:56.596Z + 2023-11-11T22:56:14.571Z https://openscapes.github.io/approach-guide/contributing/resources.html - 2023-11-07T00:19:55.964Z + 2023-11-11T22:56:13.675Z https://openscapes.github.io/approach-guide/mentors-framework/index.html - 2023-11-07T00:19:55.264Z + 2023-11-11T22:56:12.623Z https://openscapes.github.io/approach-guide/mentors-framework/nasa-openscapes.html - 2023-11-07T00:19:54.444Z + 2023-11-11T22:56:11.283Z https://openscapes.github.io/approach-guide/LICENSE.html - 2023-11-07T00:19:53.684Z + 2023-11-11T22:56:10.218Z https://openscapes.github.io/approach-guide/approach/code-of-conduct.html - 2023-11-07T00:19:53.016Z + 2023-11-11T22:56:09.270Z https://openscapes.github.io/approach-guide/approach/tooling.html - 2023-11-07T00:19:52.184Z + 2023-11-11T22:56:08.074Z https://openscapes.github.io/approach-guide/approach/seaside-chats.html - 2023-11-07T00:19:51.012Z + 2023-11-11T22:56:06.374Z https://openscapes.github.io/approach-guide/approach/partners.html - 2023-11-07T00:19:50.068Z + 2023-11-11T22:56:05.022Z https://openscapes.github.io/approach-guide/champions/lessons.html - 2023-11-07T00:19:49.140Z + 2023-11-11T22:56:03.706Z https://openscapes.github.io/approach-guide/champions/design.html - 2023-11-07T00:19:48.368Z + 2023-11-11T22:56:02.622Z https://openscapes.github.io/approach-guide/champions/pre-cohort-engage.html - 2023-11-07T00:19:47.516Z + 2023-11-11T22:56:01.446Z https://openscapes.github.io/approach-guide/champions/cohort-planning.html - 2023-11-07T00:19:46.100Z + 2023-11-11T22:55:59.398Z https://openscapes.github.io/approach-guide/champions/pre-cohort-tech.html - 2023-11-07T00:19:44.372Z + 2023-11-11T22:55:56.029Z https://openscapes.github.io/approach-guide/champions/leading-cohort-calls.html - 2023-11-07T00:19:45.720Z + 2023-11-11T22:55:58.862Z https://openscapes.github.io/approach-guide/champions/about.html - 2023-11-07T00:19:46.392Z + 2023-11-11T22:55:59.830Z https://openscapes.github.io/approach-guide/champions/index.html - 2023-11-07T00:19:47.944Z + 2023-11-11T22:56:02.050Z https://openscapes.github.io/approach-guide/champions/post-cohort-followup.html - 2023-11-07T00:19:48.752Z + 2023-11-11T22:56:03.182Z https://openscapes.github.io/approach-guide/approach/qual-assessment.html - 2023-11-07T00:19:49.748Z + 2023-11-11T22:56:04.566Z https://openscapes.github.io/approach-guide/approach/index.html - 2023-11-07T00:19:50.464Z + 2023-11-11T22:56:05.598Z https://openscapes.github.io/approach-guide/approach/onboarding.html - 2023-11-07T00:19:51.384Z + 2023-11-11T22:56:06.918Z https://openscapes.github.io/approach-guide/approach/documentation.html - 2023-11-07T00:19:52.600Z + 2023-11-11T22:56:08.666Z https://openscapes.github.io/approach-guide/approach/calendar.html - 2023-11-07T00:19:53.304Z + 2023-11-11T22:56:09.670Z https://openscapes.github.io/approach-guide/mentors-framework/engage.html - 2023-11-07T00:19:53.972Z + 2023-11-11T22:56:10.623Z https://openscapes.github.io/approach-guide/mentors-framework/onboarding.html - 2023-11-07T00:19:54.956Z + 2023-11-11T22:56:12.175Z https://openscapes.github.io/approach-guide/index.html - 2023-11-07T00:19:55.680Z + 2023-11-11T22:56:13.227Z https://openscapes.github.io/approach-guide/contributing/workflow.html - 2023-11-07T00:19:56.280Z + 2023-11-11T22:56:14.103Z https://openscapes.github.io/approach-guide/contributing/setup.html - 2023-11-07T00:19:56.900Z + 2023-11-11T22:56:15.023Z