-
-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Coordination Meeting 2025 #430
Comments
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. |
Array API + Quantity 2.0 -- Lots of discussions at Coordination Meeting 2024. Any progress after a year? |
Did we implement anything discussed in the Are there big missing pieces? breakout at Coordination Meeting 2024? |
Annual roadmap discussions.
|
Strategic Planning Role -- If we ended up filling the role after Coordination Meeting 2024, did it work? |
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! |
Reports from projects that got money from Astropy since the last Coordination Meeting (Cycle 4?). |
Celebrate getting 2025 Lancelot M. Berkeley–New York Community Trust Prize for Meritorious Work in Astronomy from AAS. Press releases:
Maybe also celebrate the 10k citation when it got a press release too: |
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) |
Re: #430 (comment) @adrn -- Is that already an issue somewhere? |
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 |
Like #349 but for 2025 meeting.
2025 meeting wiki
Running notes from 2024 meeting
Project roadmap
The text was updated successfully, but these errors were encountered: