@@ -378,7 +376,8 @@ repository's Settings) will make not only the code and files of that repo public, but also all the Issues. Which is fine, but it might add considerations in terms of what is discussed in those Issues. -### Ocean Health Index example +::: {.callout-note icon="false"} +# How we did it: OHI Team Here is an example of the Ocean Health Index team’s thought process & strategy. @@ -399,6 +398,7 @@ These two needs led us to create a single private repository named especially since our team-lead can engage in these discussions by receiving emails about the Issues in their inbox, and can respond without having to go to GitHub.com. +::: ## Your Turn: Create & comment on issues @@ -407,7 +407,7 @@ Issues. Here is what to do: - Go to [github.com/openscapes/demo/issues](https://github.com/openscapes/demo/issues) -- Create an issue, tag people in your breakout group (ask for their +- Create an issue, tag colleagues (ask for their username) - Browse issues, comment in other issues - Try: @@ -416,14 +416,14 @@ Issues. Here is what to do: - Adding Issues to a Project (create one if need be) - Closing an Issue -Have fun! And throughout the process, talk to your breakout group, and +Have fun! And throughout the process, talk to your colleagues, and share what you learn. Here's what your inbox will look like afterwards:
-{fig-align="center" width="80%"} +{fig-align="center" width="70%"}
diff --git a/core-lessons/github/github-pub.qmd b/core-lessons/github/github-pub.qmd index 1035483..a0c7873 100644 --- a/core-lessons/github/github-pub.qmd +++ b/core-lessons/github/github-pub.qmd @@ -4,20 +4,6 @@ aliases: - /github-pub.html --- -```{=html} - -``` GitHub is known as a place to store code, but it's also a powerful publishing system. It is a way to help you share about your project on the open web, which lets you share about your science earlier. ## Preamble @@ -28,10 +14,6 @@ For this GitHub Clinic, we are going to work with GitHub from the browser only, GitHub can reduce friction for open science: it gives us avenues for communicating and publishing methods, blogs, interactive graphics and more, without a lot of heavy lifting! -### Prerequisite - -You will need to create **GitHub** account at
- -](images/2022-noaa-nwfsc-fall-esr.png){fig-alt="flow diagram outlining data files, code, analysis output, end product, the types of data, their locations, and the people who must manually interact with specific components" fig-align="center" width="589"} - -
- -](images/2022-noaa-sefsc-fall-tpb.png){fig-alt="diagram with question mark in center surrounded by 3 boxes labelled Current Responsibilities, Challenges, End Goal" fig-align="center" width="588"} - -
- -{.uri}](images/swfsc-sael-site-kourtney-burger.jpg){fig-alt="screenshot of web page. Left navigation bar with round NOAA logo above a table of contents. Right side has text titled Summary above a diagram of drifting acoustic buoy" fig-align="center" width="522"} - -### Read more - -- [Champions Program blog posts](https://openscapes.org/blog#category=champions); you'll find more Pathways shared as slides and stories following the 2-month cohort - -- [A TL;DR Collection of Stories from Openscapes Champions and Mentors](https://docs.google.com/presentation/d/1YAnaRFsKX3H6cSTXoOl-GksH-eebifQ6vzN7UwfoXUY/edit?usp=sharing); these stories are largely from 3 months+ following Pathways presentations - -```{=html} - -``` diff --git a/core-lessons/team-culture.qmd b/core-lessons/team-culture.qmd index 89d4025..ee6cbff 100644 --- a/core-lessons/team-culture.qmd +++ b/core-lessons/team-culture.qmd @@ -4,7 +4,7 @@ aliases: - ../team-culture.html --- -We discuss team culture because while we know that [diverse teams are more innovative](https://www.scientificamerican.com/article/how-diversity-makes-us-smarter/), creating spaces where everyone can do their best work and feel safe to contribute takes intention; it does not happen by default. There is a lot of work to do to improve research culture, and we can lead by example in our own research groups and communities. +We discuss team culture because while we know that [diverse teams are more innovative](https://www.scientificamerican.com/article/how-diversity-makes-us-smarter/), creating spaces where everyone can do their best work and feel safe to contribute takes intention. It does not happen by default. There is a lot of work to do to improve research culture, and we can lead by example in our own research groups and communities. ::: {.callout-warning icon="false"} ## Slides @@ -57,29 +57,20 @@ Role modeling sets a lot of team culture, and there is a lot we can learn and do ## Psychological safety -Amy C. Edmondson is the Novartis Professor of Leadership and Management at Harvard Business School. +Psychological Safety is defined as "a shared belief that team members will not be rejected or embarrassed for speaking up with their ideas, questions, or concerns". This is work by Dr. Amy Edmondson, the Novartis Professor of Leadership and Management at Harvard Business School. -a shared belief that team members will not be rejected or embarrassed for speaking up with their ideas, questions, or concerns +In the article [Research: To Excel, Diverse Teams Need Psychological Safety](https://hbr.org/2022/03/research-to-excel-diverse-teams-need-psychological-safety), Edmonson & Bresman recommend three ways to build psychologically safe environments: framing, inquiry, and bridging boundaries. -https://hbr.org/2022/03/research-to-excel-diverse-teams-need-psychological-safety - -They recommend three ways to build psychologically safe environments: framing, inquiry, and bridging boundaries. - -Frame meetings as opportunities for information-sharing. Frame differences as a source of value. - -Open questions. Questions that build shared ownership and causality. - -Listening - - -``` -Hopes and goals. What do you want to accomplish? -Resources and skills. What do you bring to the table? -Concerns and obstacles. What are you up against? What are you worried about? -``` +- Frame meetings as opportunities for information-sharing. Frame differences as a source of value. +- Open questions. Questions that build shared ownership and causality. +- Listening - by asking questions around + - Hopes and goals. What do you want to accomplish? + - Resources and skills. What do you bring to the table? + - Concerns and obstacles. What are you up against? What are you worried about? ### Science benefits from diversity -And we need to be deliberate about welcoming and including people from diverse backgrounds. +We need to be deliberate about welcoming and including people from diverse backgrounds. A few articles from Nature with many more links within: @@ -109,23 +100,21 @@ Have to build trust and be intentional, don’t hope for organic. ### Sustain the culture -Overtly showing kindness & a Code of Conduct can filter out people who don’t want to be subject to its enforcement – [rOpenSci](https://ropensci.org/blog/2016/12/21/commcallv12-review-coc/) +Overtly showing kindness & a Code of Conduct can filter out people who don’t want to be subject to its enforcement – [rOpenSci](https://ropensci.org/blog/2016/12/21/commcallv12-review-coc/). Research teams have people coming and going all the time; how do you set the tone and have it be sustainable? ## Deliberately setting the tone -Opening remarks at RStudio::conf 2019, in front of an audience of 1700 at a global software conference, Chief Scientist Hadley Wickham announces the Code of Conduct, how to identify RStudio staff if you need help, and how to mingle with welcoming body posture to invite others to join. This set the tone of the whole conference to be the most positive I have ever attended. +Opening remarks at RStudio::conf 2019, in front of an audience of 1700 at a global software conference, Chief Scientist Hadley Wickham announces the Code of Conduct, how to identify RStudio staff if you need help, and how to mingle with welcoming body posture to invite others to join. This set the tone of the whole conference to be the most positive many people have ever attended. ### Collegiality -We must deliberately set the tone for collegiality to create a positive, inclusive research group environment. This builds on the [Openscapes Mindset](mindset.qmd). - -Safety and accessibility are parts of inclusion and empowerment. Does everyone feel safe to speak up? Does everyone have channels to contribute? This is especially true as the tech we use evolves. Who can participate? +We must deliberately set the tone for collegiality to create a positive, inclusive research group environment. Safety and accessibility are parts of inclusion and empowerment. Does everyone feel safe to speak up? Does everyone have channels to contribute? This is especially true as the tech we use evolves. Who can participate? > "*This builds resilience to your research group. If someone needs to leave for a family emergency, maternity/paternity leave, vacation, set yourselves up so your team continue smoothly*" — Angela Bassa in her rstudio::conf 2019 talk "[Data Science as a Team Sport](https://forum.posit.co/t/data-science-as-a-team-sport-angela-bassa-rstudio-conf-2019l-video/24858/1)" -The opportunity cost of not doing this is burnout, and people leaving science. +The opportunity cost of not doing this is low morale, burnout, staff turnover, and people leaving science. diff --git a/how-do-i/do-fix-git-things.qmd b/how-do-i/do-fix-git-things.qmd index 1bba076..658fb77 100644 --- a/how-do-i/do-fix-git-things.qmd +++ b/how-do-i/do-fix-git-things.qmd @@ -56,3 +56,4 @@ By Dr. Eli Holmes [Not just for programmers: How GitHub can accelerate collaborative and reproducible research in ecology and evolution](https://besjournals.onlinelibrary.wiley.com/doi/10.1111/2041-210X.14108) Braga et al 2023 provides 12 ways researchers in ecology and evolution use GitHub, as well as resources and examples of researchers using and learning GitHub. + diff --git a/how-do-i/index.qmd b/how-do-i/index.qmd index 06afc8b..4fdf8c3 100644 --- a/how-do-i/index.qmd +++ b/how-do-i/index.qmd @@ -3,3 +3,4 @@ title: "How Do I..." --- This is a collection of resources that complement what we cover in the Champions Lesson Series - things that often come up as questions and that folks can screenshare and do together during Seaside Chats and Coworking sessions. We point to existing resources as much as possible. + diff --git a/how-do-i/refactor-modularize-code.qmd b/how-do-i/refactor-modularize-code.qmd index fb7a967..a8271b7 100644 --- a/how-do-i/refactor-modularize-code.qmd +++ b/how-do-i/refactor-modularize-code.qmd @@ -26,4 +26,4 @@ Abstract: > Functional programming (FP) provides a rich set of tools for reducing duplication in your code. The goal of FP is to make it easy to express repeated actions using high-level verbs. I think that learning a little about FP is really important for data scientists, because it's a really good fit for many problems that you'll encounter in practice. In this talk, I'll introduce you to the basics of functional programming in R, using the purrr package. I'll begin by briefly dissecting the for loop that you're already familiar with, then continue to show why functional programming provides elegant alternatives. I'll next dive into two examples showing where FP is particularly useful in data science: when ingesting unruly datasets spread across multiple files, and producing multiple reports for different stakeholders. -You'll get the most out of this talk if you're familiar with R, or you've done data science in other languages like Python. \ No newline at end of file +You'll get the most out of this talk if you're familiar with R, or you've done data science in other languages like Python. diff --git a/how-do-i/setup-rstudio-github.qmd b/how-do-i/setup-rstudio-github.qmd index f032d86..edf73f1 100644 --- a/how-do-i/setup-rstudio-github.qmd +++ b/how-do-i/setup-rstudio-github.qmd @@ -24,4 +24,4 @@ It's developed by [Sean Kross](https://seankross.com/), who also co-created the ### R and GitHub together -Now you'll want to practice how to use RStudio and GitHub. Follow [R for Excel Users' GitHub Chapter](https://rstudio-conf-2020.github.io/r-for-excel/github.html) to create a GitHub repository, clone it to RStudio, make edits, and practice syncing. \ No newline at end of file +Now you'll want to practice how to use RStudio and GitHub. Follow [R for Excel Users' GitHub Chapter](https://rstudio-conf-2020.github.io/r-for-excel/github.html) to create a GitHub repository, clone it to RStudio, make edits, and practice syncing. diff --git a/core-lessons/images/2022-noaa-nwfsc-fall-esr.png b/images/2022-noaa-nwfsc-fall-esr.png similarity index 100% rename from core-lessons/images/2022-noaa-nwfsc-fall-esr.png rename to images/2022-noaa-nwfsc-fall-esr.png diff --git a/core-lessons/images/2022-noaa-sefsc-fall-tpb.png b/images/2022-noaa-sefsc-fall-tpb.png similarity index 100% rename from core-lessons/images/2022-noaa-sefsc-fall-tpb.png rename to images/2022-noaa-sefsc-fall-tpb.png diff --git a/core-lessons/images/afsc-ecofoci.png b/images/afsc-ecofoci.png similarity index 100% rename from core-lessons/images/afsc-ecofoci.png rename to images/afsc-ecofoci.png diff --git a/core-lessons/images/pathway-example.png b/images/pathway-example.png similarity index 100% rename from core-lessons/images/pathway-example.png rename to images/pathway-example.png diff --git a/core-lessons/images/swfsc-sael-site-kourtney-burger.jpg b/images/swfsc-sael-site-kourtney-burger.jpg similarity index 100% rename from core-lessons/images/swfsc-sael-site-kourtney-burger.jpg rename to images/swfsc-sael-site-kourtney-burger.jpg diff --git a/index.qmd b/index.qmd index 56ab612..f0c424a 100644 --- a/index.qmd +++ b/index.qmd @@ -9,129 +9,29 @@ slug: index ## Welcome {#welcome} -Hello! This is the lesson series for the [**Openscapes Champions program**](https://www.openscapes.org/champions/), an open data science mentorship program for science teams. This is a professional development and leadership opportunity for teams to reimagine data analysis and stewardship as a collaborative effort, develop modern skills that are of immediate value to them, and cultivate collaborative and inclusive research communities. Openscapes Champions is not a typical workshop --- its cohort-based remote sessions for teams introduces concepts and workflows, facilitates teams to talk about problems, then go and solve them with accountability and support. It is a remote-by-design program, launched in 2019. +Hello! This is the lesson series for the [**Openscapes Champions program**](https://www.openscapes.org/champions/), an open data science mentorship program for science teams. This is a professional development and leadership opportunity for teams to reimagine data analysis and stewardship as a collaborative effort, develop modern skills that are of immediate value to them, and cultivate collaborative and inclusive research communities. Champions is not a typical training workshop. **Through Openscapes cohorts, people focus on their own work and their own personal or team goals as they learn open science concepts, tooling, and practices with examples from their peers.** It is a remote-by-design program, launched in 2019. -{fig-alt="A landscape consisting of a grassy meadow next to a sandy beach and ocean, a winding river, and distant mountains. In the foreground, a sad bunny and skunk are working alone on their laptops, each with a rain cloud over their heads. Nearby is a trailhead with a fox holding a 'Welcome!' sign for a variety of different critters to see. Past the trailhead are branching pathways through the Openscapes landscape. No matter the path, however, there are small groups of animals working together to find their way. Nods to data science are scattered throughout the image, including mountains made of data points and a satellite in the sky" fig-align="center" width="70%"} +{fig-alt="A landscape consisting of a grassy meadow next to a sandy beach and ocean, a winding river, and distant mountains. In the foreground, a sad bunny and skunk are working alone on their laptops, each with a rain cloud over their heads. Nearby is a trailhead with a fox holding a 'Welcome!' sign for a variety of different critters to see. Past the trailhead are branching pathways through the Openscapes landscape. No matter the path, however, there are small groups of animals working together to find their way. Nods to data science are scattered throughout the image, including mountains made of data points and a satellite in the sky" fig-align="center" width="70%"}
-All Champions Program resources are designed to also be a self-paced learning resource, and we know many people use the Champions Lesson Series for their own learning and for mentoring others, which is awesome. This Champions Lesson Series is improved openly and iteratively, and the most recent version always available online for reuse and remix. Each chapter in our **Core Lessons** focus on building a mindset and skillset for collaborative, reproducible workflows and culture within teams, while developing sustained learning practices connected with broader communities. +**All Champions Program resources are designed to also be a self-paced learning resource, and we know many people use the Champions Lesson Series for their own learning and for mentoring others, which is awesome.** This Champions Lesson Series is improved openly and iteratively, and the most recent version always available online for reuse and remix. Each chapter in our Core Lessons focus on building a mindset and skillset for collaborative, reproducible workflows and culture within teams, while developing sustained learning practices connected with broader communities. -See the [Champions Program webpage](https://www.openscapes.org/champions/) for programmatic details (including frequently asked questions like [what is a team](https://www.openscapes.org/faq/)). To learn what teams accomplish, explore [stories from 20+ previous cohorts](https://openscapes.org/blog#category=champions). - -## Purpose, Outcomes, Process (POP) - -This is the Champions Program [POP](https://suzannehawkes.com/2010/04/09/pop-everything/), a planning tool that we learned from the open science team at Mozilla. - -**Purpose:** to strengthen habits for immediate benefit that will help create long-lasting resilience in teams and workflows. We'll help you reimagine data analysis and stewardship through exploring open tools and practices; develop modern skills and habits that are of immediate value to you, including confidence and agency as leaders; cultivate collaborative and inclusive research communities with a Future Us mindset, starting with your team. - -**Outcomes:** different for everybody - this is about getting your own work done. Together we'll work on changing habits to improve your work and teamwork so you shape where you invest based on what you need. We'll develop a practice of reflecting, talking, and collaborating about data workflows with your team and community. You'll leave with a tangible Pathway (a planning document) that your team will use to help identify current practices and prioritize next steps. Your team will share your Pathway as work-in-progress during our last Cohort Call. Champions have found the Pathway valuable to communicate their needs and plans and to share with supervisors as a concrete outcome. - -**Process:** through facilitated Cohort Calls, team-driven Seaside Chats & Coworking, and How We Work (how we describe technical and cultural norms); Read on to learn more about these below. Additionally, every Champions Cohort includes at least one Mentor from the partner organization or community. Often a Mentor has participated in a Champions Cohort and expressed their interest in helping empower their colleagues as they build their open science and leadership skills, collaborate on solutions to common problems, and modernize their workflows. - -## Cohort Calls - -Research teams participate as a Champions Cohort with \~7 total teams over 2 months, meeting twice-monthly for five 1.5-hour sessions we call Cohort Calls. Teams focus on their own work. Each Cohort Call has two topics that introduce concepts, tooling, and examples from their peers, with time to reflect and discuss how the topics apply directly to our work. - -Cohort Calls are highly-structured and designed to be engaging, requiring discussion and active participation through scaffolded Agendas with shared live notetaking and breakout-group discussions. We begin each Cohort Call with a reminder of our [Code of Conduct](https://openscapes.org/code-of-conduct) and end each lesson with bite-sized Efficiency Tips and Inclusion Tips. Template agendas, as well as slides, tips, and other resources we use are openly available in this [Google Folder](https://drive.google.com/drive/folders/1Iq8tj81TSfr-RstphVTZWoz783xpJMOb), ready for reuse and remix. - -| Cohort Call Topics | Series Chapters | Seaside Chat Topics | -|--------------------|------------------------|----------------------------| -| 1\. Mindset, Better Science for Future Us | [mindset](core-lessons/mindset.qmd), [better science in less time](core-lessons/better-science.qmd) | Pathways trailhead - where are you now | -| 2\. GitHub Clinic: Publishing, Project Management | [publishing](core-lessons/github/github-pub.qmd), [project management](core-lessons/github/github-issues.qmd) | Shared organizing and onboarding | -| 3\. Team Culture, Data Strategies for Future Us | [team culture](core-lessons/team-culture.qmd), [data strategies](core-lessons/data-strategies.qmd) | Pathways next steps and documentation | -| 4\. Open Communities, Coding Strategies for Future Us | [open communities](core-lessons/communities.qmd), [coding strategies](core-lessons/coding-strategies.qmd) | Pathways share preparation | -| 5\. Pathways Share, Next Steps | [pathways](/core-lessons/pathways.qmd) | | - -You can find templates in this [Champions Cohorts Resources public folder](https://drive.google.com/drive/folders/1Iq8tj81TSfr-RstphVTZWoz783xpJMOb). - -## Seaside Chats & Coworking - -Between Cohort Calls, teams have synchronous spaces via Seaside Chats and Coworking to meet, ask questions, and exchange knowledge. Seaside Chats and Coworking have been described by participants as one of the most valuable parts of the Champions Program because it helps strengthen habits and a culture of shared workflows and learning. - -[**Seaside Chats**](https://www.openscapes.org/blog/2019/03/10/seaside-chats/) ([Lowndes et al. 2019](https://openscapes.github.io/supercharge-research/)) are when a team meets together independently for dedicated time for data/workflow discussions This is where teams talk and screenshare to begin identifying and addressing shared needs: Everyone has something to learn, ask, teach; don't need to be an expert in everything. Seaside Chats can include others that are not participating in the Champions Cohort. We'll provide suggestions for these meetings aligned with the [Pathways Document](/core-lessons/pathways.qmd) to organize your thoughts. The main purpose is to focus on your work at hand and build the habit of talking about and strengthening shared workflows with your broader group. We suggest you schedule these Seaside Chats with your team as soon as possible. - -Further, we facilitate optional **Coworking sessions**. Coworking comes in different flavors. For Champions Cohorts, coworking involves doing our own work at the same time together with opportunities to check in, and sometimes screenshare to get feedback or solve a problem. Seeing how other people work is a big part of this transition to working more openly and collaboratively. Some teams join Coworking together, meeting for their Seaside Chat in a breakout room with the option of talking to others in the Cohort. We will share optional Coworking times where you are welcome to come do your own work in a social setting. - -## How We Work - -"How We Work" refers to the technical and cultural norms we will establish during the Champions Cohort, which we developed through our [Openscapes Flywheel](https://openscapes.org/approach#openscapes-flywheel) ([Robinson and Lowndes 2022](https://eartharxiv.org/repository/view/4560/)). These approaches have become some of the most valuable things teams take with them through the Champions Program, and we love hearing how folks are taking these practices to new places as they grow as leaders. - -### Welcome - -We are intentional to create a welcoming environment, through art, design, and clear norms. You are all welcome here. We are creating a positive learning space where everyone is welcome to ask questions and participate. We'll start off each call with a reminder of our [Code of Conduct](https://www.openscapes.org/code-of-conduct/). - -### Space & Place - -Together we will be creating space and place to learn, collaborate, and create shared workflows so that we aren't all responsible for this alone. - -Our Cohort will have a single **shared folder** (via Google Drive/ Microsoft Teams) that we will share ahead of time and will be linked from the calendar invite. This will have all resources specific to our Cohort. Each Cohort Call will have a highly-structured **Agenda document** so you know what is planned --- and so you can more easily catch up if your internet drops out. We use headers so that you can navigate via the Table of Contents view. (In Google Docs, you can enable Outline view by selecting View \> Show outline.) These agendas are for live-note taking throughout the Cohort Call. It is our shared responsibility to contribute & help document for future us; this is the main place for nonverbal contribution, side conversations, and to reinforce ideas. - -
- -{fig-alt="screenshot of a laptop computer screen with Zoom & Google Docs side-by-side with windows narrowed" fig-align="center" width="70%"} - -During Cohort Calls, we **encourage videos on** ("faces on") -- but it is okay if this is not possible for any reason. In Zoom, you can enable Gallery View by clicking Settings \> Video \> Display up to 49 participants. We ask you to **mute liberally/quickly** to reduce background noise -- but please unmute to speak up at any point. You'll interact in small groups via breakout groups, this will help you reflect on your work and get to know each other. - -We have a **flipped approach to screensharing**. This shows up in two ways. First, we do not screenshare slides while presenting. Instead we provide links to slides and presenters indicate when everyone should advance to the next slide. This minimizes bandwith issues and enables everyone to zoom in, click on links, linger, and go back, as they prefer. Second, we do screenshare to demonstrate keyboard shortcuts, live examples of how we work, and troubleshoot. Screensharing to show current practices and ask for help is a big part of Coworking sessions and Seaside Chats. - -At the start of each Cohort, we send **Google Calendar invites** to everyone for all Cohort Calls and optional Coworking sessions. These include the Zoom link (or Teams / Google Meet) to join, and a link to the Cohort's shared Google Folder so we don't all have to hunt for those each time. - -We start and end on time. - -### Learning & Trust - -Learning new things is uncomfortable and it can feel vulnerable to ask questions. Through creating a welcoming space we can invest in learning and trust together. We know there is a range of technical experience -- by design! We are all here because we want to learn and improve our work around data-intensive science. We're all imperfect and learning together -- Openscapes team included. We're all accountable to each other. - -Examples of how teams strengthen learning and trust within their groups are captured in our Pathways share in the final Cohort Call. Common themes are, meeting regularly, knowing who and where to ask for help, and building shared documentation and resources to reduce emails asking where things are. - -### Work Openly - -We role model working openly throughout the Cohort by sharing ideas, resources, and screensharing. All our resources are created with the same tools we teach research teams (R, GitHub, Google Drive) and shared openly. During Cohort Calls, our Agenda and open facilitation style is part of working openly --- we iterate openly as facilitators and mentors, for example through adjusting the timing live in the Agenda document. - -We send **Digests** the week following each Cohort Call (early, on Monday or Tuesday). Each digest includes the Call's goals, links to the Call's agenda, slides, and recording, and some excerpts from the shared notes. These provide a touch point in the week between Calls. See examples: [2022-nasa-champions](https://github.com/NASA-Openscapes/2022-nasa-champions/labels/digest), [2022-noaa-afsc](https://github.com/Openscapes/2022-noaa-afsc/labels/digest), [2021-fdd](https://github.com/Openscapes/2021-fdd/labels/digest). - -Many teams begin working more openly via shared documentation, project management, metadata, file organization and naming, and code organization and interoperability, using tools like Google Drive/Microsoft Teams, GitHub, R, and Python. - -### Common Workflows - -We reuse what works from other places in our work (we sometimes talk about this as "forking", borrowing a term from GitHub where you make a copy in your own workspace so you don't have to start from scratch). This often shows up in Champions Cohorts with teams reusing the Agendas structure and the concepts of Seaside Chats and Coworking with their broader research groups. - -We discuss practices from different open communities, and teams contribute so that others can build from their work as well. - -### Inspire - -Storytelling and sharing what works is so valuable for others to learn from and be inspired by. Many concepts and possibilities are new, so there is value in the idea of "show me" in a way that resonates. - -Inspiring others happens in small moments, that can look like someone leaning forward in their chair saying "I want to do that" when someone else is screensharing during Coworking. It can mean asking for 5 minutes at the start of a meeting to share something new you learned. These moments also build up to real culture change as folks give talks to their organizational leadership and broader open communities, and the Flywheel turns again. - -## Supercharge Your Research - -If you have read this page, you are prepared for your Cohort! We're often asked what people can do to further prepare in advance. Additional suggested reading include: - -[**Our path to better science in less time using open data science tools**](https://www.nature.com/articles/s41559-017-0160) (Lowndes et al. 2017). This describes a marine science team's transition to open collaborative teamwork. It was the original inspiration for creating the Champions Program and heavily influences the Core Lessons. - -[**Supercharge your research: a ten-week plan for open data science**](https://openscapes.github.io/supercharge-research/) (Lowndes et al. 2019). This was co-authored with the inaugural Champions Cohort, capturing the most valuable take-aways for marine and environmental science early career faculty. - -[**Shifting institutional culture to develop climate solutions with Open Science**](https://onlinelibrary.wiley.com/doi/10.1002/ece3.11341) (Lowndes et al 2024, Ecology & Evolution). This was co-authored by Openscapes mentors across organizations – including NASA Earthdata, NOAA Fisheries, EPA, California Water Boards, Pathways to Open Science, Fred Hutch Cancer Center. - -See also other publications and presentations at [openscapes.org/media](https://openscapes.org/media). + ## About -[Openscapes](https://openscapes.org) is an approach and a movement that helps researchers and those supporting research find each other and feel empowered to conduct data-intensive science. Through a creative approach drawing inspiration and skills from many places, we provide structures for technical skill-building, collaborative teamwork, and inclusive community development. Our work builds from many others in the open movement. +### Openscapes -Read more about How We Work: +[Openscapes](https://openscapes.org) is an open source approach and movement that helps researchers and those supporting research find each other and feel empowered to conduct data-intensive science. Through a creative approach drawing inspiration and skills from many places, we provide structures for technical skill-building, collaborative teamwork, and inclusive community development. Our work builds from many others in the open movement. -- [Openscapes Approach Guide](https://openscapes.github.io/approach-guide) -- [The Openscapes Flywheel: A framework for managers to facilitate and scale inclusive Open science practices](https://eartharxiv.org/repository/view/4560/) (Robinson & Lowndes 2022) -- [Shifting institutional culture to develop climate solutions with Open Science](https://onlinelibrary.wiley.com/doi/10.1002/ece3.11341) (Lowndes et al 2024, Ecology & Evolution) -- [3 lessons from remote meetings we're taking back to the office](https://opensource.com/article/20/6/remote-meetings) (Lowndes, Cabunoc Mayes & Sansing 2020) -- [How to run a remote workshop, Openscapes/Open Leaders-style](https://openscapes.org/blog/2020-03-11-tips-remote-workshops/) (complementing blog post) +Learn more about Openscapes [initiatives](https://openscapes.org/initiatives) through our many other [open resources](https://openscapes.org/resources), [media](https://openscapes.org/media), and [events](https://openscapes.org/events), and [connect](https://openscapes.org/connect) with us. ### This Series Book -The Series is written (and always improving) to be used as a reference, to teach, as self-paced learning, and for reuse and remix. And also, awesomely, it's created with the same tools and practices we will be talking about: R/RStudio - originally [bookdown](https://bookdown.org/yihui/bookdown/) and now [quarto](https://quarto.org) - and GitHub. +The Series is written (and always improving) to be used as a reference, to teach, as self-paced learning, and for reuse and remix ("forking", to borrow a term from open source software). And also, awesomely, it's created with the same tools and practices we will be talking about: R/RStudio - originally [bookdown](https://bookdown.org/yihui/bookdown/) and now [quarto](https://quarto.org) - and GitHub. ### Citation @@ -145,61 +45,7 @@ The citation will look something like: Please visit the Lesson Series [DOI link](https://doi.org/10.5281/zenodo.7407246) to get the most recent version - the one above is not automatically generated and may be out of date if we release an updated version. -```{=html} - -``` - ------------------------------------------------------------------------
Openscapes is licensed under a Creative Commons Attribution 4.0 International License.
-```{=html}
-
-```
diff --git a/pathways.qmd b/pathways.qmd
new file mode 100644
index 0000000..733fd64
--- /dev/null
+++ b/pathways.qmd
@@ -0,0 +1,111 @@
+---
+title: Pathways and Outcomes
+subtitle: The Pathways concept help people make and communicate progress about shifting their workflows with open science
+aliases:
+ - core-lessons/pathways.html
+---
+
+2-month Champions Cohorts go by quickly. In our final session, each team shares what they’ve learned through their work-in-progress. Outcomes are different for each team or individual, depending on what they decided to focus on.
+
+Teams share their progress through our **Pathways concept** that frames how they work now and where they would like to go in terms of reproducibility, collaboration, communication, and culture. Practically speaking, this is the Pathways spreadsheet document, a template that builds off of [Table 1 from Lowndes et al. 2017](https://www.nature.com/articles/s41559-017-0160/tables/1), but we’ve added this fourth important “culture” category so teams can be explicit about their plans for diversity, equity, inclusion as well as reproducibility, collaboration, and communication. Read on for example stories and guidance.
+
+## Pathways stories
+
+"Show-not-tell" is an important concept in Openscapes, particularly since "what does open science look like"? is a question often asked.
+
+Below are a few one-slide pictures of Pathways presented by Champions teams in their final sessions. For deeper details, [scroll the blogs](https://openscapes.org/blog#category=champions) on what Champions teams and individuals have accomplished in the 24+ Champions Cohorts over the past 5 years. People often describe what they will do next, and then we see how they've implemented those plans in the optional 3-month check-in we host after the cohort conclusion.
+
++ +](images/afsc-ecofoci.png){fig-align="center" width="85%"} + +
+ +](images/2022-noaa-nwfsc-fall-esr.png){fig-alt="flow diagram outlining data files, code, analysis output, end product, the types of data, their locations, and the people who must manually interact with specific components" fig-align="center" width="85%"} + +
+ +](images/2022-noaa-sefsc-fall-tpb.png){fig-alt="diagram with question mark in center surrounded by 3 boxes labelled Current Responsibilities, Challenges, End Goal" fig-align="center" width="85%"} + +
+ +{.uri}](images/swfsc-sael-site-kourtney-burger.jpg){fig-alt="screenshot of web page. Left navigation bar with round NOAA logo above a table of contents. Right side has text titled Summary above a diagram of drifting acoustic buoy" fig-align="center" width="85%"} + + +> “I didn’t think to find solutions, because I didn’t realize that there was a problem; I thought that this was just the nature of doing [ecological] research – an endless pile of confusingly named csv files and R scripts....Now that I can see all the ways that our lab has profited from this initial investment, I cannot imagine how I managed without Openscapes’ principles. Our lab is producing substantially more science of higher quality and we are making more of our underlying data and code publicly available as a direct result of Openscapes’ intervention.” - +Dr. Chelsea Wood, University of Washington + +See also [A TL;DR Collection of Stories from Openscapes Champions and Mentors](https://docs.google.com/presentation/d/1YAnaRFsKX3H6cSTXoOl-GksH-eebifQ6vzN7UwfoXUY/edit?usp=sharing); these stories are largely from 3 months+ following Pathways presentations. + +## Pathways concept + +The Pathways concept is put to practice by an actual document that provides a structured way for your team to think how you work and find common approaches and needs ([template](https://docs.google.com/spreadsheets/d/1rmhOly87OYrPOUqTzmccYbPrTlGmXGsN06GI1FKzxag/edit?usp=sharing)). + +This spreadsheet format has helped many groups think through their trailhead and identifying where they are now. Some groups have found it more useful to draw things out as a workflow on a whiteboard or google slide. The spreadsheet format might not work for your group, and that is okay; teams can use whatever format makes sense for them. + +::: {.callout-warning icon="false"} +## Slides + +The Pathway Intro slides in the latter part of this deck were presented in a Champions Cohort. + +[Documentation & the Pathway](https://docs.google.com/presentation/d/1vuZVu7YXyKAgCAM65hjdalvUyimIqnL94BDDsoM-uxI/) +::: + +{fig-align="center" width="85%"} + + + +### Planning guidance + +*The following is written as guidance for people using the Pathways concept.* + +You'll develop your Pathway by talking with others on your team, screensharing ("show me"), and asking questions. + +You'll use the document by creating a copy of the template and then discussing with your team. Start with the "Now" column. How do you work now? Add rows as best reflects your work, but take a moment before deleting them in case it's something you haven't thought about in this way before rather than if it's not relevant to you. Then, move on to the "Next Steps" column as you think through priorities and learn from/with/for your cohort. This will be a work in progress throughout the cohort that you'll present a snapshot of in the final Cohort Call (see next) and that you can revisit following the cohort as well. + +### Presenting guidance + +On the final Cohort Call, each team presents their Pathways. Each team has 3 minutes to share followed by 2 minutes for questions. We encourage leads not to present, and it's great when we hear multiple voices from the teams. In the spirit of teamwork, many people co-present their Pathways, and provide plans for how they are moving from solo practices toward shared practices. + +**This is informal sharing of unpolished work-in-progress.** Everyone makes progress throughout the Cohort: in mindsets, planning and actions. This is an opportunity to reflect and talk about it, building on the reflection breakout rooms that began most Cohort Calls. We've been reflective each week and we've all made progress. + +Presentations do not need be line-by-line of the Pathways Spreadsheet and there's no wrong way to talk about your progress. Whatever your group wants to create and share is great - could be a photo of a whiteboard, a slide, the Pathways spreadsheet, or a "screenshare and tell" live walk-through of your files/code/ideas. + +A few reflection prompts that can help frame the presentations: + +- What are the practices we've covered during the Cohort that most compel you? +- What are the practices we've covered during the Cohort that most confuse you? +- Are there practices that are new to you that you didn't originally think would work with your own research interests? If so, which? +- What are your two biggest take-aways from the Cohort? +- What future revisions will you propose making for your pathway? +- Any final questions you want to workshop with the Cohort? + +```{=html} + +``` + + + + +## What is the impact of this? + +What do impacts look like after the Champions Program has completed? [NOAA Fisheries](https://nmfs-openscapes.github.io/) has participated in 10 Champions Cohorts (400 staff) since 2020, which helped scaffold plans for the [Biden-Harris Administration announces support for NOAA Fisheries’ data, infrastructure, and workforce modernization in part via Openscapes](https://www.fisheries.noaa.gov/media-release/biden-harris-administration-announces-34-million-modernize-noaa-fisheries-data). They may be the best example to answer the question "What does shifting to open science look like across a federal agency like NOAA, and what are the impacts to the efficiency and quality of their scientific products?": + +- [**A Year of Open Science Community Building at NOAA Fisheries (video)**](https://www.youtube.com/watch?v=n1VaV8f6qQE&list=PLChfyH8TVDGnB_zDCm8d9oonMomfk8v9X&index=14). Eli Holmes (NOAA Fisheries Open Science), Evan Howell (Director of the Office of Science and Technology), Megsie Siple (Alaska Fisheries Science Center), Amanda Bradford (Pacific Islands Fisheries Science Center), Brian Fadely (Alaska Fisheries Science Center Marine Mammal Stock Assessments), Vivian Matter (Branch Chief of Southeast Fisheries Science Center), Kathryn Doering (Office of Science and Technology), Christine Stawitz (Office of Science and Technology), Carissa Geravsi (Gulf of Mexico Integrated Ecosystem Assessment), Lynn Dewitt (California Current Ecosystem Assessment Team). Year of Open Science Culminating Conference, March 21, 2024. diff --git a/program-summary.qmd b/program-summary.qmd new file mode 100644 index 0000000..c1b2425 --- /dev/null +++ b/program-summary.qmd @@ -0,0 +1,42 @@ +--- +title: Program Summary +subtitle: Openscapes Champions is an open data science mentorship program for science teams +--- + +## Overview + +**Openscapes Champions helps people reimagine data analysis & stewardship as a collaborative effort, develop modern skills that are of immediate value to them, and cultivate collaborative and inclusive research communities.** The Champions program was built from experience and has supported professionals in academia, government, and non-profit groups — and we have the improved the program from their needs and from current practices in the open science community. This transformational 10-week program consists of biweekly, 1.5-hour remote group sessions, with additional optional coworking times. + +## Program Details + +```{=html} + +``` +**Openscapes Champions is a multi-month program that is led remotely and designed to ignite incremental and sustainable change within research groups --- and beyond.** The program remotely convenes a cohort of science teams (7-10 teams of up to 5 people; 40 people max) twice per month over two months for 1.5-hour video calls that we call Cohort Calls. This is not a workshop. It is cohort-based facilitated sessions to help people collaboratively evolve their work (work they’re already doing) with input from peers. It helps people reflect on and modernize how they work! + +**The Champions program is designed so that small time requirements over longer time frames fosters incremental change, accountability, and community building within the realities of people's busy schedules, varying expertise and needs.** Each Cohort Call uses the [Champions Lesson Series](https://openscapes.github.io/series) you are reading; it is an open curriculum that is openly iterated with new lessons and peer examples, and with the most recent version always available online. The core lessons were originally based on what was instrumental in the Ocean Health Index team's [path to better science in less time](https://www.nature.com/articles/s41559-017-0160), and each chapter includes slides for core and newly developed lessons taught and iterated for Cohort Calls. We start off each call with a reminder of our Code of Conduct and provide multiple channels for participation, including through silent contributions to the Agenda with live note-taking, breakout groups, and full-group discussions. Each call closes with an efficiency tip and an inclusion tip to incorporate into daily practice. + +**Participants attend as teams — or sometimes individuals or subsets from teams — and come prepared for engaged participation as a whole cohort and within smaller breakout groups.** Discussions focus around collaborative mindsets, norms, and software to enable open, reproducible, inclusive research, introducing tooling like R, Python, tidyverse, GitHub, RMarkdown/Quarto, Google Drive, JupyterHubs, metadata and practices from open source communities, inclusive design, psychological safely, facilitation techniques, with examples from relevant research domains including the Ocean Health Index and previous Champions. Teams intentionally have a mix of data/coding/documentation experience and responsibilities. All skills and interests welcome - there are no coding prerequisites to participate. + +**The Openscapes Champions program is designed so that everyone can learn new approaches and make progress, no matter where they are starting from.** People sometimes participate repeatedly over years and focus on new things each time. Each team creates a Pathway document to start thinking about where they are now in terms of the tools and practices for reproducibility, collaboration, communication, and culture. Throughout the Cohort, teams develop their Pathway to help identify, prioritize and articulate their needs and next steps. Pathway progress from each team is presented in the final session, which helps participants practice articulating their data workflow plans and needs, and see similarities and allies across the cohort to continue on these paths together. + +**With Cohort Calls occurring twice monthly on alternating weeks, the time in between each session enables participants to reflect and practice new concepts while the Openscapes team incorporates feedback and iterates to better support cohort needs.** One way we suggest reinforcing this is through a regular practice of self-organized team data-workflow meetings ("[Seaside Chats](https://openscapes.github.io/supercharge-research/)") in the alternating weeks between cohort calls. This gives people an opportunity to share their learning with their broader team or collaborators and to establish norms around data and code management and inclusive onboarding practices, and identify things they want to learn together and things they can teach each other. The Openscapes team also facilitates [Coworking sessions](https://onlinelibrary.wiley.com/doi/10.1002/ece3.11341), where people can do their own work at the same time together, with opportunities to check in, ask questions, and screenshare to get feedback or solve a problem. + +**The remote- and cohort-nature of the program is designed to reinforce each other's learnings and networks across participating teams.** This has been especially important for remote and hybrid work, onboarding new colleagues, and establishing the positive culture we want in science. It also has helped people develop leadership skills as they advance in their careers. We have led over 20 Champions Cohorts with over 700 participants from academia, federal and state agencies (US and Canada), and non profits. The value of the Champions program is that it has helped participants make progress on making their own workflows more efficient and reproducible, and it has helped them connect more with their peers. Further, it has also connected them across cohorts and other parts of open science and beyond, as we all contribute to changing the culture of science. + +
+ +```{=html} + +``` diff --git a/what-to-expect.qmd b/what-to-expect.qmd new file mode 100644 index 0000000..c95df24 --- /dev/null +++ b/what-to-expect.qmd @@ -0,0 +1,208 @@ +--- +title: What to Expect (Program Level) +--- + +Openscapes Champions is not a typical workshop. It is cohort-based facilitated sessions to help people collaboratively evolve their work (work they’re already doing) with input from peers. It helps people reflect on and modernize how they work! The sessions introduce concepts and workflows and facilitate teams to talk about problems, so they can go and solve them with accountability and support. Note that whether people participate as teams or as individuals, we focus on teamwork and provide opportunities for people to find common parts of their workflows and "find their teams" beyond any traditional definition, so that we can all help make science less lonely and more networked. + +## Purpose, Outcomes, Process (POP) + +This is the Champions Program [POP](https://suzannehawkes.com/2010/04/09/pop-everything/), a planning tool that we learned from the open science team at Mozilla. + +**Purpose** The purpose is to strengthen habits for immediate benefit that will help create long-lasting resilience in teams and workflows. We'll help you reimagine data analysis and stewardship through exploring open tools and practices; develop modern skills and habits that are of immediate value to you, including confidence and agency as leaders; cultivate collaborative and inclusive research communities with a Future Us mindset, starting with your team. + +**Outcomes.** Outcomes are different for everybody - this is about getting your own work done. Together we'll work on changing habits to improve your work and teamwork so you shape where you invest based on what you need. We'll develop a practice of reflecting, talking, and collaborating about data workflows with your team and community. You'll leave with a tangible Pathway (a planning document) that your team will use to help identify current practices and prioritize next steps. Your team will share your Pathway as work-in-progress during our last Cohort Call. Champions have found the Pathway valuable to communicate their needs and plans and to share with supervisors as a concrete outcome. + +**Process.** The Champions Program operates via facilitated Cohort Calls, team-driven Seaside Chats, and Coworking, and role modeling open science via How We Work — all of which are described more below. Additionally, every Champions Cohort includes at least one Mentor from the partner organization or community. Often a Mentor has participated in a Champions Cohort and expressed their interest in helping empower their colleagues while addressing needs specific to their organization. + +## Cohort Calls + +The main synchronous time during Champions Cohorts are twice-monthly 1.5-hour sessions we call Cohort Calls. Each Cohort Call has two topics that introduce concepts, tooling, and examples from their peers, with time to reflect and discuss how the topics apply directly to their work. + +Cohort Calls are highly-structured and designed to be engaging, requiring discussion and active participation through scaffolded Agendas with shared live notetaking and breakout-group discussions. We begin each Cohort Call with a reminder of our [Code of Conduct](https://openscapes.org/code-of-conduct) and end each lesson with bite-sized Efficiency Tips and Inclusion Tips. + +| Cohort Call Topics | Series Chapters | Seaside Chat Topics | +|--------------------|------------------------|----------------------------| +| 1\. Mindset, Better Science for Future Us | [mindset](core-lessons/mindset.qmd), [better science in less time](core-lessons/better-science.qmd) | Pathways trailhead - where are you now | +| 2\. GitHub Clinic: Publishing, Project Management | [publishing](core-lessons/github/github-pub.qmd), [project management](core-lessons/github/github-issues.qmd) | Shared organizing and onboarding | +| 3\. Team Culture, Data Strategies for Future Us | [team culture](core-lessons/team-culture.qmd), [data strategies](core-lessons/data-strategies.qmd) | Pathways next steps and documentation | +| 4\. Open Communities, Coding Strategies for Future Us | [open communities](core-lessons/communities.qmd), [coding strategies](core-lessons/coding-strategies.qmd) | Pathways share preparation | +| 5\. Pathways Share, Next Steps | [pathways](/core-lessons/pathways.qmd) | | + +Template agendas, as well as slides, tips, and other resources we use are openly available in this [Champions Cohorts Resources public folder](https://drive.google.com/drive/folders/1Iq8tj81TSfr-RstphVTZWoz783xpJMOb), ready for reuse and remix. + +## Seaside Chats & Coworking + +Between Cohort Calls, teams have synchronous spaces via Seaside Chats and Coworking to meet, ask questions, and exchange knowledge. + +**Seaside Chats** ([Lowndes et al. 2019](https://openscapes.github.io/supercharge-research/)) are when a team meets together independently for dedicated time for data/workflow discussions. Seaside Chats are where teams talk and screenshare to begin identifying and addressing shared needs. Everyone has something to learn, ask, teach; people do not need to be an expert to share what they know. Seaside Chats are encouraged to include others that are not participating in the Champions Cohort. The main purpose is to focus on the work at hand and build the habit of talking about and strengthening shared workflows with a broader group. We will provide suggestions about what you could focus on to get started. + +**Coworking** [(Lowndes et al. 2024)](https://onlinelibrary.wiley.com/doi/10.1002/ece3.11341) comes in different flavors. For Champions Cohorts, coworking involves people doing their own work at the same time together with opportunities to check in, and sometimes screenshare to get feedback or solve a problem. Seeing how other people work is a big part of this transition to working more openly and collaboratively. Some teams join Coworking together, meeting for their Seaside Chat in a breakout room with the option of talking to others in the Cohort. We will share optional Coworking times where you are welcome to come do your own work in a social setting. + +**Seaside Chats and Coworking have been described by participants as one of the most valuable parts of the Champions Program because it helps strengthen habits and a culture of shared workflows and learning.** See also: [\[Sea\]side Chats for data workflows](https://www.openscapes.org/blog/2019/03/10/seaside-chats/), a 2019 blog. + + + +## How We Work + +"How We Work" refers to the technical and cultural norms we will establish during the Champions Cohort, which we developed through our [Openscapes Flywheel](https://openscapes.org/approach#openscapes-flywheel) ([Robinson and Lowndes 2022](https://eartharxiv.org/repository/view/4560/)). These approaches have become some of the most valuable things teams take with them through the Champions Program, and we love hearing how folks are taking these practices to new places as they grow as leaders. + +### Common Workflows + +We reuse what works from other places in our work (we sometimes talk about this as "forking", borrowing a term from GitHub where you make a copy in your own workspace so you don't have to start from scratch). This often shows up in Champions Cohorts with teams reusing the Agendas structure and the concepts of Seaside Chats and Coworking with their broader research groups. + +We discuss practices from different open communities, and teams contribute so that others can build from their work as well. + +### Inspire + +Storytelling and sharing what works is so valuable for others to learn from and be inspired by. Many concepts and possibilities are new, so there is value in the idea of "show me" in a way that resonates. + +Inspiring others happens in small moments, that can look like someone leaning forward in their chair saying "I want to do that" when someone else is screensharing during Coworking. It can mean asking for 5 minutes at the start of a meeting to share something new you learned. These moments also build up to real culture change as folks give talks to their organizational leadership and broader open communities, and the Flywheel turns again. + +### Welcome + +We are intentional to create a welcoming environment, through art, design, and clear norms. "You are all welcome here." We aim to create a positive learning space where everyone is welcome to ask questions and participate. We start off each call with a reminder of our [Code of Conduct](https://www.openscapes.org/code-of-conduct/). + +### Space & Place + +Together we will create space and place to learn, collaborate, and create shared workflows so that we aren't all responsible for this alone. + +Each Cohort will have a single **shared folder** (via Google Drive/ Microsoft Teams) that we will share ahead of time and will be linked from a calendar invite so there are multiple ways to find it again. This will have all resources specific to each Cohort. Each Cohort Call will have a highly-structured **Agenda document** so people know what is planned --- and so they can more easily catch up if/when the internet drops out. We use headers so that it is possible to navigate via the Table of Contents view. (In Google Docs, you can enable Outline view by selecting View \> Show outline.) These agendas are for live-note taking throughout the Cohort Call. It is a shared responsibility to contribute & help document for Future Us; this is the main place for nonverbal contribution, side conversations, and to reinforce ideas. + +
+ +{fig-alt="screenshot of a laptop computer screen with Zoom & Google Docs side-by-side with windows narrowed" fig-align="center" width="70%"} + +During Cohort Calls, we **encourage videos on** ("faces on") -- but it is okay if this is not possible for any reason. In Zoom, the Gallery View is enabled by clicking Settings \> Video \> Display up to 49 participants. We ask people to **mute liberally/quickly** to reduce background noise -- but unmute to speak up at any point. Participants will interact in small groups via breakout groups, which will help them reflect on how examples apply to their work and to get to know each other. + +We have a **flipped approach to screensharing**. This shows up in two ways. First, we do not screenshare slides while presenting. Instead we provide links to slides and presenters indicate when everyone should advance to the next slide. This minimizes bandwith issues and enables everyone to zoom in, click on links, linger, and go back, as they prefer. Second, we do screenshare to demonstrate keyboard shortcuts, live examples of how we work, and troubleshoot. Screensharing to show current practices and ask for help is a big part of Coworking sessions and Seaside Chats. + +At the start of each Cohort, we send **Calendar invites** to everyone for all Cohort Calls and optional Coworking sessions. These include the Zoom / Teams / Google Meet to join, and a link to the Cohort's shared Folder so we don't all have to hunt for those each time. + +We start and end on time. + +### Learning & Trust + +Learning new things is uncomfortable and it can feel vulnerable to ask questions. Through creating a welcoming space we can invest in learning and trust together. We know there is a range of technical experience and comfort in every cohort -- by design! Participants are all opting in to the cohort to learn and improve work around data-intensive science. Everyone is imperfect and learning together -- Openscapes team included. We build accountability to each other. + +Discussions focus around collaborative mindsets, norms, and software to enable open, reproducible, inclusive research, introducing tools like R, Python, tidyverse, GitHub, RMarkdown/Quarto, Google Drive, JupyterHubs and practices from open source communities, inclusive design, psychological safely, facilitation techniques, with examples from relevant research domains including the Ocean Health Index and previous Champions. + +Examples of how teams strengthen learning and trust within their groups are captured in our Pathways share in the final Cohort Call. Common themes are, meeting regularly, knowing who and where to ask for help, and building shared documentation and resources to reduce emails asking where things are. + +### Work Openly + +We role model working openly throughout the Cohort by sharing ideas, resources, and screensharing. All our resources are created with the same tools we teach research teams (R, GitHub, Quarto, Google Drive, JupyterHub) and shared openly. During Cohort Calls, the Agenda and open facilitation style is part of working openly --- we iterate openly as facilitators and mentors, for example through adjusting the timing live in the Agenda document. + +We send **Digests** the week following each Cohort Call (early, on Monday or Tuesday). Each digest includes the Call's goals, links to the Call's agenda, slides, and recording, and some excerpts from the shared notes. These provide a touch point in the week between Calls. See examples: [2022-nasa-champions](https://github.com/NASA-Openscapes/2022-nasa-champions/labels/digest), [2022-noaa-afsc](https://github.com/Openscapes/2022-noaa-afsc/labels/digest), [2021-fdd](https://github.com/Openscapes/2021-fdd/labels/digest). + +Many teams begin working more openly via shared documentation, project management, metadata, file organization and naming, and code organization and interoperability, using tools like Google Drive/Microsoft Teams, GitHub, R, and Python. + +## Supercharge Your Research + +We're often asked what people can do to further prepare in advance. Additional suggested reading include: + +[**Our path to better science in less time using open data science tools**](https://www.nature.com/articles/s41559-017-0160) (Lowndes et al. 2017). This describes a marine science team's transition to open collaborative teamwork. It was the original inspiration for creating the Champions Program and heavily influences the Core Lessons. + +[**Supercharge your research: a ten-week plan for open data science**](https://openscapes.github.io/supercharge-research/) (Lowndes et al. 2019). This was co-authored with the inaugural Champions Cohort, capturing the most valuable take-aways for marine and environmental science early career faculty. + +[**Shifting institutional culture to develop climate solutions with Open Science**](https://onlinelibrary.wiley.com/doi/10.1002/ece3.11341) (Lowndes et al 2024, Ecology & Evolution). This was co-authored by Openscapes mentors across organizations – including NASA Earthdata, NOAA Fisheries, EPA, California Water Boards, Pathways to Open Science, Fred Hutch Cancer Center. + +### Learn more about How We Work + +- [Openscapes Approach Guide](https://openscapes.github.io/approach-guide) +- [The Openscapes Flywheel: A framework for managers to facilitate and scale inclusive Open science practices](https://eartharxiv.org/repository/view/4560/) (Robinson & Lowndes 2022) +- [3 lessons from remote meetings we're taking back to the office](https://opensource.com/article/20/6/remote-meetings) (Lowndes, Cabunoc Mayes & Sansing 2020) + - [How to run a remote workshop, Openscapes/Open Leaders-style](https://openscapes.org/blog/2020-03-11-tips-remote-workshops/) (complementing blog post) + +See also other publications and presentations at [openscapes.org/media](https://openscapes.org/media). + +## Teams: FAQs + +One thing that makes Openscapes Champions Cohorts impactful is a focus on **teamwork**. People most often sign up as teams, with varying skillsets and responsibilities, perhaps with a shared project and perhaps not. People can also sign up as individuals. Some Champions have said that “finding their teams” during the cohort – finding what’s common and feeling less alone while learning skills with their peers – has been the most valuable part of Openscapes. + +Openscapes Champions was originally designed with academic research groups in mind, to provide resilience where there is high turnover and folks might be struggling with similar challenges around data analysis — while working on different projects. But over half of cohorts have been groups with different structures and needs, some producing big annual government reports or indicators! We expect — and design for — a range of technical ability and comfort with technology and open science concepts. The most important thing is that people opt-in who have interest in improving their work somehow and want to strengthen their collaboration and leadership skills. + +Here are answers to some Frequently Asked Questions (FAQs). + +### How many people participate? + +The Champions Program operates as cohorts of 7-10 teams of up to 5 people; 40 people max in the cohort. + +### Why do people join a Champions cohort? + +People join because they (as an individual or team): + +- Want to learn about or work with open Science +- Want to meet peers working on similar workflow or data issues +- Have a ‘big goal’ that involves changing how you work; you want to make progress on making your data and science workflows more efficient and reproducible + +### What is a team? + +There is a lot of flexibility in choosing your team. + +Teams do not need to be a formal research group; they can be collaborating in other ways. Team members do not all need to have technical or data interests, but share a curiosity and interest in improving something about how they work. Participants are expected to have ‘Seaside Chats’ together with their broader research groups in the weeks between Cohort Calls, so it is OK, and expected, that only a subset of a team participate. + +### What skills are required? Coding? GitHub? + +No. This is not a coding workshop. + +The purpose is strengthen relationships and shared systems with folks with different responsibilities and skills, so there is less reinventing and less knowledge lost. + +During the cohort, people focus on what is important to them, often something hard to do, something they want to change. Throughout the cohort, as Openscapes introduces modern concepts, tooling, and peer examples, people learn together and get unstuck through identifying and making progress on barriers. Each cohort call (90 minutes) has 30-40 minute of lessons and the rest of the time is you reflecting and discussing how this could help you with your own work. + +### How do I choose my team? + +Choosing your team can be based on interests around data analysis and around leadership. There are no prerequisite skills to participate, just an interest to learn and contribute. The "homework" between Champions sessions and beyond is to meet with your full research group (beyond workshop participants, and optional for the lead) to establish shared workflows and habits within the research group. + +>*How you define \"team\" is completely up to you and having one person be in the cohort and using in-between session \"seaside chats\" to bring back the information to another group is 100% fine. That is common in the cohorts. In my first Openscapes cohort, I was the only person from my project. My personal goal was to use the Openscapes structure to help a team that I am on figure out how to tackle some off-boarding tasks due to a retirement. During my second cohort, there were 2 team members in the cohort and 2 not in the cohort. We focused on standardizing our data to get ready for our GitHub served data package. For the 3rd cohort I am doing, ^2^⁄~3~ of our team is in the cohort as we start to get organized for a major revamp of our report into a reproducible workflow.* **- Eli Holmes (NOAA NWFSC, NMFS-Openscapes)** + +We e invite research group leads (faculty, lecturers, program managers, etc.) and members (students, analysts, lab managers, etc.) participate together as teams so that 1) everyone sees and values what is possible; 2) leads enable members to invest time to learn skills and develop shared workflows; 3) members have guidance, agency, and support to incorporate concepts into their work; and 4) everyone can make progress on what is important to them, while strengthening the community of practice within the research group, cohort and beyond. + +### What if I don’t have a team? + +That’s ok, please sign up! We’ll help you connect with participants who share some of your goals or needs. + +### Does a team need a shared research project? + +No, teams do not need to have a specific shared research project to participate. + +The idea is that by developing shared open data science habits within the research group, it will be easier to onboard new folks and offboard knowledge/data/code/etc when folks leave. And, as more and more research groups work this way, it can ease transitions between research groups (i.e. when people leave projects or students graduate). + +When there are formal research groups, we invite research group leads (faculty, lecturers, program managers, etc.) and members (students, analysts, lab managers, etc.) to participate together as teams so that 1) everyone sees and values what is possible; 2) leads enable members to invest time to learn skills and develop shared workflows; 3) members have guidance, agency, and support to incorporate concepts into their work; and 4) everyone can make progress on what is important to them, while strengthening the community of practice within the research group, cohort and beyond. + +### Is attendance required for all Cohort Calls? + +Yes; we do try to have everyone on the team attend all Cohort Calls – but know that sometimes that’s not possible. All the lessons, slides, and also recordings are available if people have to miss, but everyone should sign up expecting to be at the Cohort Calls. + +### Do I as the PI need to attend the Cohort Calls, or just my team? + +It’s important that team leads attend with their team. The Champions program is designed to reduce the burden for PIs in the long term and develop leadership within and across their teams. With this investment now, team leads and members will build resilient and enduring practices for their research group, even as that research group changes into the future. The idea is that together, the whole team sees what’s possible with open data science and builds confidence, ownership, and a shared pathway forward. Then it’s the entire team, not just the PI, who puts it to practice in between sessions. + +### Does a cohort need a shared research project or to be closely related? + +No, the cohort does not need a shared project; each team will work on what they need to for their own work. Teams within a cohort do not need to be closely related, but having teams somewhat related can be good for community building (i.e. environmental science as a domain or a specific agency within government). + +### Can we have smaller teams so more teams can participate in a cohort? + +From our experiences so far think that ~8 teams with 4-5 participants per team (maximum of ~40 participants) is a good size so there is time for everyone to be engaged and contributing (and not feeling like a passive webinar). Also, having a good amount of members per team is really key to the whole model of Openscapes: we want to reduce the amount of burden for PIs to have to relay info to their research groups. Having more members participate as a team in the Openscapes program helps more team members feel agency to build resilient systems with less transmission time. +