Ways of work: create project and documentation

[Davsarper]

Based on the strategy session and following discussion with the team, create a project and repository structure with associated documentation.

• Design repos structure
• Design issue and their use
• Create project and associated views
• Create and customize project fields and issue labels
• Write document laying out Ways of work

[Davsarper]

• Created issue templates
  • Created milestones
  • Draft issues for all goals agreed on strategy meeting
  • New board to rule them all https://github.com/orgs/alan-turing-institute/projects/111/views/1
  • Currently writting up an explanation on the proposed way to use it, hope to finish (the draft) by monday https://github.com/alan-turing-institute/data-safe-haven-team/blob/main/WaysofWork.md
  • Would like use co-working time to present and discuss
• Created issue for event planning: Events plan and budget #42
  • Need to work on it together (not necessarily at the same time)

[Davsarper]

Being open: what to make public?

• Public
• Private
  • Personal plans, travel, details
  • Finance codes

Project board

There is a project board for stories and one for tasks, how much do you want to focus on the hackmd updating and how much on the boards? Should we use them during the meeting?

Questions, feedback and changes from captured in previous conversations:

• Do we need to open an issue for everything we do? How much time does that take? We already have issues and places to update them, to update in yet another place can be burdensome.
• What about other repos, especially repos not owned by the Turing org?
• Will people appreciate being pinged in our project management repo?
• What happens when we have information we can’t or shouldn’t share publicly?
• Take FTE effort from body of template if it is already in Project fields
• How to reflect work done by those not directly accountable, but responsible -> This could be done by specific tasks within the story, with assigned effort?