Skip to content

Commit c64c5ce

Browse files
40thievesSallyMcGrathillicitonion
authored
Add minutes for 2024-12-03 (#1219)
* Add minutes for 2024-12-03 * Update org-cyf-guides/content/contributing/minutes/index.md * Update org-cyf-guides/content/contributing/minutes/index.md * Check off an action from last time Co-authored-by: Daniel Wagner-Hall <[email protected]> --------- Co-authored-by: Sally McGrath <[email protected]> Co-authored-by: Daniel Wagner-Hall <[email protected]>
1 parent 21deaa8 commit c64c5ce

File tree

2 files changed

+103
-703
lines changed

2 files changed

+103
-703
lines changed

org-cyf-guides/content/contributing/minutes/index.md

Lines changed: 103 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,96 @@ Attendees:
1717

1818
---
1919

20+
## 2024-12-03
21+
22+
Attendees: Ali Smith, Sally McGrath, Mitch Lloyd
23+
24+
### ❗Actions from last time
25+
26+
* [ ] All: Collaboratively put together LOs and name for ITP Introduction Module
27+
* [x] Daniel: Sync with Karen on Piscine dashboard requirements
28+
29+
### 📝 Agenda points
30+
31+
#### ITP first module
32+
33+
* Action item from last time was to write LOs for the reworked first module of ITP
34+
* Sally made [a doc](https://docs.google.com/document/d/1SHjRnvhoMp0NLDzEc8-lLMy4bx_FR87-_QxYRI9qRqY/edit?tab=t.0), but we got no further
35+
* Naming
36+
* Sally: Would like to override the vote of naming to be Introduction module
37+
* There's too much confusion with _Intro_ to Digital & _Intro_ to Programming as a whole course - "I completed the Introduction module" is too ambigious
38+
* Decision: Will be called the Onboarding module
39+
* Reasoning: It ties nicely into onboarding at a company, introduces that jargon
40+
* Welcome module naming was rejected
41+
* ITD feels like the true "Welcome to CYF"
42+
* LOs
43+
* Action: Sally to pick this up
44+
45+
#### Testing libraries
46+
47+
* Context: Ali added a Piscine project that uses `nock` for network testing - which got us talking about testing
48+
* Should we use just `node:assert` & `node:test` instead of Jest?
49+
* Have seen some issues where trainees are running into problems with ESM & Jest
50+
* But also in general Jest seems very complex for our use case: run some tests, with basic equality assertions
51+
* Ali: generally dislike Jest: very poorly documented, confusing API, as well as the ESM issues
52+
* Also discussed in [this Slack thread](https://codeyourfuture.slack.com/archives/C012UUW69S8/p1732730885296249)
53+
* Decision: We would like to simplify testing and move away from Jest to built-in Node tools
54+
* We think it would be useful to have materials on testing in-depth (e.g. introducing more complex assertions, mocking, unit vs integration vs e2e, philosophies around testing etc)
55+
* Action: Mitch to write up a ticket
56+
57+
#### How will tracks work?
58+
59+
* Demand led - if there's a job, we can create a track for it
60+
* Sally: Have started on a SAP FI/CO Track
61+
* [Curriculum link](https://tracks.codeyourfuture.io/sap-fico/)
62+
* If we land a deal with a large enterprise company, then we'll run this Track
63+
* Financial / Enterprise Resource planning
64+
* Will run as workshops on Saturdays, with volunteers from the company
65+
* They'll also provide environments for trainees to use
66+
* Anyone who completes, should be eligible for submitting their CV to the company
67+
* Sally: Working with employers to agree LOs, pre-reqs for getting the job
68+
* [Example doc](https://docs.google.com/document/d/1zJomRiMshLluuWq_F_dM8fAxSM-ljmZZrl4H1o9aZxc/edit?tab=t.0)
69+
* Sally: Centre for Public Impact have awarded us a grant to run an AI Essentials track
70+
* [Press release](https://centreforpublicimpact.org/ai-opportunity-fund/)
71+
* Will run by their provided trainers, essentially it's a version of their online video course
72+
* Workshops will run on Saturdays
73+
* Approx 50% capacity assigned to London as that's where we have ~50% trainees
74+
* Scheduled for Feb 2025
75+
* Sally: Working create an IT Service Management (Support) Track
76+
* Sally has [made a start](https://github.com/CodeYourFuture/Track-ITSM)
77+
* Structured around a scenario: a user is stuck with a problem - have to write as a support person to a user
78+
* 1 trainee would act as a user, 1 as a support person
79+
* Trainees have to manage conflict, prioritise, triage
80+
* Work with tickets: triage, label appropriately, etc
81+
* Mitch: Are there docs for creating a Track (in the Curriculum)
82+
* Sally: Kind of yes, have a few quick start docs that might be a good basis for creating this
83+
* Ali: What are the reqs for creating a Track?
84+
* Ali: Envision problems where volunteers want to create Tracks to "feel useful", leading to questions about who is "allowed" to create a track
85+
* Sally: Tracks should to be tied to an agreement with CYF - there should be some realistic expectation that there will be X job(s) available to trainees at the end of the track
86+
* Sally: General expectation is that trainees at this point should be applying for entry level jobs!
87+
* Sally: Other learning materials created for trainees at this level can go on the curriculum website, but as _self-study_
88+
* The [old React module](https://tracks.codeyourfuture.io/react/) is now in the self-study section of the curriculum website
89+
90+
#### Volunteer onboarding
91+
92+
* Ali: When attending in-person workshop on 23rd Nov, encouraged all volunteers to gather together and chat about any questions they had, introduce new people to how CYF works (how the courses fit together etc)
93+
* Also tried to encourage regular volunteers to run this small meeting regularly
94+
* The goal was to try to encourage a community of practice and share knowledge
95+
* Sally: Asked German to run [a workshop on community building](https://docs.google.com/document/d/1sMxm8y-mV1PVNATdQpPPVUpUZziBiNeSWxifxcOSfTA/edit?tab=t.0)
96+
* Do _not_ want to explain why lecturing is a bad thing!
97+
* Ali: Perhaps need to think about how we can filter out this sort of thinking before we get to this stage
98+
* Ali: Have been thinking about conference talks with the idea that we can try to attract people with a matching mindset & skills
99+
* Have put in for several CFPs, but not got anything back yet
100+
* Sally: German to ask Ali about what CYF can do to help in this area
101+
* Ali: The main thing is time!
102+
103+
### ❗Actions
104+
105+
* [ ] Sally: Write LOs for ITP Onboarding module
106+
* [ ] Mitch: Write up a ticket to replace Jest with vanilla Node testing libraries
107+
108+
---
109+
20110
## 2024-11-19
21111

22112
Attendees: Ali Smith, Daniel Wagner-Hall, Sally McGrath
@@ -201,46 +291,46 @@ Attendees: Ali, Sally, Daniel
201291
#### Piscine availability
202292

203293
- Ali will be away for the first week of Feb
204-
- So first 2 weekends will be away :/
205-
- It just needs to start and end in Feb. Possibly could shift Piscine to last 3 weeks of Feb, so that Ali only misses 1 week rather than 2
294+
- So first 2 weekends will be away :/
295+
- It just needs to start and end in Feb. Possibly could shift Piscine to last 3 weeks of Feb, so that Ali only misses 1 week rather than 2
206296
- Daniel to check in on other people's availability
207297

208298
#### "Gatekeeping" in ITP
209299

210300
- How strictly should volunteers enforce review requirements in ITP?
211301
- Decision: we shouldn't enforce too strictly
212-
- It's not the goal of ITP to be strict in assessment, that's the goal of Piscine
213-
- We want ITP to be easy to re-try, give lots of chances to succeed
214-
- While Piscine needs to be strict so that we can be realistic when it comes to SDC
302+
- It's not the goal of ITP to be strict in assessment, that's the goal of Piscine
303+
- We want ITP to be easy to re-try, give lots of chances to succeed
304+
- While Piscine needs to be strict so that we can be realistic when it comes to SDC
215305
- Will some volunteers might be "gatekeep" in ITP anyway?
216-
- Mostly likely yes, but we think it is better to err on the side of being overly strict than the opposite
217-
- This may cause some complaints from trainees about unfairness, but we can deal with this easier than unrealistic expectations in SDC
306+
- Mostly likely yes, but we think it is better to err on the side of being overly strict than the opposite
307+
- This may cause some complaints from trainees about unfairness, but we can deal with this easier than unrealistic expectations in SDC
218308

219309
#### Replacing Scrimba in ITD
220310

221311
- Team want to switch to freeCodeCamp
222-
- Possibly worth exploring other options, but don't have other ideas currently
312+
- Possibly worth exploring other options, but don't have other ideas currently
223313

224314
#### Resources for SDC
225315

226316
- Daniel has started to divide up SDC outcomes into "stuff we should create ourselves" and "stuff we can point to other people's existing good resources"
227-
- So if there is any good materials you know of, then point Daniel towards them
317+
- So if there is any good materials you know of, then point Daniel towards them
228318

229319
#### Volunteers confused about what to do on Saturdays
230320

231321
- Sally: volunteers are asking quite a lot about what to do on a Saturday, they seem not to be reading the curriculum at all
232-
- We expect them not to read it in depth, but we do need them to read _something_
322+
- We expect them not to read it in depth, but we do need them to read _something_
233323
- Should understand the prep, day plan & backlog structure enough to figure it out for themselves
234324
- Aside: the How This Works module is targeted at volunteers, we might want to consider an equivalent for trainees. But this is a big package of work that isn't super high priority for us right now
235325
- Decision: one pager to explain the concepts, with a **very obvious** link on the CYF curriculum site
236-
- We also think it would be useful to have a memorable short link (e.g. bit.ly/what-to-do-at-cyf-on-saturdays) that can be shared on Slack
326+
- We also think it would be useful to have a memorable short link (e.g. bit.ly/what-to-do-at-cyf-on-saturdays) that can be shared on Slack
237327

238328
#### Connecting remote volunteers to mid week session support & PR reviews
239329

240330
- Sally: we have a bunch of remote volunteers and opportunity to do mid-week learning sessions & PR reviews
241331
- Need to get Tech Ed volunteers to understand that giving PR feedback to trainees is important
242-
- Do new volunteers not understand the important of giving PR feedback? Or is it that they don't know where to look (or haven't been obviously sign-posted enough)?
243-
- We think it's the latter - so we need to find ways of directing the attention that way
332+
- Do new volunteers not understand the important of giving PR feedback? Or is it that they don't know where to look (or haven't been obviously sign-posted enough)?
333+
- We think it's the latter - so we need to find ways of directing the attention that way
244334
- We have very low numbers of volunteers outside of London - so can't really lean on in-person volunteers to do reviews on Saturdays - so instead we should try to lean into using remote volunteers for PR reviews
245335
- Lili has been gathering new remote volunteers into a Slack channel - should point ITP leaders in that direction to ask for help
246336

0 commit comments

Comments
 (0)