---
# System prepended metadata

title: The Turing Way - Core Staff delivery plan Meeting (7 August)
tags: [planning, 'governance ', TTW Staff meeting]

---

# The Turing Way - Core Staff delivery plan Meeting (7 August)

## Bi-weekly meetings

:::info
**Sessions in June & July:**
- Thursday 08 June - **[Meeting notes](https://hackmd.io/cR7dO1RvRNyVraIL005zXg)**
- Wednesday 28 June - **[Meeting notes](https://hackmd.io/IuFUjKgrTwaCooE8Zd1bIg)**
- Thursday 13 July - **[Meeting notes](https://hackmd.io/ZIxxwf67QoSuuvi0SElgNw)**
- Monday 7 August 
- Thursday 7 September (13:00-14:30)


**Join Zoom Meeting**
https://turing-uk.zoom.us/j/99448423769?pwd=NkkzZ3JjL2J3R3BJRmFHcVFtWm45dz09

**Meeting ID**: 994 4842 3769
**Passcode**: 429581
:::


**Participants** 
This call is joined by *The Turing Way* Core Staff:

* Kirstie Whitaker
* Malvika Sharan
* Anne Lee Steele
* Alexandra Araujo Alvarez 
* Arielle Bennett (subject to her availability)


## To Review Pre-Meeting

- [Governance Discussion on Github](https://github.com/alan-turing-institute/the-turing-way/discussions/3215)
- [The Turing Way and The Turing Institute](https://hackmd.io/@KirstieJane/turing-way-turing-inst)
- [Theory and Practice of Working Groups](https://hackmd.io/@aleesteele/SyxRDBath)
- [TTW Three level of decision making](https://hackmd.io/p_VjibHcT2uvDK2FC7Dx8A?both) DRAFT
- Notes from previous meetings
    - Thursday 08 June - **[Meeting notes](https://hackmd.io/cR7dO1RvRNyVraIL005zXg)**
    - Wednesday 28 June - **[Meeting notes](https://hackmd.io/IuFUjKgrTwaCooE8Zd1bIg)**
    - Wednesday 13 July - **[Meeting notes](https://hackmd.io/ZIxxwf67QoSuuvi0SElgNw)**

## Check-in

- Alex 
- Malvika
- Kirstie
- Anne
- Arielle

## Agenda

Review together the agenda and agree on priorities and timings.  

:hourglass_flowing_sand: **Timing:** Total 90 min
---

[ Alexandra ]

| Duration | Activity |
| ---- | -------- |
| Start | 👋 Welcome |
| 05 mins | Check in   |
|  | 1. Previous commitments Review |
| 10 mins | 1.1 The Turing Way and Turing Institute / Updates from previous meeting and next steps (Kirstie)
10 mins | 1.2 Theory and Practice of Working groups / Updates from previous meeting and next steps (Anne)
10 min | 1.3 Three level of decision-making (Ale) 
20 min | 2. Ongoing project status: Github new organisation / Fireside Chats 2023 / Book Dash Committee Planning (Liz's email) / Newsletter   
10 min | 3. Core team retirement
10 min | 4. Preparation for Core Team Meeting on ?? (was it on September?)
5 mins | Wrap up 

### Format:
* Adheres to TTW Code of Conduct 
* We will keep to time (Alex & Anne will keep us on track!)
* What we don't get done here, we'll move to the next meeting

---

**Parking lot for End of July/Beginning of August**

- Three way decision making (Alex): send it to Core Staff delivery by Friday 01 September
- Working groups (Anne): send to Core Staff Delivery by Friday 01 September
- Core Team retirement - 
- Rebuilding a steering and an advisory committee
    - with the community leaders/volunteers
    - TPS staff who substantially contribute to TTW (lead on areas important for TTW)
- Various TPS team members' roles
- Who applies for funding and how to do it
- Newsletter
- TTW Book documentation/updates - fortnightly

---

### 1. Previous Committments

#### 1.1 The Turing Way and the Turing Institute (Kirstie): 

- Clarifying TPS+Turing Way relation
[The Turing Way and The Turing Institute](https://hackmd.io/@KirstieJane/turing-way-turing-inst)

- CoC : was updated in the book. What is the process to find a new Ombundsman?


**Status/next steps**:
- Action for Kirstie: Edit document on TPS & Turing Way relationship
- Action for Kirstie: Bring up date on Code of Conduct to next delivery team meeting
    - Who are the members of the committee
    - Make sure that the distinction for reporting to line manager is clear
        - Edit 
-


#### 1.2 Theory and General process of working groups (Anne)


- Review the updated version of the theory and general process for working groups
update this document before we involve WG in writing about their working group: https://hackmd.io/@aleesteele/SyxRDBath


**Status/next steps**: 
- Incorporate a leadership team/level - invite some people from maintainer level 
- Adding more information from toolkit, reviewing community charters
-


#### 1.3 Three level decision making chart (Alex)

- Levels of decision making (ref shared by BGT: https://wiki.p2pfoundation.net/Three_Levels_of_FOSS_Governance)

Alex's Draft:
https://hackmd.io/p_VjibHcT2uvDK2FC7Dx8A?both

**Status/next steps**: 
- Comments are include in the Hackmd
- Alex will create a new version where we show the relationship between each layer in a circular way, 
- 
-
-
### 2. Ongoing Project Status

#### 2.1 Github New Organisation status

(Anne)

##### Notes:
-
-
-
-

#### 2.2 Fireside Chat 2023 status

- September: Practitioner's Hub - EiR speakers - We will propose this on 9 August, Check potential date: **Thursday 28 September**
- October: Mantainance - **Scheduled for 26 October**
- November:  BOOK DASH - Closember - No fireside chat
- December: Town Hall (Governance top decision players are there to answer questions)

##### Notes:
-
-
-
-

#### 2.3 Book Dash Committee Planning

* Committe planning applicants: https://hackmd.io/@aleesteele/r19osF052
    * Applications review
    * Commitee Planning Payment/Incentives (Liz's email)

Other Questions about the Bookd Dash Planning:
* Should The Experts in Residence be encourage to apply?
* External Hubs - Funding
* Group Activities within the week: i.e. JonnyWritesWords

Next steps
Liz's email:
* KW: we can't pay here as the current governance doesn't allow them to do it. If we would, it should be a decision to be taken by the accessibility working group
* AB: overarching point, it would be good to discuss it with the community. Fundamental level we should have the conversation. On the operational level, we don't have a transparent policy to pay her and unfair for the rest of the community. No good mechanisms to pay her. 
    * About paying to volunteers, David is doing the work and as volunteers, at the moment they don't get the honorarium. We will have a policy however it might not cover all the people, specially internationally
    * Contribution acknoledgment, look at different models in open source spaces
* who decides who gets reimbursed for their work
* how is that reimbursement dispensed
* MS: how do we create a mechanism to support people who need funding. There are grants that might support this type of proposals. 
    * How to make this opportunities open and available directly to the people who need them
* There should be policies for types of funding available and which options people have the option to apply
* Each working group will have policy documentation in place to make decision, and payment options (if it applies)
- **Malvika will come back to Liz**


BookDash Commitee
- Arielle, Esther and Emma could decide who will be part of the planning committee
- Ale will add the agenda on the github discussion and send the calendar invite for a meeting. 
- This time around, we will not split the WG to the planning committe
- Github issue: https://github.com/alan-turing-institute/the-turing-way/issues/3231#issuecomment-1647578024

#### 2.4 Newsletter

- we have changed the sender (our gmail account) to our turingway@turing.ac.uk
- Comments

#### 3. Core Team Retirement

* What should we plan here?

##### Notes:
-
-
-
-

#### 4. Preparation for Core Team Meeting

* Can we confirm when this meeting should happen and what should be prepared for it? Deadline to share previous information from the Governance review