Public launch minimum requirements

[cisaacstern]

An upcoming public launch has been discussed in recent group meetings. The codebase is open already, of course, so this would mean promoting the existence of Pangeo Forge on Twitter, Discourse, and other public forums, and encouraging new users to the try the platform. Here's a list of items culled from our various Issue and PR trackers which we either definitely need to, or might want to, complete before that happens.

Priorities reflected below are to ensure that new users will:

1. Understand how to write and submit a recipe
2. Be able to have that recipe run in a Columbia-owned Bakery
3. Can get data back out via an approachable and documented STAC interface
4. Don't hit any major friction points along the way

I welcome any and all feedback on these points: additions, subtractions, edits, etc.

Bug fixes

• copy_pruned subset_inputs potential incompatibility. pangeo-forge-recipes#200

  Possibly interferes with our ability to register test runs of recipes that use subset_inputs feature?

Features

• Handling Secrets pangeo-forge-recipes#79 ?

  Prioritization depends on how frequently we expect users to need a solution for this.

Infrastructure

• Deploy GCP bakery into Columbia-owned project pangeo-forge-gcs-bakery#19
• STAC catalog sprint: to-do items pangeo-forge-catalog#1
• Finalize Github workflow logic for running recipes in feedstocks. staged-recipes#67

  Some of the questions here are already resolved, but others are not, such as those relating to Recipe name pangeo-forge-recipes#36

• ADR 6: REST API #31 ?

Docs

• Define contribution process pangeo-forge-recipes#71
• DOCS: create "introduction tutorial" pangeo-forge-recipes#189
• DOCS: expand "what is Pangeo forge?" page pangeo-forge-recipes#188

cc @pangeo-forge/dev-team

[rabernat]

Thanks for putting this together Charles! So helpful.

We already have a minimal working product. The bakeries can run recipes and store data. Yes, there are many bugs to fix and new features to add, but the base functionality is there.

So for me the, absolute "must haves" for the public launch are:

• Define contribution process pangeo-forge-recipes#71 - without this, people won't know how to participate.
• Deploy GCP bakery into Columbia-owned project pangeo-forge-gcs-bakery#19 - we can't launch without a bakery in production!
• STAC catalog sprint: to-do items pangeo-forge-catalog#1 - without a catalog of some sort, it's impossible to know what data we have stored

So I would put laser focus on those three issues. Once we solve them, I think we can make the big announcement that Pangeo Forge is open for business (with the caveat that there are still many kinks to work out).

[cisaacstern]

For my reference, from pangeo-forge/staged-recipes#74 (comment)

The manual validation of the recipe that @wildintellect and @sharkinsspatial did in https://github.com/sharkinsspatial/zarr_examples/blob/main/imerg_sample.ipynb was a very useful QC point. We need to make that part of the process! Once the test recipe has been run, a bot should post a link to the data and encourage the use to play with it. Maybe even provide a binder link to open it up directly.