Coordination Meeting 2024

[pllim]

Like #255 but for 2024 meeting, since I think collecting ideas on an issue had been pretty successful for the 2023 meeting.

2024 meeting wiki

Running notes from 2023 meeting

Project roadmap

[pllim]

@WilliamJamieson and @nstarman might propose a topic related to array API, though this depends on how stable the array API is by the time this meeting happens. Also see:

• units and constants and NEP 42 astropy#13460
• Cannot create a Quantity with the new numpy.array_api astropy#15071
• modeling should be compliant with numpy.array_api astropy#15072
• NDData should be compliant with numpy.array_api astropy#15073
• https://data-apis.org/array-api/latest/ (Scipy 2023 talk)

[jdswinbank]

Suggestions of SOC meeting, 2023-11-28:

• Ask new roles (e.g. community manager) to introduce themselves and tell us they have been / will be doing.
• Reports from funded projects

[pllim]

Re: ask new roles -- Also @taldcroft can report on mentoring progress.

[hamogu]

Suggestion for topic, coming out of the dev-telecon: Discussion of Science platforms (e.g. SciServer, ...) Do we recommend any? Do we want to maintain our own at some point? Do we want to test any? Do we need to do anything to make it work better? Or make it work less (evil_grin)?

[pllim]

@hamogu can provide a debrief on how that contracting work initiative has worked out. By this meeting, both contracts with Clément and Mridul would have ended. Also see:

• https://github.com/astropy/astropy-project/blob/main/finance/proposal-calls/cycle3/user-dev-support-rse.md

(If this counts as "funded projects" in #349 (comment) , then feel free to resolve this comment as duplicate. I was not sure. Thanks!)

[pllim]

Review and discuss @nstarman proposed APE 22 on Public API:

• Public API astropy-APEs#85

[pllim]

Exploratory implemetation of mypy in typing efforts (maybe it can drive some discussions on how to actually do this for real):

• Add mypy configuration file that ignores existing errors on a per-file and per-error basis astropy#15794
• Add a tox environment to run mypy for static type checking astropy#15815
• ci: mypy config astropy#16312

[pllim]

Princess Bride screening for the benefit of @dhomeier , as requested by @eteq .

[pllim]

Maybe a demo at the meeting?

@nstarman on 2024-01-16

Hi! I've created and am continuing to refine a GPT for Astronomy in Python using the Astropy ecosystem. I've trained it on (in order of priority) Astropy, the coordinated packages, and all affiliate packages. Here's the link if you want to try it out https://chat.openai.com/g/g-oucCOdFuw-astronomy-python-copilot. Let me know if there are any improvements you'd like to see!

Disclaimer (as reported by laurent.michel on that Slack conversation): Testing this API requires to sign-in for ChatGPT+ (20$/month).

[hamogu]

Quantity 2.0 (led by @nstarman):

• Quantity 2.0 astropy-APEs#91

PL edit: Maybe related?

• units and constants and NEP 42 astropy#13460

[pllim]

If this issue is still open:

• DOC: Make ruff less rough for new contributors astropy#16035

[pllim]

Astropy in the age of The Cloud (AWS):

• Do not include tests in Astropy wheels (reduce wheel size for AWS Lambda) astropy#16152
• BUG: Fix loading parser tabs on pyc-only installations astropy#16159

[kelle]

If anyone wants to work on this and needs support for the ChatGPT+ subscription, please post in #finance-committee on Slack or send an email to finance@astropy.org.

[pllim]

If there is still no consensus on this APE 0 term limit proposal by the meeting, I say we just put it to a vote at the Coordination Meeting and be done with it. Though I think as per policy, all the 5 current CoCo members are not allowed to vote accept/reject this.

• APE0: Coco term limits and Ombudsperson astropy-APEs#89