---
# System prepended metadata

title: The Turing Way - Core Staff delivery plan Meetings (13 July)
tags: [TTW staff Meeting, 'governance ']

---

# The Turing Way - Core Staff delivery plan Meeting (13 July)

## Bi-weekly meetings

:::info
**Sessions in June & July:**
- Thursday 08 June - **[Meeting notes here](https://hackmd.io/cR7dO1RvRNyVraIL005zXg)**
- Wednesday 28 June - **[Meeting notes here](https://hackmd.io/IuFUjKgrTwaCooE8Zd1bIg)**
- Thursday 13 July
- Monday 7 August (previous meeting changed as Full Day Practitioners Hub Workshop was happenning on 27 July)


**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 [ooo]
* 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)
- Notes from previous meetings
    - Thursday 08 June - **[Meeting notes here](https://hackmd.io/cR7dO1RvRNyVraIL005zXg)**
    - Wednesday 28 June - **[Meeting notes here](https://hackmd.io/IuFUjKgrTwaCooE8Zd1bIg)**

## Check-in

- Alex (A/L)
- 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 Review Github discussion (Malvika) 
20 mins | 1.2 Review "Clarifying TPS + The Turing Way relation" section (Kirstie)
20 min | 1.3 Review "theory and general process for working groups" section (Anne) 
20 min | 2. The Turing Way Communications
5 mins | Wrap up 

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

---

### Previous Committments

- Malvika: To summarise the governance review notes and add the action on GitHub: https://docs.google.com/spreadsheets/d/1gjAtPCgk8Izh-xB1iK56wDOTe2ygHq5NG_-WFEPX-40/edit#gid=1687914303
Share resources and reference that the team need on Slack
**Status**: Done (https://github.com/alan-turing-institute/the-turing-way/discussions/3215)

- Kirstie: Clarifying TPS+Turing Way relation
Turing’s investment transparency about The Turing Way
Code of Conduct: utilising the RCM team (nice to have by 13 July 2023): https://github.com/alan-turing-institute/open-community-building/blob/main/CODE_OF_CONDUCT.md
**Status**: Clarifying TPS + Turing Way relation to be presented on 13 July
  - Draft: https://hackmd.io/@KirstieJane/turing-way-turing-inst

- Anne: Update the theory and general process for working groups
update this document before we involve WG in writing about their working group: https://docs.google.com/document/d/1Z_r0G6dmtlw0icQ_ctkhLG_QxZDhuRZaSTSkGvAVK6w/edit

- Note: [added draft here](https://hackmd.io/@aleesteele/SyxRDBath), and can post to document for further comments once presented

**Status**: section to be reviewed on 13 July 

---

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

- 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
- Alex: Three level decision making chart
    - Levels of decision making (ref shared by BGT: https://wiki.p2pfoundation.net/Three_Levels_of_FOSS_Governance)
- Github independent organisation: 
Involve the Infrastructure team asap. Make it clear that they havethe agency to decide the timeframe and community. **(Anne) will make the issue and it will be reinforced in the infrastructure meeting on 13 July** (PM)
- Accessibility WG: updates on process & support so far.

---

## 1. Previous Commitments review

### 1.1 Summary of the governance review notes and add the action on GitHub (Malvika)

**Status**: Done (https://github.com/alan-turing-institute/the-turing-way/discussions/3215)

Comments:
- Sent out in newsletter
- Splitting the 10 actions into issues and tag the right people
-
-

### 1.2 Clarifying TPS+Turing Way relation (Kirstie)
Turing’s investment transparency about The Turing Way

**Status**: to be presented by Kirstie

- Kirstie: Clarifying TPS+Turing Way relation
Turing’s investment transparency about The Turing Way
Code of Conduct: utilising the RCM team (nice to have by 13 July 2023): https://github.com/alan-turing-institute/open-community-building/blob/main/CODE_OF_CONDUCT.md
**Status**: Clarifying TPS + Turing Way relation to be presented on 13 July
  - Draft: https://hackmd.io/@KirstieJane/turing-way-turing-inst
  - Notes: 
      - Code of Conduct will be added in there
      - Institutional vision alignment in open source
      - Support:
          - Financial
              - Splitting the employment and other cost
          - Organisational/Personnel
      - Financial document
      - Limitations in terms of policies
          - we can't just accept or give money
      - Who owns The Turing Way?
          - As an open source it belongs to the community
      - 
- Next steps?
	- KW to do one more pass through 
	- Review document once other documentation in place (later in the year)


### 1.3 Update the theory and general process for working groups (Anne)

**Status**: to be presented by Anne

https://hackmd.io/@aleesteele/SyxRDBath

- Comments
	- AB/MS: Include accountability mechanisms for the wider community, e.g. expectations around presenting to community calls
	- AB: need something in there about mechanisms for sunsetting outside of the working groups
	- AB: charter, toolkit, should be created to help guide people 
	- KW: Propose that chairs of working groups join TTW leadership team (have chair and deputy chair)
	- KW: Minimum level of alignment with the strategy, leadership group to approve working groups - anyone can explore creating working groups but need some assessment
	- MS: Carptentries Handbook has toolkit templates to reuse potentially 
	- Maybe build on these: https://github.com/alan-turing-institute/the-turing-way/blob/main/ways_of_working.md#commitments
	- KW: Should this be two documents? A philosophy and a practice of working groups?
- Next steps
    - ALS brings second draft in two weeks time, then expanding to wider group


## 2. The Turing Way Communications

### 2.1 Communications channel
Activities/ Tools we have running:

*Based on priorities*

- GitHub: 
purpose:
benefits:
costs: 

- Newsletter (once a month)
purpose:
benefits:
costs: 

- Slack
purpose:
benefits:

- YouTube
purpose:
benefits:
costs:

- Twitter
purpose:
benefits:
costs: 

- Mastodon
purpose:
benefits:
costs: 

#### What is the most relevant communications tool TTW has? and why?
-
-
-
-

#### Should we consider other platforms? such as Threads / LinkedIn?
-
-
-
-

#### Should this be raised with the core team?
-
-
-
-

#### Do we have the capacity to explore other options?
-
-
-
-

Reasons for bringing this up:
- Audit of platforms (relevant/remit for CM)
- What platforms are we not on? (i.e. Linkedin, Threads, etc) (relevant/remit for CM)
- What platforms, shifts, etc are being advocated for by various individuals and teams? (F/OSS by infra folks, most accessible platforms re: accessibility)
- Who makes this final decision around this?ecision around this?

Question added by Kirstie:
* Who should make these decisions? What are the future governance requirements? Do we need a comms working group?

Notes: 
* Who makes the bigger decisions?
* Who should give feedback (community? core team?)
* "If you're not in the arena, I'm not interested in your feedback"
* What can be automated?
* Upskilling & providing advice? What can be provided as advice?

Next steps:
* Work with Alex in creating this, not high priority
* CM can have power in this, but think about how decision is made: i.e. can make Linkedin page, and test with community