-
-
Notifications
You must be signed in to change notification settings - Fork 46
Cycle5: Improving astropy vo and votable capabilities #500
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
base: main
Are you sure you want to change the base?
Conversation
|
thank you so much @ManonMarchand! |
|
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. |
|
Yeap, I can reformat, we just pulled the list out of a slack thread so others can see it. |
|
Apparently I'm unable to edit that cell, but anyways, some of the actual details will go into the actual text in this PR. |
|
This FR still needs a budget. |
|
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. |
|
Please react to this comment to vote on this proposal (👍, 👎, or no reaction for +0). |
|
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) |
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