Coordination Meeting 2026 Topics

[taldcroft]

Issue for proposing and discussing topics for the 2026 Astropy Coordination Meeting at SKAO in the UK. This is like #430 from 2025.

2026 Meeting Wiki (in work)

Running notes from 2025 meeting

Project Roadmap

[pllim]

Topic suggestion: Start and fund a campaign to back up issue and PR discussions outside of GitHub. This can be achieved using either REST API or GraphQL, though some investigation is needed to see if linked issues/PRs need special handling or not. It has to be done gradually to avoid rate limits. And once the current stuff is backed up, it has to keep running to keep up with new contents going forward.

Motivated by https://ziglang.org/news/migrating-from-github-to-codeberg/

• Back up issue and PR discussions outside of GitHub #529

Copied from #472 (comment)

[pllim]

Topic suggestion: Move our dev wheels from https://pypi.anaconda.org/astropy/simple to https://pypi.anaconda.org/scientific-python-nightly-wheels/simple . This would affect:

• astropy
• photutils
• regions
• reproject
• astropy_healpix

These will NOT be moved over as they seem unmaintained and not really Coordinated nor core:

• semantic_version
• gala
• python_abi
• astroalign
• agnpy

Additionally, reach out to https://pypi.anaconda.org/liberfa/simple to see if they want to follow suit.

Copied from #472 (comment)

[pllim]

Different way to load constants

• Load CODATA constants from text files astropy#19786 for What constants to have and which to calculate astropy#3843

Proposal: Load from text file
Counter-proposal from Marten: Should we vendor their (scipy's) parser? Finally make scipy a required dependency?

[neutrinoceros]

Migrating away from Google services (Gmail, Google Docs...)

[neutrinoceros]

Assessing the effectiveness of our recently adopted AI policy.

[neutrinoceros]

An update on Free-Threading and the state of the ecosystem in Python 3.15

[neutrinoceros]

Ways to reduce our dependency on GitHub (Microsoft) free compute (GHA).

[neutrinoceros]

Re-assessing our linting strategy: moving ruff config to a set of opt-ins instead of opt-outs ?

[neutrinoceros]

An update on modern type checkers (ty, pyrefly, zuban ?) and their applications for improved guarantees around correctness.

[astrofrog]

Ways to reduce our dependency on GitHub (Microsoft) free compute (GHA).

Related: Archiving (as in backup) of the project and starting to make contingency plans for moving away from GitHub

[pllim]

@astrofrog isn't your #535 (comment) a duplicate of my #535 (comment) above?

[neutrinoceros]

moving away from codecov.io and what to replace it with. We could switch to a different service, or use standalone GHA.
More radically, we could move from measuring test coverage to measuring type coverage, which is far lower now, but much easier to measure as it doesn't require running the code (typestats). It doesn't need to be a replacement, it could also be lower-maintainance complement.

[pllim]

Re: #535 (comment)

@neutrinoceros do you mean using this instead?

• Add support for doing code coverage reporting entirely on GitHub OpenAstronomy/github-actions-workflows#189