# Documentation & Governance Days Plan

## Summary

The Documentation & Governance Days will follow a similar, but softer, structure to the [Turing Way Book Dashes](https://the-turing-way.netlify.app/community-handbook/bookdash.html).

It will focus on both:
- Governance and processes
- Documentation (for instance, contributing files, README, website docs etc.)

Over the course of three days, we will run 2x 2.5 hour slots per day for members of the community to come and help us either:
- Review and iterate docs we have created
- Write new docs that haven't been created yet

The idea will be to have a 'hack week' where the community can join whenever they can to contribute to the first version of these documents, leaving enough time for us to synthesize contributions down into a first version by the March meeting.

### Aim

1. Have live, open documents for our governance processes and any community documentation, ready to be synthesized and finalised for the March community meeting.
2. Engage the community in co-creating our key documentation and governance processes

## Logistics
### Time/date
- Thursday 29th Feb 14:00 - 16:30
- Monday 4th Mar 14:30 - 17:00
- Tuesday 5th Mar Feb 10:00 - 12:30

### Location
- Fully online

### Number of people
- Any!

### Resources required
- Open files (e.g. Google Docs) for all key processes
- Diagram outlining connection between processes

## Agenda
The agenda for each session will look like the following:

1. Attendees comes together to announce progress on docs so far
2. Attendees are presented with the current work that could be done. This includes:
- **Write**: Create the first version of a particular document
- **Review**: Review a pre-created document
3. Attendees select what they would like to work on, and breakout rooms are created
4. Attendees join the relevant breakout rooms, and work for x minutes together
5. Attendees come back together to wrap up from breakoout rooms and give a progress update
6. Break
7. Repeat from step 1

In between sessions the CMWG synthesizes progress and prepares the current work to be done for the next session

| Time | Activity |
| ---- | -------- |
| 0 - 10 mins | Intro |
| 10 - 15 mins| Deciding breakout rooms |
| 15 - 55 mins | Breakout rooms |
| 55 - 65 | Wrap up of breakout room |
| 65 - 80 mins | Break |
| 80 - 85 mins| Deciding breakout rooms |
| 85 - 125 mins | Breakout rooms |
| 125 - 135 mins | Wrap up |
| 135 - 150 mins | Padded times |

## Costing

| Item | Quantity | Cost |
| ---- | -------- | ---- |
| Tea and cake/lunch budget | pp | £10 |

Allocated £500 (50 people)

## Actions
- [ ] Create list of all docs we need
- [ ] Create open files for all of the docs
- [ ] Create overview diagram showing how they link together
- [ ] Create as many first versions as possible ahead of the meeting
- [ ] Create open doc for how we are managing these sessions, and reviewing community outputs