Github milestones give you another way to slice views of issues and are good for tracking progress towards a deadline.
To help get clarity about priorities for the remaining couple of weeks of the RAMP period and make sure everyone is aware of them I thought we could use this feature.
My suggestion is that we agree a few top level priorities for things to do before the end of July and make issues for them with this milestone and the "July goal" label (or similar). Then we ask key people planning work to add the milestone to existing issues that are essential for those priorities and to raise any missing ones. This should let us have a view of everything needed and check who is doing what without duplicating the detailed issues as they still exist in the relevant projects etc.
What do you think? Scope could be just the software / modelling work or broader but either way could discuss how to phrase those top level goals at the management meeting or just write some and discuss/refine after maybe.
Github milestones give you another way to slice views of issues and are good for tracking progress towards a deadline.
To help get clarity about priorities for the remaining couple of weeks of the RAMP period and make sure everyone is aware of them I thought we could use this feature.
My suggestion is that we agree a few top level priorities for things to do before the end of July and make issues for them with this milestone and the "July goal" label (or similar). Then we ask key people planning work to add the milestone to existing issues that are essential for those priorities and to raise any missing ones. This should let us have a view of everything needed and check who is doing what without duplicating the detailed issues as they still exist in the relevant projects etc.
What do you think? Scope could be just the software / modelling work or broader but either way could discuss how to phrase those top level goals at the management meeting or just write some and discuss/refine after maybe.