02 Call Digest [ 2022-nasa-champions ]

[jules32]

Hi @NASA-Openscapes/2022-nasa-champions-team,

Thanks for another great session last week. We had hands-on time “committing” edits in GitHub and previewed what it will look like in JupyterHub (in preparation for our hands-on JupyterHub Clinic next week!) and discussed psychological safety. Below is a light digest of Call 02. 

We’ll see you tomorrow during Co-Working if you can make it (optional)! There is no agenda: it’s a time for you to work on your own code/open data science work in a social space and have others around you too to ask questions and learn with. 

Your Seaside Chat topic before next time is to practice/discuss GitHub with your larger group. We wanted to highlight the (CryoGARS)Team (@ellynenderlin @julialiu18 @RaineyAbe @khzikan @amankc @phoebekinzelman) that created a GitHub Organization for their research group (tweet). Discussing whether this makes sense for your groups too is a good Seaside Chat topic - some inspiration below.

Cheers,

The NASA-Openscapes Mentors @NASA-Openscapes/mentors-2021

Digest: Cohort Call 02 [ 2022-nasa-champions ]

Cohort Folder - contains agendas, video recordings, pathways folder
Cohort webpage: https://nasa-openscapes.github.io/2022-nasa-champions 

Goals: We practiced GitHub hands-on for collaborative research from the browser, demoed how this works with JupyterHub, and discussed team culture.

Task: Have a Seaside Chat with your research group to explore/practice GitHub.

Ideas:

• Update your team's information to the README: https://github.com/NASA-Openscapes/2022-nasa-champions#participating-teams 
• Review GitHub Clinic slides with your broader team
• Discuss “Excuse Me, Do You Have a Moment to Talk About Version Control?” (Bryan 2017, PeerJ) 
• Share updates in Slack or as a GitHub Issue!
  • Reply to this Issue or create new issues - Practice tagging your team and adding labels   
• Considering a GitHub Organization for your research group - here is additional inspiration:
• https://github.com/Openscapes/how_we_work
• https://pinsky.marine.rutgers.edu/fishbowl-chat-1/

Slide Decks:

• Intro to GitHub (slides)
  • 2 chapters in the Champions Lesson Series detail what we covered:
  • GitHub for Publishing
  • GitHub for Project Management
• Psychological safety (slides) 

A few lines from shared notes in the Agenda doc:

Most of our activity was in this GitHub repository; check out the commit history

• ‎Early career folks - how to be psych safe:
  • Think of the multitude of ‘requirements’ on your time and work as a constrained optimization problem - Constraints are everywhere, doing the best we can. Never stop learning
  • New people - what is the culture? Intention
  • https://thefaylab.github.io/lab-manual/ 
•  “Sharing mistakes” sessions where people can learn from each other. 
• Clear expectations and roles are important. If you know what you are expected to do (tasks, deliverables, meetings, etc)  and how everyone is supposed to professionally interact, that helps direct people. Training is also important!