Possible process refinement for cobudget
- Common timeframe for co-budget projects. 3 month periods? We are currently in April-Jun.
- So we have a call for contributions and there is a cut off date. Then if projects are funded, they proceed and are labelled “funded” on co-budget.
- At the end of every month, toggle totals for that project are reported in the co-budget project. For example by editing the project and adding in an “update” (this is the responsibility of project sponsor).
- At the end of the project a total is reported and request for payment made (by project sponsor to contributors) (as per existing process).
- When paid, the co-budget project is labelled “paid” (as per existing).
- This means that ongoing projects like “code review and merge” could be partitioned into 3 month blocks for the purpose of tracking and acquitting payments.
- This process would still complemented by the “co-budget stewardship spreadsheet” – but the project initiation, progress and acquittal is made more transparent in co-budget itself?
Playing catch-up
- We need to start – if everyone agrees – by switching the “ongoing buckets to “April-June” timeframe.
- For this period, we suggest that everybody has until the end of the week (eg May 14) to update contributions in co-budget.
- Aus also needs to set-up a new bucket for “Standing Orders – unfunded”.
Specifics for Code Review and Merge bucket
- At end of every month update report in cobudget (eg from toggle) includes all PRs nos. that have been reviewed and/or merged ?