Forked Lessons

“Forking” is a concept from GitHub where you make a copy of someone’s files (traditionally code and documentation) into your own workspace so you can reuse, tailor, and extend to your needs. Importantly, your forked work is still networked back to the original with credit, and it is visible to others so they can learn from you, and find the original source.

Open science ideas and Openscapes approaches can be forked - this is a contributing way we can see culture change in action. There are growing resources developed by the Openscapes community as they make real change within their research groups, across their organizations, and beyond.

This is the beginning of a growing list; please share others to add as you see them You can suggest via GitHub on the right of this page - click “Edit this page” or “Report an Issue”, or email hello @ openscapes.org.

NASA Openscapes Cloud Tutorials

The NASA Earthdata-Openscapes Mentors team and other contributors are creating open educational resources to help researchers migrate workflows to the Cloud - all available for reuse and remix.

NASA Earthdata Cloud Cookbook

NOAA Fisheries Openscapes

The overarching vision of the NOAA Fisheries Openscapes is to support scientific researchers within the National Marine Fisheries Service (NMFS) by providing training in reproducible scientific workflows and platforms, facilitating collaboration across divisions in common scientific data science tasks, and providing shared “best practices” resources. Check out the NMFS R UG (R Users Group) for upcoming events and Wiki for links to resources and examples of open science at NOAA Fisheries.

NMFS-OpenSci (github)

NMFS-OpenSci Resource Book

NMFS-Openscapes (github)

Highlighting a few lessons by Eli Holmes and Em Markowitz:

Fay Lab Manual

This is the lab manual for the Fay Lab at the University of Massachusetts Dartmouth School for Marine Science and Technology.

https://thefaylab.github.io/lab-manual/

Check out how they’ve organized this onboarding document that prospective students and postdocs have said stood out to them. Consider reusing/remixing for your own group!

Slides from Gavin Fay’s 2022 talk at NOAA Alaska Fisheries Science Center

Getting to Know Open Science

Getting to Know Open Science: How to Engage and Flourish in the Growing Open Science Community

This is a slide deck presented on August 9, 2023 by Bri Lind at the NASA Hyperwall at the Ecological Society of America 2023 Annual Meeting, Portland, Oregon.

It is a super introduction to why open science.

California Water Board Data Center

https://github.com/CAWaterBoardDataCenter

R for Excel Users

This course is for Excel users who want to add or integrate R and RStudio into their existing data analysis toolkit. It is a friendly intro to becoming a modern R user, full of tidyverse, RMarkdown, GitHub, collaboration & reproducibility.

https://rstudio-conf-2020.github.io/r-for-excel/

Check out the resources throughout as well - it’s not only for Excel users, it’s for everyone.

Allison Horst - open educational resources

Allison Horst shares many open educational resources, including workshops and slides, at https://www.allisonhorst.com/:

“I actively work to contribute to open educational resources, including software for data science education (e.g. the palmerpenguins R dataset package), and artwork for data science & stats teachers and learners. From 2019 - 2020 I was RStudio’s first Artist-in-Residence. You can read more about my motivation in that role in this blog post, and you can find some of my R- and stats-related artwork in this repo.”

Allison developed the environmental data science program at UCSB https://ucsb-meds.github.io/.

Tidy Tuesday with lab groups

Reusing open approaches and ideas learned in Openscapes is awesome! Tidy Tuesday is a great example of this.

Allison Horst, 2019 Champion describes how she hosted in-person events with students and broader community:

https://openscapes.org/blog/2019/05/02/tidy-tuesday-coding-club/

Nyssa Silbiger, 2021 Champion describes how she hosted sessions with her research group:

For our group we had 2 hour sessions (1 hour is a bit too short for more novices and 2 hours gives the more advanced students time to try really new cool things). And we have a facilitator (usually me) that just checks in with the crew every few minutes and helps when students get stuck. But, it is very informal in that everyone just shows up and codes and chats. I have done this both in a conference room and at a bar. I also usually have people put some of their works in progress or final plots on the screen to show everyone else and share their “coding wins” or ask for help from the audience. And, yes, we use the Tidy Tuesday data because then they can also share their plots and code on twitter with the community and see the awesome creativity of the broader R community as well.