Add cycle 5

finance/proposal-calls/cycle5/cycle5.md

@@ -0,0 +1,108 @@
+# Cycle 5 funding requests and ideas
+
+# Changes relative to the previous cycle
+
+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.
+
+FRs shall foster the Astropy Project goals of community, shared work, and cooperation and shall be described, reviewed, and executed in this manner.
+
+# Funding amount
+
+We anticipate a maximum of **$XXX,XXX** (US) to be available for this funding cycle. 
+
+# Period of Performance
+
+The period of performance should be for one year. Ideally, Jan 1–Dec 31, 2026.
+
+# What can the funding be used for?
+
+Money can be used for travel, subscriptions, etc, in addition to direct financial support to individuals, including individuals based outside of the United States.
+
+Funding requests may be submitted even if they include the recruitment and hiring of another person to complete the task. See below: Open Hire Process.
+
+The funds currently come from a NASA ROSES grant. NumFocus, the Project’s fiscal sponsor, and the Finance Committee assume responsibility for ensuring that all budgets are consistent with any applicable funding agency rules.
+
+# Funding Request Process Overview
+
+We envision a two stage FR process to enable the community to discuss and improve ideas, to merge teams with similar ideas, and for the SPOC to ensure as much of the Roadmap as possible is being addressed.
+
+* Oct 17, 2025: **_Draft_** FR Deadline 
+* Three week iteration and discussion period during which draft FRs can be fleshed out and modified. During this time:
+  * The SPOC may submit and/or solicit new proposals that fill gaps not addressed by the initial round of requests. 
+  * The Finance Committee will review budgets and may provide feedback and/or request more information. 
+* Nov 7, 2025: Finalized FRs are due, two week Voting period begins
+* Nov 24, 2025: The SPOC and Finance Committee will work together to select funding requests and allocate budgets. 
+* Dec 8, 2025: Announcement of selected FRs. Drafting contracts begins.
+* Jan 1, 2026: Work commences
+
+Note that these dates are nominal, and unplanned events like a government shutdown could extend some of the dates/deadlines.
+
+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.
+
+The Coordination and Finance Committees will select FRs based on the voting results, alignment with the Roadmap, confirmation of available people to implement, and available funds.
+
+# How to Submit a Funding Request
+Funding Requests (FRs) should be posted as pull requests to https://github.com/astropy/astropy-project/ with the initial title text "Cycle 5 Funding:". The goal is to make this process as easy as possible for everyone, so we impose a limit of 100 lines assuming 80 char/line. We provide a template: [Cycle 5 template](https://github.com/astropy/astropy-project/tree/main/finance/proposal-calls/cycle5/template.md). Please place the file with your FR in the [cycle 5 folder](https://github.com/astropy/astropy-project/tree/main/finance/proposal-calls/cycle5/), the same location as the template.
+
+# Post-request process
+
+Once selection is completed, an FR that is *not* selected does not continue further, although it can always be re-proposed. It is also possible that if more funds become available before the next cycle, a proposal may be accepted later but with a revised timieline.
+
+If an FR *is* selected, 🎉! Now the work begins. 
+
+Once a proposal is accepted, the Finance Committee will assign a committee member contact to ensure invoices are submitted, process is followed, etc.  At the same time, the Coordination Committee will assign a COTR (see below) for that FR.
+
+The following general steps follow whan an FR is selected:
+
+1. The FR is assigned a final budget and funding source, and the PR is merged.
+2. A new tracking issue is created for the FR (by the finance committee member contact), which includes the budget, period of performance, and identifies the assigned COTR.
+3. Work updates are given in the tracking issue, although out-of-band clarifications/conversations with the finance committee contact or COTR are welcome. It is the responsibility of the COTR to ensure these updates happen (although they don't necessarily need to be done by the COTR themselves).
+4. As work is completed, the funded personnel or their institutional representative submit invoices to NumFocus.
+5. The issue is closed when the FR's work is completed, the budget is exhausted, or the period of performance expires.
+
+# COTRs
+
+As in last Cycle, all proposals will be assigned a COTR (Contracting Officer's Technical Representative).  This concept is borrowed from government funding agencies, although it is to be stressed that Astropy's goal is to make the COTR role as low-overhead as possible.
+
+COTR's key responsibilities include:
+
+* Technical expertise: COTRs are experts in the contract's specific area, evaluating the contractor's performance with their technical knowledge.
+* Contract compliance: COTRs monitor and ensure the contractor follows contract terms, reviewing deliverables to meet expected Astropy community standards.
+* Performance evaluation: COTRs assess contractor performance, verifying the work meets contract expectations.
+* Issue resolution: COTRs play a role in resolving issues or disputes, collaborating with the finance committee, the Coordination Committee, and the broader Astropy Project.
+* Communication and reporting: Acting as a liaison, COTRs ensure transparent communication, and reporting progress and issues (see above).
+
+
+# Fostering constructive discussion
+
+We want to stay true to the "radical transparency" ethos of the Project and thus we are asking the community to comment on the FRs publicly. At the same time, we want to ensure that the conversations stay as constructive as possible to foster the Astropy Project’s commitment to maintaining a positive and welcoming culture. Thus, here we provide some example language that might help commenters stay constructive with their comments.
+
+Example of non-constructive comments are:
+
+* “This is not worth our time.”
+* “Person X has never really done anything that I think is good.”
+
+Examples of constructive comments are:
+
+* “This is probably not a good way to spend Project funds because package abc already provides the same functionality.”
+* “It's not clear to me the value that this would bring to the Project. Do the proposers have a way of assessing impact?"
+* “I’m concerned the project team does not have the necessary skills to get this done. Can the team offer more proof of expertise, or bring in help from team members who have more relevant expertise?"
+
+If you are worried about your comments being perceived as inappropriate, you are welcome to send your feedback directly to the Finance Committee at finance@astropy.org or ask on Slack. You are also welcome to use the “thumbs down” vote without adding comments. If you have any concerns about this process and the ensuing discussion that you would prefer to discuss privately, contact the ombudsperson at confidential@astropy.org.
+
+
+# Open hire process
+
+FRs can include an “open hire” process to identify people to undertake the activities described. Should such a request be accepted, the Finance Committee will organize a recruitment process to find the right person (or people) to carry out the work. Members of the FR team will be asked to assist in the recruitment and hiring process. The number of open hire requests selected may be limited by Finance Committee staffing availability.
+
+We envision a recruitment process that expands beyond the US Astronomy community and would include the various Research Software Engineering forums in addition to the AAS Job Register. We are in the process of putting together a hiring guide.
+
+
+# Template and examples
+
+The following is a template proposal: [template.md](template.md). We also include an [example](example_draft_FR.md) that is an acceptable **Draft** FR (due March 1) to emphasize that drafts can include minimal information and are meant to be fleshed out and modified based on feedback before the final deadline (March 22). You can also refer to successful Cycle II/3/4 **Finalized** FRs at [this link](https://github.com/astropy/astropy-project/tree/main/finance/proposal-calls/2021-proposal), [this one](https://github.com/astropy/astropy-project/tree/main/finance/proposal-calls/cycle3), or  [this one](https://github.com/astropy/astropy-project/tree/main/finance/proposal-calls/cycle4)  .

finance/proposal-calls/cycle5/template.md

@@ -0,0 +1,31 @@
+### Title
+
+### Project Team
+Describe who is expected to work on the project. If work will be undertaken by an open hire instead of (or in addition to) other project members, please indicate that here.
+
+### Project Description / Scope of Work
+Briefly describe how this work will benefit Astropy packages / users / community. 
+This section, including the below subsections, will be used as the Scope of Work in the resulting contracts funding approved FRs. 
+
+#### Roadmap Items
+List which [roadmap](https://github.com/astropy/astropy-project/blob/main/roadmap/roadmap.md) item(s) this work will help address?
+
+#### Project / Work / Deliverables
+Provide the details of the planned work so that the Astropy community members will understand what is planned. This should include a description of expected specific results and/or deliverables.
+
+### Approximate Budget
+Currency: US $
+The approximate budget should be specified in USD. However, we are open to spending funds internationally. Budgets should be converted to USD using a plausible exchange rate.
+
+Include overheads, fringe, etc. if money is paid as sub-award to an institution.
+
+- Salary / contractor fees etc. (give sum here, details about contract, payment method (contract/sub-award) etc. can be worked out with the finance committee later)
+- TOTAL
+
+Please note that we would happily accept budget items other than the above.
+
+Travel and conference registration should be submitted separately from this funding request, as needed.
+
+### Period of Performance
+
+List the expected range of time the budget should be allocated for. For Cycle 5, the ideal period of performance is Jan 1, 2026–Dec 31, 2026.