This PR, which should update the intro paragraph here was approved and merged, but the displayed text has not been updated. The displayed text is:

Pythia Cookbooks provide example workflows on more advanced and domain-specific problems developed by the Pythia community. Cookbooks build on top of skills you learn in Pythia Foundations.

It should read:

Pythia Cookbooks provide example workflows on more advanced and domain-specific problems developed by the Pythia community. Cookbooks build on top of skills you learn in Pythia Foundations.

Cookbooks are created from Jupyter Notebooks that we strive to binderize so each Cookbook can be executed in the cloud with a single click from your browswer. See documentation here for details. In some instances executing a Cookbook will require downloading the Notebook to your local laptop or desktop as described here.

[cookbook-template]

Test

Root Repository Name

kerchunk-cookbook

Did you check if your contribution would be better suited as an addition to an existing Cookbook, before generating a new one?

yes

Additional comments

No response

Looks like these repos will start to diverge, should we detach them so that it no longer says "this repo is X commits behind" when those commits are not ones we want to include here.

Some of the cookbooks will be binderized, but some may not be (or not publicly accessible via binder). Should we add guidance, adding to the text here perhaps, that:

1. tells users how to launch via binder
2. cautions the reader that binder may or may not be an option
3. instructs them how to download the notebook file in the case that binder isn't an option?

Maybe we should just point them to this info on Foundations?

The gallery page at https://cookbooks.projectpythia.org gives (broken) links to https://mybinder.org

The Binder links on the Gallery should always match the Binder links on the README page for each cookbook. E.g. for the HRRR Cookbook the link should be
http://binder.mypythia.org/v2/gh/ProjectPythia/HRRR-AWS-cookbook.git/main

I suggest this is a high priority to get fixed before AGU if possible.

We can grab title, author, tag, and thumbnails all from the Jupyterbook conf.py files in each repository. I am going to change the code to do this because it is much more flexible and robust.

You may see some PRs on your cookbooks to add these elements to your cookbook, but feel free to customize them more.

Currently I'm running the script on my laptop to generate the yaml and then pushing the yaml up. I need to use GH actions for this. How often should it occur?

Whenever the thumbnail or _config.py files are changed in a relevant cookbook, we want the gallery to rebuild to display that cookbook's gallery card appropriately.

Some possible resources:
https://github.community/t/triggering-by-other-repository/16163
https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows

As discussed in #103, the new Binder badges with the correct links drawn dynamically from each Cookbook's _config file do not display properly in the Chrome browser.

From ProjectPythiaTutorials/projectpythiatutorials.github.io#3.

CNAME points to tutorials.projectpythia.org. Is this file doing anything? Should it point to cookbooks.projectpythia.org? Pinging @kmpaul because you edited this file.

We've discussed this at numerous working group meetings, and today (11/21/2022) we made a final decision to end-of-life the ProjectPythiaCookbooks organization.

The main reason is to simplify our project management.

Some early experiments in migration are here:
ProjectPythia/xgcm-cookbook#17

This issue addresses one of the migrating Pangeo Gallery items listed on Issue #20: xgcm Examples and Usecases

Root Repository Name

cookbook-template

Did you check if your contribution would be better suited as an addition to an existing Cookbook, before generating a new one?

yes

Root Repository Name

cookbook-template

Did you check if your contribution would be better suited as an addition to an existing Cookbook, before generating a new one?

yes

Additional comments

Test

Root Repository Name

intake-cookbook

Did you check if your contribution would be better suited as an addition to an existing Cookbook, before generating a new one?

yes

Additional comments

No response

Now that we have a few cookbooks that mostly work (CESM LENS on AWS, CMIP6, HRRR AWS, and Radar), should we remove the entries that are currently only the template material (Packaging, XGCM) or broken (Physical Oceanography)? Maybe also the Matplotlib Colorbars cookbook, depending on overlap with this recent merge in Foundations.

Migrate the pangeo CESM LENS on AWS notebook into the cookbook gallery.

The are two notebooks in this collection.

Root Repository Name

intake-cookbook

Did you check if your contribution would be better suited as an addition to an existing Cookbook, before generating a new one?

yes

Additional comments

No response

Root Repository Name

intake-cookbook

Did you check if your contribution would be better suited as an addition to an existing Cookbook, before generating a new one?

No response

Additional comments

No response

The mpl-colorbar-cookbook is being archived because the information in it is better suited for the Project Pythia Foundations Page. The content has already been moved to the foundations page, and now the cookbook needs to be removed from the website.

Migrating the Pangeo CMIP6 gallery into the Pythia Cookbook format.

There are several non-template related issues open on the template repo that should be migrated to this repo.

Root Repository Name

intake-cookbook

Did you check if your contribution would be better suited as an addition to an existing Cookbook, before generating a new one?

yes

Additional comments

No response

We need to add all of our new hackathon cookbooks to the gallery.

I followed @andersy005 's instructions here, but the Netlify deployment still doesn't seem to be working

I've added the GH secrets and the preview.yml file. I'm hoping to make any necessary changes here

Per the discussion started by @brian-rose there are a few things we might do to facilitate citation and giving credit to authors of cookbooks. Some things we might consider:

1. Add an author(s) field to the template
2. Display authors in the gallery "cards"
3. Facilitate (provide guidance) on optionally creating a DOI for the notebook and display the DOI in cards and template.

test ignore

' - [cesm-lens-aws-cookbook]'

Edit 1.

' - cookbook-template'

<!-- Feel free to add comments below this line -->

Just a test... again.

One of the Pangeo Gallery items listed on #20 is http://gallery.pangeo.io/repos/pangeo-gallery/physical-oceanography/

I will be working on migrating this content to Pythia during the hackathon.

Migrate the Pangeo Tutorial Gallery into the Pythia cookbook gallery.

There are four tutorials in this collection (Dask, geopandas, intake, and Xarray). The xarray tutorial may be a bit repetitive of existing Pythia content

Root Repository Name

cookbook-template

Did you check if your contribution would be better suited as an addition to an existing Cookbook, before generating a new one?

No response

Additional comments

No response

This is a continuation of ProjectPythiaTutorials/projectpythiatutorials.github.io#1. Now that we have a separate main site for the Project Pythia Cookbooks in this organization, we should move the gallery content here.

Now that recent infrastructure work affecting the cookbook template like ProjectPythia/cookbook-template#89 and ProjectPythia/cookbook-template#61 are done, it's time to get all the existing cookbook repos updated to use the latest infrastructure.

Repos that have already been updated include

• Radar Cookbook
• HRRR AWS Cookbook
• CMIP6 Cookbook

and maybe others.

#107 brought to my attention the fact that we're not running any link checkers on this repo. And maybe not on the main portal repo either?

We should be able to use the sphinx link checker to accomplish this.

Root Repository Name

intake-cookbook

Did you check if your contribution would be better suited as an addition to an existing Cookbook, before generating a new one?

yes

Additional comments

No response

The new cookbook gallery submission workflow needs permissions to push changes to the repo. The action is currently failing when trying to push changes.

https://github.com/ProjectPythiaCookbooks/projectpythiacookbooks.github.io/runs/7243006662?check_suite_focus=true

The goal of this cookbook is to adapt a notebook presented at the 2021 AMS Python/Pangeo short course into the cookbook-template framework.

I think it makes sense to mint new releases of the Cookbook template each time we have a working update.

This could help with our future automation for pushing updates out to all the individual cookbooks. An action can be triggered by each new release to open PRs on every Cookbook repo.

We could simply adopt Calendar Versioning like do for the pythia-datasets package

My attempt to open a PR on ProjectPythiaCookbooks is being redirected to ProjectPythiaCookbooks.

Git says:

remote: Create a pull request for 'issue_17' on GitHub by visiting:
remote:      https://github.com/ProjectPythiaCookbooks/projectpythiacookbooks.github.io/pull/new/issue_17

But the URL is redirected to the https://github.com/ProjectPythiaTutorials/projectpythiatutorials.github.io/

cc @kmpaul

Every time I locally build the site it updates index.md but this is rewritten when the site is built, no? Should this file be in .gitignore to reduce confusion as to where to make edits to the site (see #38 )

Root Repository Name

gridding-cookbook

Did you check if your contribution would be better suited as an addition to an existing Cookbook, before generating a new one?

yes

Additional comments

Hello! This has been sent before, but @dcamron asked for me to re-send this. Please let me know if this is a duplicate effort :).

Best,
Thomas

edit by @dcamron

Root Repository Name

cesm-lens-aws-cookbook

Did you check if your contribution would be better suited as an addition to an existing Cookbook, before generating a new one?

yes

Root Repository Name

cookbook-template

Did you check if your contribution would be better suited as an addition to an existing Cookbook, before generating a new one?

no

One of the goals of the hackathon is to get a few example cookbooks using this template and the material in the Pangeo Gallery. Here are some that I think would make good cookbooks:

• Glaciology
• Physical Oceanography
• CMIP6 Gallery
• ESIP Gallery
• xgcm Examples and Usecases
• Landsat 8 Tutorial (only 1 notebook, but additional notebooks could be added that go into more detail about the libraries used)

We frequently have a need to push identical (or very similar) changes out simultaneously to all Cookbook source repos. One example is changing the URL for the binder link in the _config.yml in each repo as discussed in #85

Currently we have no better option than manually edit and opening identical PRs in each repo.

Two possible alternatives for keeping the infrastructure updated across all repos:

1. Some kind of bot service (like dependabot) that can automatically open PRs across all repos (e.g. when we make a change in the template repo). This still requires people to inspect and approve the PRs for each repo, but would speed things up and help ensure consistency while still allowing individual Cookbook authors to customize their own infrastructure as necessary
2. Migrating more of the Cookbook infrastructure out of individual repos and into some centralized repository. For example, instead of hard-coding the Binder URL in each repo's _config.yml, there could be a lookup step. This would mean only opening a single PR to change any of the centralized infrastructure across all Cookbooks.

Currently most of our Cookbooks are failing their nightly health checks due a bad link, e.g.
https://github.com/ProjectPythiaCookbooks/HRRR-AWS-cookbook/runs/7778415916?check_suite_focus=true

The cause is that the Pangeo Binder service at https://binder-staging.2i2c.cloud is permanently offline.

As discussed at today's IWG, we are hoping to direct Cookbooks to a dedicated BinderHub running on JetStream2, but it is not ready for prime time just yet.

In the mean time we will redirect all Cookbook binder links to mybinder.org

Root Repository Name

cookbook-template

Did you check if your contribution would be better suited as an addition to an existing Cookbook, before generating a new one?

No response

Additional comments

Test