Skip to content

Commit

Permalink
Merge pull request #54 from NASA-Openscapes/captions
Browse files Browse the repository at this point in the history
restore captions by rm backslashes; add Champs to Upcoming events
  • Loading branch information
stefaniebutland authored Feb 28, 2024
2 parents e4b9134 + 558f122 commit 80cfa55
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 8 deletions.
4 changes: 2 additions & 2 deletions index.qmd
Original file line number Diff line number Diff line change
Expand Up @@ -14,10 +14,10 @@ We are influenced and inspired by many leaders and community organizers, particu

**Upcoming Events:**

- Feb 20, 2024 [Community Call](https://openscapes.org/events/2024-02-20-github-calendaring/): GitHub for NASA Openscapes community calendaring & project management. An open work in progress. (register to attend)
- The [2024 NASA Openscapes Champions Cohort](https://nasa-openscapes.github.io/news/2024-04-03-nasa-champions/) is a mentorship and professional development opportunity for research teams using NASA Earthdata to learn open science practices and spend time experimenting and planning what their analytical workflows with NASA Earthdata look like in the Cloud. Starts April 3, 2024.

Learn about our recent work: [News](news.qmd)[Presentations](/about.qmd#slides)[Annual Reports](https://github.com/NASA-Openscapes/how_we_work)[Flywheel Preprint](https://nasa-openscapes.github.io/about.html#flywheel-preprint)[White Paper: The Value of Hosted JupyterHubs](https://nasa-openscapes.github.io/about.html#white-paper-value-of-hosted-jupyterhubs)

[![](images/earthaccesslogo.png){fig-alt="hexagonal earthaccess logo, an illustrated earth as pixels with blue text arcing across" fig-align="left" width="51"}](https://earthaccess.readthedocs.io/en/latest/) [earthaccess](https://earthaccess.readthedocs.io/en/latest/) python library • [Earth Science Data Simplified](https://www.earthdata.nasa.gov/learn/blog/earthaccess) (NASA Earthdata blog!)
![](images/earthaccesslogo.png){fig-alt="hexagonal earthaccess logo, an illustrated earth as pixels with blue text arcing across" fig-align="left" width="30"} [earthaccess](https://earthaccess.readthedocs.io/en/latest/) python library • [Earth Science Data Simplified](https://www.earthdata.nasa.gov/learn/blog/earthaccess) (NASA Earthdata blog!)

Project announcements: [NASA](https://earthdata.nasa.gov/learn/openscapes)[Openscapes](https://www.openscapes.org/blog/2021/03/10/nasa-announcement/) • Please connect with us on Mastodon [\@openscapes\@fosstodon.org](https://fosstodon.org/@openscapes) or join [our newsletter](https://docs.google.com/forms/d/e/1FAIpQLSdgVXRp3V-w94GPWkR31RUfyBl37EphdQSlCOcnyeNlf8OLWw/viewform)
12 changes: 6 additions & 6 deletions news/2024-02-28-github-community-call/index.qmd
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ image: github-roadmap-view.png

## How do we know what we’re doing together and when we’re doing it?

NASA Openscapes Mentors develop, teach, and support **many** conference workshops, webinars, and participate in project hackdays with their main goal being to support scientists using NASA Earthdata as they migrate their workflows to the cloud. Bri set the stage with our motivation. People working across 11 NASA data centers ([DAACs](https://www.earthdata.nasa.gov/eosdis/daacs)) need a way to see a year’s worth of “who’s here; what are we doing; when are we doing it; where can we find overlap with each other?” The work requires advance planning, and we’d love to avoid having everyone need to separately look up the registration deadlines for conferences. That can all be on a community calendar. We need a solution that is lightweight, with a low barrier to entry, and agnostic to specific calendaring software like Google Calendar vs Microsoft Outlook.\
NASA Openscapes Mentors develop, teach, and support **many** conference workshops, webinars, and participate in project hackdays with their main goal being to support scientists using NASA Earthdata as they migrate their workflows to the cloud. Bri set the stage with our motivation. People working across 11 NASA data centers ([DAACs](https://www.earthdata.nasa.gov/eosdis/daacs)) need a way to see a year’s worth of “who’s here; what are we doing; when are we doing it; where can we find overlap with each other?” The work requires advance planning, and we’d love to avoid having everyone need to separately look up the registration deadlines for conferences. That can all be on a community calendar. We need a solution that is lightweight, with a low barrier to entry, and agnostic to specific calendaring software like Google Calendar vs Microsoft Outlook.

## How we’re using GitHub for calendaring and management

Expand All @@ -34,19 +34,19 @@ NASA Openscapes Mentors develop, teach, and support **many** conference workshop

For the past three years, we have been using GitHub as a community to collaborate around code, tutorials, and documentation, taking advantage of its features for version control, code review, and workshop book publishing. This is important not only because it helps us develop collaboratively as a team, but it’s also the same technology that Earth science researchers use, so we are able to develop practical experience to help them every day as we work. It made sense to explore using GitHub more deeply for our planning and calendaring. 

We started using GitHub as a centralized place where any of the \~40 NASA Openscapes Mentors can post dates and information for a conference workshop they are leading, for example. Everyone else can see it, and someone might comment “I’m speaking at the same conference. I can give some hands-on help.”, or “Here’s a python notebook I created for a similar workshop last month.” During the Community Call, Stef screenshared our [MainPlanning](https://github.com/orgs/NASA-Openscapes/projects/7) GitHub Project, the Roadmap view (screenshot below) that gives a calendar perspective and the Table view for details on each item. She demo’d creating a GitHub Issue, associating it with the Project, adding topic labels, and a Start date to have it appear in the Roadmap. She showed how we’re also documenting this as we go with screenshots in [NASA Earthdata Cloud Cookbook - GitHub for Calendaring and Project Management](https://nasa-openscapes.github.io/earthdata-cloud-cookbook/contributing/calendar-project-management.html#github-for-calendaring-and-project-management).
We started using GitHub as a centralized place where any of the ~40 NASA Openscapes Mentors can post dates and information for a conference workshop they are leading, for example. Everyone else can see it, and someone might comment “I’m speaking at the same conference. I can give some hands-on help.”, or “Here’s a python notebook I created for a similar workshop last month.” During the Community Call, Stef screenshared our [MainPlanning](https://github.com/orgs/NASA-Openscapes/projects/7) GitHub Project, the Roadmap view (screenshot below) that gives a calendar perspective and the Table view for details on each item. She demo’d creating a GitHub Issue, associating it with the Project, adding topic labels, and a Start date to have it appear in the Roadmap. She showed how we’re also documenting this as we go with screenshots in [NASA Earthdata Cloud Cookbook - GitHub for Calendaring and Project Management](https://nasa-openscapes.github.io/earthdata-cloud-cookbook/contributing/calendar-project-management.html#github-for-calendaring-and-project-management).

\
![Roadmap view of a GitHub Project for NASA Openscapes Mentors and collaborators](github-roadmap-view.png){width="85%" fig-alt="screenshot of a github project page roadmap view with rows for issues whose dates are shown along a timeline"}\

![Roadmap view of a GitHub Project for NASA Openscapes Mentors and collaborators](github-roadmap-view.png){width="85%" fig-alt="screenshot of a github project page roadmap view with rows for issues whose dates are shown along a timeline"}

## How NASA’s LP DAAC and EMIT science teams are expanding this approach

NASA JPL’s Earth Surface Mineral Dust Source Investigation (EMIT) instrument aboard the International Space Station (ISS) uses imaging spectroscopy to detect surface mineralogy, methane gas plumes and ground surface characteristics from space. The NASA Land Processes data center works closely with the EMIT science team to distribute data and develop tutorial resources and they wanted a way to do that more fluidly. A place to strategically link meeting agendas/ notes/ tasks/ progress in [a single ‘open’ location](https://github.com/orgs/NASA-Openscapes/projects/9/views/1?pane=info) that allows individuals on both teams to be aware of progress and decisions as they are being made. The teams are using this space to do more things in the open and having fewer reasons to say “Where’s that doc? Can you email it to me?”

\

![Table view of a GitHub Project for NASA Land Processes data center and EMIT science team](github-lp-emit-table-view.png){width="85%" fig-alt="screenshot of a github project page table view with rows for issues and showing columns for start date, labels. Right side shows a readme with a checklist"}

\


## Dig into the discussion

Expand Down

0 comments on commit 80cfa55

Please sign in to comment.