###### tags: `data-science-AI-educators'-programme`

[TOC]

# Meeting // 30 November 2022 // 4 - 5pm
## Agenda

Outline proposed changes (20 minutes):
- Structural changes
- Speaker Honorarium
- No conclusion here: no clear policy from other teams. Alternative ways to incentivise speakers (not in a financial way) e.g. free tickets to AIUK (contact Events Team and block tickets, paid for from Skills budget)/running events/names on website/credits, potential to do vouchers. SKills Team need to pull together a policy on this. Decision to be made later - small working group to pull together a doc highlighting external contribution (raising visibility). What additional support can we offer e.g. per session evaluations capture relevant info to benefit the speaker (which might help them get a promo). In-person networking event for speakers. Could pay for a speaker from a large company but would be a one off and would need to potentially benefit the wider Turing community.
- Actions: reach out to events team
- Actions: create small working group
-
- Cohort call timings
- Speaker briefing (focus more on educator elements rather than project elements)
- Target Audience including definition
- Framed as predominantly HE but soft wording to show not too selective. [Pain points regarding HE stakeholders from DST session](https://miro.com/app/board/uXjVO7AkF5A=/)
- UK only more of a problem - international knowledge exchange is beneficial.
- Peer-mentoring in-person element
- F2f interaction numbers could be low: play it by ear to see what numbers are like.
- Regional events to allow for in-person networking
- Hub approach? Champion in a region or university setting. Self-organised. Could we support the catering? What could we support? Support with a playbook - draft agendas, send a few people from the Turing to attend but onous of organising is on the host institution/champion of that region. Bringing people together regionally for peer-mentoring groups?
- Provide clear information on what we're doing, when we're doing it and make it clear what is available for UK residents only e.g. these items are only available in the UK (but still open to international).
- Rather than now in cost-of-living crisis, would it be beneficial to pitch to Remo and encourage meet-up through that? Could open up to peer-mentoring groups too.
- Tie-in F2F element at AI UK?

## Notes on curriculum

- Introduction networking event as part of Carpentries sessions. Opportunity to get to know one another. Use the platform 'Gather'/'Gathertown'/Remo? (blocked by IT)
- Action: Contact IT (VM)
- Action: Find an alternative platform (AD)
- Action: Add budget line for software licenses (MN)
-

# Meeting // 6 December 2022 // 3 - 4pm

## Agenda

Discuss remaining questions (40 minutes):
- Curriculum questions (run cohort calls around noon)
- Discuss curriculum pain points
- Speaker suggestions
- Peer-mentoring questions (re-named 'discussion' groups)
- Timeline
- Start date

AOB
- If we were to run the DS and AI Educators' Programme twice in 2023, do you have ideas for a second target audience?
- Something about apprenticships?
- Alternative pathways into DS and AI?
- Programmes that needs Skills to be their main offering

**Widening participation**

- Drop 'widening participation' and discuss 'bias'
- Data feminisim as a lense for teaching
- Is it strategic 'EDI in your teaching'?
- Part 2 of ethics - why is DS and AI so biased? How do we change the bias?
- Call it and focus on **decolonising the curriculum**
- [ACTION] Conversation with public engagement
- Call should highlight examples/tools/when things go wrong (not obvious examples and use grey areas)
- Awareness raising of using certain datasets

Multiple levels of empowerment:
- Individual teaching practice
- Raising awareness at a higher level e.g. with faculty

Make call 5 and 6 a two-piece session and follow on from Carpentries equity module
- Diversity in curriculum development
- Diversity after the programme
- Diversity in datasets
- [ACTION] email Chris Burr

**Elements of CC10 that we might want to keep.**

**Keep call open in some way to other spaces. Scope with RAMS.**