---
# System prepended metadata

title: The Turing Way - Core Staff delivery plan Meeting (10 October)

---

# The Turing Way - Core Staff delivery plan Meeting (10 October)

## Bi-weekly meetings (with some exceptions)

:::info
**Sessions in June - October 2023:**
- 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 - **[Meeting notes](https://hackmd.io/PKaO_8d7Qo2pLhDEo3DzaA)**
- Thursday 7 September - **[Meeting notes](https://hackmd.io/qtPtKBKUSVqebqFU0a_xgQ)**
- Thursday 21 September - **[Meeting notes](https://hackmd.io/igAh4unTSkGquDOtSRdAmg?edit)**
- Tuesday 10 October


**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)

## Agenda

Review together the agenda and agree on priorities and timings.  

:hourglass_flowing_sand: **Timing:** Total 75 min
---

[ Alexandra ]

| Duration | Activity |
| ---- | -------- |
| Start | 👋 Welcome |
| 05 mins | Check in   |
| 30 mins | 1. Governance Review: next steps, communications, etc |
| 10 mins | 2. Next Core Team Meetings: Nov-Dec
10 mins | 3. Funding Applications Status 
10 min | 4. Other Logistics: Febs Blog post and Open UK
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:**

- Develop a TTW Funding Policy
- TTW Book documentation/updates - fortnightly (https://github.com/the-turing-way/the-turing-way/issues/3272)
- Develop a TTW Policy for Participating in conferences
- TTW Website and URL (https://github.com/the-turing-way/the-turing-way/issues/3266)
- Reviewing TTW Coworking Call (& use for governance)
- Review of last events of the year

---

## 1. Governance Review after Core Team Meeting
- Link to the Core team Meeting Agenda (28 September): https://pad.sfconservancy.org/p/ttw-sep23-communitycall
- Link to the miro questions added by the community: https://miro.com/app/board/uXjVMnA6G50=/?share_link_id=315031474203


Questions / Notes

::: info
### Previous relevant material
Governance documents to review and share with the core team:
- [The Turing Way and The Alan Turing Institute](https://hackmd.io/@KirstieJane/turing-way-turing-inst)
- [Theory and Practice of Working groups](https://hackmd.io/@aleesteele/SyxRDBath)
    - Core changes: 
        - Decision-making section
        - Community charter: starting a template
        - Storing notes, documentation, reporting -> should this be in a Github organisation
            - Transparent processes for people including leadership -> things should immediately be externalised into a Github issue
            - MS: If any decision is being made, where are you unable to make decisions
        - NOTES FROM ALS:
            - Key questions: ability to make new chapters (does this sit with decision making?)
- [Three way decision making](https://hackmd.io/p_VjibHcT2uvDK2FC7Dx8A?both)
    - Timeline with the changes, when is this happening, how is that looking? What is the process? 
    - The advisory and steering group are out and they are not a working group
    - Working group for Institutional Partnerships 
- (https://miro.com/app/board/uXjVMnA6G50=/?share_link_id=810801549803) -- > the arrow represent the chairs that join the leadership team
:::

Notes
- There are people in the room that don't speak up and we need to hear their voices. 
- Keep working and showing them how we are progressing
- We are asking for clarity it's very hard to give those answers
- Put the documentation in Github? 
- How to create interactions? / What do people want to ask the community?
- MS misses feedback, is this the right direction to go
- KW is the core team the right people to be asking and find out why they are not engaging if not, who is the right people?
- Either there's something wrong or they like the direction we are going
- ALS written survey where people can react to and send their honestly comments.
- MS this is happening in more spaces than TTW, how can we have imperfect feedback.
- ALS: what sort of feedback we want? 
- MS: We want to co-create the process of understanding. We want them to direct us, guide us, excited and co-working, etc. 
- ALS: no reporting mechanism that is more informal reporting. 
- KW: KW has received the feedback that when she comes to meetings we don't get enough feedback. 1:1 sessions to find out what excites people about TTW. TTW is very understaff and therefore the focus is very low on the rest of the community (apart from TTWPH). Push these ideas through. She is pushing a lot to make more people available
- Loadly adding the notes to Github vs quietly adding the notes. She's more blocked
- MS: regularly reporting, meetings 1:1 to have more impressions about the community engagement. Honestly could be a good thing. 
- Is the core team channel the right channel?
- **ACTIONS**: are we going to do something. Add this into Kirtie's To-do list. 
    - For 19 October, we should have the updated version of the documents, not the last one or the right one but one that we would upload in Github.
    - For the aim of collecting data, we will invite people to  
    - Meetings with core team, capture data in different forms 

## 2. Schedule next Core team meetings

- November: During the Book Dash? Thursday 16 November / Friday 17 November?
- December
- January or March?

Notes
- MS: would not push for it, but working group share-out
- We will ask working groups to report their progress or what they would love to share with the community. ---> invitation to join to the working group Share out
    - we could record it for people to watch later    
- There will be 2 regular share outs + working group share out
- We end up the Book Dash with ways to stay engaged. Anne would share this session.


## 3. Funding Applications Status
- ORFG: submitted on 15 September, not granted. Waiting to get feedback.
- DIIF: Submitted on 30 October by Elisabeth Wadge
- CZI EOSS Jupyter Hub: MS got worried about how KW involvment time in the project

Notes
-
-
-
-

## 4. Other Logistics: Febs Blog post and Open UK

Open UK
- It's sorted and we will participate
- Table is a good idea. We should try to get more itc - Correct KW's email and add Ale

Febs Blog Post
- MS would check the examples and see what was requested 
-
-





# Core team

## Actively engaged

* Kirstie Whitaker
* Malvika Sharan 
* Anne Lee Steele 
* Alexandra Araujo Alvarez
* Jim Madge
* Bastian Greshake Tzvoaras

## Engaged, needs specific ask

### Malvika chats

* Emma Karoune --- Malvika
* Cassandra Gould Van Praag --- Malvika

### Alex chats

* Arielle Bennett --- Alex
* Esther Plomp --- Alex

### Anne chats

* Jennifer Ding --- Anne
* Danny Garside --- Anne
* Liz Hare --- Anne

### Kirstie chats

* Sarah Gibson --- Kirstie
* Batool Almarzouq, Melissa Black & Andrea Sánchez-Tapia --- Kirstie
* Alejandro Coca Castro --- Kirstie

## Would benefit from a specific conversation

### Alex chats

* Hari Sood --- Alex (Hari is on A/L most of October)
* David Sarmiento Pérez --- Alex
* * Shakir Laher --- Alex 

### Malvika chats

* Eirini Zormpa --- Malvika
* Carlos Martinez-Ortiz & Lena Karvovskaya --- Malvika

### Anne chats

* Vicky Hellon --- Emma or Anne
* Kalle, Fran, Sophie --- Anne (group onboarding)

### Kirstie chats

* Alden Conner --- Kirstie
* Shakir Laher --- Alex 
 
## Appropriately engaged, but could give insights

* Brigitta Sipőcz

## Good reasons to not engage

* Aida Mehonic
* Sophia Batchelor
* Camila Rangel-Smith
* Gabin Kayumbi
* Christopher Burr --- topic for Kirstie in a 1:1
* Fran
* Sophie Arana
