Add cycle 5 #481
Draft
Add cycle 5 #481
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Erik Tollerud <[email protected]>
Add more details
Updated the project/work section to clarify deliverables and revised budget details for sub-awards. Added specific period of performance for Cycle 5.
Revise template for Cycle 5 proposal calls
Removed clarification about matching roadmap as a goal.
Removed TODO items for updating numbers and adding SPOC role.
Updated selection criteria for funding requests to emphasize alignment with the Roadmap and available effort.
Updated the funding request deadlines and related timelines.
mention SOW in template
Update funding amount section in cycle5.md
Co-authored-by: Adrian Price-Whelan <[email protected]>
Co-authored-by: Erik Tollerud <[email protected]>
Co-authored-by: Adrian Price-Whelan <[email protected]>
Co-authored-by: Erik Tollerud <[email protected]>
Revise Cycle 5 funding request guidelines
Cadair
reviewed
Oct 2, 2025
| The primary change for Cycle 5 (relative to Cycle 4) is that the [Roadmap](https://github.com/astropy/astropy-project/blob/main/roadmap/roadmap.md) will be used to determine funding priorities. In addition, as the maintainers of the roadmap, the Strategic Planning and Organizing Committee (SPOC) will participate in funding request review, solicitation, and selection. Also, due to funding uncertainties, the period of performance and budgets should be just one year, as opposed to multiple years. | ||
|
|
||
| # Funding goals | ||
| Funding requests (FR) should address items on the Astropy Project’s Roadmap. In particular, funding will be prioritized for “red” and “orange” roadmap items, which have been identified by the community as being high priority. |
There was a problem hiding this comment.
Is regular maintenance out of scope?
astrofrog
reviewed
Oct 6, 2025
| The primary change for Cycle 5 (relative to Cycle 4) is that the [Roadmap](https://github.com/astropy/astropy-project/blob/main/roadmap/roadmap.md) will be used to determine funding priorities. In addition, as the maintainers of the roadmap, the Strategic Planning and Organizing Committee (SPOC) will participate in funding request review, solicitation, and selection. Also, due to funding uncertainties, the period of performance and budgets should be just one year, as opposed to multiple years. | ||
|
|
||
| # Funding goals | ||
| Funding requests (FR) should address items on the Astropy Project’s Roadmap. In particular, funding will be prioritized for “red” and “orange” roadmap items, which have been identified by the community as being high priority. |
There was a problem hiding this comment.
Suggested change
| Funding requests (FR) should address items on the Astropy Project’s Roadmap. In particular, funding will be prioritized for “red” and “orange” roadmap items, which have been identified by the community as being high priority. | |
| Funding requests (FR) which address one or more items on the Astropy Project’s Roadmap will be prioritized, with proposals that include work towards “red” and “orange” roadmap items being prioritized the most, since these have been identified by the community as being the most critical. |
Or could say 'should address one or more' if we want to require they do
|
|
||
| We aim to achieve broad consensus before the vote. Requesters are encouraged to combine ideas and teams, modify, or withdraw FRs during the discussion period, as appropriate. Discussion is open to anyone; it is not restricted to voting members. | ||
|
|
||
| Voting members of the Astropy Project vote on the FRs using thumbs up/down on a dedicated comment. Every voting member of the Astropy Project has equal voting rights. |
There was a problem hiding this comment.
I think I asked this in the past, but are we going to actually check the votes against the voting member list? If so maybe could then also say "Non-voting members are free to vote on FRs, but these votes will not be included in the count to determine funding allocations"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the announcement for cycle 5 and relevent documents - the SPOC and finance have agreed this is good, with the important caveat that finance needs to get the lastest number for how much we plan to allocate (@kelle is planning to do this in the next few days). So I'm opening this as a draft until we have that number.