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?

• Planning the Strategic Planning Committee #461

[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
• Should we set up a retirement plan for unmaintained affiliated packages under the old scheme as well?

[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

(More seriously, can be part of "State of Astropy" update.)

[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)

[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.

• BLD: Switch to meson build system astropy#17760

[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.

• Automated bugfix release astropy#12889

[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.

• Automated bugfix release astropy#12889

[pllim]

@dhomeier -- Update code recommendation for Unicode

• Update and extend recommendations on Unicode usage in Coding guidelines astropy#17731

[eli-schwartz]

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.

The main advantage that SciPy sought from switching to meson wasn't about automating the release process but rather more reliable and speedier builds :) especially because setuptools is effectively impossible to really parallelize whereas meson is extremely parallelizable.

[pllim]

New policy discussion -- removing roles

• New policy to remove roles #462

[dhomeier]

GSoC – 2025 applications are already closed; is there interest in mentoring projects for 2026 and demand for an Astropy coordinator?

[astrofrog]

Re: automate release -- What exactly needs to be automated still?

I mean in principle bugfix releases could be completely automatic and happen periodically if there are new backports to the release branch

EDIT by pllim: Conversation moved to astropy/astropy#12889

[pllim]

astropy user survey

Action item for the meeting: @jeffjennings (or his colleagues involved in the survey) could present survey results.

As posted on https://groups.google.com/g/astropy-dev/c/5JqGiadcufw

Example announcement:

The Astropy Project is running its first user survey! Please take 15 minutes to give your input before April 1 to help us better understand how astropy is being used, how it can be improved, and how we can best continue to support the astronomy and scientific research communities. Thank you in advance for helping us shape the future of Astropy!