P. L. Lim

Benchmark failure unrelated (https://github.com/astropy/astropy-benchmarks/issues/137) but also means we cannot test that in PR right now. `....time_large_gauss_combined_2d_SLSQPLSQFitter failed`

I also wonder if this problem would propagate to the fields in ASDF data schema, etc. 😬

Still a problem during astropy v7.0 integration testing. I worked around it by forcing gwcs to install downstream.

If you want Trusted Publisher, you cannot use OpenAstronomy, see https://github.com/OpenAstronomy/github-actions-workflows/issues/136

Hmm how does that affect listing in https://astropy.org/team and https://github.com/astropy/astropy-project/blob/main/policies/permissions.md ? Does it still count as falling under Astropy proper or affiliated?

I still think what Learn needs can be accomplished without moving out to its own org, while I am against assigning individuals to specific repo access (instead of teams) and...

For the next 2 years, there is no worry because the roles of Learn Coordinator and CoCo6 overlap. Hopefully you don't need to continue to create repos in bulk after...

> if it's too expensive, THEN we can re-evaluate. This concerns me. I don't want to split into 2 orgs, have regrets, and then have that extra churn to merge...