Project Pythia Meeting Notes

Zoom | password: pythia23

2024-1-23: Education Working Group:

Facilitator:                 | Note-taker:

Attendees:  [Name / Institution / GitHub Username]

Quick Updates:

• Please sign in on this page above (and add any quick updates, including accomplishments)

.

Agenda + Notes:

• Pythia hackathon

2023-10-09: Education Working Group:

Facilitator: Drew Camron | Note-taker:

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle
• Julia Kent  / NCAR / @jukent
• Max Grover / Argonne / @mgrover1

Quick Updates:

• Please sign in on this page above (and add any quick updates, including accomplishments)
• KT / Pangeo Showcase (ArrayLake) - will ask for ProjectPythia to join private beta
• MG - presenting on ESGF + CMIP6 cookbook at Thursday ESGF webinar

• New example with hvPlot + ENSO
• Adding another one using globus compute for serverless
• Invitation info

Greetings Colleagues:

• To continue receiving ESGF Webinar announcements, please join the ESGF Announce Group at https://groups.google.com/g/esgf-announce
• Recordings of previous ESGF Webinars are available on YouTube at https://www.youtube.com/playlist?list=PLsmg4BlLl0fWu8HXUDaKZ-dauRwFLgyIC

The next ESGF Webinar will be presented by Max Grover (Argonne National Laboratory) on Thursday, October 12, 2023, at 17:00 CET / 15:00 UTC / 11:00 EDT / 10:00 CDT / 9:00 MDT / 8:00 PDT. The title and abstract are as follows:

Open Science in ESGF: Collaborations and Innovations with CMIP6 Cookbooks

Maxwell Grover, Argonne National Laboratory

User computing is a key focus of the United States Department of Energy-funded Earth System Grid Federation (ESGF) 2 project. The Climate Model Intercomparison Project v6 (CMIP6) dataset is just one example of a critical dataset hosted by ESGF cyberinfrastructure. We worked with existing communities that have developed a suite of example computational workflows, mainly the Pangeo community educational working group, Project Pythia (https://projectpythia.org/cmip6-cookbook). We tested the existing content, and contributed to new example workflows, highlighting new tools developed as a part of the ESGF2-US project. These recent updates include comparisons with observational datasets such as data from the DOE Atmospheric Radiation Measurement (ARM) user facility, and tutorials on using Globus Compute frameworks to execute climate analysis workflows at scale.

Please register at https://docs.google.com/forms/d/e/1FAIpQLScc9hr9WkmHM1zLA__ZCCYibNGMvSVfEztrBmX4wGGdJgAvPA/viewform?usp=sf_link to receive an email and calendar invitation with a link to join the webinar on the day of the event.

Agenda + Notes:

• OWG Update

• September Quarterly Newsletter draft soon - first will be a longer one
• BR leading OSTP Challenge effort
• Slack Workspace!
• Engage with LinkedIn posts when you’re around

• Make sure to repost - great way to bring people in!

• New resource highlight post structure

• Questions and to-do items for new meeting schedule

• New meeting notes/agenda routine?
• Calendar updates + some documentation
• Discourse announcement

• Consider doing a Pangeo Showcase: 11/29, 12/6, 12/13 available at this time

2023-10-03: Outreach Working Group

Zoom | password: pythia23

Attendees:  [Name / Institution / GitHub Username]

• Drew Camron / Unidata / @dcamron
• Max Grover / Argonne / @mgrover1
• Julia Kent / NCAR / @jukent

Agenda + Notes:

• OSTP Call

• Brian leading this White House challenge
• Starting to draft things up

• Slack Workspace - Join Here

• Not to be used for hackathons
• Encourage public to engage on Discourse, this is for quick turn around with the active team

• Outline for quarterly newsletter

Action items:

• Draft highlight of cookbooks

2023-10-02: Infrastructure Working Group

Facilitator: John Clyne | Note-taker: ???

Facilitation rotation sign-up and schedule

Attendees:  [Name / Institution / GitHub Username]

• Brian Rose / UAlbany / @brian-rose
• John Clyne / NCAR / @clyne
• Drew Camron / Unidata / @dcamron
• Rob Ford / UAlbany / @r-ford
• Orhan Eroglu / NCAR / @erogluorhan
• Kevin Tyle / UAlbany / @ktyle
• Julia Kent / NCAR / @jukent
• James Munroe / 2i2c / @jmunroe

Quick Updates:

• Please sign in on this page above (and add any quick updates, including accomplishments)
• JC: John giving a presentation on Pythia to UCAR’s new Center for Ocean Leadership program on Wednesday.
• KT: Fall semester class will be playing in the Git/GitHub Foundations sandbox the next week or two
• BR: Looking into submitting something to the The White House Office of Science & Technology Policy Open Science Recognition Challenge. Main requirement is a 5000-character narrative for a general audience “telling the story of an open science project”. Winning submissions will be highlighted as Champion of Open Science, featured on federal websites and possibly invited to a future workshop. Due date 11/22/23
• BR: Full list of GEO OSE awards has been released.
• DC: cookbook review template update

• pyOpenSci software peer review template - will model after
• template in action
• Planning to use GitHub issues + projects board with synchronous review component

Agenda + Notes:

• Proposed new Pythia meeting schedule

• Remainder of CY23:

• Community meeting - 1st Monday of the month, 1pm MT

• Kick off Nov. 6
• Attendance: everyone
• Chair - Brian

• OWG - unchanged (every other Tuesday, 9am)
• Iteration planning meeting - 3rd Monday of the month, 1pm MT

• Kick off Oct 16
• Attendance: TBD
• Chair - Orhan
• First meeting of the new schedule
• Who should attend?

• OE suggests any folks developing for Pythia can be present, consider excluding “stakeholders” regularly
• Irregular contributors can fluctuate attendance; “core” developers should attend regularly
• Regular attendees identified from major project planning for next 4-5 iterations

• Open Ad Hoc meeting – 4th Monday of the month, 1pm MT

• Kick off Oct 23
• Attendance: varies

• Starting in CY24, pending Brian and Kevin’s academic schedule:

• Community meeting - 1st Tuesday of the month, 1pm MT
• OWG - TBD
• Iteration planning meeting - TBD
• Open Ad Hoc meeting – 4th Tuesday of the month, 1pm MT
• Scheduling to be revisited with updated academic schedules

• We should choose a specific asynchronous space in support of fewer face-to-face meetings

• Considerations re Zulip, Slack, etc.
• JC will explore costs of Slack for the project. Multiple voices in support of persistent Slack workspace for small team with support for intermittent hackathon/community participation

• Status of high priority IWG issues:

• Public cloud storage needed to support cookbook data - Kevin Tyle

• Pathway for community submissions of data to JS2 - none currently exist
• Only real path         for JS2 at moment is directly through KT - if there’s repeat need for particular data right now, start here

• Automate collection of metrics - Julia Kent

• Requested administrative permission (had view only)
• Supposedly administrators are JC, BR, KT, and RM based on a comment in an issue from 2 years ago
• Update: just got access! Thank you everyone - it’s always a different menu
• Automation in progress now!

• Update theme to use newest Sphynx Book Theme - Drew

• Currently testing theme specs against variety of sphinx extensions, generally positive so far

• Failing cookbooks

• Kerchunk

• Fix in, should be passing now

• Xbatcher

• Fix ready, URL update

• Automation of requesting reviews from identified cookbook maintainers

• Triage of unprioritized infrastructure issues: https://github.com/orgs/ProjectPythia/projects/3/views/11

• cookbook-template#114 - likely not an issue, being addressed by BR
• cookbook-actions#62 - could be addressed quickly, but has some nuance
• cookbook-actions#70 - could be done easily if chosen, but is very low priority and currently exists only to run once as a snapshot of the workflow as copied from template
• physical-oceanography-cookbook#37 - tied to larger data problem

• Other topics?

Action Items:

• Update calendar invites

2023-09-25: Education Working Group

Facilitator: Brian Rose | Note-taker: ??

Facilitation rotation sign-up and schedule

Attendees:  [Name / Institution / GitHub Username]

• Brian Rose / UAlbany / @brian-rose
• Julia Kent / NCAR / @jukent
• Max Grover / Argonne / @mgrover1
• Kevin Tyle / UAlbany / @ktyle
• John Clyne / NCAR / @clyne
• Rob Ford / UAlbany / @r-ford

Quick Updates:

• Please sign in on this page above (and add any quick updates, including accomplishments)
• KT/OWG: September Quarterly Newsletter: suggest any subjects that do not already appear in the outline (and sign up for one of the listed topics)
• Tuesday  Wednesday 9/26 9/27 5:00PM EDT/3:00 MDT: Binderhub will be down for maintenance (estimate 30 minutes)
• JK - running into permissions errors exploring Google Analytics Python API
• MG - thoughts on applying for OSTP Open Science recognition for Pythia? https://www.challenge.gov/?challenge=ostp-year-of-open-science-recognition-challenge

• BR will look into this

Agenda + Notes:

• Proposal for new Pythia meeting structure [BR]

• People should have received a poll about meeting times; please reply ASAP so we can move forward
• Need to decide when to get started, and when the first Community meeting will be
• We will discuss asynchronously on this

• NCAR SIParCS 2024 internships [JC]

• project proposals due October 9 at noon
• Ideas on submissions?

• Share thoughts with JC about topics

• Need a CISL mentor.

• Room for team-based mentorship like we did 2 years ago?
• Interest within CGD about a CESM-related cookbook?

• Discussion: What makes a cookbook a cookbook, and not just a notebook? [JC]

• When do you encourage people to create a cookbook and not just a notebook?

• We’ve made it really simple for people run the code in Cookbooks. Don’t need lots of previous knowledge etc.
• A notebook demonstrates a relevant task, should we encourage people to turn it into a Cookbook?

• Would these recent ESDS blog posts make good cookbooks?

• Efficient processing of lots of CESM outputs
• Visualizing CAM-SE data
• These are notebook-based but it’s not straightforward to actually run the code, no environment etc.
• Really good candidate for a cookbook - https://ncar.github.io/CESM-Tutorial/README.html

• What about this Project Raijin notebook on visualizing MPAS and CAM-SE without resampling?
• There are obvious benefits to having cookbooks for the above content
• There are also challenges (e.g. data access, additional effort for authors)
• Are there things we should do to encourage and facilitate creation of cookbooks for topics like the examples above?
• Should making a Cookbook imply taking responsibility for maintenance?
• Are people making these blog posts being turned off by the burden of making a cookbook?

• Can we keep making it easier to turn a notebook into a Cookbook?
• Keep looking at cookiecutter solutions?
• Easier to get a blog post going within NCAR due to reliance on local data

• Scope of cookbook should be to answer some kind of question. It’s bigger than a one-off notebook. Everything should be as easily reproducible as possible. If not binderhub, then simple instructions for local execution.
• Running cookbooks on privileged compute services? Can we route notebook execution to binderhubs running on institutional compute services that can access local data (e.g. at NCAR)
• There’s still too much boilerplate in going from our Template to a working cookbook.

• The “how to run” section could be completely removed
• Example of jupyterbook template - https://github.com/executablebooks/cookiecutter-jupyter-book

2023-09-19: Outreach Working Group

Zoom | password: pythia23

Attendees:  [Name / Institution / GitHub Username]

• Drew Camron / Unidata / @dcamron
• Kevin Tyle / UAlbany / Kevin Tyle
• Max Grover / Argonne / @mgrover1

Agenda + Notes:

• Quarterly newsletter?

• September Quarterly Newsletter
• Highlight efforts from first grant, preview of what is to come
• Simple and quickest: Markdown document

• Social media platform

• Considering implications if Twitter/X goes to a mandatory pay model
• BlueSky: Matplotlib, PyART, condaforge et al. all have presences now
• LinkedIn: some interaction following the repost of the NSF funding announcement; Anaconda/Panel are using it fairly extensively now

• Blog posting

• JK/DC exploring the Sphinx blog theme

Action items:

• Set up BlueSky account
• Advertise Hackathon 2024 save-the-date on existing platforms and BlueSky
• Newsletter outline by end of next week (9/29)

2023-09-18: Infrastructure Working Group

Zoom | password: pythia23

Facilitator: Brian Rose | Note-taker: Kevin Tyle

Facilitation rotation sign-up and schedule

Attendees:  [Name / Institution / GitHub Username]

• Brian Rose / UAlbany / @brian-rose
• John Clyne / NCAR / @clyne
• Kevin Tyle / UAlbany / @ktyle
• Julia Kent / NCAR / @jukent
• Max Grover / Argonne / @mgrover1
• James Munroe / 2i2c / @jmunroe
• Rob Ford / UAlbany / @r-ford
• Drew Camron / Unidata / @dcamron
• Orhan Eroglu / NCAR / @erogluorhan

Quick Updates:

• Please sign in on this page above (and add any quick updates, including accomplishments)
• KT:

• JS2 status:

• Just under 50% of our Discover Access allocation has been used to date

• At current rate, we’d hit 100% in December
• Plan to ask for the full allocation we applied for (2x what we were granted, which was expected) by early November
• Plan for an amped-up allocation for the next phase of Pythia
• Get metrics on usage of our binderhub

• Tuesday 9/26 5:00PM EDT/3:00 MDT: Binderhub will be down for maintenance (estimate 30 minutes)
• Binderhub was used in support of AMS Radar Conference workshop, and will be used in support of an open science workshop in Colombia in late October
• WIP: PangeoForge recipe for datasets
• ktyle@albany.edu Unidata folks have minimal automation in place already, but are glad to chat about the resources they do have and the tools they’ve been exploring - one suggestion: https://blog.jupyter.org/accurately-counting-daily-weekly-monthly-active-users-on-jupyterhub-6fbec6c6ce2f

• ARCO-ERA5 Dataset now includes isobaric surfaces, 1959-2022! (486 TB)

• Good opportunity to add some additional cookbooks/notebooks that exploit this dataset
• To do: open issues on the Cookbook

Agenda + Notes:

• Checking on action items from last IWG:

• Progress on metrics - Julia

• Google Analytics Embed API

• Investigating possible Sphinx theme solutions - Drew
• Public cloud storage needed to support cookbook data - Kevin Tyle

• Plan to follow the google ARCO-ERA5 example

• Proposal for new Pythia meeting structure [BR]

• “Iteration planning meeting” – term from Agile method
• 2i2c: iteration planning meetings occur every 2 weeks
• What is the difference between product owners, stakeholders, and PIs, as it pertains to Pythia?

• Product owner: Orhan
• Stakeholders == PIs
• Stakeholders can also include members of the community
• It’s a bit of a gray area … we don’t have to lock into any strict definition at this time

• The group is in agreement to move forward with this plan!
• TBD: meeting day (Mondays can be problematic due to holidays)
• May not want to align with Pangeo weekly meeting … might be best to have Pythia meetings be analogous to Paneo working groups, that meet on their own schedule (e.g. Array working group)

• Mechanics of cookbooks reviews [JC]

• What is the process (the PR doesn’t include preview, code changes, etc)?

• GitHub issues, and ultimately managing them with GH projects as the best single means of management of those issues
• Cookbook preview infrastructure will function as intended on PR’s of contributed cookbooks. This means “preview” … not the reviewNB. That has to be enabled manually. But may not be necessary anymore … rich text git diffs are now available on GH
• Leverage what PyOpenSci has already done

• How to handle warnings in cookbooks?

• Still an open question. Warnings today may mean failures tomorrow. But across-the-board cookbook failures warrant a more short-fuse investigation

• Triage of unsorted infrastructure issues: https://github.com/orgs/ProjectPythia/projects/3/views/11

• 161: assigned to medium priority
•  158: likely can be closed, RF will confirm
• 153: assigned to low priority
• 348: high priority: JK will re-title; DC, BR, MG will add presentations
•  77: medium priority
•  424: medium priority
• 157: medium priority
• 114: BR/KT will assess

Action Items:

• Open issue on getting usage metrics for Binderhub
• Open issue for new cookbooks / additions to existing ARCO-ERA5 cookbook given the new ERA5 ARCO dataset availability
• Decide on a day for the meetings
• Reach out to Pangeo folks regarding new Pythia meeting plan schedule (esp. Week 1)

2023-09-11: Education Working Group

Zoom | password: pythia23

Facilitator: Drew Camron | Note-taker: rford2@albany.edu

Facilitation rotation sign-up and schedule

Attendees:  [Name / Institution / GitHub Username]

• Brian Rose / UAlbany / @brian-rose
• Drew Camron / Unidata / @dcamron
• John Clyne / NCAR / @clyne
• Rob Ford / UAlbany / @r-ford
• Julia Kent / NCAR / @jukent

Quick Updates:

• Please sign in on this page above (and add any quick updates, including accomplishments)
• KT: on vacation this week
• JC: Our NSF annual report has been approved
• BR:

•  the UAlbany NSF report also approved
• Planning to submit a Pythia abstract to AGU Ocean Sciences

• JK: Cookbook on Viz current state

Agenda + Notes:

• Cookbook review criteria

• Posting on the Pangeo Discourse for feedback

• KT: What are people’s thoughts on Eric Bruning’s issue?

• Quick start guide? We should be more opinionated about how to use Python (tools, env manager)

• JK: This issue on metrics says that MetPy has scripts for this - can someone link them to me?

• Issues with displaying metrics on Pythia website

• Quick metrics discussion on #319
• 2 cookbooks under review:

• Interactive Sentinel-2 (cookbook repo)

• Waiting for one more review from John C.

• Vapor Python (cookbook repo)
• Cordex vis notebook.

• Keeping track of cookbooks

• Use GitHub (labels?)

• How complete should a cookbook be before publishing it to the gallery?

• BR:

• Should not include cookbooks that are broken or empty
• Can be a single notebook

• JC: as soon as it is useful (Minimum Viable Product - MVP)
• DC: we can use releases to allow for further development

2023-08-28: Education Working Group

Zoom | password: pythia23

Facilitator: Rob Ford | Note-taker: John Clyne

Facilitation rotation sign-up and schedule

Attendees:  [Name / Institution / GitHub Username]

• Drew Camron / Unidata / @dcamron
• Rob Ford / UAlbany / @r-ford
• John Clyne / NCAR / @clyne
• Kevin Tyle / UAlbany / @ktyle
• Brian Rose / UAlbany / @brian-rose
• Julia Kent / NCAR / @jukent

Quick Updates:

• Please sign in on this page above (and add any quick updates, including accomplishments)
• JC: submitting annual report today
• KT: AMS Abstract deadline this Thursday, 8/31

• Drew and KT submitting separate abstracts. Link to AMS2024 folder

• DC: LinkedIn repost with grant announcement made - interact!
• BR: the Albany NSF Annual report also due… will be putting it together this week

Agenda + Notes:

• Cookbook Review Criteria doc [DC]

• DC: Next steps

• Set up a timeline
• Explore tools to facilitate/automate

• 2 cookbooks under review:

• Interactive Sentinel-2 (cookbook repo)

• Waiting for one more review

• Vapor Python (cookbook repo)

• Needs reviewers. Use as a test case for new review criteria?
• N.B. this notebooks requires GPUs, which we don’t have, so this won’t have binder support for now.

• BR: one more cookbook queued up: Cordex vis notebook. Plan is to use this as another review criteria test case.
• JK: has a viz cookbook that is ready to go - another guinea pig.
• BR: we should add a statement in cookbooks, such as VAPOR, that aren’t binderized, that the notebooks can be run locally.

• Summer hackathon -  confirmed for 2024 for June 10-14 (John)

• Main Seminar Room: 8-5pm, M-F
• Monday, June 10:  Library, Damon & Chapman 10-3pm
• Tuesday, June 11: Library & Chapman & Penthouse 10-3pm
• Wednesday, June 12: Library, Damon & Chapman 10-3pm
• Thursday, June 13: Library, Damon 10-3pm, Penthouse 10-12/1-3pm
• Friday, June 14: Library, Damon & Chapman 10-3pm
• BR: we should put out a save the date. How about on our new blog. John will put a blog together.

2023-08-22: Outreach Working Group

Zoom | password: pythia23

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle
• Drew Camron / Unidata / @dcamron

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• AMS abstracts due Aug 24

• Python-tech abstract + educational abstract (provisional title: “Cooking up a Storm”)

• We have an invite code for BlueSky (thanks to Hannah Aizenman)

Agenda + Notes:

• Action items from last meeting:

• Rope in Thomas for Geology discussion [DC]
• September newsletter: about grant acceptance, about COESSING collaboration, UAlbany article about Pythia

• Takeaway priorities: discourse / linkedin > twitter / new portal news page & blog > email list
• Reach out to geologists
• Blog posts, summarize year of cookbooks, what next grant looks like.
• Upcoming hackathon link was kind of hacky, want a more permanent place for updates
• Make past publications more visible and updated
• Update footer of portal and explore upstreaming footer content and formatting to theme
• September for first newsletter to go on Portal (and email list?)

Action Items:

2023-08-21: Infrastructure Working Group

Zoom | password: pythia23

Facilitator: John Clyne | Note-taker: Brian Rose

Facilitation rotation sign-up and schedule

Attendees:  [Name / Institution / GitHub Username]

• John Clyne / NCAR / @clyne
• Kevin Tyle / UAlbany / @ktyle
• Julia Kent / NCAR / @jukent
• Orhan Eroglu / NCAR / @erogluorhan
• Brian Rose / UAlbany / @brian-rose
• Rob Ford / UAlbany / @r-ford
• James Munroe / 2i2c / @jmunroe
• Drew Camron / Unidata / @dcamron
• Max Grover / Argonne / @mgrover1
• Ryan May / Unidata / @dopplershift

Quick Updates:

• Please sign in on this page above (and add any quick updates, including accomplishments)
• JC: Planning to submit NSF report *sometime* this week. If you have further input, please let me know ASAP. Thanks for your contributions!
• JC: Summer hackathon confirmed for week of June 10-14. Please add to your calendar!!! In Boulder at the Mesa lab
• DC: time to continue Pythia Cookbook Review Criteria discussion at next EWG
• MG: Presenting on Radar Cookbook at AMS Radar next week

Agenda + Notes:

• AMS deadline is later this week (Thursday Aug 24 – but might be extended)

• OWG chatted about 2 abstracts

• Kevin: Pythia in educational setting (Programming languages of open science conference – teaching, training, and building communities around Python)
• Drew: Community and technology updates

• Look for abstracts later this week
• Chance that Pythia might be invited for a core science keynote… stay tuned on this.
• Should we reach out to Cookbook contributors to encourage submissions of content to AMS?

• Post to the hackathon slack [DREW]

• Authorship of conference abstracts: How do we decide what names are included?

• Bigger issue of tracking contributions across all of Pythia (and getting it on our home page)
• This should be automatable with a github “enterprise” account.

• Open a trial and test it out?
• But pricing is per member of org, so this is not likely to be viable solution for Pythia

• Look at Jupyter project’s “tiers” of participation
• Short term action: use last year’s author list, remove names of people who are definitely gone from the project, add new folks.

• Review infrastructure backlog

• Update status, reassess “high priority” items
• Lots of issues are “high priority”, but there can only be one “highest priority”. What is it?

• Going through and closing or updating lots of issues
• Still leaving behind quite a few high priority issues

• Which issues are the biggest roadblocks for growth of community and content?

• Data storage for Cookbooks?

• Storage (1 TB) is available on our current Jetstream2 allocation. We just need to develop pangeo-forge recipes to get data written to the right storage buckets

• The Sphinx theme problem? It’s not currently holding anyone back but our whole infrastructure might break with no warning.

• Also security risks from using old package versions

• Authentication on our Binderhub?
• Who has the ability to push solutions forward?
• Metrics issue might be lower effort

• Consensus on highest priority items for IWG:

• Public cloud storage needed to support cookbook data - Kevin Tyle
• Automate collection of metrics - Julia Kent
• This repo needs tests OR Update theme to use newest Sphynx Book Theme - Drew

• These two tasks may need further consideration to prioritize

• Agile for Pythia - some scattered ideas/points

• Orhan looking into similar projects and their Agile applications as well as reading
• Met with NCAR’s Cloud Pilot project’s Nick Cote

• Start with an Agile (Scrum, Kanban, Scrumban, etc.) and know things would change over time because of learning the structure

• Continuous feedback and improvement

• Determine Team capacity
• Re Pythia’s pile of high priority issues: Looking at issues of the last x (say 30) days would give some ideas

Action Items:

• Post to hackathon slack encouraging Cookbook contributors to submit content to AMS meeting [DREW]
• Progress on metrics [JULIA]
• Take a look at possible Sphinx theme solutions [DREW / KEVIN]

2023-08-14: Education Working Group

Zoom | password: pythia23

Facilitator: John Clyne | Note-taker: ktyle@albany.edu

Facilitation rotation sign-up and schedule

Attendees:  [Name / Institution / GitHub Username]

• John Clyne / NCAR / @clyne
• Kevin Tyle / UAlbany / Kevin Tyle
• Rob Ford / UAlbany / @r-ford
• Julia Kent / NCAR / @jukent
• Max Grover / Argonne / @mgrover1
• Brian Rose / UAlbany / @brian-rose

Quick Updates:

• Please sign in on this page above (and add any quick updates, including accomplishments)
• KT: busy preparing for start of semester next week
• MG: ARM ASR meeting last week. M. Sharma nicely summarized the cookbook he worked on during the June Hackathon; was nicely received by those in attendance
• BR: press release about new grant came out last week https://www.albany.edu/news-center/news/2023-researchers-team-build-open-geoscience-community-through-16-million-national

Agenda + Notes:

• OWG Report

• AMS Abstracts due soon (8/24). Current plan for 1 educational “in the classroom” abstract (KT) and 1 “tech/community update” abstract (DC). JK will also be co-presenting a data viz short course (including Vapor)
• Avenues for grant announcement and asynchronous community updates - will start a “newsletter” report, aiming for 2-3 month frequency to be posted to Discourse/LinkedIn and directly to the portal via blog (JK)

• Metrics are accessible … more comprehensive and meaningful than Twitter
• Once we get more content posted, the metrics will be more useful. Right now just 10 followers … mostly Pythia core members

• Portal review and update, including hidden “about” section w/ publications
• Dave Hart posted this story on the CISL website about Pythia 2.0

• Summer hackathon, 2024. Two options for dates (John)

• Main Seminar Room available 8am to 10am, 3pm - 5pm
• *** Agreed to pick June 10-14th. Room availability is key ***

• Can attend: Ryan, John, Brian, Drew, Kevin, Julia, Max
• Maybe attend: Orhan, Julia, James Munroe
• Library, Damon, and Chapman available for breakouts

• June 17-21st: Not enough room availability and NCAR is closed 6/19!!

• Can attend: Ryan, John, Brian, Drew, Kevin, Orhan, James, Julia, Max
• Maybe attend: Julia
• Library available all week. Chapman available M,W,Th

• Additional rooms/times may open up as people release holds
• Hybrid will be the plan. Worked well in 2023.

• NSFProjectReport2023If you’ve been tagged, please have your input in by August 18.

• Everyone is welcome and encouraged to review and provide input (comments or suggested text)

• Should we add content to better support open science? Draft forum posting:

• Pythia’s educational materials cover many of the technologies and practices that are vital to Open Science principles such as transparency, accessibility, and reproducibility. But for a scientist not accustomed with many of these technologies, putting everything together in a way that allows them to create a shareable, reproducible workflow may not be obvious. Should Pythia consider adding a section that leverages the Foundations modules and provides more of a step-by-step guide to creating a reproducible workflow with a Jupyter Notebook that is backed by GitHub reproducibility and shareability? Such a guide might include a template repo with a Notebook and conda environment management, and so on.

• JK: Great idea! Environment maintenance is a very frequently-asked question. Will be presenting something similar in a workshop later this month.
• BR: Cookbook template already has environment reproducibility built-in. Not a fan of pinning packages, though.
• JC: Thinking more of a trimmed down version of the cookbook template … but maybe the existing cookbook template is enough.
• JK: might be a good idea to at least reference the versions of the most important packages included

• Cookbook template may be a bit too over-expansive for a use-case where one would just want to reproduce their workflow

• KT: include version #’s in a text document, rather than strictly pin them in environment.yml
• MG: Upload docker image with each unique version
• BR: there is a plugin that shows versions … watermark?

• https://github.com/rasbt/watermark
• Can’t guarantee reproducibility, as earlier package versions will eventually prove impossible to rebuild from scratch

• JC: will create an issue and then post and link to it on the forum

• Pythia 1.0 (EarthCube) -> Pythia 2.0 (GEO OSE)

• 2.0 partners: Albany (lead, PI: Brian Rose), NCAR, Unidatata, 2i2c
• Overlap in PoP (Period of Performance):

• 1.0: Sept 2020 - August, 2024
• 2.0: January, 2024 - December, 2027
• Strive for continuity: PI’s Clyne (1.0) and Rose (2.0) in close consultation on major decisions

• Changes in meeting structure under discussion

• Community meeting: focused on engagement with community. Current meetings are problematic in terms of organization and not being welcoming to community attendees.

• Most of our “getting things done” meetings are focused on infrastructure. Create a new meeting structure that is more tied into the community needs

• Management meeting: operational aspects of achieving our goals
• KT: tie community meetings into the weekly Pangeo meetings?
• MG: Pangeo weekly call morphs into a combined Pangeo/Pythia community call
• BR: 2.0 explicitly calls for a Pangeo Education Steering Council, tasked with setting high-level priorities for what the community is looking for. Avoid having both a Pangeo/Pythia “council” AND the explicitly-proposed Steering Council.

• Cookbook Review Criteria doc

• Turn into checkboxes a bot comments on a PR for adding a file to the Cookbook gallery
• Review for final discussion and implementation at 8/28 EWG call

• Pythia Blog now on our website
• Add how-to-cite to portal (JK)

• Should this be on mainpage vs in the appendix?
• Thoughts on footer menu?
• Thoughts on left navbar structure of ‘about’ etc
• Site needs overhaul, but we need to go forward on this PR!
• A site overhaul might be better suited to a more formal overhaul, ideally with insights from professional website developers
• Sphinx-pythia-theme still needs attention … JK researching it
• Approve existing PR and open new issue so we can move forward

Action Items:

• See items highlighted in bold/purple above

2023-08-08: Outreach Working Group

Zoom | password: pythia23

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle
• Julia Kent / NCAR / @jukent
• Drew Camron / Unidata / @dcamron

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• AMS abstracts due Aug 24

• Consider python-tech abstract + educational abstract

Agenda + Notes:

• Press release about grant acceptance, about COESSING collaboration, UAlbany article about Pythia

• Twitter, LinkedIn, Pangeo discourse

• Draft - Discourse post for grant announcement

• Email list?
• Takeaway priorities: discourse / linkedin > twitter / new portal news page & blog > email list

• Reach out to geologists
• Blog posts, summarize year of cookbooks, what next grant looks like.

• Upcoming hackathon link was kind of hacky, want a more permanent place for updates

• Make past publications more visible and updated
• Update footer of portal and explore upstreaming footer content and formatting to theme
• September for first newsletter to go on Portal (and email list?)

Action Items:

• Don’t lose track of September newsletter summary
• Rope in Thomas for Geology discussion [DC]

2023-08-07: Infrastructure Working Group

Zoom | password: pythia23

Facilitator: Note taker:

Attendees:  [Name / Institution / GitHub Username]

• Rob Ford / UAlbany / @r-ford
• John Clyne / NCAR / @clyne
• Kevin Tyle / UAlbany / @ktyle
• Julia Kent / NCAR / @jukent
• James Munroe / 2i2c / @jmunroe
• Brian Rose / UAlbany / @brian-rose
• Chinwendu Agbaetuo / @dindustack
• Orhan Eroglu / NCAR / @erogluorhan

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• Facilitator sign-up for IWG has been updated through end of year. Please sign up for a slot!
• Facilitator sign-up for EWG needs sign-ups from 11 September to end of year
• Before EWG Monday 8/14, add and comment on Cookbook Review Criteria doc
• JC: NSF Annual report is due August 31. If you have been tagged for input, please provide it by Friday, August 18. 
• JC: working on dates for next year’s hackathon. The summer calendar is already VERY full. Please respond to Lisa’s poll ASAP so we can get this nailed down. We may not be able to accommodate everyone’s preferences.
• JC: Paige Martin (and organizers) using Foundations for Coastal Ocean Environment Summer School In Nigeria and Ghana this month.  (COESSING)
• JC: Can someone provide some more specific guidance on this post?
• KT: Binderhub
• BR: press release about our newly awarded NSF grant coming out later this week

• Further discussion on tomorrow’s OWG on additional/complementary posts / blog articles that can follow up on the UAlbany article (Brian will not be able to attend, but others on the OWG will discuss).

Agenda + Notes:

• Q&A with Chinwendu
• Issue with a cookbook environment: https://github.com/ProjectPythia/interactive-sentinel-2-cookbook/issues/2

2023-07-31: Education Working Group

Zoom | password: pythia23

Facilitator: ktyle@albany.edu | Note-taker: Drew Camron

Facilitation rotation sign-up and schedule

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle
• Brian Rose / UAlbany / @brian-rose
• Drew Camron / Unidata / @dcamron
• John Clyne / NCAR / @clyne
• Rob Ford / UAlbany / @r-ford
• Max Grover / Argonne / @mgrover1
• Ryan May / Unidata / @dopplershift

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• JK - working on an advanced visualization cookbook
• BR: our Pythia 2.0 NSF grant has been awarded. A public news release is coming by end of this week
• No facilitator has signed up for next week, please sign up here

Agenda + Notes:

• Outreach highlights

• AGU abstracts: Due this Wednesday, 8/2!

• BR will share an abstract for review asap, planning to submit and present

• AMS abstracts due Aug 24. Will be discussed at upcoming OWG and likely to be well-represented by Pythia.
• BR will likely submit at Ocean Sciences as well
• Consider non-talk presence at eg AMS. Deadlines for short courses, town halls are passed. May be able to blend with Unidata Python @ AMS Student Conference session

• Updates on cookbooks in Cookbook Roundup 
• NSF Annual Project Report (John)

• Due August 31
• Stay tuned for writing assignments
• Metrics needed
• No Cost Extension approved (EarthCube grant PoP runs through August, 2024)

• Next year’s hackathon (John)

• Limited dates available for summer. Is fall or spring an option?

• Pythia Cookbook Review Criteria

• Goal for a cookbook author: follow along with each of the enumerated checkbox items
• Comments?

• BR: Zenodo DOI link check has now been disabled in the template.
• “Good” programming practices:

• BR: appreciate John’s point about best practices, e.g. avoid loops when array syntax is possible. Reviewers should be aware of obvious ways for the code to be more expressive and less error-prone. As we develop a “feel” for this process, we may then be able to describe/define some of these best practices as part of the checklist.
• JC: agree with BR

• Content maintenance

• BR: each cookbook should have a team. This way whoever is part of the team will be tagged for reviews, etc.

• Items to add?

• Timeline: what can an author expect in terms of how long it will take for a cookbook to proceed through review and to final publication on the gallery
• JL: what’s the best way for someone who has a cookbook idea to get an initial “green light” to start proposing/working on a cookbook?

• BR: Discourse/other informal channels would be best.

Action Items:

• DC: will take initial pass at the checklist. Nothing will be deleted yet. Next meeting, get a more formal document finalized.
• BR: whatever final list looks like, it needs to be in two places: contributor’s guide, and as a form that will appear as part of a PR.

2023-07-24: Outreach Working Group

Zoom | password: pythia23

Attendees:  [Name / Institution / GitHub Username]

• Julia Kent / NCAR / @jukent
• Drew Camron / Unidata / @dcamron
• Andrew Huang / Anaconda / @ahuang11
• Kevin Tyle / UAlbany / @ktyle

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• Facilitator sign-up for IWG has been updated through end of year. Please sign up for a slot!; Facilitator sign-up for EWG also still up and needs sign-ups
• Before EWG Monday 7/31, add and comment on Cookbook Review Criteria doc
• DOI document (can skip to step 8, I believe)
• AH attended ESIP meeting ft. Kerchunk and cloud-native data; consider enhancing cookbook descriptions with more information
• ForceSMIP hackathon

• general ideas around good coding practices, like commenting code, doc strings, (re)using functions rather than e.g. copying and pasting code between projects, code review
• python for climate, mostly xarray but if there are other toolboxes that are particularly helpful, introducing them as well
• how to make a maintain a github repo

Agenda + Notes:

• AGU Abstract Submission Deadline: Wednesday 8/2

• Full-day innovations session: Voices from the Global Open Science Community: Showcasing Progress, Challenges, and Lessons Learned

• The organizers “are looking to include time for a few 25 minute workshops.  While discussing options, we thought about having some sort of interactive workshop focused around building a community around open science, and I thought of Project Pythia as a great example of this. I'm not sure exactly how it would work, but I'm curious if you or anyone else involved in the project would be interested in giving some sort of workshop on this topic. We're not looking so much for "here's how to use this tool", but "here's how we operate to create an effective community". “This would be an invited talk.T

• Please consider “Session Title: IN002. Accelerating Science: The Convergence of Inclusive Computational Resources, Cloud-Optimized Data, Open-Source Tools, and Open Collaborative Communities. “ (disclosure: James M. is a session organizer)
• Possible submission for CMIP6 cookbook

• The Dawn of the Era of Cloud based Climate Informatics
• Over the past two decades, the size of data available from climate models and observations has grown several-folds. As a result, the traditional approach of downloading climate data and manipulating it locally is becoming increasingly challenging, even for researchers with access to large national computing infrastructures. We've been hearing for a few years how remote computing is the solution to our problems with data volume. Despite examples and demos showing this can actually work, we're not seeing widespread adoption yet from the scientific community. Is it just inertia or is something missing in that model that is preventing it from widespread adoption? This session is intended to bring together submissions that seek to facilitate this new approach to climate informatics. Submissions on what technologies should be adopted, what feedbacks have been received and obstacles encountered to-date and how to bring value to interdisciplinary climate research are encouraged.

• ESIP Meeting: `kerchunk` + `titiler-xarray`; on the fly web tile generation

• Getting Cookbook on WMS published
• Cookbook tag descriptions are extremely underwhelming, until I attended the kerchunk presentation. Instead, maybe they should just use the Motivation section.

• Kerchunk “makes a NetCDF file look like a Zarr file, a cloud-native, efficient file format for reading”

• Adding to the kerchunk cookbook 

• Visualizing a streamed dataset with kerchunk
• Considerations for coding practices
• “Download as .py” an option?
• Scripts instead of notebook, e.g. https://www.ncl.ucar.edu/Applications/coamps.shtml
• “Too many cookbooks” leading to duplicate implementations, potential noise, reduced quality, difficulty to maintenance
• Repository of “applications” or script https://www.ncl.ucar.edu/Applications/
• Template reorg: copy “how to run notebooks” section to primary sidebar
• Considerations for viewability of both galleries

Action Items

• Drew Camron open issue for zenodo link + release + link check failure and workflow
• Drew Camron will explore LinkedIn (and mention at EWG)

2023-07-24: Infrastructure Working Group

Zoom | password: pythia23

Facilitator: Kevin Tyle; Note taker: Drew Camron

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle
• Rob Ford / UAlbany / @r-ford
• James Munroe / 2i2c / @jmunroe
• Drew Camron / Unidata / @dcamron
• Ryan May / Unidata / @dopplershift

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• Facilitator sign-up for IWG has been updated through end of year. Please sign up for a slot!
• Facilitator sign-up for EWG also still up and needs sign-ups
• Before EWG Monday 7/31, add and comment on Cookbook Review Criteria doc

Agenda + Notes:

• Action items from previous IWG meeting:

• Dates for next year’s Pythia hackathon? Need to get dates settled ASAP from NCAR logistics point of view.

• Action: JC will get the ball rolling with a list of potential dates

• PRs for sandbox. What do we do with them? See latest.

• OPen issues for this (JC)
• Add a bot to auto-comment on new PRs in the sandbox (JK)
• Add a bot to auto-close stale PRs in the sandbox

• AGU abstracts related to Pythia? Deadline coming up early August

• Will be discussed at tomorrow’s OWG meeting

• Please consider “Session Title: IN002. Accelerating Science: The Convergence of Inclusive Computational Resources, Cloud-Optimized Data, Open-Source Tools, and Open Collaborative Communities. “ (disclosure: James M. is a session organizer)

• Binderhub

• KT attended last week’s Jupyter/Binderhub Collaboration Cafe

• Persistent sessions: appears easy to implement (ref: https://www.youtube.com/watch?v=dwidVhPtQT4&ab_channel=JupyterCon)
• Multiple simultaneous user sessions: harder
• KT will re-enable GH auth for BinderHub, needs to explore multiple sessions support
• KT is exploring BinderHub on top of JupyterHub w/ JetStream GPU support for cookbooks that can benefit from. Unidata has some expertise here if needed

• Current open issues/PRs 

• Public cloud storage option for cookbook data

• https://radiant.earth/? mission-aligned non-profit that might be able to provide storage options

2023-07-17: Education Working Group

Zoom | password: pythia23

Facilitator: Drew Camron | Note-taker: Kevin Tyle

Facilitation rotation sign-up and schedule

Attendees:  [Name / Institution / GitHub Username]

• Brian Rose / UAlbany / @brian-rose
• Rob Ford / UAlbany / @r-ford
• Max Grover / Argonne / @mgrover1
• Kevin Tyle / UAlbany / @ktyle
• Elena Romashkova / NCAR / @rmshkv
• Erin Rhoades / Unidata / @erin6541

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• Drew: Facilitator signup form has been updated to add our next several meeting dates. Please sign up at the link above.
• Julia - absent today due to CISL director search. I will be attending AGU but likely to present on GeoCAT content. OWG was unable to meet last week due to SciPy, but does anyone plan on presenting on Pythia content? Abstracts due Aug 2.

• BR: I plan to attend AGU. OWG will meet next week and decide on a plan
• KT: AMS 2024 deadline is 8/24

• Erin Rhoades:

• Working on MetPy cookbook, especially SkewT and Xarray content. Some of the Xarray-related materials would be worthy of incorporation into our Foundations material.
• https://github.com/erin6541/xarray-cb/blob/main/notebooks/xarray-cb.ipynb

• BR: had a meeting with Shelley Stall and Brian Sedora from the AGU Notebooks Now! Initiative to talk about alignment between Notebooks Now! and Pythia cookbooks.

• They are excited about what Pythia is doing and eager to help promote our content as resources for AGU members
• In turn, AGU can help turn Cookbooks into scholarly objects, e.g. pitching a “special issue” of a journal devoted to cookbooks.
• We will hopefully keep talking about all this

• Elena - physical oceanography cookbook update, got data access fixed for 2 / 5 notebooks, working on the others
• Max - one of the radar cookbook contributors (Millind Sharma) will be presenting on the radar cookbook + Project Pythia at our ARM/ASR Programmatic meeting around DC in a few weeks 🎉

• Scientific Python’s education group was interested in our material

• Lecture series

• RM: It was clear at SciPy that our educational material is very relevant

Agenda (with notes from the meeting):

• SciPy roundup

• Drew and Kevin presented Friday afternoon; link to presentation will be placed in our Google Drive space

• Drew noted that links to our public presentations are buried in our website … needs to be improved (add to IWG Project Board)

• And updated with lots of more recent talks!

• Lots of interest in the GitHub Actions that power our Cookbook/Foundations content

• BR: a big chunk of functionality in our custom GitHub Actions could be “upstreamed” into Jupyterbook (e.g. routing notebook execution to Binder). That would make it much easier for other groups to use the functionality AND vastly simply the Actions code that we have to maintain. It’s a win-win that deserves an allocation of some developer time.
• MG: Metric-related gathering: Scientific Python’s devstats looks like a good model to follow. Will help address our issue 319

• State of cookbooks not in the gallery

• Dask: recent PR fixed data access issue. Seems ready to add
• Gridding: removed because of an issue. Can it be added back?

• BR: yes. I worked with the author last week to fix the builds for this cookbook, it should be ready to go

• Web Map / Feature Services:

• Needs reviews

• NA-CORDEX Data Visualization

• Needs reviews

• Marine Heatwaves and EOFs: WIP
• A few more works in progress from the 2023 hackathon listed at https://docs.google.com/document/d/1INcckmrrGtCn-H8gP8kMANwcAxzVHmie3QX52sQvojo/edit

• Guidance on reviewing cookbooks for inclusion in the gallery: can we write down a simple policy? Need something other than just “does it run?” This is really necessary now that we’re reaching a critical mass of newly-contributed cookbooks.

• MG: Set up some sort of queue When newly-contributed cookbooks get added, add them to the queue. Automatically set up a “ready to review” issue.
• DC: Create a project board dedicated to cookbooks added to the queue.
• BR: Whatever we come up with should serve the purpose of keeping things open and moving … not creating barriers and making this hard.

• Need two reviewers to approve the cookbook
• When a reviewer “signs off” on a cookbook, that includes two things:

• Mechanics of the cookbook repo are “solid” and up to date
• Scientific content passes muster

• Make sure that references to cited content appear
• Assure that the citations.cff file is complete

• MG: aim for consistency in cookbook layout, e.g. title (“Dask Cookbook” rather than “NCAR Dask Tutorial”
• RF: While scientific content could be reviewable by anyone, the “style guide” part of the content would most likely require someone familiar with the styles used in our template. Sort of “infrastructure-related” content.
• BR: these are similar issues for, e.g. journal reviewers/editors. But let’s grow to that point, and that starts with a general guide for what’s needed to get a cookbook approved.
• MG: might not be necessary to require two separate reviewers, as long as the technical and content boxes are checked. This will help in terms of getting cookbooks reviewed and posted in a timely fashion.
• DC: will draft cookbook review document and ask folks for comment. Besides just sharing a document, will also post on the relevant Discourse channel
• MG: whatever we come up with should be added to a PR template for use by cookbook authors
• BR: what should we do with the cookbooks that are already waiting for review? Wait two weeks or move forward with a sense of the review criteria we have discussed today?

• DC: proceed with reviewing but hold off on final approval for two weeks
• MG: For those cookbooks that appear ready to go (e.g. webmap notebook) and whose authors are eager for it to be published, go forward with those.
• RF: same can be said for the Dask and Gridding cookbooks (Dask cookbook has already gone through review, and Gridding cookbook was previously in the gallery)

• RF: Jobs in the Update Cookbook Gallery workflow are being skipped. Will open an issue and will be discussed at next week’s IWG

Action Items

• EWG agenda

• Cookbook review document 1
• Discourse post (+ review doc 2?)
• Async contributions before sync review

• OWG agenda

• AGU / AMS conference abstract deadlines (8/2 and 8/24)
• Scientific Python

• IWG agenda

• Cookbook gallery workflows being skipped
• Links to past talks hard to find (and more recent talks need to be added)

2023-07-10: Infrastructure Working Group

Zoom | password: pythia23

Attendees:  [Name / Institution / GitHub Username]

• Julia Kent / NCAR / @jukent
• John Clyne / NCAR / @clyne
• Rob Ford / UAlbany / @r-ford
• Brian Rose / UAlbany / @brian-rose
• James Munroe / 2i2c / @jmunroe
• Orhan Eroglu / NCAR / @erogluorhan

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• JC: Cookbook discourse thread. Needs response. (RF: done)
• JC: NCE submitted to NSF
• JC: John meeting with Tricia OKeefe, NCAR partnership development, on Wednesday (1115 MT) to explore possible industry support
• BR: hopefully meeting soon with the AGU Notebooks Now! Folks about coordinating on “Cookbooks as scholarly objects”

Agenda + Notes:

Notes from last month’s EarthCube workshop in L.A. (JC)

• Raleigh Martin, NSF PO

• No plans for an EarthCube2.
• GEO OSE program supports Geo-CI (Think EarthCube lite).
• NSF taking an “incremental approach” with OSE to see what is needed (No OSE office planned at this time)

• EarthCube meeting is now a grassroots effort. May come to NCAR next year. Can we leverage with cookbook hackathon?
• John met with Arika Virapongse, Community engagement consultant for Earth Science data infrastructure. May be able to help with Pythia’s community engagement efforts.

• Dates for next year’s Pythia hackathon? Need to get dates settled ASAP from NCAR logistics point of view.

• Action: JC will get the ball rolling with a list of potential dates

• PRs for sandbox. What do we do with them? See latest.

• OPen issues for this (JC)
• Add a bot to auto-comment on new PRs in the sandbox (JK)
• Add a bot to auto-close stale PRs in the sandbox

• AGU abstracts related to Pythia? Deadline coming up early August

• Bring this up ASAP at the next AGU meeting

AGU abstract deadline approaching

2023-06-27: Outreach Working Group

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle

Quick Updates:

• Please sign in on this page above (and add any quick updates)

Agenda + Notes:

• Post-hackathon items:

• Remove announcement on main projectpythia.org page
• Tweet out newly-published (or expanded) cookbooks

• Upcoming conferences

• SciPy
• AGU
• AMS

• Radar (8/28→9/1)
• Annual meeting (1/28→2/1)

2023-06-26: Infrastructure Working Group

Attendees:  [Name / Institution / GitHub Username]

• Julia Kent / NCAR / @jukent
• Rob Ford / UAlbany / @r-ford
• Kevin Tyle / UAlbany / @ktyle
• John Clyne / NCAR / @clyne

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• KT: ERA5_interactive cookbook ready to be added to gallery

• Inline images not appearing on website: seems to be an issue in how the notebooks/images directory gets mapped to the _images directory in the published jupyterbook
• Procedure for adding to gallery post-form submission? A GH action should be triggered when someone submits a new cookbook to the gallery using the form. However it’s a simple one-line addition to the file https://github.com/ProjectPythia/cookbook-gallery/blob/main/site/cookbook_gallery.txt

• JC: John is giving a Pythia talk at the EarthCube community meeting on Wednesday in L.A.. Draft slides here. Please provide any updates by 4pm MT. Raleigh Martin will be in attendance. Discussion topics to bring up with Raleigh?
• JK: Went through steps for adding DOIs to several Cookbooks (published and unpublished), 5 left
• JK: talking about event at ESDS meeting right after this. slides
• BR: still working on the cookbook build actions to handle github secrets – should finish this this week

Agenda + Notes:

• Cookbook post-mortem

• Who is shepherding hackathon WIP?

• How to make sure work isn’t lost? Somebody from Pythia team shepherd through process, pair up with contributor, no blockers
• Make an assessment of WIPs
• Post hackathon, reach out once to the community asking for their current repository homes, drop links (Google doc, or sheets?)
• “Pythia team is interested in helping you get your work across the finish line, we’d like to have eyes on it so we can identify blockers, if you want to be on list drop link to repository with work in progress” do it ASAP, don’t pin them down on if they need help, include offer to adopt something that will not be worked on (sometimes people only have time during hackathon) - BR will do that

• “New” infrastructure issues

• Need GPU nodes on Binder services
• Storage for cookbook data, smaller buckets
• Where should these issues be opened - cookbook-gallery or cookbook-actions, discussion boards, projectpythia.io repo from portal for overall issues. Doesn’t matter if you add it to the project board? Still provide some guidance on this. There will be questions about the Pythia binder service, and where should those go? Not ready to build that out
• Remove Pythia members list from portal page, dynamic and automated, currently unhelpful to community building. Scrap it? Only project PIs? - BR to remove what we have, have an anonymous “your name here” box, how to acknowledge someone who is no longer active on the project “distinguished contributors” look at Jupyter project

• Binder?

• Short-term:

• Re-enable GitHub authentication (how to have more than one session)
• Decide on either reducing the VM CPU-class for the worker nodes and/or ask for the additional 750K SUs on JS2 that we originally applied for

• Medium-term:

• Investigate GPU-enabled Binderhub
• Persistent storage for authenticated users
• Multiple simultaneous sessions for authenticated users

2023-06-23: Hackathon Report Out and Quarterly Meeting

Attendees:  [Name / Institution / GitHub Username]

• Brian Rose / UAlbany / @brian-rose
• Julia Kent / NCAR / @jukent
• Max Grover / Argonne / @mgrover1
• Kevin Tyle / UAlbany / @ktyle
• Elena Romashkova / NCAR / @rmshkv

Quick Updates:

• Please sign in on this page above (and add any quick updates)

Agenda + Notes:

• Cookbook post-mortem

• What worked?

• Good week, people showed up for free, gave time, were engaged, met new people, that was our goal
• Hybrid component worked remarkably well. AV was flawless, whole room could be heard by virtual attendees. Hybrid plenary twice a day, anyone remote or in the room could share screen. No audio issues.
• Slack was a great decision! Helped bridge the gap between in person and virtual attendees. Future of the slack? Does it stay live? We’re on a free slack service, content sunsets after 90 days. Not an archive but can still be used for collaboration going forward. Don’t want to find confusion among community or make it burdensome for organizers. We don’t want to continue monitoring tech support channel.
• Discourse great for more thoughtful conversation, slack great for real time back and forth. Good for continuous synchronous collaboration. Do nothing. It may stay active for a few more months while people finish up their Cookbooks. Use same slack channel (without old content) for next year. Make a note that content will be lost to the users.
• Infrastructure held up well.
• Not everyone who signed up came, but everyone who made it was really dedicated. Lots of progress made on content and infrastructure. Was worth it to reach out to people ahead of time to form cohort or team.
• 36 people active on the slack channel. Can target a larger group next year, might need a crash course that isn’t relevant for all attendees.
• Helpful to see what level of comfort people came in at. Great knowledge sharing and spin up!
• It was hybrid in people joining remotely some days and in person others.
• Thoughts from RF: Slack and breakout rooms. Max of 2 people in the room though, small group worked, waiting for people to join call wasn’t too frustrating

• What could work better?

• Need stickers
• Better guidance as developing cookbook for realistic expectations on how much resources their Cookbook will demand. What is a typical environment? People asking for guidance.
• Negin’s suggestions about 5 mg buckets for data.
• Build frequency for health checking is daily, might be able to slow that down to save resources. Testing is biggest use of our resources. Much greater than people using the books.
• Data road blocks, lots of issues that got in the way of what Elena wanted to work on. Datasets weren’t available on the cloud or were too large to upload. CISL might host datasets later on. Encourage people to upload small representative subset of the data. Worth getting whole dataset out into open and then taking sample of it for demo purpose.
• More effort into subject matter champions that invest in building their cohort prior to hackathon and reaching out to people in that subfield to join. Less time selling ideas and shopping around for people on day 1.
• The split of half hack time and half in a jupyter tutorial was a little awkward. Possibly address this with a day 0, so people who need spin up tutorials show up earlier. Or half day on a Monday so people can travel in on Monday. And time for the organizers to get together Monday morning.
• Get some input on how remote attendance worked.
• Sometimes failed to join the Zoom room right away, they were cumbersome but seemed like the best solution. Clustering of channels into smaller group was a good idea that worked well! Some clusters probably worked used Zoom more than others.

• Survey: https://docs.google.com/forms/d/1-KjOdAhlljzE1cSEBW80MwZ4Tm7XFa9hEDoI_cqUV6M/edit?ts=6495fc27 

• Quarterly meeting

• Hit promised deliverables except getting good automated metrics collected and posted on website, will benefit us as we track the growth of the community, understand hot spots of community interest.
• Proposal status, Brian is the PI
• Steering counsel, split up grant writing from community aspect, under Pythia or Pangeo label for setting priorities. Meets quarterly or semi annually.
• Replace Pythia members page on homepage, PIs is out of date.
• Let cookbooks run wherever they best run. NSF cloud and Pythia infrastructure. No need to all run on same place.
• Pangeo medium blog on Cookoff? Get in habit of “workshop report” for event, something informal, JK presenting at ESDS meeting on Monday
• Collaborate on article or journal about Cookbooks, JOSS journal of open source education, BAMS article (format essay, targets meteorology community). What are they and what problems are they trying to solve?
• Target special issue publication of Cookbooks, outline vision in a concise place that is future home of publishing content. Look more at AGU Notebooks Now!
• Plans to submit to AGU open science sessions? Discuss soon at next EWG
• Guidance on how to handle binderhub. Burn rate is high right now, was bumped up for the event. Could be addressed by IICC

2023-06-13: Outreach Working Group

Attendees:  [Name / Institution / GitHub Username]

• Brian Rose / UAlbany / @brian-rose
• Rob Ford / UAlbany / @r-ford
• Drew Camron / Unidata / @dcamron
• Andrew Huang / Anaconda / @ahuang11

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• Nearly 50 people registered, split between in person and remote
• Made a loose list of topic ideas, particularly from people who agreed to facilitate a breakout group

Agenda + Notes:

• https://docs.google.com/spreadsheets/d/106hLC5dprO9gGJBPCtASh6euXV0_wHLDgAm8SeK4hak/edit?resourcekey#gid=1810097786
• Potential cookbook topics

• Subsurface geology, if other geologists are interested.
• Packaging/repo/SE best practices resources
• Can provide support on any cookbook
• Interactive analysis, meteorological observations
• 3D data visualization and/or open-source development
• Interactive visualization; ARCO dataset analysis/visualization
• Xarray
• Foundations + jupyterlite

• Plans to form groups and facilitate interactions?

• Advance organization vs real-time project pitches on day 1?
• Don’t want 2 groups with 20 people etc.
• Set up a Discord/Slack?

• We don’t have access to a paid Slack service
• Free Slack is an option but not persistent
• Discord is free to use

• Some people don’t like it because of associations with gaming
• Probably fine in the hackathon space
• “Another app” factor – most people already using slack

• Decision: set up a Slack – it’s familiar and useful. Emphasize to participants that it is NOT persistent.

• First day content

• Max Grover just gave a cookbook orientation, can reuse this material. About 1 hour or 1:15 to dig through the whole thing
• First hour plenary:

• Overview of Pythia, current state of Cookbooks, high level goals (20 minutes) (BR)
• Schedule and expectations (20 minutes) (DC)
• Bit of a break for conversations

• 10 am: project pitches and group formation
• Afternoon tutorials

• Could be concurrent sessions?
• First 90 minutes: three choices

• Just go dive in to hacking
• Intro Python overview room
• For project leaders: discussion of logistics for the week

• Second 90 minutes:

• Tutorial on building a Cookbook

Action items

• (DC) inquire with ESDS folks about Zulip, do they really want us to use it?
• (DC + MG) set up a Slack workspace
• (BR) prepare overview talk and slides (tap other people as necessary)
• (DC) prepare “schedule and expectations” talk and slides (tap other people as necessary)

2023-06-12: Infrastructure Working Group

Zoom | password: pythia23

Facilitator: Brian Rose | Note-taker: Drew Camron

Attendees:  [Name / Institution / GitHub Username]

• Brian Rose / UAlbany / @brian-rose
• Rob Ford / UAlbany / @r-ford
• John Clyne / NCAR / @clyne
• Drew Camron / Unidata / @dcamron

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• JK:

• At an NCAR CISL event today
• CookOff Run of Show 

• will be in Main Seminar Room with Google Meets for open and close of days so people can join in companion mode
• but will be in Zoom for break out rooms because of how it handles breakout rooms better with the same link for the entire event but conference rooms cannot join en masse (on individual laptops)
• Please register so we can all have name tags (you can add your name to the excel sheet)
• We need to tell people to bring headphones and need to make sure breakout rooms are not behind security doors
• Last I checked, 20 virtual and 26 in person attendees

• KT:

• Back in office Thu. 6/15
• Book build failing for new binderhub server likely due to GitHub authorization requirement
• Previous Binderhub server fails to launch (see JK’s Zulip post from 6/8)
• Update sphinx-pythia-theme : have been looking into this, but will not be a quick fix. IMHO not necessary to fix this pre-hackathon.

• RF: cookbook contributor’s guide updated

• DOI steps? Julia Kent to-update (OWG)

Agenda (with notes from the meeting):

• Reminder: facilitator sign-up for IWG
• PRs/issues/forum in need of response (john)

• Propagating changes in cookbook templates

• Suggestions to explore

• Proposed Cookbook: Web Map Tile Services (WMTS)

• These were addressed, or will be as part of the hackathon
• Potential considerations for contributor’s guide confusion

• Proposed Cookbook: na-cortex-viz
• Cookbook gallery PR

• Pointing all cookbooks to new BinderHub at https://binder.projectpythia.org (example at https://github.com/ProjectPythia/cookbook-template/pull/116)
• High-priority infrastructure issues review: What needs doing in the next week prior to the hackathon? https://github.com/orgs/ProjectPythia/projects/3/views/14
• Untriaged issues: https://github.com/orgs/ProjectPythia/projects/3/views/6
• Infrastructure breakouts in the hackathon

• Will label good issues with hackathon label, brose@albany.edu will add new label
• Folks to address some above issues

• Q’s for hackathon:

• How will attendees communicate with organizers when need help?
• How do we ensure that unfinished work isn’t lost?

2023-06-05: Education Working Group

Zoom | password: pythia23

Facilitator: John Clyne | Note-taker: Julia Kent

Facilitation rotation sign-up and schedule

Attendees:  [Name / Institution / GitHub Username]

• Julia Kent / NCAR / @jukent
• John Clyne / NCAR @clyne
• Rob Ford / UAlbany / @r-ford
• Elena Romashkova / NCAR / @rmshkv

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• KT:

• On vacation until 6/15
• Working on conda → mamba material

• RF:

• Updates to contributing guide PR incoming

Agenda (with notes from the meeting):

• OWG report

• Julia meeting on Wednesday with the multi-media team at NCAR
• Accepted everyone who responded by first deadline, time to accept remaining registrants
• Added locations and times to agenda
• Good ratio of projects proposed to attendants

• Hackathon preparation status (organizing committee)
• Other hackathon items:

• Photographer?
• Plans for grouping people? - project pitches on Tuesday
• Agenda on website? https://projectpythia.org/pythia-cookoff-2023/schedule.html (can’t post one with meeting coordinates)
• What happens after?

• What can we do to ensure work in progress is finished, reach out again, understanding that it is open source

• Cookbook submission status

• Dask cookbook

• Data access issues - make it work with smaller data
• RF will follow up

• Other submissions?
• Do we have a cookbook shepard?

• Review project board
• Other topics?

2023-05-30: Outreach Working Group

Attendees:  [Name / Institution / GitHub Username]

• Drew Camron / Unidata / @dcamron
• Max Grover / Argonne / @mgrover
• Julia Kent / NCAR / @jukent

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• Julia sent acceptances to all registered attendees

Agenda + Notes:

• Updated the schedule with room locations
• KT listed invited people; DC to reach out
• Potential cookbook topics

• Subsurface geology, if other geologists are interested.
• Packaging/repo/SE best practices resources
• Can provide support on any cookbook
• Interactive analysis, meteorological observations
• 3D data visualization and/or open-source development
• Interactive visualization; ARCO dataset analysis/visualization
• Xarray

2023-05-22: Education Working Group

Zoom | password: pythia23

Facilitator: Drew Camron | Note-taker: brose@albany.edu

Facilitation rotation sign-up and schedule

Attendees:  [Name / Institution / GitHub Username]

• Brian Rose / UAlbany / @brian-rose
• John Clyne / NCAR / @clyne
• Rob Ford / UAlbany / @r-ford
• Julia Kent / NCAR / @jukent
• Ryan May / Unidata / @dopplershift
• Drew Camron / Unidata / @dcamron
• Max Grover / Argonne / @mgrover1

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• JK: Sciparcs starting, intern working on xarray stuff, will be joining our cookoff
• JK: will be making a video walk-through of Pythia content for Climatematch Academy
• DC: one of our interns very interesting in contributing to basic Pythia content (Foundations)
• JC: John met with EDS Book team (Alejandro and Anne) to discuss how we might collaborate. Next step: share roadmap *after* we hear about NSF GEO/OSE award.
• JC: Reschedule canceled May meeting for June. During hackathon?

• Will propose a time slot for this in latter half of hackathon week

• JC: Need to discuss NCE for pythia soon
• BR: I’m off-grid as of this Wednesday until Friday 6/9. Reach out ASAP if you’d like my input on any high-priority work
• MG: I noticed that our nightly builds do not actually push the built content to github pages - do we want to do that?'

• BR: it was built that way intentionally, but we could add the option to publish each build
• MG will open an issue on the cookbook-actions repo for this (see #62)

• MG: Created a collection of draft cookbooks for our interns at Argonne - will transfer toward end of summer when notebooks more developed (over in this organization https://github.com/EVS-ATMOS)
• RF: Issue with cookbook author permissions, on the agenda below

Agenda (with notes from the meeting):

• OWG Report
• Hackathon update

• How many registrations? 34 including Pythia members

• About half in-person

• Announced registration deadline extension until June 2
• But Hotel deadline in May 24
• More complete draft agenda https://projectpythia.org/pythia-cookoff-2023/schedule.html
• Pythia team members, please register for the Cookoff, our UCAR staff need to know who’s who
• Working on inviting specific individuals
• Collecting ideas for logistics,
• Feeling pretty good about numbers right now. Should expect the list to grow a bit more until the deadline, especially with outreach
• Time to start reaching out to group facilitators

• Cookbook submission workflow explained

• Negin Sobhani transferred ownership of a cookbook (on Dask, yay!). Now what?
• A consultant who produces a lot of tutorial content
• What happens next? Current process:

• Open a PR on gallery generator repo, there is a form to fill out with gallery tags
• This step hasn’t occurred yet for that cookbook

• Should cookbook authors have the Admin role on their cookbook repo?

• https://github.com/ProjectPythia/landsat-ml-cookbook/issues/15
• Only downside we have identified is the possibility of accidental deletion
• Policy should be to make content creators admins on the specific cookbook repo
• We should “elevate” everyone already designated as “outside collaborator” to members of the pythia org
• Let’s not use the “outside collaborator” status for Pythia

• Updates to Cookbook contributors guide

• https://github.com/ProjectPythia/.github/issues/47
• This should be high priority, pre-hackathon

• Post-hackathon summary?

• Leads could get together on Friday afternoon at end of hackathon to hack together a quick summary of successes
• Possibility of presenting this to the ESDS group the following Monday

• Pythia Binderhub and Jupyterhub up and running, with GitHub authentication!

• https://binder.projectpythia.org
• Kevin Tyle is out right now, but let’s test this out and collect questions, issues, and feedback

• Review “content” backlog - discussion

• Triage unprioritized new issues
• Assign/volunteer staff to high priority tasks
• Review status of “in progress” tasks.

• Use ‘iterations”?

2023-05-16: Outreach Working Group

Zoom | password: pythia23

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle
• Rob Ford / UAlbany / @r-ford
• Drew Camron / Unidata / @dcamron
• Brian Rose / UAlbany / @brian-rose

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• KT: Binderhub now has secure https enabled; next step is Github auth

Agenda + Notes:

• Pythia Cookoff

• List of registrants (13 virtual, 18 in person)
• Deadline extension? - June 2nd - needs announced
• Hotel booking deadline is May 24 (just note this in the deadline extension email)
• Need agenda by end of month
• Need to respond now to everyone who did register

• Names

• Deepak Cherian, Katie Dagon (NCAR)
• Anderson (Carbonplan)
• Scott Henderson (U Washington)
• Chelle G
• Johnny
• Tom (Microsoft)
• Julius and Tom Nicholas
• Rich Signell (USGS)
• Jessica (U New Hampshire)
• Max Jones
• AMS Hackathon list from Denver
• Vapor team (GPU instance on Jetstream 2)
• Marshall (previous SIparCS intern) presented on Xarray things
• Tonya Snow, Colorado School of Mines
• This year’s SIParCs interns
• EOL folks (ex. Mike Dixon, LROSE development group)
• Kim Wood (MSST), Casey Davenport (UNC), Jon Thielen (CSU)
• GeoCAT team
• UCAR EdEC (Curtis Walker)
• Brian Blaylock (HRRR / “Herbie” library)

• Hackathon agenda:

• Start time 9 am each day
• Morning plenary 9 - 10 am
• Scheduled lunch 12:30 - 1:30 pm
• Afternoon debrief 4 - 5 pm
• Asynchronous updates from groups in different time zones through a doc

• Slido or jam board or google slides

• Shortened session on Wednesday to make room for outing

• Lunch is earlier, plenary could be 1:30 - 2:30
• Outing starts 3 pm

• Do we need a facilitation ideas doc?

• Good ideas about using slides for the group check ins – both for in-person and remote groups
• Outdoor activities

• Offer either a hike behind NCAR or excursion to Pearl Street

• Carpool signup

Action Items

• Announce deadline extension [DC, discourse + twitter]

• Announce extension on conference web page [BR]
• Announce at Pangeo call [KT]

• Email current registrants with draft agenda and hotel reminder [KT will draft, send it to Taysia]

• Include website link
• Suggest following Pythia twitter
• Reminder about the hotel deadline

• Send email to the above list of potential invitees [DC] [KT will obtain contact info]
• Investigate weeknight trivia options in Boulder [JK + DC]
• Update agenda on website [BR]

2023-05-15: Infrastructure Working Group

Zoom | password: pythia23

Facilitator: Drew Camron | Note-taker: ktyle@albany.edu

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle
• Brian Rose / UAlbany / @brian-rose
• Max Grover / Argonne / @mgrover1
• Rob Ford / UAlbany / @r-ford
• Drew Camron / Unidata / @dcamron
• Orhan Eroglu / NCAR / @erogluorhan

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• KT: Binderhub update

• Working on https and GitHub authorization

• MG: Still working on troubleshooting the secrets issue
• BR: thinking about a limitation in our testing strategy re: failing notebooks that still “pass” our CI tests

• Opened in issue on jupyterbook: https://github.com/executablebooks/jupyter-book/issues/2011
• When a notebook executes and has failures not already set as “expected” failures, it should in fact, fail and we should be notified as such.
• The appropriate flag exists in myst-nb but it is not clear how to enable it in our Juptyerbook config
• DC: See Advanced Sphinx usage for a possible way to fix this

• DC: label-syncing looks to be working!

Agenda (with notes from the meeting):

• Reminder: facilitator sign-up for IWG
• Project Board

• Untriaged Infrastructure:

• 334: still waiting for response from original poster
• 319: On hold - still needs to be assigned priority/personnel

• High priority Infrastructure

• 306: Max will open a relevant issue on the Radar Cookbook; other cookbook authors (e.g. Thomas) are also welcome to create a citation with their ORCID
• 344:
• Sphinx Pythia Book Theme: DC: looks a bit more complicated than at initial glance
• 48: CMIP6 cookbook: MG suggests we remove this from the cookbook gallery until the secrets issue can be worked out. BR notes that binderbot is currently ignoring the table of contents, so the cookbook would need to be removed from the repo temporarily. MG: the functionality in Binderbot seems to support secrets, but not clear how to exploit it yet.
• 20: (Kerchunk cookbook) Data artifacts: in contributor’s guide, make it clear to cookbook authors that they should strive to use publicly-available data; if not, consider making a small snippet available. Longer term: explore if JS2 or other public large storage could be used for Cookbook datasets.  

• Infrastructure needed for cookbook-athon

• Binderhub
• MG: Get DOI generator workflow running smoothly
• MG: Ensure our existing cookbooks are working as expected and documentation is correct
• DC: Coordinate breakout volunteers; add participants to the organization so they can readily transfer ownership
• MG: what are participants proposing in terms of what they’d like to work on?
• DC: ensure that virtual participants have an easy way to participate
• BR: Health checks for cookbooks need to be finding “unhealthy” cookbooks

2023-05-08: Education Working Group

Zoom | password: pythia23

Facilitator: ktyle@albany.edu | Note-taker: brose@albany.edu

Facilitation rotation sign-up and schedule

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle
• Julia Kent / NCAR / @jukent
• Rob Ford / UAlbany / @r-ford
• Brian Rose / UAlbany / @brian-rose

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• DC: reminder to sign up for IWG facilitation rotation
• DC: will shortly have a markdown tutorial for Foundations ready
• BR: gave a talk and demo to the ESDS book community connected with the Climate Informatics Reproducibility Challenge, notes here:

• https://pad.sfconservancy.org/p/ci2023-repro-challenge-talk-8may-brian
• Built a new Cookbook in real time!

• JK: Need everyone’s ORCID, what to do for people who’s we’re missing?

• Still missing Kevin Paul, will wait a few more days before merging the citation document

• KT:

• Jetstream2 instance setup is ongoing. Almost ready to fire up the BinderHub.

• Still working on secure https.
• Should get a certificate issued on projectpythia.org
• KT and JK might talk offline about this.
• Can still use a jetstream.cloud.org domain if we can’t make it work

• New intensive cookbook from @bonnland (Brian Bonnlander?) will serve as a good test case for dask-intensive workflows.

Agenda (with notes from the meeting):

• OWG Report

• Reg deadline for hackathon is this Friday May 12.
• Currently have around 20 people signed up, including some from beyond immediate Pythia people, and including some overseas people (remote).
• At least 3 people here at uAlbany planning to participate.
• Hackathon: would be great to do a walkthrough of Cookbook construction on day 1, a more relaxed version of the demo that Brian gave today
• We will most likely extend the deadline for registration
• Next week we will hash out the hackathon agenda in more detail.

• Untriaged Issues

• Pyart-gridding notebook: assigned to MG
• xbatcher-ML-1-cookbook: some broken code
• Should we have a “cookbook maintenance” repo tag to identify broken cookbooks that need attention?
• Using mamba – high priority - KT assigning himself

• High Priority Issues 

• defer any Infrastructure issues to next week; tag any non-Content issues that are actually Content-related
• Discussed a number

• Medium Priority issues

• Same tag-related comment as in High Priority

• Pre-hackathon needs that are content-related:

• THere’s a number of broken notebooks currently in our Cookbooks
• BR will open an issue to catalog these
• Our build system shouldn’t be pushing broken notebooks to the published gallery
• Improvements to the Cookbook guide?

• Team members should walk through the Cookbook creation process and get as familiar as possible.
• Identify potential simplifications to the guide.
• What’s the path of least resistance to creating a working Cookbook?

2023-05-02: Outreach Working Group

Meeting link: Zoom | password: pythia23

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle
• Julia Kent / NCAR / @jukent
• Taysia Peterson

Quick Updates:

• Please sign in on this page above (and add any quick updates)

Agenda + Notes:

• Pythia Cookoff

• Registration form
• 14 people have registered so far (mostly NCAR)
• Taysia will do some math on how many people our breakout rooms can support
• Drafting up an acceptance email - notify the 15th
• Those who have registered receive an auto-acknowledgment
• Taysia’s questions: need answers by end of May

• How many teams will there be, so breakout rooms can be planned
• Need to inform the NCAR multimedia team the detailed agenda for each day.

• Twitter - KT

2023-05-01: Infrastructure Working Group

Zoom | password: pythia23

Facilitator: ktyle@albany.edu | Note-taker:

Facilitation rotation sign-up and schedule

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle
• Julia Kent / NCAR / @jukent
• Rob Ford / UAlbany / @r-ford
• Drew Camron / Unidata / @dcamron
• Brian Rose / UAlbany / @brian-rose

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• BR and JC plowed through a lot of issue triage. Take a look at the Project Board, especially at things labeled “medium”: https://github.com/orgs/ProjectPythia/projects/3/views/13 to see if anything really needs to be elevated
• JK will be investigating infrastructure surrounding DOI/citation

• Copy editing has been completed on foundations with the work of JK and L

• DC will add some material on Markdown, motivated by upcoming Unidata Users Workshop

• Additional exploration with EDS/ROHub workflows before we chat with them again

Agenda (with notes from the meeting):

• Facilitator / note-taker schedule for upcoming IWG meetings

• Default: previous facilitator will be next meeting’s note-taker

• Jetstream2 update

• VM has been set up (IP 149.165.152.50); next step is to build and deploy Binderhub 
• DNS Registration needs to be set up for binder.projectpythia.org and hub.projectpythia.org [JK + KT]

• Mybinder.org capacity reduction
• Untriaged infrastructure issues

• Labels in user support: consider avoiding “low priority” until work timeline lines up with that description for community issue submission
• Will add “needs more information” label once label syncing is ironed out (BR)

• High priority infrastructure issues

• Cookbook-actions testing: in-progress as exploration and testing, not currently requesting outside support
• DOI/citations: project/foundations citation in zenodo with DOI, requires addressing #344 re addressing foundations releases

• brose@albany.eduRyan May noted as zenodo+software experience and will support JK as that progresses
• Next steps include workflow automation for cookbooks

• Label syncing: this has become more relevant; still lower priority than above

• Shortest path: provide PAT
• Adjacent to cookbook-actions testing, DC/BR will explore new optional action for users

• Theme: dependency issues and release-ability

• Will require someone taking on the knowledge background on the theme

• Data in cookbooks:

• Pythia-datasets still just for foundations
• Other considerations (ACCESS credits, git LFS?) for intermediate data or necessary accessible data

• Other issues deprioritized, combined, or re-worded as appropriate

Action Items:

• Sign up for 5/15, 6/12, 6/26 IWG slots

2023-04-24: Education Working Group

Zoom | password: pythia23

Facilitator: brose@albany.edu | Note-taker: rford2@albany.edu

Facilitation rotation sign-up and schedule

Attendees:  [Name / Institution / GitHub Username]

• Brian Rose/ UAlbany / @brian-rose
• Rob Ford / UAlbany / @r-ford
• John Clyne / NCAR / @clyne
• Max Grover / Argonne / @mgrover1
• Julia Kent / NCAR / @jukent
• Kevin Tyle / UAlbany / @ktyle

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• JC: John submitted abstract to NSF EarthCube Geoscience and Cyberinfrastructure workshop 
• KT:

• UAlbany senior undergrad Michael Barletta will be presenting the Pangeo Showcase this Wednesday (4PM EDT/2PM MDT)
• Used and adapted Py-ART cookbook material in the last few class meetings of my co-taught Python class (see, e.g. https://www.atmos.albany.edu/facstaff/ktyle/atm350/core/week12/radar_AWS.html) 

• MG:

• Submitting a cookbook-related abstract to the AMS radar meeting

• JK:
• BR: said yes to an invitation from the EDS book folks to talk about Pythia at the Climate Informatics Reproducibility Challenge, https://eds-book.github.io/reproducibility-challenge-2023/intro.html. Details to come.

Agenda (with notes from the meeting):

• OWG Report

• Hackathon planning update

• Application live, posted on Pangeo Discourse
• Should keep track of number of participants
• All active Project Pythia members should register
• Planning team should meet soon (likely at next Tuesday’s OWG)

• Meeting with EDS Book team

• Clarifying goals/differences between cookbooks and EDS book
• Likely to set up another meeting for further discussion
• JC meeting in person soon
• Publishable original work vs. example workflows?
• MG: EDS uses hvplot, which we don’t have material on. We could collaborate to add hvplot content to Pythia
• JC: reference each other’s work, but note differences

• Product backlog for “content” issues?
• Triage of backlogged content issues https://github.com/orgs/ProjectPythia/projects/3/views/12

• GitHub releases for Foundations. Also Radar Cookbook
• Content on creating a good Python package

• JK: Maybe some work will be done on this at the Cook-off
• MG: related to pyOpenSci efforts

• Interactive plotting would be a good addition to Foundations, since multiple cookbooks may reference it.
• Markdown content PR needs a few small changes and reviews

2023-04-18: Outreach Working Group

Meeting link: Zoom | password: pythia23

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle
• Drew Camron / Unidata / @dcamron
• Brian Rose / UAlbany / @brian-rose
• Julia Kent / NCLAR / @jukent
• John Clyne / NCAR /@clyne
• Anne Fouilloux / Simula Research Laboratory / @annefou
• Alejandro Coca-Castro / The Alan Turing Institute / @acocac

Quick Updates:

• Please sign in on this page above (and add any quick updates)

Agenda + Notes:

• EDS / Pythia discussion

• EDS is a bit further along in terms of their ability to efficiently mint DOIs for their content
• Let’s focus on the overlap and differences between our two entities:

• EDS focus more on producing publishable objects. Uses RoHub (see docs here).

• Example: Sea ice forecasting using IceNet. In that notebook, it has a DOI, links to launch Binder, and a RoHub link.
• In RoHub, versions of the research object can be forked / snapshotted; they serve an analogous purpose to forks/commits/versions in GitHub

• EDS uses citation as an education tool for responsible science
• Pythia more on targeted use-cases, repeatable workflows (Cookbooks)
• Pythia focuses on the basics … get people familiar with the Pangeo Python ecosystem
• EDS: focuses on best practices how to write publishable, reproducible notebooks. Emphasize on common metadata standards in these notebooks. Represents an evolution in the traditional peer-reviewed paper paradigm.
• Pythia cookbooks: more tightly-focused than Foundations … want to build infrastructure to make it easy and attractive for those who want to share their workflows using datasets / methods of interest to them … and having a common repository to house them (rather than having various useful notebooks randomly scattered across the internet).
• Pythia cookbook philosophy: build it and they will come. Make it an attractive way for the community to share useful workflows. We’re at the proof of concept phase … need to get the community entrained.
• The best example of what Pythia envisions to be an effective cookbook is the Radar cookbook. It follows a two-part model:1)  background information about the question at hand (what is radar data? Where can I find it?), and 2) specific use-case examples (e.g. load a NEXRAD archive from cloud storage and create some interesting visualizations from it)
• There’s nothing stopping a cookbook author from having their cookbook be a published, refereed product … although at this point that isn’t what we envision to be the main motivation for someone to build and share a cookbook. But we do want them to have a citable reference!

• From EDS’ perspective:

• Notebooks as citable research objects, usable metadata
• Pythia has good infrastructure in terms of automated workflows, integrated with GH actions; integration with cloud binder/hubs
• Review process and community
• Outreach and hackathon

• Potential collaborative opportunities:

• Take the radar cookbook and integrate into an EDS-like gallery object
• Leverage MystNB to cross-reference notebooks
• Anne & Alejandro: Explore Pythia Cookbooks process

2023-04-17: Infrastructure Working Group

Meeting link: Zoom | password: pythia23

Attendees:  [Name / Institution / GitHub Username]

• Brian Rose / UAlbany / @brian-rose
• John Clyne / NCAR / @clyne
• Drew Camron / Unidata / @dcamron
• Julia Kent / NCAR / @jukent
• Rob Ford / UAlbany / @r-ford

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• KT

• Will be setting up our new JS2 allocation this week
• SciPy talk approved! Will coordinate presentation plan with Drew.

• JC:

• AGU Notebooks Now!: The goal of AGU’s Notebooks Now! Effort is to “Elevate Computational Notebooks as Primary Elements of the Scientific Record”. Exploring many of the same issues we’re facing with cookbooks. Information on joining Notebooks Now working groups available here.
• Anne Fouilloux and Alejandro Coca-Castro will join the OWG tomorrow (Tuesday) to discuss the Environmental Data Sciences Book project
• CISL event planning resources here and here

Agenda + Notes:

• From previous meeting: Devote time at each IWG to review open issues/PRs, e.g.:

•  triage un-triaged new issues
• Assign staff to high priority items
• Check progress for active items

• Current/untriaged new issues/PRs:

• Issue 329 (Portal site not publishing/previewing in GH pages)

• PR 331 resolves the publishing issue
• PRs 330, 332 are attempting to resolve the previewing issue

2023-04-10: Education Working Group

Zoom | password: pythia23

Facilitator: rford2@albany.edu | Note-taker: Julia Kent

Facilitation rotation sign-up and schedule

Attendees:  [Name / Institution / GitHub Username]

• Julia Kent / NCAR / @jukent
• Rob Ford / UAlbany / @r-ford
• John Clyne / NCAR / @clyne
• Max Grover / Argonne National Lab / @mgrover1
• Kevin Tyle / UAlbany / @ktyle
• Drew Camron / Unidata / @dcamron

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• JC: NCAR is deploying an on-prem, prototype cloud. This is a pilot project, whose goals include exploring feasibility of a production deployment. John would like to include support for Pythia’s cloud needs as a use case.

• JK user/client to help come up with specs for this
• Pilot project but if it is deployed we may want to use it instead of jetstream
• KT - any integration with research data archive, besides thread service? Great way to have datasets in object store Zarr format. JC- Yes we want to provide some python APIs to NCAR data holdings. Looking for use cases to drive these services. Look KT into convo.
• MG - Radar cookbook has RDA huge gridded dataset that would serve as a good dataset to show capability

• KT: Who manages our projectpythia.org domain? We will need to register a binder.projectpythia.org DNS entry soon.

• Need to set up Cname record to point to jetstream service - JK manages this, ready in next couple weeks

• BR: absent from today’s meeting. The meeting form looks good to me!

• Hackathon sign up form from Taysia Peterson.
• RF - last question about leading a break out session, is plan to collect people into groups
• Self select into 2-4 to work on cookbooks, question encourages people to bring ideas
• We should submit too
• https://docs.google.com/forms/d/1uaWZrOPFvtREofduAoSlIF3tNdQ_TlqXUfwSZbJOiXs/edit 

• MG: Went through and created a list of Pangeo gallery authors, serving as a potential list of people to explicitly invite

• We should expand this list…

• Deepak Cherian, Katie Dagon (NCAR)
• Anderson (Carbonplan)
• Scott Henderson (U Washington)
• Chelle G
• Johnny
• Tom (Microsoft)
• Julius and Tom Nicholas
• Rich Signell (USDS)
• Jessica (U New Hampshire)
• Max Jones
• AMS Hackathon list from Denver
• Vapor team (GPU instance on Jetstream 2)
• Marshall (previous SIparCS intern) presented on Xarray things
• Tonya Snow, Colorado School of Mines
• This year’s SIParCs interns
• EOL folks (ex. Mike Dixon, LROSE development group)
• Kim Wood (MSST), Casey Davenport (UNC), Jon Thielen (CSU)
• GeoCAT team
• UCAR EdEC (Curtis Walker)
• Brian Blaylock (HRRR / “Herbie” library)

Agenda (with notes from the meeting):

• OWG Report

• Identifying folks to explicitly invite to participate in the hackathon

• See the OWG notes (mainly pangeo-gallery related folks)

• Finalize hackathon signup form

• Link to form

• JC - we should reach out to James Munroe about coffee breaks through 2i2c
• Working on linking to cook off page - PR
• Uncertain on how many people will be there. Invite James to next meeting
• 20 hotel room block, 100 capacity of seminar room, ideal capacity? Over 50 is too much. What is a good group size? When should registration cut off be?
• Add info to form, pick a date that we have to tell them by. Friday May 12th tell them. May delay by a week at deadline time, Change from June 12th on form. Hotel block deal available until May 24. Know in advance if we have to down-select. Maybe notify first X as soon as possible. If it looks like we’re getting too many applicants, slow down the confirmation process (more competitive at the end).
• Check current number of applicants at every meeting. Hard deadline, but rolling review process.
• Mix of in-person vs virtual. Use UCAR zoom for remote participation. Limitations on participation over Zoom? No
• If too many applicants, what is the process of deciding who can come and who doesn’t? First come first serve or based on statements of interest. (include a statement that completing the form doesn’t guarantee acceptance and you’ll be notified by such and such date if they don’t meet criteria, make it clear that interest statement can be used to make this discussion).
• PR for adding sign up form

• Environmental Data Science (EDS) book project (John & Brian, 5 mins)

• Pythia has a lot of overlap with the European EDS Book project. See slides, and accompanying Pangeo Showcase talk (once posted) 
• Anne Fouilloux, one of the principals, has expressed interest in possibly working with us. Wants to make our resources more FAIR
• Next steps?
• BR: I had previously invited Anne to a Pythia meeting, there were problems joining the Zoom (https://discourse.pangeo.io/t/making-cookbooks-citable-best-practices/3170/10)
• Encourage everyone on the team to look at slides linked above, great presentation. Talk from the Pangeo showcase will be posted on Zenodo. Worth hearing entire presentation and thinking about overlap and thoughts on how to collaborate
• Review process is fairly robust, more detailed conversation will be great.
• Meet during OWG time? Tuesdays at 9 MT?

• KT- foundations or cookbook effort? Thread on twitter for plotting data with metpy on maps. Want to identify gaps in plotting instructions. We only have one cartopy notebook. Good cookbook candidate? Flesh out intro to cartopy chapters. Haven’t added much new foundations content in a bit, good opportunity to revise and add content. Add snippet to gallery of how-tos. Need to identify the underlying missed need.

• Create an Issue on Foundations to propose extending the Cartopy content
• Invite people to hack on open foundations issues as well as Cookbooks? Current way the form is written doesn’t call out leading a cookbook on X, form focused on “breakout” section

2023-04-04: Outreach Working Group

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle
• Drew Camron / Unidata / @dcamron
• Brian Rose / UAlbany / @brian-rose
• Max Grover / Argonne National Lab / @mgrover1
• James Munroe / 2i2c / @jmunroe
• John Clyne / NCAR / @clyne

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• MG: applications are out for Climate Match Academy (Abigail Bodner is leading the effort). Signup sheet is live now

• JK is helping out with that
• MG is retweeting their links

• MG: retweeted Radar Cookbook

Agenda (with notes from the meeting):

• Hackathon Planning

• https://discourse.pangeo.io/t/save-the-date-project-pythia-summer-hackathon/3241/4
• https://github.com/ProjectPythia/pythia-cookoff-2023
• https://docs.google.com/forms/d/e/1FAIpQLSdRAe9BQqWXTfHEtubpcBAo_SxdMO2BwQr9XIDkpVPaC0oCvw/viewform?usp=sharing
• Follow up to those who have filled out the form and engage in further conversation about their goals?
• JM:

• Ideas:
• 1. Can the registration form include (or at least link to) a description of the objectives of the hackathon?
• 2. Can you be open and public with those you have already registered?

• 3. Are there targeted individuals that are going to be invited to the hackathon?

• K. Goebbert / Valpo
• EDS Book team +1
• Identify authors on various Pangeo gallery notebooks
• Py OpenSci folks
• CryoCloud (Tasha Snow, Jessica Scheick - icepyx).

• 4. Need to aim for a blend of senior / “keynotey” people, along with newbies. These folks could lead a daily keynote/kickoff session. Don’t want it to consist of mostly/all newbies.

• Action items:

• Update registration form, including:

• Opt-in for having their name visible:
• Demographic details: Drew will liaise with NCAR folks (John/Julia)
• Open-ended question asking why they are attending (what area do you work on? What are you interested in working on? Do you have a link to a GH repo … paper/presentation?)
• If registration does not automatically lead to acceptance, then the form might need to say “registrations need to be approved by the organizing committee” or something to that effect. Their answer to the open-ended question will inform their approval. This should be a low bar, but needs to exist and be defined.
• Deadline for form submission: Friday May 12. Critical for motivating those who will defer until the deadline date and also for informing us on how many may attend
• Publicize on social media / email channels

• Identify / invite the targeted individuals

• NCAR Gallery - Brian Bonnlander (NCAR), Anderson Banihirwe (Carbon Plan)
• CESM LENS - Scott Henderson (Univ. Washington)
• NASA CCMP - Chelle Gentemann (NASA)
• Cloud benchmarks - Ryan Abernathy (Earthmover)
• Glaciology - Jonny Kingslake (LDEO)
• Landsat 8 - Tom Augspurger (Microsoft)
• CMIP6 - Julius Busecke (LDEO), Tom Nicholas (LDEO)
• Pangeo tutorial - Rich Signell (USGS)
• Icesat cookbook - Jessica Scheick (Univ. of New Hampshire)

2023-04-03: Infrastructure Working Group

Meeting link:

• Meeting link: https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle
• Brian Rose / UAlbany / @brian-rose
• John Clyne / NCAR / @clyne
• Rob Ford / UAlbany / @r-ford
• Drew Camron / Unidata / @dcamron
• Orhan Eroglu / NCAR / @erogluorhan

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• JK - Will change to UCAR Zoom link with password “pythia23” next week? YES!
• JC: NSF hosting Building upon the EarthCube community summer event, June 27 - 28, Los Angeles. There is funding available for early-career scientist
• JC: John, Brian, and Julia had a very informative meeting with Kieth Maull and Mathew Mayernik on citing cookbooks. See Julia’s excellent notes
• JC: NCAR’s Doug Schuster is working with AGU’s Notebooks Now working group, which are exploring the requirements needed to support publication of executable notebooks as journal articles. John will follow up with Doug.
• KT: Jetstream2 allocation was approved, but is still not accessible. I have emailed JS2 support for a status update.

• RF: Will this new Binderhub resolve the issues we have on the cookbooks that require more substantial resources? THAT IS THE GOAL

• BR: Plans to open an issue regarding better documentation of how we automatically preview PRs (other folks outside Pythia, e.g. Julius Busecke, would like to use it)

Agenda + Notes:

• Summary of Citing Pythia Cookbooks discussion with NCAR librarians Mathew Mayernik and Keith Maull (full notes):

• Open to change -  DOIs in the journal context are assigned to things that don’t change, but outside of that there are DOIs to things that do change (datasets that are continuously growing, or minor or bug fixes in software packages, etc)
• What to cite - The GitHub repository seems the most stable (if the site went down for any reason)
• Authorship vs contributors - We want to encourage primary scientific contribution and overall maintenance contribution. We’ll have a changing contributor base over time. Zenodoc has lots of “contributors” options but they don’t appear in citation. Open inclusive authorship policy.
• Versioning - make sure time stamps and accessibility of older versions. How big of a change warrants a new version (not minor maintenance fixes, but significant changes to dataset, the science, or how to use a dependent package). This opens the door to the user citing the wrong version.
• Releases - doesn’t sound like we need a regular release schedule. But what can we automate/simplify of the release process? Put machinery in place to handle creation of DOI, release, archiving of code, etc in a formal process to reduce the number of hoops.
• Zenodoc vs UCAR to create DOIs - Zenodo will meet our needs, will archive a Zip file of the GitHub repository at each snapshot/version we save. Potential issue is that we store unexecuted notebooks, they are populated at run time in the name of reproducibility. So if it isn’t runnable anymore that output is lost?

• BR - I think we could set up a “release” pipeline that would commit executed notebooks (at the end of our book-build workflow) to a dedicated branch of the repo and include those in the archived snapshot identified with a DOI.

• Add a “how to cite” section to each resource. If it isn’t prominent, readers will make up their own citation method and the DOI won’t be used. Also add the DOI to README files and to gallery cards.
• DC: What would administration of issuing DOIs look like? Would we need to have a group of folks who would have DOI-minting privileges on Zenodo? Both Ryan May and Brian Rose have existing DOI-minting privs from MetPy/Climlab.
• Matt M and Keith M have a workflow for DOI minting; JC has folks on his team as well who have the expertise. John will post a pointer to step-by-step guide.

• See here and here

• New “releases” → New DOI. Previous versions’ DOIs point to an archive on Zenodo.

• Status of outstanding issues/PRs:

• Project Board

• Sort by tags. Let’s at least get the high priority items assessed!
• OE:

• The project board does not “automatically” pick up new issues. The issue originator must do so. Similarly, we can’t easily search for issues that are not on the project board … however, as long as you are not sorting “By-repo”, you can click on Add Item, add a hash tag, and then you can see repository issues and add them to the project board.
• Our practice at this point is to just include Issues. We can link to the PR, but do not include a PR as its own project item (i.e. row)
• Orhan created and saved a new view with the High Priority tag.
• BR: can one also view unlabeled issues, since that is part of the weekly triaging? Alternatively, can one view newly-created issues?
• KT: is there a way to configure GitHub so any new Issue automatically gets an appropriate (e.g. “Unassigned” or “New”) tag assigned?
• Multiple label search: e.g. -label:"high priority" -label:"medium priority" -label:"low priority" shows what items are NOT assigned
• Going forward: We need to devote ~5 minutes each week to new issues that have come up.

• Does it make sense to create a new weekly/biweekly iteration that would hold these new issues?

• BR: Are merged issues automatically marked with a status of “Done” by GH? OE: Not sure
• JC: Perhaps a good way to wrap this up is to figure out what we want to do for a standing process starting at the next IWG meeting? For example, triage un-triaged new issues, making sure staff are assigned to high priority items, checking on progress for active items, etc.

• What is the best guidance on how to review PRs submitted by bots?

2023-03-27: Education Working Group

https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09

Facilitator: Julia Kent | Note-taker: Drew Camron

Facilitation rotation sign-up and schedule

Attendees:

• Julia Kent / NCAR / @jukent
• John Clyne / NCAR / @clyne
• Brian Rose / UAlbany / @brian-rose
• Rob Ford / UAlbany / @r-ford
• Drew Camron / Unidata / @dcamron
• Kevin Tyle  / UAlbany / @ktyle
• Ryan May / Unidata / @dopplershift

Quick Updates:

• Please sign in on this page above (and add any quick updates here)

• JC: NSF/GEO does not have funds to support summer hackathon at this time. Possibly have funds sometime in June. We can check back then.
• JC: Meeting scheduled with Mathew Mayernik (NCAR librarian / project scientist for Thursday to discuss citing cookbooks.
• BR + KT: taking the first steps to setting up a “new and improved” Pythia Binder on Jetstream2 using our dedicated ACCESS allocation
• MG: Environmental data science folks holding a “reproducibility challenge”

• See the thread here
•  Challenge Registration Closes: 22 April
•  Teams & Projects Announced: 30 April
•  Challenge Begins: 1 May
•  Peer Review Begins: 15 May
•  Challenge Ends: 31 May
•  Results Announced: 15 June
•  Published in @eds_book: Summer

Agenda (with notes from the meeting):

• Pythia Cook-Off website is up here: https://projectpythia.org/pythia-cookoff-2023/

• (site actually uses Cookbook infrastructure – see https://github.com/ProjectPythia/pythia-cookoff-2023)
• Site needs work - target by end of next OWG

• Revision of Foundations etc to encourage use of mamba? https://discourse.pangeo.io/t/mamba-mature-enough/3154/9
• Revert to UCAR Zoom account for Pythia meetings, with a simpler password? (e.g. “Pythia”)

• Restrictions on UAlbany Zoom have been problematic at times
• Alternatively, clarify the instructions on our portal: https://github.com/orgs/ProjectPythia/projects/3/views/1?pane=issue&itemId=24059210

• ProjectPythiaTutorials content, gallery, landing page, and organization

• Current landing page is empty
• Should we construct a gallery?

• In general, no. To support “first party” recurring Pythia tutorials, possibly yes

• Support paid content in resource gallery

• Should consider our stance here, currently have not had to support this explicitly

2023-03-21: Outreach Working Group

Meeting link:

• Meeting link: https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09

Attendees:  [Name / Institution / GitHub Username]

• Brian Rose / UAlbany / brian-rose
• Max Grover / Argonne National Lab / @mgrover1
•  Julia Kent

Agenda (with notes from the meeting):

• Hackathon planning!

• Link to registration form
• Rooms and hotel block - done
• NSF funding request (no word) - done
• Pangeo discourse save the date - done
• Workshop description we sent to NSF: https://docs.google.com/document/d/1wQOVOnH0cny1SjqkCyjjm7vko15oDi3Qgp_cCIGjcFI/edit
• Plans for remote participation

• Two times a day checkins, planning to cluster people into groups for group projects

• Add page to Pangeo site for reference - use Cookbook template, own github repo that can be edited with project pitches

• Title
• Dates
• Description
• Prelim agenda
• Hotel information
• Plans for remote participation

• Suitable equipment enabled to support hybrid meetings
• 2 synchronous check-ins per day

• What experience to come with? What spin up tutorials are planned?

• Bring science content and put in self=publishing self-maintaining content, doesn’t know infrastructure, improve workflow to use better parallel computing and Pangeo-stack tools
• Assume know Python and Jupyter notebooks, might not be 100% on GitHub
• Go through Cookbook development workflow, adding notebook to repo with workflow, troubleshoot development process, leverage foundations for self-study leading up to event.
• Brief intro to Pythia -> what are Cookbooks
• Smaller break out room for GitHub or Pangeo questions
• Try to blend groups, someone to usher the group through Github issues

2023-03-20: Infrastructure Working Group

Meeting link:

• Meeting link: https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09

Attendees:  [Name / Institution / GitHub Username]

• John Clyne / NCAR / @clyne
• Drew Camron / Unidata / @dcamron
• Ryan May / Unidata / @dopplershift
• Rob Ford / UAlbany / @r-ford
• Julia Kent / NCAR / @jukent
• Max Grover / Argonne National Lab / @mgrover1
• Brian Rose / UAlbany / @brian-rose

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• JC: NSF OSE GEO proposal submitted. Thanks to all who contributed!
• JC: Possibly submitting an unsolicited proposal to NSF to support summer hackathon.
• MG: Went through and made more changes to the hackathon registration form

• https://docs.google.com/forms/d/1IVo1cCqVU_88SPIO9UqBktLZsxbwzBsZBJ-CfdHs1HY/edit

Agenda + Notes:

• Data access

• Xbatcher cookbook data access: https://github.com/ProjectPythia/xbatcher-ML-1-cookbook/issues/5
• Update Contributor’s Guide (RF, MG)
• https://data.ucar.edu/

Action

• Set up meeting with Matthew Mayernik. Who are the attendees?

2023-03-13: Education Working Group

https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09

Facilitator: Drew Camron | Note-taker: ktyle@albany.edu

Facilitation rotation sign-up and schedule

Attendees:

• Julia Kent / NCAR / @jukent
• Max Grover / Argonne National Lab / @mgrover1
• Drew Camron / Unidata / @dcamron
• Tyler Erickson / free-range / @tylere
• Rob Ford / UAlbany / @r-ford
• Kevin Tyle / UAlbany / @ktyle
• Ryan May / Unidata / @dopplershift

Quick Updates:

• Please sign in on this page above (and add any quick updates here)

• DC: Three new cookbooks “published” to the gallery!

• Regridding
• Kerchunk
• Xbatcher + ML

• BR: still out today but Pythia GEO OSE proposal was submitted to NSF today!
• KT: working with senior undergrad on Holoviz-related apps; he will present on Pangeo showcase on 4/26
• RF: Cookbook contributor guide updated
• MG: Drafting form for summer hackathon registration

• Topic suggestions
• Other part of form is dependent on whether NSF provides travel funds

• TE: still learning about Pangeo and its related projects

Agenda (with notes from the meeting):

• OWG Report

• *check about pangeo showcase
• Save the date on Pangeo discourse

• RF: xbatcher cookbook: not building/rendering output yet but it’s published … what can we do to get some output from it? (see https://projectpythia.org/xbatcher-ML-1-cookbook/notebooks/surface_currents.html)

• Action item: KT, DC, RF will look into it

• MG: We still have some Pangeo notebooks to fold into Cookbooks … can we encourage the original authors to participate in the summer Hackathon?

• Action item for next OWG

• KT: longer term … just watching advances in the foundational ecosystem such as Pandas’ upcoming 2.0 release, which leverages Apache Arrow
• MG: good opportunity to add some material for our data format foundational content that is Pandas-specific … such as working with tabular/columnar data CSV, Parquet, Apache Arrow
• DC: working with MetPy development folks on updating the MetPy tutorial and integrate into a Cookbook

2023-03-07: Outreach Working Group

Meeting link:

• Meeting link: https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany/ @ktyle
• Julia Kent / NCAR / @jukent
• Drew Camron / Unidata / @dcamron
• Max Grover / Argonne / @mgrover1  

Agenda (with notes from the meeting):

• SciPy draft submitted
• June 20-23 Hackathon planning

• https://docs.google.com/document/d/1wQOVOnH0cny1SjqkCyjjm7vko15oDi3Qgp_cCIGjcFI/edit
• Should we hold off on major outreach until we hear about funding?

• Identify local institutions who may be able to attend (e.g. MSC, CU Boulder, CSU, NOAA, etc.)
• Tweet out a save the date

• OWG project management tools

• A shared Google calendar is up and running

• Twitter duties: Drew up for one more week
• Comb through the external resource gallery each month: add new resources and maintain existing ones

2023-03-06: Infrastructure Working Group

Meeting link:

• Meeting link: https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle
• Julia Kent / NCAR / @jukent
• Ryan May / Unidata / @dopplershift
• Rob Ford / UAlbany / @r-ford
• Drew Camron / Unidata / @dcamron
• Orhan Eroglu        / NCAR / @erogluorhan
• Tyler Erickson / / @tylere

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• Volunteer for notetaking?
• NSF GEO-OSE proposal status: text finished, now in hands of the various partners’ research proposal support staff
• SciPy 2023: Talk proposal submitted 3/1
• Julia K: Lily K. is working on the edits for the Foundation notebooks / content
• Rob: working with Drew on new cookbook
• Drew: has resolved token authentication issue with cookbooks, will document the workflow and discuss at an upcoming meeting

Agenda (with notes from the meeting):

• Pythia Project Board
• Cookbook transfer process: discuss here or in next week’s EWG?

• Consensus is to have contributors be on an equal footing in terms of their GitHub memberships (i.e., don’t have them be “relegated” to Outside Contributor status)
• Similar model followed by Matplotlib

• EWG Facilitator sign-up
• Tyler Erickson (recently left Google; involved with Google Earth Engine): more familiar with nbdev (which is based on Quarto) … curious about how it differs from Jupyterbook

• Jupyterbook is an easy “next step” for folks who have taken the leap into presenting their research/lectures/etc via a Jupyter notebook. It would be a an additional step for learning a new workflow that uses nbdev/quarto
• Also curious if we are looking into in-browser (e.g. Jupyterlite) as a platform/sandbox

• One issue is how much of a load it is … especially dataset-wise
• At this point, does not integrate with a Dask cluster

Items from previous IWG meeting:

• Align CI workflow across all of Project Pythia

• cookbook-gallery still missing some of these pieces, including link-check
• cookbook-actions is itself un-tested and has little CI checking on updates and enhancements

• Drew working on this

• DEFER to future meeting: To mamba or not to mamba, that is the question

• Use mambaforge as the basis for environments, or:
• Use conda, but with built-in libmamba
• See Discourse discussion here.
• (This might be considered an educational content question, so we could take it at the next EWG)

• DEFER to future meeting: Ruff: highly performant linter

• Several projects (e.g. Xarray) adopting Ruff

2023-02-27: Education Working Group

https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09

Facilitator: Ryan May | Note-taker: Kevin Tyle

Facilitation schedule

Attendees:

• Ryan May / Unidata / @dopplershift
• Kevin Tyle / UAlbany / @ktyle
• Rob Ford / UAlbany / @r-ford
• Max Grover / Argonne / @mgrover1
• Brian Rose / UAlbany / @brian-rose
• Rich Signell / USGS / @rsignell-usgs

Quick Updates:

• Please sign in on this page above (and add any quick updates here)

• Julia Kent – can’t make today due to SIParCS interviews. Summer event update from Taysia:

• Booked the Damon and Chapman rooms Tuesday-Friday the entire day (except Wednesday 12pm-1:15pm the Chapman Room)
• Booked ML680 after 10am on Tuesday, all day except 2-3pm Wednesday, and all day Thursday/Friday.
• Do we want additional space in the library?

• Heavily dependent on whether NSF funds a portion of the event.

• Requesting a 20-room hotel block June 19-24th

• Kevin

• Nothing!

• Max: reverting radar cookbook update until Binderbot authentication can be worked out
• Brian: racing to NSF proposal deadline for follow-on to Project Pythia! Including folks from UAlbany, NCAR, Unidata, 2i2c, USGS
• Ryan: working on NSF proposal above
• Rob: cookbook maintenance
• Julien: Pythia and cookbooks being discussed with his group (Paleocube) . What makes up an effective notebook?

• Brian: Our notebooks articulate how long it would take a “typical” user to work though the notebook. We haven’t as yet received feedback that a specific notebook’s time estimate needs revision.

• Rich: Interesting learning links from ESIP meeting today. There could be a good opportunity for Pythia to organize a meetup of “Pangeo educators” to discuss how folks are doing things.
• Dedicated EWG meeting, which could then lead to:

• Townhall @ AGU/AMS?
• SciPy BoF

• This could also help establish a steering board should “Pythia-Next” be funded

Agenda (with notes from the meeting):

• OWG Report

• SciPy proposal - submitting to the tending the garden session (scroll down to see this session’s details)
• Hackathon planning

• SciPy abstract due Wednesday

• Kevin / Drew working on it

• Volunteer to present at Pangeo Showcase in March or April

• Brian presenting for ESDS group at NCAR this week - will submit the above-linked form expressing interest

• Hackathon update and planning

• Submitted 2 page document to NSF program officer contact (early last week)

• Waiting to hear

• Further discussion with Julien: in terms of developing notebooks, what should we be focusing on?

• How to use the “technology”, e.g. xarray

• B. Rose: Foundations and Cookbooks focus on this, but in a scientific use-case perspective

• How to practice and present good science (e.g. EOF analysis)
• Ryan: Up to the notebook author! Could certainly include (2) as part of (1)
• Julien: But it’s up to the audience as well.
• Brian: up to this point, much of the community’s involvement has been motivated by how to use the “techonology”. An author would want to have made the conscious choice to post their work in the form of an executable notebook, not just in a PDF/journal.
• Max: Radar cookbook has started with tools, but now adding content talking about wx radar science itself. Incorporating content delivered in the recent AMS Short Course on radar.

• Dual pol variables
• Gridding radar data 

• Julien: relates scenario of how a chemist might not be aware of how to properly compute statistics (need to multiply by cosine of latitude)
• Brian: Goal is to ease the path toward bringing your scientific content to a notebook if it can be readily linked to data + software
• Max: is the cookbook template better-suited to a classroom lecture, or better to take pieces to place in a course?

• Max: should we draft a registration form for the hackathon yet?

• Brian: wait a bit longer for funding situation clarification
• Ryan: but can we at least start with drafting the form, noting that funding is pending?
• Max will proceed on making a form
• Continue to promote on Twitter, etc.
• Rob: is there going to be a hybrid component? Yes, although if it is funded, more effort on in-person.

2023-02-21: Outreach Working Group

Meeting link:

• Meeting link: https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany/ @ktyle
• Max Grover / Argonne / @mgrover1
• Drew Camron / Unidata / @dcamron

Agenda (with notes from the meeting):

• SciPy (deadline 3/1)

• Draft proposal
• Drew and Kevin will iterate independently the rest of the week but will meet up via Zoom at noon EST / 10 AM MST Friday

• June 20-23 Hackathon planning

• https://docs.google.com/document/d/1wQOVOnH0cny1SjqkCyjjm7vko15oDi3Qgp_cCIGjcFI/edit

• OWG project management tools

• Project board, a la the new Github board that Orhan demoed?

• Probably overkill

• A shared Google calendar may be more appropriate, which would include

• Deadlines (e.g. conference submissions)
• Rotating duties (e.g. Twitter)

• Twitter duties (will be scheduled on the above-mentioned Google calendar)

2023-02-13: Education Working Group

Meeting link:

• https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09
• Passcode: (see calendar for passcode)

Facilitator: Drew Camron | Note-taker: mgrover@anl.gov

Attendees:  [Name / Institution / GitHub Username]

• Elena Romashkova / NCAR/CGD / @rmshkv
• Max Grover / Argonne / @mgrover1
• Rob Ford / UAlbany / @r-ford
• John Clyne / NCAR / @clyne
• Drew Camron / Unidata / @dcamron
• Brian Rose / UAlbany / @brian-rose
• Ryan May / Unidata / @dopplershift

Quick Updates:

• Please sign in on this page above (and add any quick updates here)

• KT

• Kicking off new semester of new Pythia model teaching
• Using Py-ART for the radar stuff

• JC: Reminder that Brian Rose will be visiting NCAR Feb 17 - March 3.
• BR: Coming to Boulder on Friday :)

• Submitted proposal to ACCESS CI program
• Computer time on Jetstream2 - secured more substantial allocation there 🚀

• Lots of credits, approved in minutes

• RF: No updates
• ER: cookbook in progress ideas coming later in the agenda
• MG: No updates
• RM: No updates
• DC: Pinged Brian about testing actions issue

Agenda + Meeting Notes:

• OWG update

• Did come to conclusion to submit a SciPy abstract (deadline Feb 22)

• More on specifics related to Pythia infrastructure
• KT + DC working on this
• SciPy proposal workshop - 15th/17th of Feb

• Updates on Hackathon discussed during quarterly meeting
• Julia linked the hackathon title/description sent to admin folks (see below)

• Requested rooms for breakout rooms, hotel room block

• Updates from meeting with UCAR’s EdRC office re hackathon - John, Brian

• Notes here
• Encouraged us to reach out to other groups who have done this before (ex. Unidata)
• Unidata experience with workshops?
• What is plan B if we can’t get support for external participants?

• The need for this is real…
• Chances of securing funding is very low, look at engaging virtual people as well
• Could recruit more NCAR/UCAR/CU people too
• Make sure to have remote as an option, worked OK last year, can improve

• Hackathon title and description sign-off for space requests
• Taking stock of cookbooks

• Regridding cookbook (Thomas Martin)

• Ready to publish
• DC checking with him after this meeting to get this moving

• Kerchunk cookbook (Raphael Hagen)

• KT will follow up
• Currently in a “polishing” stage
• Priority here should be getting this to the finish line

• Intake cookbook (James Morley)

• Currently published, work left to do?
• No updates

• Packaging cookbook

• Worth checking with Julia + team on this one

• VAPOR 3D visualization (Julia Kent)

• Julia had a meeting with the VAPOR team last week about this

• CGD/Matt Long (Elena Romashkova)

• Have a notebook plotting some FEISTY fish model data as maps + timeseries, with some data organization and potentially interactivity involved…would this be a useful cookbook?

• FEISTY workflow

• Read data using xarray
• Applying some calculations
• Visualize at the end
• GO FOR IT!

• Ocean Model Diagnostics

• Jupyter notebook based diagnostics
• Working with MOM6 ocean model
• Good to coordinate with COSIMA recipes

• MetPy topics (Drew C)

• Unidata “python-training” pythia-ized

• Asynchronous training materials for

• Getting spun up with workshop content
• Intro to Python/Jupyter
• Met-focused content

• Creating 1-2 cookbooks out of this material, have things cross-referenced, consolidated
• Mostly not started, main thing contributed near hackathon season 😀
• Where should the content not in Foundations go?

• Ex. Basic Python, including control flows, etc.
• Could consider putting this into its own cookbook, or building on Foundations

• RM - if we include, we should include in (new) section in Foundations

• Next up after actions testing

• Cloud centric workflows (Rich Signell)

• Covered by Kerchunk topics

• Consolidated content from Pangeo + EarthML (Jim Bednar, Anaconda; Max Jones, Columbia)

• Plan was to hold off until infrastructure issues (binderbot) resolved
• Infra more related to Pangeo gallery

• Data infra issues related to Pangeo gallery

• We have ironed out most of these things - good to check up with them

• Our stuck Pangeo migration cookbooks

• xgcm-cookbook
• Not at the top of any one person’s plate. Some compute and data limitations, but needs revisiting
• Would be good to contact the original pangeo gallery developers

• Contribute, and attend the summer event :)

• General Circulation of the Atmosphere (Brian Rose https://brian-rose.github.io/general-circulation/home.html)
• Fall 2022 ATM433/533 (Kevin Tyle)

• ERA-5 via RDA THREDDS

• One variant allows for “cookbook-like” generation of animations for NOAA Science on a Sphere visualizations

• Holoviz (see https://twitter.com/MikeBWeather/status/1625163528905564160)

• Cookbook Contributor’s Guide

• How should people contact us?

• Pangeo Discourse (recommended)

• Want this to be a focal point
• Repeat this message
• Focus should be on engaging with people there

• Open issue in cookbook-gallery

• Where do we put the guide?

• Append to main contributor’s guide
• Somewhere in cookbook-gallery
• The more links to it the better, make sure it is on the cookbook gallery page
• Maybe removing the overall contributors guide would make it more clear - and making it bold/highlighted

• Action Items

• Update cookbook gallery according to discussion today - RF
• Draft an issue template for cookbook contributions - OWG
• Drafting the FEISTY content into a cookbook - ER
• Follow up with Pangeo + EarthML folks - JC
• Reach out to Pangeo gallery people to migrate content - OWG

2023-2-6: Quarterly Meeting

Meeting link:

• Meeting link: https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09

Attendees:  [Name / Institution / GitHub Username]

• John Clyne / NCAR / @clyne
• Kevin Tyle / UAlbany / @ktyle
• Max Grover / Argonne / @mgrover1
• Brian Rose / UAlbany / @brian-rose
• Drew Camron / Unidata / @dcamron
• Julia Kent / NCAR / @jukent

Agenda (with notes from the meeting):

• Metrics doc

• Status of planned submissions (notes from our October 24 meeting)

• Regridding cookbook (Thomas Martin)

• WIP. repo exists, but has not been added to gallery yet.
• Ready to publish

• Consolidated content from Pangeo + EarthML (Jim Bedner, Anaconda; Max Jones, Columbia)

• Plan was to hold off until infrastructure issues (binderbot) resolved

• Our stuck Pangeo migration cookbooks

• Not at the top of any one person’s plate. Some compute and data limitations, but needs revisiting

• Cloud centric workflows (Rich Signell)

• Use ESIP dask gateway?

• Fall 2022 ATM433/533 (Kevin Tyle)
• Intake cookbook (James Morley)
• VAPOR 3D visualization (Julia Kent)
• CGD/Matt Long (Elena Romashkova)

• Potential topics include CESM (and others) data wrangling, comparisons to eg obs data, analysis and viz workflows

• MetPy topics (Drew C)

• Unidata “python-training” pythia-ized

• General Circulation of the Atmosphere (Brian Rose https://brian-rose.github.io/general-circulation/home.html)

• How do we move these forward?

• BR: have the hackathon!
• JC: do we need to have more cookbooks available to attract attendees?
• BR: It might be helpful to have some key cookbooks that exercise infrastructure
• KT: Having more content in time for NSF GEO OSE proposal might be helpful
• BR: can we identify low hanging fruit, particularly for “external” CBs. External CBs probably more valuable (to reviewers) than from core team.
• KT: what about kerchunk cookbook

• Incorporating project boards into our best practices
• Summer event

• Who is on the organizing committee?

• OWG + BR
• Optimal hackathon size: ~50

• Update on interactions with NSF

• Open discussion

• Are there areas where we can improve?
• What is one thing that you would change?
• Are there opportunities that we should pursue that would help achieve our goals?

• BR: securing additional funding
• RM: Scipy CFP is out, and due Feb 22.

• 4 hour tutorial?
• Talk?

• MG: there will be another ARM meeting in August. Plan to develop cookbooks.

• Citability of cookbooks

• BR: How do we incentivize scientists to contribute cookbooks?
• MG: should we mint DOIs for each CB? Easily done through Zenodo.
• BR: we should figure this out before the summer event.
• MG: we should engage the NCAR librarians: Matt Marenick (sp?)
• BR will post Discourse question.

  ---

2023-02-07: Outreach Working Group

Meeting link:

• Meeting link: https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany/ @ktyle
• Brian Rose / UAlbany / @brian-rose
• Julia Kent / NCAR / @jukent
• James Munroe / 2i2c / @jmunroe
• Drew Camron / Unidata / @dcamron
• Max Grover

Agenda (with notes from the meeting):

• SciPy?

• OWG leaning against submitting a tutorial
• In support of submitting for a 30-min talk on cookbook infrastructure, GHA+binderbot, executable book workflows, etc.
• List of tracks - https://www.scipy2023.scipy.org/present

• Possibly under “tending your open source garden + community”

• Consider JupyterCon?
• KT + DC will start to draft abstract

• June 20-23 Hackathon planning

• Title: (drafts below)

• Pythia Cook-off: hacking together cookbooks for Pangeo
• Project Pythia [event]: cooking up recipes for the Pangeo stack

• Description:
• Fee for provided lunch:
• Currently exploring funding opportunities for travelers
• Goal headcount: ~50
• Potential 2i2c sponsorship opportunity for snack/coffee break(s)
• Brainstorming

• Start with “here’s what can be done” and leave people room to generate from start?
• “Bring your own project”, asking people to come with workflows and code in hand, and let the hackathon turn these into cookbooks, eg this paleo project (it’s the same dates, oops - joint session opportunity?)
• JM links other “recipe” effort from COSIMA
• Tutorial/content groups to connect with:

• https://book.cryointhecloud.com/tutorials/index.html
• https://oceanhackweek.org/ohw22/tutorials-index/index.html
• https://the-environmental-ds-book.netlify.app/gallery/exploration/general-exploration-landcover_io/general-exploration-landcover_io.html

• Making room for groups to gather and combine similar efforts into cohesive cookbooks
• Reach educators looking to use these in their classes?

2023-2-6: Infrastructure Working Group

Meeting link:

• Meeting link: https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle
• John Clyne / NCAR / @clyne
• Brian Rose / UAlbany / @brian-rose
• Drew Camron / Unidata / @dcamron
• Rob Ford / UAlbany / @r-ford
• Orhan Eroglu / NCAR / @erogluorhan
• Ryan May / Unidata / @dopplershift
• Julia Kent / NCAR / @jukent

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• Volunteer for notetaking? Drew
• Quarterly meeting: tomorrow 12 Noon EST / 10 AM MST. Send agenda items to John (or just add to this document). Draft agenda items thus far:

• Review of metrics
• Prioritizing tasks (with support of new project boards)
• Summer event
• Open discussion

Agenda (with notes from the meeting):

• Summer Hackathon: June 20-23

• Brainstorming during tomorrow’s OWG meeting (and likely quarterly meeting thereafter)

• ACCESS Jetstream2 Discovery Allocation Request

• Link to Draft
• Can be submitted any time, will word smith and delegate submitters; can iterate with funders as-needed

• NSF GEO OSE Proposal

• Link to last week’s planning meeting notes
• One pager draft in the works and will need quicker feedback later this week

• Pythia Project Board

• Currently populated with cross-org issues, organized into separate views
• Can be populated with any issue or PR, OE prefers to focus on issues and have PRs explicitly tied to relevant issues in-PR
• Expect some limitations and headaches with automation
• Board allows creating items that are not explicitly tied to repo issues
• Iteration (ie “sprint”) duration and recurrence can be defined - tie to meeting schedule? Longer?
• Value of “Comment” field for specific project-based history, etc.
• Individuals can modify views without affecting entire team, then edits can be saved or exported to new views

• Align CI workflow across all of Project Pythia

• cookbook-gallery still missing some of these pieces, including link-check
• cookbook-actions is itself un-tested and has little CI checking on updates and enhancements

• DEFER to future meeting: To mamba or not to mamba, that is the question

• Use mambaforge as the basis for environments, or:
• Use conda, but with built-in libmamba
• See Discourse discussion here.
• (This might be considered an educational content question, so we could take it at the next EWG)

• DEFER to future meeting: Ruff: highly performant linter

• Several projects (e.g. Xarray) adopting Ruff

2023-1-30: Education Working Group

Meeting link:

• https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09
• Passcode: (see calendar for passcode)

Facilitator: Brian Rose | Note-taker: Rob Ford

Attendees:  [Name / Institution / GitHub Username]

• Brian Rose / UAlbany / @brian-rose
• John Clyne / NCAR / @clyne
• Rob Ford / UAlbany / @r-ford
• Julia Kent / NCAR / @jukent
• James Munroe / 2i2c / @jmunroe
• Kevin Tyle / UAlbany / @ktyle

Quick Updates:

• Please sign in on this page above (and add any quick updates here)

• JC: Quarterly Meeting rescheduled for Tuesday, Feb 7, 10am MT. Our usual zoom coordinates. “Required” for PIs/senior-personnel        
• RF: Landsat ML Cookbook by Demetris Roumis added to gallery
• BR: harmonized build/preview/test infrastructure across repos
• JM: shoutout for pyOpenSci: https://www.pyopensci.org/

• Link to it (resource gallery)?
• JC: note in our content when something is reviewed by pyOpenSci (maybe)

Agenda + Meeting Notes:

• OWG update

• Scipy call for proposals due Feb 22
• Additional discussion points for hackathon and foundations updates below

• Summer Event (June 20 - 23) - john
• Current status

• NCAR Main Seminar Room reserved June 20 - 23

• Capacity > 100

• Taysia Peterson (taysia@ucar.edu) is our “event planner”

• Can help with a variety of logistics (A/V coordination, registration, room reservations, etc.,)
• Need to find out what else Taysia can do for us

• Meeting with UCAR EdEC on Feb 13, 11am MT

• What can they do for us (e.g. advertising, provide content)
• Help with funding (to support external participant travel)?

• Potential interest form
• 

• Near term priorities

• What kind of event are we holding?
• Reserve additional rooms if needed
• Complete the CISL Event Request Form and meet with Taysia
• Identify the conference  committee. Tasks:

• Program
• Advertising
• Hybrid or in-person only
• Budget (registration fees? Support from NSF?)
• Lodging for external participants
• Etc.

• Hackathon/workshop ideas

• BR: Come with an idea for a cookbook, work on it, and get help with infrastructure. Present work at the end/last day
• JM: contributors could come out of the event with a DOI
• JC: could attract a larger audience by covering foundational/cookbook content (first half-day?). Need to think more about what to cover.
• KT: bring in other NSF-funded groups to contribute content (AI2ES, other EarthCube awardees)
• JC: Should reach out to EarthCube office. John will do.
• Event title ideas:

• Focus on “cooking”?
• Cookbook Kitchen
• Project Pythia Cookbook Workshop
• (OWG will continue)

• Questions about Foundations (see OWG notes below for context)

• Is our “spinning up” workflow opinionated enough, and is there enough pre-setup to get started in Foundations without digging through multiple textbook chapters (OWG opinion: no, move some conda-based setup to the very beginning)
• When does the benefit of advocating for mamba/mambaforge outweigh any burden on learners with switching gears to mamba?

• No clear downside, but we need to ask others: open discussion on Pangeo Discourse

• How do we proactively keep Foundations alive regularly?

2023-01-24: Outreach Working Group

Meeting link:

• Meeting link: https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany/ @ktyle
• Drew Camron / Unidata / @dcamron
• Julia Kent / NCAR / @jukent

        
Quick Updates:

• Please sign in on this page above (and add any quick updates)

Agenda (with notes from the meeting):

• 148 (how to get involved, now a draft PR 297)

• Status update?

• Twitter/Mastodon schedule

• Kevin: twitter ambassador until 2/7
• Every new cookbook release
• Hackathon plans

• Open issues on Discourse (make this a regular agenda item for OWG)

• Note question about Xarray Pythia Cookbook (Kevin will follow up)

• Julia may submit an abstract for the upcoming NCAR SEA conference
• SciPy Call for proposals due Feb 22
• During last week’s MetPy community call, Eric Bruning (Texas Tech) mentioned Pythia as a resource … noted that finding the “Installing & Managing Python with Conda” section is buried a bit too deep

• Should we move this section up in the “Getting Started with Python” chapter?

• June Pythia Hackathon planning (6/20-23)

• Set up an interest form?
• Further discussion on next Monday’s EWG meeting
• Hybrid as well as in-person? If hybrid component, need to have a dedicated hybrid leader(s)
• Think about rewarding external participants (stickers, etc.)

• Drew: will look into ordering more stickers

• Themes for hackathons

• Questions for EWG re Foundations

• Prerequisite conda “setup” clearer up front
• Using mambaforge and an opinionated workflow
• General review of foundations intro material

2023-1-23: Infrastructure Working Group

Meeting link:

• Meeting link: https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle
• John Clyne / NCAR / @clyne
• Rob Ford / UAlbany / @ r-ford
• Brian Rose / UAlbany / @brian-rose
• Julia Kent / NCAR / @jukent
• Drew Camron / Unidata / @dcamron
• Orhan Eroglu / NCAR / @erogluorhan
• Naheem Adebisi / Boise State Univ

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• Brian Rose will visit NCAR Feb 17 - March 3.
• AMS report out

Agenda (with notes from the meeting):

• Thursday’s quarterly meeting (1/26) - John

• Needs rescheduling; John will reach out to non NCAR folks

• Issues/PR’s

• High priority infrastructure-related:

• Establishing pythia-wide project board to facilitate tracking high priority issues, etc.

• OE will lead; set up foundation over the next month

• DONE: Please see Pythia Projects Board

• Synchronize Foundations / Portal actions with Cookbook actions (see 339 )

• RM/DC are reviewing this PR

• Identify and fix gaps in the Cookbook testing workflows

• A thorough review of our cookbook testing suite is in order, but first order of business is to synchronize Foundations actions with Cookbooks

• Binderhub

• Apply for Discover Access allocation

• Brian: request ACCESS account so you can be co-PIs (looks like John already has one)

• BR: I should already have one carried over from XSEDE (https://identity.access-ci.org/new-user) but I can’t find any login page to test it

• Status of recently submitted cookbooks

• E.g. @norlandrhagen, kerchunk; @jnmorley, librarynb

• KT will follow up with @norlandrhagen
• JM’s work with JK and Pythia team ended at 2022, but JK feels the cookbook is not too far from the goalline

• Larger question: what do we consider “good enough” for a Cookbook?

• BR: A cookbook that runs, passes tests, is “correct enough” in the sense that a couple pairs of eyes have looked at it should be published.
• BR: and this is why we need some robust testing cookbook-wise
• JC: what’s the minimal useful product we can put into people’s hands? Go for that rather than striving for the “perfect cookbook”
• BR: what’s the sufficient amount of content to deem a cookbook publishable? Is one notebook, wrapped in the cookbook template, enough? Yes if there is a clear link to other content and/or clear direction toward a more complete cookbook. Else, look to combine with other published cookbooks
• RM: needs to show a certain amount of “connected ideas on a subject”
• BR: on the other hand, don’t want to put up unnecessary barriers to folks who want to contribute
• Action item: open a discussion on Pangeo Discourse
• What happens when someone transfers a repository to Pythia?
• For content, best to follow up with original cookbook author, but if the issue is infrastructure related (e.g. JSON issue preventing jupyterbook from fully executing)

• Landsat-ml-cookbook by @droumis

• RF: coordinated with cookbook author; currently there is an infrastructure issue that’s keeping it from being built (likely the JSON/Jupyterbook/JupyterServer issue)

• Best use of github org and teams to manage access?
• OpenAQ (proposed)
• How to come up with metrics for how people are interacting with cookbooks … whether it’s just a search, or developing a new cookbook, etc; look at Google analytics for trends in searches for Cookbooks

• Welcome Naheem Adebisi (Boise State Univ.) … discovered Pythia while learning Xarray

2022-12-19: Education Working Group

Meeting link:

• https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09
• Passcode: (see calendar for passcode)

Facilitator: Drew Camron | Note-taker: ktyle@albany.edu

Attendees:  [Name / Institution / GitHub Username]

• Julia Kent / NCAR / @jukent
• John Clyne / NCAR / @clyne
• Drew Camron / Unidata / @dcamron
• Rob Ford / UAlbany / @r-ford
• Brian Rose / UAlbany / @brian-rose
• Kevin Tyle / UAlbany / @ktyle
• Max Jones / CarbonPlan / @maxrjones
• Ryan May / Unidata / @dopplershift
• Max Grover / Argonne / @mgrover1

Quick Updates:

• Please sign in on this page above (and add any quick updates here)

• JC: Deepak Cherian expressed interest in consolidating CGD examples as Cookbooks in ~Feb timeframe. Has funding from “Jupyter Meets Earth” award to support this. John will follow up in February.
• JC: external cookbook contributions from @droumis (via discourse) and Max Jones. Latter needs response.
• JC: Looking into dates for possible summer workshop/hackathon on the Mesa that would include external participants.
• RF: Still working on fixing issues with the CMIP6 cookbook … could be related to Xarry October update
• JK: looking at cataloging various ESDS blog posts … they should be good potential cookbook topics
• MJ: Cookbook topics: EarthML and Kerchunk. Could link into existing Foundations chapters as well as cookbooks.
• MG: At ESGF meeting this past Monday, folks were interested in assisting with CMIP6 cookbook, also include xcdat

Agenda + Meeting Notes:

• OWG Report

• No meeting last week. May not meet next week either since it’s a holiday week.
• JC: Please tweet out upcoming Pythia activities at AMS
• MG: A few more Mastodon followers. “Tweets” are termed “Toots” (although “posts” is preferred)

• AGU report out

• John:

• Strong presence at AGU: talks from Julia and John. Poster presentation from Kevin T. Pictures here.
• John and Brian met with NASA’s Paige Martin (TOPS PO)  to discuss ways to work with NASA’s TOPS initiative.
• John met with NSF GEO/EAR PO Eva Zanzerkia. Eva is promoting Pythia to “solid earth” community.
• Lots of awareness of Pythia at AGU!
• 

• Cookbook contribution issues and documentation:

• https://discourse.pangeo.io/t/ready-to-transfer-cookbook-draft-to-pythia-could-i-get-added-as-outside-collaborator/3016/2

• How can we add an external collaborator so as to enable the transfer of the contributed cookbook repo to our organization? More generally, how can we make the cookbook contributing process more seamless? Simple Google form?
• https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository - “To transfer a repository that you own to an organization, you must have permission to create a repository in the target organization.”
• MJ: Xarray has a model for repo transfers
• RF will work with the contributor to get his EarthML cookbook added. Will use this as an opportunity to better document the cookbook contributor’s guide.
• DC: suggest that organization owners enable 2FA

• https://discourse.pangeo.io/t/questions-about-pythia-cookbooks/3021/3

• Kerchunk cookbook

• NetCDF and other formats (GRIB)

• Cookbook authors should consider whether they should have it runnable in GitHub actions or if it needs a Binder instance

• AMS breakout group organizing. MJ will be sending out instructions for those who want to lead a breakout
• Brainstorming on summer 2023 Pythia workshop. Working with NCAR staff in terms of dates. More to follow.

• RM: Unidata triennial workshop 6/5 to 6/8.

• Infrastructure short-term needs (since we may not meet for a while)

• Nuances regarding nightly testing continue to exist
• Are these issues significant enough to warrant refactoring cookbook code? Not at this time …

• With end of year approaching, time to look at Google Analytics (and other relevant metrics). JC asks JK to take a look. Will discuss at an upcoming OWG or a separate meeting.

2022-12-05: Education Working Group

Meeting link:

• https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09
• Passcode: (see calendar for passcode)

Facilitator: Julia Kent | Note-taker: brose@albany.edu

Attendees:  [Name / Institution / GitHub Username]

• Julia Kent / NCAR / @jukent
• Brian Rose / UAlbany / @brian-rose
• Rob Ford / UAlbany / @r-ford
• Kevin Tyle / UAlbany / @ktyle
• John Clyne / NCAR / @clyne
• Max Grover / Argonne / @mgrover1
• Drew Camron / Unidata / @dcamron

Quick Updates:

• Please sign in on this page above (and add any quick updates here)

• KT: working on poster for AGU, using summer EarthCube poster as base. Will invite comments maybe tomorrow afternoon
• JC: John will be on an AI in the Earth Sciences panel at AGU, Data and education: Empowering AI/ML in Geosciences, Monday, 12/12, 2022, 12–18 CT, S406a
• BR: we’ll do a crash course in migrating repos to ProjectPythia org after today’s meeting
• RF: CMIP6 Cookbook is still failing nightly build, needs looking into
• DC: Will give the OWG update
• MG: Xarray + Dask content got merged into Foundations! Can work with RF on CMIP6 Cookbook issues. ESGF meeting Monday at AGU, hoping to show this Cookbook off.
• JK: EarthCube demos booth looks very sparse so far. Only Pythia!

Agenda + Meeting Notes:

• OWG Report

• Plan to create online + print-friendly version of “How to Get Involved with Pythia” flyer this week, before AGU.
• Look out for PRs this week
• Should have plenty of stickers for AGU in the hands of various people. Keep an eye on numbers to see if more need to be ordered prior to AMS meeting

• https://github.com/ProjectPythia/pythia-foundations/issues/337 on typos. Still a work in progress.

• New spreadsheet link: Copy of Kailyn-ProjectPythia-WalkingWebTree

• Migration steps

• ProjectPythiaCooksbooks contains (cookbooks, cookbook-specific actions, gallery generation), each cookbook will need action references updated
• Transfer to education+infrastructure teams
• Todo

• Rename cookbook gallery generation repo and fix subdomain (if necessary)

2022-11-29: Outreach Working Group

Meeting link:

• Meeting link: https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09

Attendees:  [Name / Institution / GitHub Username]

        Kevin Tyle / UAlbany / Kevin Tyle

• Max Grover / Argonne / @mgrover1

• Drew Camron / Unidata / @dcamron
• Julia Kent / NCAR / @jukent

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• Prepare for AGU!

• Post list of talks/posters on the Pangeo discourse

• Prepping short courses

• MetPy
• Open Science in the Rockies

• Student fee waiver application

Agenda (with notes from the meeting):

• 148 (how to get involved)

• Divide this up so we can get it done!
• Opening a draft PR

2022-11-28: Infrastructure Working Group

Meeting link:

• Meeting link: https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle
• John Clyne / NCAR / @clyne
• Brian Rose / UAlbany / @brian-rose
• Julia Kent / NCAR / @jukent
• Rob Ford / UAlbany / @r-ford
• Drew Camron / Unidata / @dcamron
• Ryan May / Unidata / @dopplershift
• Orhan Eroglu / NCAR / @erogluorhan

Quick Updates:

• Please sign in on this page above (and add any quick updates)
• JC: Highlights from today’s “Future Opportunities for Geoscience-CI Community Engagement” webinar

• There was an AGU Notebooks Now workshop on November 3,4. Info and recordings here. Goal of Notebooks Now!: “Elevating Computational Notebooks as Primary Elements of the Scientific Record”
• NSF solicitation 23-521 (Strengthening the Cyberinfrastructure Professionals Ecosystem). Solicitation goals include “fostering innovative and scalable education, training, and development of instructional materials, to address emerging needs and unresolved bottlenecks in CIP workforce development.” Deadline Feb. 23 2023. Worth looking into.

• Zoom meetings “sign in to join, this meeting available to authorized participants only”. Is this what we want?

• Old way (NCAR-hosted, have to type in a password)
• New way (UAlany hosted, t
•  Create some appropriate verbiage on the relevant page and/or calendar link?

Agenda (with notes from the meeting):

• Pre-AGU to-do list

• Organization coalescing

• Provisional minihackathon: devote last part of EWG agenda 12/5 and some time afterward

• Cookbooks
• AGU booth demo signup

• Issues/PR’s

• High priority infrastructure-related:

• 345 (make allow_errors=False and add flags for any cells that are expected to fail, so we don’t miss problems such as what occurred in 343)

• Create PR to resolve similar issue in this CMIP6 Cookbook
• We should add some verbiage for cookbook contributors so they know how to add that flag

• 344 (Mint GitHub releases for Foundations)

• Rule of thumb: new release when there is some clearly-visible new content or revised look … but not for trivial typos/fixes.
• Also gives us a formal way of citing content with a DOI
• GitHub makes automating a version release fairly easy … some human intervention is still necessary, but can be pretty minimal
• What is the imagined scenario where someone would cite us?
• If we don’t provide the citation link, then we won’t be cited :)
• Consider a quarterly release by default?
• Would we also want to preserve previous versions so they could be visible on, e.g. GitHub pages?

• Zenodo’s archiving provides a source archive, not a visible/rendered archive … maybe not perfect, but it’s do-able, and low-hanging fruit
• Bigger issue in general! How do we properly archive electronic content such as Foundations? Larger than Pythia. JC will reach out to AGU for their thoughts.

• 267(How to communicate with us)
• 231 (Autoapprove/automerge bot PRs)

• Based on R. May’s comment, close?
• Can we have two people tagged for review, but only need one to merge? YES … on a per-team basis.
• If not, tag one, need one to merge.
• PR author will need to exercise some judgment. If the author feels it needs a 2nd reviewer, the author will need to do explicitly tag them.
• What do we do about auto-assigned reviewers who are not currently active on the project? Time to cull those who are no longer active. Just need to take those folks off the relevant teams (notify them at the same time that they are being removed)

• 148 (how to get involved)

• Discuss at tomorrow’s OWG

• Contact email for the GitHub org needs to be changed from Kevin P to John C.

• Binderhub

• Jetstream2 has a new set of detailed setup instructions. KT will likely spin up a new test instance based on them.

2022-11-21: Education Working Group

Meeting link:

• https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09
• Passcode: (see calendar for passcode)

Facilitator: brose@albany.edu | Note-taker: Ryan May

Attendees:  [Name / Institution / GitHub Username]

• Brian Rose / UAlbany / @brian-rose
• Julia Kent / NCAR / @jukent
• John Clyne / NCAR / @clyne
• Kevin Tyle / UAlbany / @ktyle
• Drew Camron / Unidata / @dcamron
• Rob Ford / UAlbany / @r-ford
• Ryan May / Unidata / @dopplershift

Quick Updates:

• Please sign in on this page above (and add any quick updates here)

• JC: EarthCube will have a booth at the upcoming AGU meeting in Chicago. If you would like to volunteer to do a demo of your tool at the booth, please sign up here

• Demo a notebook or two, some of the infrastructure
• KT, JK interested in signing up for slots

• JC: There will be several EarthCube sponsored events at AGU. A complete list is here.
• BR: migrating Cookbooks to the main ProjectPythia GitHub org is more complicated than we thought due to some GitHub magic around URLs for Pages.

• Difficult to maintain cookbooks.projectpythia.org domain for the repos under the normal Project Pythia organization
• Decision: cookbooks.projectpythia.org -> gallery and just host cookbooks under projectpythia.org/mysubject-cookbook, thus allowing us to continue migration to single GitHub org (which is the bigger win vs. cookbooks.projectpythia.org namespace for cookbooks).

• JK: Updated some cookbooks for infrastructure (e.g. binderbot)
• DC: Unidata workshop at CSU

Agenda + Meeting Notes:

• OWG Report:

• Fosstodon https://fosstodon.org/home @projectpythia
• Scientific Python community has not come to a consensus on where it’s moving yet

• EWG efforts prioritization going into conference season

• KT: Duplicating on-going topic from Discourse: https://discourse.pangeo.io/t/project-pythia-content-priorities-before-agu-ams/2914
• Foundations polishing https://github.com/ProjectPythia/pythia-foundations/issues/337

• Julia working on 0-10
• James working on 20-30

• Dask + Xarray content: revise and merge https://github.com/ProjectPythia/pythia-foundations/pull/321

• BR: Should be really close

• Update the Team page with new people https://github.com/ProjectPythia/projectpythia.github.io/issues/287

• JC: Not particularly high priority, maybe SIPARCS student?

• Clarify how to contact / get involved https://github.com/ProjectPythia/projectpythia.github.io/issues/267

• RF: Need to link to pangeo discourse at some place immediately visible on Project Pythia site.
• BR: Org README too [ Assigned to Robert Ford]
• DC: https://github.com/ProjectPythia/projectpythia.github.io/discussions/260
• Pinned post on each GitHub discussion board linking to Pangeo Discourse [Drew Camron]

• Fix CESM-LENS cookbook code https://github.com/ProjectPythiaCookbooks/cesm-lens-aws-cookbook/issues/3

• Cookbook doesn’t currently run properly
• Migrated from Pangeo, good demo of “larger” cookbook
• Assigned to Robert Ford and Brian Rose

• Update Cookbook contributor’s guide https://github.com/ProjectPythiaCookbooks/.github/issues/6

• BR: Outdated for current infrastructure and wrong on some points. Should be high priority since this leads potential contributors.
• Assigned to Kevin Tyle

• Use Cookbook infrastructure for Foundations https://github.com/ProjectPythia/pythia-foundations/pull/339

• BR: Would reduce maintenance, but not high priority since doesn’t affect contribution process

• Markdown tutorial for Foundations https://github.com/ProjectPythia/pythia-foundations/pull/248

• Drew Camron will pick this up a little after the holiday

2022-11-16: Outreach Working Group

Meeting link:

• Meeting link: https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle
• Julia Kent / NCAR / @jukent

Quick Updates:

Agenda:

Social Media Platform:

        Twitter message thread: https://twitter.com/messages/1572270698579591168 

        Sci. Python Mastodon draft governing document: https://hackmd.io/qw3V_E08TviYYGA1x83w7A 

                They propose rolling it out coincident with PyDataGlobal (12/1-3)

Got on waitlist to join Fosstodon (same password as Twitter account)

AGU:

time to start working on posters and talks

        AMS:

                Pangeo hackathon on Friday of that week. Waiting for updates from organizers. Pythia-led breakout group.

                Saturday the week before, AI2ES meet up at Center Green. KT will be attending.

        Pythia summer 2023 hackathon: time to start investigating dates; mention during tomorrow’s Pangeo call - KT

        Pangeo Open Science Working group? Last meeting was 7/1/2022; MG asked Ryan A. during last week’s Pangeo call; apparently group is still active

        Pangeo showcase:Information/signup page - https://pangeo.io/pangeo-showcase.html

2022-11-14: Infrastructure Working Group

Meeting link:

• Meeting link: https://albany.zoom.us/j/97375285304?pwd=bGQzeldCcGs4VEdpVnc4aDlxMEFZdz09

Attendees:  [Name / Institution / GitHub Username]

• Kevin Tyle / UAlbany / @ktyle
• Julia Kent / NCAR / @jukent
• Max Grover / Argonne / @mgrover1
• Rob Ford / UAlbany / @r-ford
• Brian Rose / UAlbany  / @brian-rose
• James Morley / UVU / @jnmorley
• Orhan Eroglu / NCAR / @erogluorhan

Quick Updates:

• Please sign in on this page above (and add any quick updates)

• NASA TOPS: Decided against pursuing the Dec. 2022 call
• KT: presenting on RAPIDS-AI-accelerated analysis/visualization of NLDN data during  Dask Demo Day Thurs. 11/17 11AM EST / 9AM MST
• JM: Prototype for new tool for launching Jupyter Books locally
• OE: Held a two-day ESDS fall event last week in which there was Python tutorials (50 attendees; Julia led the Pythia-related content
• RF: working on CESM cookbook
• MG: still working on integrating radar cookbook with Binderbot
• JK: focusing on updating the infrastructure in cookbook

Agenda (with notes from the meeting):

• BinderHub

• Testing GitHub-based auth + HTTPS this week

• Celebrate closed and discuss open Infrastructure Issues and PRs

• Env Data Science Book added to gallery https://github.com/ProjectPythia/projectpythia.github.io/pull/285)

• Do these still need to be done manually? (Follow up with Drew)

• Bot PRs, e.g. #286:

•  As mentioned in issue 231 is there a best practice we should follow to get these quickly reviewed/merged?
• What should we look for as potential reasons to not approve/merge?

• The issue that has bedeviled us has been in the pre-commit jobs which wants to include pre-release versions of tools (e.g. alpha version of some of the related packages )
• OE: with geocat, they do not use pre-commit autopush services at all. Instead, have the developers use it in their local versions when they do a commit. It gets developers in the habit of best practices/standards, e.g. PEP-8.
• BR: this is where we started, but then moved to enabling the automatic precommit. We made this decision in order to ease the path for external contributors. MG concurs.
• Until the pre-alpha issue goes away, we can either: