Hi @Openscapes/css-cohort ,
Thank you all so much for participating in the Openscapes Champions program! A few things to wrap up:
-
Feedback! Openscapes improves with each cohort based on candid feedback. Because of our funding from Code for Science and Society we have two survey requests. Please fill out these surveys by Friday July 9:
- Openscapes survey for specific feedback on Openscapes
- This survey provides feedback to CS&S (pick Openscapes: Empowering Diverse Open Science Leaders.
-
Invitation to an optional 3-month check-in call on September 24, 10-11am PT (1-2pm ET); We will send a calendar invite now and a reminder email with light structure closer to the date. This will be a time for folks to share informal updates, reconnect, and ask questions.
-
We’ll draft a blog post in our Archive folder later this week; we invite you to add comments or suggestions if you’re interested.
-
Snail mail! Please email an address for your team to Julie so we can send stickers!
We are so grateful for your thoughtful engagement and impressed with your progress and pathway plans. We hope you continue to iterate your Seaside Chats with your research groups and we are happy to meet with your research groups during a Seaside Chat since not everyone from each team was able to make it to our last call. Please get in touch to schedule.
Please keep in touch on Slack and Twitter!
Cheers,
Julie & Erin
Digest: Cohort Call 4 [ CSS ]
Archive folder containing video recording and agenda
Goals: In our final session, each team shared their pathway and we heard a bit more about groups further along in their journey toward Open science.
Themes that came across through the final pathways shares:
- “Seaside chats” - Many groups shared plans to build community around shared open science data practices
- Lots of actions and next steps. We were excited to hear about groups using GitHub and creating code of conducts and lab manuals!
- We will spend more time in future cohorts on Pathways presentations :-)
Resources:
- PathwayShare
- “Graduation gift” - Openscapes badges by Allison Horst!
A few lines from the Agenda doc:
- Martin’s Star Trek themed pathway presentation
- We heard from Dr. Gavin Fay on how his group had progressed following participation in the Openscapes Champions program. It was interesting to hear how Openscapes-style working helped his group transition to remote work over the last year. He shared a slide deck and there are notes starting on pg 5.
- There was a lot of interest in Tidy Tuesday
Hi @Openscapes/css-cohort ,
Thank you all so much for participating in the Openscapes Champions program! A few things to wrap up:
Feedback! Openscapes improves with each cohort based on candid feedback. Because of our funding from Code for Science and Society we have two survey requests. Please fill out these surveys by Friday July 9:
Invitation to an optional 3-month check-in call on September 24, 10-11am PT (1-2pm ET); We will send a calendar invite now and a reminder email with light structure closer to the date. This will be a time for folks to share informal updates, reconnect, and ask questions.
We’ll draft a blog post in our Archive folder later this week; we invite you to add comments or suggestions if you’re interested.
Snail mail! Please email an address for your team to Julie so we can send stickers!
We are so grateful for your thoughtful engagement and impressed with your progress and pathway plans. We hope you continue to iterate your Seaside Chats with your research groups and we are happy to meet with your research groups during a Seaside Chat since not everyone from each team was able to make it to our last call. Please get in touch to schedule.
Please keep in touch on Slack and Twitter!
Cheers,
Julie & Erin
Digest: Cohort Call 4 [ CSS ]
Archive folder containing video recording and agenda
Goals: In our final session, each team shared their pathway and we heard a bit more about groups further along in their journey toward Open science.
Themes that came across through the final pathways shares:
Resources:
A few lines from the Agenda doc: