Coordination Meeting 2025

[pllim]

Like #349 but for 2025 meeting.

2025 meeting wiki

Running notes from 2024 meeting

Project roadmap

[pllim]

If we try something from https://astropy-dei.orgmycology.com/ after Coordination Meeting 2024, should report back on what we tried and whether it worked.

[pllim]

Array API + Quantity 2.0 -- Lots of discussions at Coordination Meeting 2024. Any progress after a year?

[pllim]

Did we implement anything discussed in the Are there big missing pieces? breakout at Coordination Meeting 2024?

[pllim]

Annual roadmap discussions.

• Update from last year: Roadmap 2024 #433

[pllim]

Strategic Planning Role -- If we ended up filling the role after Coordination Meeting 2024, did it work?

[pllim]

Note for SOC: If the LOC plans to do a press release about this meeting, should add a "are you okay with your photo being used" question in the registration form. Thanks!

[pllim]

APE 22 follow-up (if necessary):

• APE 22 follow-up: Candidates for pyOpenSci trial review period astropy.github.com#571
• Coordinated Packages also submit to PyOpenSci review as per APE 22 #437

[pllim]

Reports from projects that got money from Astropy since the last Coordination Meeting (Cycle 4?).

[pllim]

Celebrate getting 2025 Lancelot M. Berkeley–New York Community Trust Prize for Meritorious Work in Astronomy from AAS.

Press releases:

• https://aas.org/press/astropy-collaboration-receive-2025-berkeley-prize
• https://www.stsci.edu/contents/news-releases/2024/news-2024-401

Maybe also celebrate the 10k citation when it got a press release too:

• 10k citation action items #431

[adrn]

In addition to the array API bullet, it would be useful to resurrect the discussion of creating a "Quantity/unit API" analog to the array API (cc @mhvk @nstarman @jeffjennings)

[pllim]

Re: #430 (comment)

@adrn -- Is that already an issue somewhere?

[adrn]

I don't know if it's an issue or an email thread or a section of a google doc or a discussion in a separate issue, but @mhvk or @nstarman might remember :).

[mhvk]

Discussion so far has been mostly about Quantity 2.0, at astropy/astropy-APEs#91 - there hasn't been much discussion about a units API beyond astropy/astropy#8210

[pllim]

@astrofrog -- Hack session to reconsider layout of current astropy documentation landing page.

[pllim]

Leverage https://github.com/scientific-python/sync-teams-action to automate project team membership and access? Would like to discuss pros, cons, security implications specific to our project.

[nstarman]

Switching to Meson build system?
My primary motivation is that it would be incredible if Astropy could automate the release process to the point that bugfix releases could be done on a small-n group of bugs basis.
Also, match scipy and other leaders of the ecosystem.
We can also then leverage useful tools from scientific-python like spin to ensure that we have a consistent CL regardless of the tool, e.g. if we ever switch from tox to nox people could use the nox command if they want OR not have to learn anything new because we use spin.

[nstarman]

Idea 2: Hack day using LLMs to rewrite some of our various C(ython,++,#,?) codes into a single framework, probably whichever best supports Numpy.

[nstarman]

Idea 3) Build a feature release & planned refactors GH Project board. Then we can see what everyone in Astropy thinks needs improving / adding to.

[Cadair]

My primary motivation is that it would be incredible if Astropy could automate the release process to the point that bugfix releases could be done on a small-n group of bugs basis.

I am +1 on this, but I don't think it would involve swapping build system, we could almost certainly automate most of the drudgery with actions.

[pllim]

Re: automate release -- What exactly needs to be automated still? We already use the publish workflow from OpenAstronomy. Things like website update and community announcement are still manual but a matter of copy paste.