List view
Below is one way to adapt the planning spreadsheet for sustained team use. At the top level, we would create GitHub milestones (on some agreed-on repository) that document the big, high-priority things requiring advance planning. Then listing all the milestones produces a simple dashboard on the team's status. Supporting each milestone, we could optionally create GitHub issues that document important sub-tasks towards milestone completion. We could also assign each issue/sub-task to any team members. These issues would allow us to measure progress on each milestone. If we wanted a more sophisticated dashboard than just listing the milestones, we could use GitHub projects (as suggested by John Owens) to display a spreadsheet-like view of any issues we wanted.
Overdue by 2 year(s)•Due by March 17, 2023Approximate date for workshop on teaching performance engineering.
Overdue by 2 year(s)•Due by July 7, 2023•0/5 issues closedMIT deadline for NSF CCRI proposal.
Overdue by 2 year(s)•Due by July 14, 2023MIT deadline for NSF POSE Phase II proposal.
Overdue by 2 year(s)•Due by August 30, 2023•0/1 issues closedSpeedCode tutorial in Orlando, FL.
Overdue by 2 year(s)•Due by June 16, 2023•0/3 issues closedCSAIL Alliances HPC Day for US government agency.
Overdue by 2 year(s)•Due by April 26, 2023Proposals due July 7, 2023. Sessions are Nov 14-16. Probably an open-source roadmap, pertaining broadly to performance engineering.
Overdue by 2 year(s)•Due by November 14, 2023•0/6 issues closed