-
Notifications
You must be signed in to change notification settings - Fork 0
Planning meeting 2023 03 08
Kenneth Hoste edited this page Mar 8, 2023
·
2 revisions
see https://github.com/multixscale/WP_1_5
(Caspar + Kenneth)
- fine-grained things to do in scope of WP1+5 tasks
- assign issue to who's working on it
- used for internal planning
- specficies (soft) target end date
- determined by need for this issue in function of other issues
- modify end date when issues is finished?
- automatically using a bot?
- only set when task has actually started
- M3/6/9/12/...
- indicates by when issue MUST be done
used for filtering (in issue list, project board)
- Tasks (T1.1, ...)
- Deliverables (D1.1, ...)
- Work Package (WP1, WP5)
- overall roadmap, grouped by milestones: https://github.com/orgs/multixscale/projects/1/views/3
- T1.1 roadmap, grouped by milestones: https://github.com/orgs/multixscale/projects/1/views/9
- D5.2 roadmap, grouped by milestones: https://github.com/orgs/multixscale/projects/1/views/7
- Complete list of issues for WP5 (Kenneth)
- Create missing labels for WP5 (tasks + deliverables)
- Create milestones M3/M6/M9/M12/... + assign each issue to a milestone (Caspar)
- WP1 (Caspar)
- WP5 (Kenneth)
- Set soft target end dates for all issues
- for issues that do not have a clear deadline, use end date of task
- WP1 (Caspar)
- WP5 (Kenneth)
- Create missing project boards (kanban or roadmap?)
- one per task (using label filter)
- WP1: T1.1, T1.2, T1.3 (Caspar)
- WP5: T5.1, T5.2, T5.3 (Kenneth)
- one per deliverable due in M12
- WP1: D1.1, D1.2 (Caspar)
- WP5: D5.1, D5.2 (Kenneth)
- one per task (using label filter)