Skip to content

Conversation

@bsipocz
Copy link
Member

@bsipocz bsipocz commented Nov 1, 2025

This is proposal is very much a draft and will benefit from discussions at the upcoming IVOA interop.

Also, no language tuning was made, sending through the AI machinery could improve the fluff.

@tomdonaldson @andamian -- I mentioned 3 of us in the text as it's clear we cannot take on contracts so at best we can coordinate this project (by definition, if we do it well, it should not add much burden on the existing maintainers team).

Also, cc @ManonMarchand and @msdemlei, I hold on hope that you could take on the contract if it's selected, but either way, let's discuss it in Görlitz

@bsipocz bsipocz marked this pull request as draft November 1, 2025 00:31
@ManonMarchand
Copy link
Member

ManonMarchand commented Nov 13, 2025

As discussed, here are the estimates from yesterday -- to be discussed/edited freely:

Week(s) of work

astropy/astropy#17098
astropy/astropy#12416
astropy/astropy#9646
astropy/astropy#18893
astropy/astropy#17257
astropy/astropy#18728
astropy/astropy#8911
astropy/astropy#18057
astropy/astropy#17949
astropy/astropy#17224
astropy/astropy#8705
astropy/astropy#16314
astropy/astropy#15352 seems similar to astropy/astropy#7036
astropy/astropy#15194 and astropy/astropy#15172
astropy/astropy#14505
(object dtypes) astropy/astropy#7480 and astropy/astropy#12892
astropy/astropy#6798 (to read again now that masked values are different in astropy)

Month(s) of work

astropy/astropy#8995
astropy/astropy#9433
astropy/astropy#1248 (requires writting an STC parser, a nice internship project ?)
astropy/astropy#7259 (refactoring)
astropy/astropy#15472
astropy/astropy#15394

Months of work (one bundle)--these issues are all about making votable more integrated in astropy's systems)

astropy/astropy#9960
astropy/astropy#18402
astropy/astropy#17986
astropy/astropy#3822
astropy/astropy#8725

Long and complex issues (often performance)

astropy/astropy#8946
astropy/astropy#18729
astropy/astropy#14577
astropy/astropy#8191

need some review from us

astropy/astropy#18454 and astropy/astropy#18442 (linked to astropy/astropy#6519 ?)

Unclear solution (decision/discussion needed)

astropy/astropy#18667
astropy/astropy#18516
astropy/astropy#11092
astropy/astropy#18277
astropy/astropy#18167
astropy/astropy#18000
astropy/astropy#15429
astropy/astropy#10389
astropy/astropy#8978

Upstream fix/update needed

astropy/astropy#18059
astropy/astropy#9414
astropy/astropy#18515

@bsipocz
Copy link
Member Author

bsipocz commented Nov 13, 2025

thank you so much @ManonMarchand!

@pllim
Copy link
Member

pllim commented Nov 13, 2025

I don't want to accidentally both the beautiful list above, so just FYI that if you turn them into bullet points, GH will render also the issue titles and state (close/open) for easier future reading.

@bsipocz
Copy link
Member Author

bsipocz commented Nov 13, 2025

Yeap, I can reformat, we just pulled the list out of a slack thread so others can see it.

@bsipocz
Copy link
Member Author

bsipocz commented Nov 13, 2025

Apparently I'm unable to edit that cell, but anyways, some of the actual details will go into the actual text in this PR.

@pllim
Copy link
Member

pllim commented Nov 13, 2025

(Reposting the comment above but as lists, in case it helps.)

@ManonMarchand

As discussed, here are the estimates from yesterday -- to be discussed/edited freely:

Week(s) of work

Month(s) of work

Months of work (one bundle)--these issues are all about making votable more integrated in astropy's systems)

Long and complex issues (often performance)

need some review from us

Unclear solution (decision/discussion needed)

Upstream fix/update needed

@kelle
Copy link
Member

kelle commented Nov 18, 2025

This FR still needs a budget.

@kelle
Copy link
Member

kelle commented Nov 18, 2025

It looks like y'all are already thinking about this, but want to explicitly say that it would be useful to see a budget range.

@AnaGabela
Copy link
Contributor

Please react to this comment to vote on this proposal (👍, 👎, or no reaction for +0).

@bsipocz bsipocz marked this pull request as ready for review November 25, 2025 16:35
@eteq
Copy link
Member

eteq commented Dec 8, 2025

The Cycle 5 funding request process has been hugely successful! On the downside, that means our funds are severely oversubscribed. Even after the Finance Committee and SPOC have taken into consideration community feedback/voting and alignment with the roadmap, there are still more funding requests than we can afford in 2026.

We would like to stretch the budget as far as possible, and to fund as many activities as possible, while making sure the Project remains volunteer-driven. Hence, we would like to know if this project will still meet its deliverables if minimum your budget is reduced by 25%, 50%, or 100%. Or if there’s some other minimum, feel free to specify that instead.

As a reminder, there will be more funding for 2027 and we expect the Cycle 6 call for 2027 funding requests to begin in the Fall of 2026.

Thank you for your engagement and understanding as we continue to optimize our funding and budgeting processes and the balance of volunteer vs funded work! (@bsipocz)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants