P. L. Lim

This might be a typo. I can try to remove the ".csv" in my refactoring and see what happens: https://github.com/spacetelescope/jwst/blob/b38915d73031c771332b543bf991ca64bd0e332e/jwst/regtest/test_associations_sdp_pools.py#L95-L99

I see that pool files in https://github.com/spacetelescope/jwst/tree/main/jwst/associations/tests/data are also used outside of https://github.com/spacetelescope/jwst/blob/main/jwst/regtest/test_associations_standards.py , e.g.: https://github.com/spacetelescope/jwst/blob/d5ad1d4e5e00c15768d930d3a8af8e03d2d786aa/jwst/regtest/test_associations_standards.py#L79 and https://github.com/spacetelescope/jwst/blob/d5ad1d4e5e00c15768d930d3a8af8e03d2d786aa/jwst/associations/tests/test_level3_spectrographic.py#L35 If I replace `pool_019_niriss_wfss` in that regtest, I do *not* have to...

PR now is https://github.com/spacetelescope/jwst/pull/9855

reproject isn't in core library, but a coordinated package. Not sure if the policy strictly applies to this package. I think you could have just opened a PR straight if...

Okay then. CoCo will meet on 2024-07-22.

> I believe they follow the same process as core If only we could speak for maintenance as well... But that is a battle for another day.

Re: https://github.com/astropy/astropy-project/issues/435#issuecomment-2239194529 Might go faster if you open a PR with proposed change and CoCo can discuss on Monday.

Oh, I mean proposal to *update the policy*. 😅

> I'm not really sure about changing it What do you mean? Does your request at https://github.com/astropy/astropy-project/issues/435#issuecomment-2239194529 still stand or you have a different request now?

Whatever you chat about, please take high-level notes, @astrofrog and/or @svank , because I think we need a real maintainer onboarding guide!