APE 24: Astropy Affiliated Packages with pyOpenSci (now APE 22)

[pllim]

Initial authors: @pllim @lwasser @WilliamJamieson @dhomeier

• Close Affiliated packages: Clarify last-updated field in policy astropy-project#350
• Close Update affiliated package precedures to state how potential reviewer list is updated astropy-project#340
• Close Have a roadmap to re-review existing affiliated packages astropy-project#139
• Fix Affiliated Package: Consolidate with pyOpenSci? astropy-project#334

TODO

• Start a draft APE during Scipy 2023.
• Finish filling in the text.
• Have co-authors proof-read and address feedback.
  • ✔️ Leah
  • ✔️ Derek
  • ✔️ William
  • ✔️ Moritz
• Open up to general comment period and address feedback. Done on 2023-10-23
• Address feedback from general comment period.
• Wait for CoCo decision. 2023-12-18: 2 abstained, 2 approved, 1 absent
• CoCo to update PR with decision and merge.
• ???
• Profit!!!

[eteq]

Alright, I'm happy with this, as is the rest of the coco. Merging!

[eteq]

Oops, I was supposed to do the decision rationale, etc in this PR but I'll just do it directly in main instead. My bad.

[pllim]

Thanks, all!

[eteq]

Not also this was renumbered to APE22 in 6964140

[pllim]

Wait... why is the APE number changed?

[pllim]

APE 22 is already claimed but just not merged:

• APE 22: Public API #85

Any chance you can change this back to original APE 24 to avoid confusion?

[pllim]

Also there is a typo in the rationale: commitee -> committee

[eteq]

@lwasser - I think I found the right ORCiD for you in https://doi.org/10.5281/zenodo.10581891, but let me know if any of that is wrong and I can fix the metadata!

[eteq]

Any chance you can change this back to original APE 24 to avoid confusion?

The procedure in the README covers this @pllim - the numbering is in merging order. the numbering prior to merging is to be thought of as preliminary.

(The backstory is that we were struggling with deciding what to do here, and then we wrote it into the instructions and no one seemed to mind... So if we want to change that it's just a matter of changing the README instructions. I don't have a terribly strong opinion other than "we should make sure the instructions are explicit about it and follow whatever they say at any given time")

[pllim]

🤪

[dhomeier]

I suppose the final renaming is only done right in the merge commit then – any special tricks how to do this?