shift amplify first, near-final blog post

Author: jules32

mentors.qmd

@@ -36,11 +36,11 @@ This year we are focused on how to continue to improve this critical user suppor
 
 NASA Earthdata has volumes of remote sensing data collected from satellites, as well as substantial suborbital data collected from field sampling, airborne sampling, boats, and buoys that is used to ground-truth satellite data, among other research. Suborbital science teams (i.e. science teams creating suborbital data via NASA programs) archive data at several NASA Distributed Active Archive Centers (DAACs) including ORNL, LP DAAC, and NSIDC, and receive additional support from other NASA centers and Headquarters (HQ). 
 
-This year we have added focus on strengthening the suborbital Mentor community and supporting suborbital science teams with the [Openscapes Flywheel](https://nasa-openscapes.github.io/about.html#flywheel-preprint) (engage • empower • amplify): 
+This year we have added focus on strengthening the suborbital Mentor community and supporting suborbital science teams with the [Openscapes Flywheel](https://nasa-openscapes.github.io/about.html#flywheel-preprint) (engage • empower • amplify, this time starting with amplify): 
 
-1. **Engaging a suborbital science team community.** Suborbital teams are already meeting in smaller groups, perhaps based on mission or a specific DAAC; and we will develop these relationships further into a cross-DAAC community. 
-2. **Empowering suborbital science teams involves leading a Notebook Clinic** that will be remote, cohort-based, and designed for their needs. 
-3. **Amplifying suborbital science teams involves bringing them into the fold of NASA Openscapes Flywheel, along with increasing numbers of NASA center staff.** As always, open documentation and storytelling via blogs and talks will center this work. 
+1. **Amplifying suborbital science teams involves bringing them into the fold of NASA Openscapes Flywheel, along with increasing numbers of NASA center staff.** As always, open documentation, contributing to the NASA Earthdata Cookbook, and storytelling via blogs and talks will center this work. We will onboard new NASA Mentors from NASA's SOAR (SubObrital Archive Readiness) Team and other parts of NASA to collaborate across the agency to support science teams.
+2. **Engaging a suborbital science team community.** Suborbital teams are already meeting in smaller groups, perhaps based on mission or a specific DAAC; and we will develop these relationships further into a cross-DAAC community. 
+3. **Empowering suborbital science teams involves leading a Notebook Clinic** that will be remote, cohort-based, and designed for their needs. 
 
 This work is in collaboration with the CryoCloud/StratusGeo Community, which is an exciting continuation of the JupyterHub community work we have been collaborating on with them with in the past years.
 

news/2026-03-03-suborbital/index.qmd

@@ -11,16 +11,18 @@ categories: [blog, nasa-framework]
 image: TODO
 ---
 
-*TODO: refine. This blog post is introducing some additional focus we have in 2026. TO ADD next week: welcoming a new team member!*
-
-*Quicklinks:*
+*In 2026 we are proud be supporting NASA teams in additional ways, building from our work with the NASA Openscapes Mentors over the past five years. This year we will additionally be supporting suborbital science teams and growing the NASA Openscapes Mentor community to develop reproducible workflows.*
 
 ------------------------------------------------------------------------
 
-NASA Earthdata has volumes of remote sensing data collected from satellites, as well as substantial suborbital data collected from field sampling, airborne sampling, boats, and buoys that is used to ground-truth satellite data, among other research. Suborbital science teams (i.e. science teams creating suborbital data via NASA programs) work with staff at several NASA Distributed Active Archive Centers (DAACs) to archive data, including ORNL, LP DAAC, and NSIDC. They receive additional support from other NASA centers and Headquarters (HQ).
+## NASA suborbital science and Openscapes proposed support
+
+NASA Earthdata has volumes of remote sensing data collected from satellites, as well as substantial suborbital data collected from field sampling, airborne sampling, boats, and buoys that is used to ground-truth satellite data, among other awesome research like studying Arctic coastlines via the [FORTE mission](https://espo.nasa.gov/forte) and glaciers and ice sheets via the [Snow4Flow mission](https://snow4flow.lpl.arizona.edu/). Suborbital science teams (i.e. science teams creating suborbital data via NASA programs) work with staff at several NASA Distributed Active Archive Centers (DAACs) to archive data, including ORNL, LP DAAC, and NSIDC. They receive additional support from other NASA centers and Headquarters (HQ).
 
 Starting in March and for the rest of 2026, we will be supporting NASA suborbital science teams to develop reproducible workflows. Below is our planned approach from our proposal, presented through POP: Purpose, Outcomes, Process.
 
+We are thrilled to welcome [Ronny Hernández Mora](https://ronnyale.com/) to the Openscapes core team to support this work! Ronny works at the intersection of Earth data, open and reproducible workflows, and has spent the last past eight years teaching professionals and researchers in industry and academia how to adopt collaborative, open, and maintainable workflows in real-world contexts.
+
 ## Purpose
 
 The purpose is to develop user skills and reproducible workflows for using NASA suborbital data. This work will communities using NASA Earthdata and open science more broadly, as well as growing the NASA Openscapes community in a new focus area. This work is in collaboration with the \[CryoCloud/StratusGeo Community\]([https://cryointhecloud.com](https://cryointhecloud.com/)), which is an exciting continuation of the JupyterHub community work we have been collaborating on with them with in the past years.
@@ -31,23 +33,33 @@ Suborbital science teams will create reusable open source notebooks (Jupyter, Qu
 
 ## Process
 
-This work will be aligned with NASA HQ priorities to identify and meet suborbital teams, understand goals, progress, tooling, and needs. The following are distinct but overlapping activities.
+This work will be aligned with NASA HQ priorities to identify and meet suborbital teams, understand goals, progress, tooling, and needs. The following are distinct but overlapping activities. Our approach of engage • empower • amplify is cyclical, and for this suborbital work will start with **amplify**.
 
-1.  **Developing a suborbital science team community.** Suborbital teams are already meeting in smaller groups, perhaps based on mission or a specific DAAC; and we will develop these relationships further into a cross-DAAC community. This will involve joining meetings already ongoing, asking questions and building relationships, giving talks, sending followup messages, having open documentation of activities, 1:1 conversations; all to welcome and support scientists with busy schedules. We will lead biweekly “Coworking” learning meetings with suborbital science teams where we will increasingly fold in NASA center staff to learn and build relationships with suborbital users. For suborbital science teams, this will be a chance to ​​help find what is common (i.e. airborne data differs but they all have flight tracks; all need to learn version control and write metadata), and build together, always with a “future us” and reuse mindset.
-2.  **Empowering suborbital science teams involves leading a Notebook Clinic** that will be remote, cohort-based, and designed for their needs. Lessons will focus on developing reproducible workflows with Jupyter Notebooks, Quarto, and GitHub, using the earthaccess python library, and writing documentation that focuses on reuse and onboarding. This Clinic will not focus on specific datasets, but the methods for writing reusable analyses that combine different datasets, using open source tooling and practices. 
-3.  **Amplifying suborbital science teams involves bringing them into the fold of NASA Openscapes Flywheel, along with increasing numbers of NASA center staff.** By connecting users and NASA Openscapes Mentors (DAAC user support staff), data access issues will be surfaced for NASA development teams (e.g. earthaccess, CMR, cloud optimized). We will develop a process to add suborbital teams’ tutorials after the Notebook Clinic to the NASA Earthdata Cookbook for increased discoverability and reuse. Throughout, we will share and connect suborbital science teams with others at NASA and the broader open science community so they become confident contributors to further support science with NASA Earthdata.
+1.  **Amplifying suborbital science teams involves bringing them into the fold of NASA Openscapes Flywheel, along with increasing numbers of NASA center staff.** By connecting users and NASA Openscapes Mentors (DAAC user support staff), data access issues will be surfaced for NASA development teams (e.g. earthaccess, CMR, cloud optimized). Throughout, we will share and connect suborbital science teams with others at NASA, StratusGeo, and the broader open science community so they become confident contributors to further support science with NASA Earthdata.
+2.  **Developing a suborbital science team community.** Suborbital teams are already meeting in smaller groups, perhaps based on mission or a specific DAAC; and we will strengthen these relationships further as a cross-DAAC community. This will involve joining meetings already ongoing, asking questions and building relationships, giving talks, sending followup messages, having open documentation of activities, 1:1 conversations; all to welcome and support scientists with busy schedules. We will lead ~biweekly “Coworking” learning meetings with suborbital science teams where we will increasingly fold in NASA center staff to learn and build relationships with suborbital users. For suborbital science teams, this will be a chance to help find what is common (i.e. airborne data differs but they all have flight tracks; all need to learn version control and write metadata), and build together, always with a “future us” and reuse mindset.
+3.  **Empowering suborbital science teams involves leading a Notebook Clinic** that will be remote, cohort-based, and designed for their needs. Lessons will focus on developing reproducible workflows with Jupyter Notebooks, Quarto, and GitHub, using the earthaccess python library, and writing documentation that focuses on reuse and onboarding. This Clinic will not focus on specific datasets, but the methods for writing reusable analyses that combine different datasets, using open source tooling and practices. We will develop a process to add suborbital teams’ tutorials after the Notebook Clinic to the NASA Earthdata Cookbook for increased discoverability and reuse.
 
-## Methodology
+### Methodology
 
 We will follow the NASA Openscapes Flywheel mechanism (Robinson & Lowndes 2022, <https://eartharxiv.org/repository/view/4560>) to facilitate and scale open source practices (e.g. from groups like Pangeo, rOpenSci, The Carpentries):
 
--   **To develop the suborbital community** we will reuse and grow from what works from the last five years of building the NASA Openscapes Mentor community, and connecting to community momentum at NASA. This will not happen in a vacuum, but coordinating with other NASA groups takes time. We know scientists and NASA staff are busy, and also know many do not know where to ask for help. This work involves:
+-   **To amplify suborbital teams and grow the Mentor community** we will create opportunities to share work, both through talks and through a mechanism for adding contributions to the Earthdata Cloud Cookbook. This involves:
+
+    - Giving talks to different groups, particularly with NASA staff, NASA Openscapes network of open source communities, industry, academia, other government agencies. 
+
+    - Connecting suborbital teams to Openscapes’ network of engineers, teachers, managers, scientists, facilitators, we can help people get the help they need, and help their work get in front of people who need to hear about it.
+
+    - Onboarding new NASA Mentors from NASA's SOAR (SubObrital Archive Readiness) Team and other parts of NASA to collaborate across DAACs and across the agency to support science teams.
+    
+    - Improving documentation and onboarding for suborbital teams (and anyone) to contribute workflows to the NASA Earthdata Cookbook.
+    
+-   **To develop the suborbital community** we will reuse and grow from what works from the last five years of building the NASA Openscapes Mentor community, and connecting to community momentum at NASA. This will not happen in a vacuum, but coordinating with other NASA groups takes time. We know scientists and NASA staff are at the same time busy and feeling stuck+alone, not knowing where to ask for help. This work involves:
 
     -   Joining existing meetings, getting a sense of the group, giving talks, asking questions, sending followup messages, having open documentation of activities, scheduling 1:1 conversations, seeking out people at conferences.
 
     -   Hosting regular Coworking sessions; a light-weight way where they connect and help solve common challenges. This will build trust so they would prioritize time for the Clinic, as we design the Clinic to fit their needs. 
 
--   **To empower teams through the** **Notebook Clinic** we will draw from what we’ve learned from leading 27 Champions Cohorts (Openscapes’ flagship program where we have helped 175 teams make real change around reproducible and transparent workflows). We will design the Clinic for what best meets suborbital team needs, likley forking the structure of the Champions program: 10 weeks, 1.5 hours each week, with alternating weeks being lesson-based and hands-on work based <https://openscapes.github.io/series>). Our approach includes:
+-   **To empower teams through the** **Notebook Clinic** we will draw from what we’ve learned from leading 27 Champions Cohorts (Openscapes’ flagship program where we have helped 175 teams make real change around reproducible and transparent workflows). We will design the Clinic for what best meets suborbital team needs, likely forking the structure of the Champions program: 10 weeks, 1.5 hours each week, with alternating weeks being lesson-based and hands-on work-based. Our approach includes:
 
     -   Focusing on developing relationships with potential participants (above) as well as developing the Clinic itself. The Clinic will build on the rhythm from Coworking and be a friendly place to learn. We will invite suborbital teams to join via a short nomination form, both which Openscapes has found to increase buy-in and decrease attrition. 
 
@@ -57,12 +69,5 @@ We will follow the NASA Openscapes Flywheel mechanism (Robinson & Lowndes 2022,
 
     -   We will teach with an open facilitation approach, drawing on our experience as Carpentries certified instructors, using agenda as live shared note taking, and having multiple channels for asking help, including asynchronous chat and synchronous having breakout rooms.
 
-    -   ​​Notebook Clinic lessons will be added to the Earthdata Cloud Cookbook for discoverability and reuse.
-
--   **To amplify suborbital teams’ reproducible workflows** we will create opportunities to share work, both through talks and through a mechanism for adding contributions to the Earthdata Cloud Cookbook. This involves: 
-
-    - Giving talks to different groups, particularly with NASA staff, NASA Openscapes network of open source communities, industry, academia, other government agencies. 
-
-    - Connect suborbital teams to Openscapes’ network of engineers, teachers, managers, scientists, facilitators, we can help people get the help they need, and help their work get in front of people who need to hear about it.
+    -   Notebook Clinic lessons will be added to the Earthdata Cloud Cookbook for discoverability and reuse.
 
-    - Improving documentation and onboarding for suborbital teams (and anyone) to contribute workflows to the NASA Earthdata Cookbook.