Skip to content

Commit db7ded2

Browse files
authored
Additional updates
1 parent f45692d commit db7ded2

File tree

1 file changed

+17
-9
lines changed

1 file changed

+17
-9
lines changed

finance/proposal-calls/cycle4/cycle4.md

Lines changed: 17 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,9 @@
44
# Changes relative to the previous cycle
55

66
TBD ...
7+
* COTR exist, are needed for each FR
8+
* Only one funding source
9+
* PoP should be specified, can be longer (should be for subcontracts)
710

811

912
# Funding goals
@@ -17,29 +20,36 @@ FRs need to clearly identify how the the funding will be used (e.g. "pay $YYY (U
1720

1821
# Funding amount
1922

20-
We anticipate a maximum of **TBD** (US) to be available for this funding cycle. This is significantly larger than previous cycles. This means that approved funding requests in this cycle may be limited more by the available time of current community members rather than by the amount of funding available. We therefore urge the community to **aim high**, either by ambitious and/or expensive proposals for their own work, or by bringing in new members via the “open hire” process that is new in this cycle (outlined below).
23+
We anticipate a maximum of **TBD** (US) to be available for this funding cycle. We urge the community to **aim high**, either by ambitious and/or expensive proposals for their own work, or by bringing in new members via the “open hire” process (outlined below).
24+
25+
# Period of Performance
26+
27+
Each FR should specify how long the project will last (the "Period of Performance"). A project can be anywhere from 1-3 years. For ongoing projects longer periods of performance are better, as that lowers the administrative overhead of the project. In particular, FRs for subawards are best done with longer periods of performance e.g. 3 years.
28+
29+
Note that if your proposal has a longer Period of Performance than one year, funds beyond that horizon are contingent on funds from the project being available.
2130

2231

2332
# What can the funding be used for?
2433

2534
Money can be used for travel, subscriptions, etc, in addition to direct financial support to individuals.
2635

27-
The funds come from two grants: a [Moore Foundation Data-Driven Discovery Grant](https://www.moore.org/grant-detail?grantId=GBMF8435) and a NASA ROSES grant.
36+
The funds currently come from a NASA ROSES grant. It includes the following general areas:
2837

29-
* Both grants include funds for basic maintenance and development on all aspects of the Project.
30-
* The Moore grant has a focus on mentoring and spectroscopy,
31-
* The NASA grant has a focus on support for project-wide infrastructure, affiliated packages, and Learn.
38+
* Basic maintenance and development on all aspects of the Project
39+
* Project-wide infrastructure
40+
* Affiliated packages
41+
* Astropy Learn and Community Engagement
3242

3343
The Finance Committee assumes responsibility for ensuring that all awards made are consistent with any applicable funding agency rules.
3444

3545

3646
# Funding Request process
3747

38-
Funding Requests (FRs) should be posted as pull requests to https://github.com/astropy/astropy-project/ with the initial title text "Phase 3 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 below. Please place the file with your FR at https://github.com/astropy/astropy-project/tree/main/finance/proposal-calls/cycle3 (the same location as the template).
48+
Funding Requests (FRs) should be posted as pull requests to https://github.com/astropy/astropy-project/ with the initial title text "Cycle 4 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 below. Please place the file with your FR at https://github.com/astropy/astropy-project/tree/main/finance/proposal-calls/cycle4 (the same location as the template).
3949

4050
We envision a two stage FR process to enable the community to discuss and improve ideas, teams with similar ideas to merge, etc.
4151

42-
52+
TBD: THE DATES NEED UPDATING FOR CYCLE 4
4353

4454
* DATE1: **_Draft_** FR Deadline (new requests after this date will not be reviewed this cycle)
4555
* Six week iteration and discussion period during which draft FRs can be fleshed out and modified
@@ -65,8 +75,6 @@ Once a proposal is accepted, the finance committee will assign a committee membe
6575

6676
DESCRIPTION OF PROCESS FROM CYCLE 3, BUT WITH THE COTR RESPONSIBILITIES ADDED
6777

68-
Given the added administrative complexity of sub-awards, FRs for subawards are best done with periods of performance longer than a year if possible.
69-
7078
Note that if your proposal has a longer Period of Performance than one year, funds beyond that horizon are contingent on funds from the project being available.
7179

7280

0 commit comments

Comments
 (0)