|
4 | 4 | # Changes relative to the previous cycle
|
5 | 5 |
|
6 | 6 | 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) |
| 7 | +* COTR wording needs proofreading |
| 8 | +* Dates need updating |
| 9 | +* Budget amount |
| 10 | +* Template needs updating |
10 | 11 |
|
11 | 12 |
|
12 | 13 | # Funding goals
|
@@ -71,12 +72,30 @@ Once selection is completed, an FR that is *not* selected does not continue furt
|
71 | 72 |
|
72 | 73 | If an FR *is* selected, 🎉! Now the work begins.
|
73 | 74 |
|
74 |
| -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 for that FR. |
| 75 | +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. |
75 | 76 |
|
76 |
| -DESCRIPTION OF PROCESS FROM CYCLE 3, BUT WITH THE COTR RESPONSIBILITIES ADDED |
| 77 | +The following general steps follow whan an FR is selected: |
| 78 | + |
| 79 | +1. The FR is assigned a final budget and funding source, and the PR is merged. |
| 80 | +2. A new tracking issue is created for the FR (by the finance committee member contact), which includes identifying the COTR. |
| 81 | +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). |
| 82 | +4. As work is completed, the funded personnel or their institutional representative submit invoices via OpenCollective (exact details of this will be clarified for each issue as details vary from person-to-institution). |
| 83 | +5. The issue is closed when the FR's work is completed, the budget is exhausted, or the period of performance expires. |
77 | 84 |
|
78 | 85 | 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.
|
79 | 86 |
|
| 87 | +# COTRs |
| 88 | + |
| 89 | +New this Cycle, all proposals will be assined 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. |
| 90 | + |
| 91 | +COTR's key responsibilities include: |
| 92 | + |
| 93 | +* Technical expertise: They are experts in the contract's specific area, evaluating the contractor's performance with their technical knowledge. |
| 94 | +* Contract compliance: COTRs monitor and ensure the contractor follows contract terms, reviewing deliverables to meet expected Astropy community standards. |
| 95 | +* Performance evaluation: COTRs assess contractor performance, verifying the work meets contract expectations. |
| 96 | +* Issue resolution: COTRs play a role in resolving issues or disputes, collaborating with the finance committee, the Coordination Committee, and the broader Astropy Project. |
| 97 | +* Communication and reporting: Acting as a liaison, COTRs ensure transparent communication, and reporting progress and issues (see above). |
| 98 | + |
80 | 99 |
|
81 | 100 | # Fostering constructive discussion
|
82 | 101 |
|
|
0 commit comments