the-turing-way · JimMadge · Jul 1, 2025 · Jul 1, 2025 · Jul 1, 2025 · Jul 1, 2025
diff --git a/README.md b/README.md
@@ -1,2 +1,8 @@
-# infrastructure-working-group
-Information hub for the infrastructure working group
+# Infrastructure Working Group ⚙️🧑‍🔧
+
+Information hub for the Infrastructure Working Group
+
+- [Project board](https://github.com/orgs/the-turing-way/projects/9)
+- [Our team](https://book.the-turing-way.org/afterword/subprojects#subprojects-infra-wg)
+- [Meetings (in *The Turing Way* calendar)](https://calendar.google.com/calendar/embed?src=theturingway%40gmail.com)
+- [Meeting notes](./meeting-notes/)
diff --git a/meeting-notes/20221110-notes.md → meeting-notes/2022-11-10-notes.md b/meeting-notes/20221110-notes.md → meeting-notes/2022-11-10-notes.md
@@ -3,24 +3,24 @@
 ### Code of conduct
 
 _The Turing Way_ Code of conduct applies to this call.
-* [Take a moment to read this](https://github.com/alan-turing-institute/the-turing-way/blob/master/CODE_OF_CONDUCT.md)
-* For any question or concern please reach out to Malvika and Anne ([email protected], [email protected]).
+
+- [Take a moment to read this](https://github.com/alan-turing-institute/the-turing-way/blob/master/CODE_OF_CONDUCT.md)
+- For any question or concern please reach out to Malvika and Anne ([email protected], [email protected]).
 
 # Agenda
 
 **Time**: Friday, 11 November, 14:00 UTC ([in your timezone](https://arewemeetingyet.com/london/2022-11-11/14:00))
 **Chair**: Anne
 **Scribe**: Otter.ai (from Sarah)
 
-
-| Duration | Activity |
-| ---- | -------- |
-| 10 mins | 👋 Welcome + Introductions  |
-| 5 mins | Review of WG Proposal |
-| 10 mins | Revisiting Purpose of WG |
-| 10 mins | Developing Principles & Ways of Working |
-| 15 mins | Processes and Tasks |
-| 5 mins | Action items & Next steps |
+| Duration | Activity                                |
+| -------- | --------------------------------------- |
+| 10 mins  | 👋 Welcome + Introductions              |
+| 5 mins   | Review of WG Proposal                   |
+| 10 mins  | Revisiting Purpose of WG                |
+| 10 mins  | Developing Principles & Ways of Working |
+| 15 mins  | Processes and Tasks                     |
+| 5 mins   | Action items & Next steps               |
 
 ## Welcome + Introductions
 
@@ -29,30 +29,31 @@ Time: 0:00-0:10
 (Please add your name and you can respond to the questions verbally during the introduction.)
 
 **Name (optional: pronouns) + How did you start getting involved with open source infrastructure (with The Turing Way or otherwise?)?**
-* Sarah / Binder project (intro to infrastructure), infra work since 2019
-* Jim Madge (he/him) / playing around with self-hosting
-    * computational chemistry
-* Danny Garside (he/him) / 
-    * computational neuroscience -> TTW for 5 years, 
-* Brigitta Sipőcz (she/her) / python library infrastructure for many years -> Turing Way 2 years ago for book dash -> runs a few projects based on JupyterBook 
+
+- Sarah / Binder project (intro to infrastructure), infra work since 2019
+- Jim Madge (he/him) / playing around with self-hosting
+  - computational chemistry
+- Danny Garside (he/him) /
+  - computational neuroscience -> TTW for 5 years,
+- Brigitta Sipőcz (she/her) / python library infrastructure for many years -> Turing Way 2 years ago for book dash -> runs a few projects based on JupyterBook
 
 ## Kickoff: Review of Proposal of WG
 
 Time: 00:10 - 00:15
 
 [Anne]
 
-
 ## Purpose: Why is this work important to the larger community?
 
 Time: 00:15 - 0:25
 
 Notes:
+
 - DG: It seperates out the content creation from all the other stuff - people don't need to worry about the process behind it. For me, it enables other people to do good work.
-- JM: Reading the book, 
+- JM: Reading the book,
 - SG: Site-reliability engineering. Needs to be accessible for both reading and contributing
-- BS: Being proactive, building the most automated tools to prevent issues. Lots of people involved at contributor level, but some rules are needed 
-- 
+- BS: Being proactive, building the most automated tools to prevent issues. Lots of people involved at contributor level, but some rules are needed
+-
 
 ## Principles: How can we work together to achieve this?
 
@@ -61,67 +62,76 @@ Time: 00:25 - 00:40
 [Taken from Github Issue](https://github.com/alan-turing-institute/the-turing-way/issues/2690)
 
 Notes:
+
 - Interest + Availability:
-    - DG: busy end of 2022, more free in 2023
-    - SG: 2i2c, community strategic lead role, worried about dividing time into too many slices, strategic vision, tool to solve that problem, writing
-    - BS: Ad-hoc basis, not a fan of documentation, how to notice pull requests that need another set of eyes, way of being able to look at permissions
-    - JM: tag for infrastructure, github teams
+  - DG: busy end of 2022, more free in 2023
+  - SG: 2i2c, community strategic lead role, worried about dividing time into too many slices, strategic vision, tool to solve that problem, writing
+  - BS: Ad-hoc basis, not a fan of documentation, how to notice pull requests that need another set of eyes, way of being able to look at permissions
+  - JM: tag for infrastructure, github teams
 - Github organisation, github teams
-    - Github permissions:
-    - Label hack
+  - Github permissions:
+  - Label hack
 - Communication: platform, cadence, method
-    - Immediate issues: visibility of infrastructure work
-    - Kanban boards
-    - Tags immediately
-    - State & prompt:
+  - Immediate issues: visibility of infrastructure work
+  - Kanban boards
+  - Tags immediately
+  - State & prompt:
 - Openess: sharing with TTW communinity
 - Membership: who should be in this group?
 
 ## Process: What do we work on?
 
 Time: 00:40 - 00:55
 
-### 1. Reviewing ongoing tasks 
+### 1. Reviewing ongoing tasks
+
 [Taken from Github Issue](https://github.com/alan-turing-institute/the-turing-way/issues/2690)
-> * Day to day: package updates, managing bug reports
-> * Longer-term: managing automation requests from working groups, developing strategy for tech adoption, onboarding new infrastructure maintainers, self-directed projects
-> * Preparation required: developing documentation (for internal use, to be added to the Community Handbook)
+
+> - Day to day: package updates, managing bug reports
+> - Longer-term: managing automation requests from working groups, developing strategy for tech adoption, onboarding new infrastructure maintainers, self-directed projects
+> - Preparation required: developing documentation (for internal use, to be added to the Community Handbook)
 
 Notes:
-- What is this missing? 
+
+- What is this missing?
 
 ### 2. Reviewing timeline
+
 [Taken from Github Issue](https://github.com/alan-turing-institute/the-turing-way/issues/2690)
+
 > 1. Phase 1: Documentation
 > 2. Phase 2: Testing and Developing System
 > 3. Phase 3: Expanding system & maintainers group
 
 Notes:
-- Are these the logical steps to take? 
+
+- Are these the logical steps to take?
 
 ### 3. Planning for Phase 1
+
 [Taken from Github Issue](https://github.com/alan-turing-institute/the-turing-way/issues/2690)
+
 > Answering questions like 'Who is doing what?' and 'What do people need to know when they join?', these phase is focused on documenting existing processes to develop, update, and maintain TTW as it is currently. This can form the framework for something like an SRE guide for TTW maintainers, including resources like a Q&A, and information about its platform building tools
 
 Notes:
-- Action Points:
-    - ALS - Making issue of what should go in documentation?
-    - SG - Sending otter.ai transcript
 
+- Action Points:
+  - ALS - Making issue of what should go in documentation?
+  - SG - Sending otter.ai transcript
 
 ### Next Steps
 
 Time: 00:55 - 01:00
 
 - Tasks until end of year (Async)
 - Next Meeting: Async or real-time?
-    - When2Meet: early 2023?
+  - When2Meet: early 2023?
 
-----
+---
 
 ## References
 
-* List of members: 
-    * 
-* Link to transcript: 
-    * https://hackmd.io/@turingway/Hk5Ywl2Bo
+- List of members:
+  -
+- Link to transcript:
+  - https://hackmd.io/@turingway/Hk5Ywl2Bo
diff --git a/meeting-notes/2023-03-29-notes.md b/meeting-notes/2023-03-29-notes.md
@@ -0,0 +1,117 @@
+# 29-03-23 Infrastructure Working Group Meeting 2
+
+### Code of conduct
+
+_The Turing Way_ Code of conduct applies to this call.
+
+- [Take a moment to read this](https://github.com/alan-turing-institute/the-turing-way/blob/master/CODE_OF_CONDUCT.md)
+- For any question or concern please reach out to Malvika and Anne ([email protected], [email protected]).
+
+# Agenda
+
+**Time**: Wednesday, 29 March, 16:00 UTC+1 ([in your timezone](https://arewemeetingyet.com/london/2023-03-29/16:00))
+**Chair**: Anne
+**Scribe**: Otter.ai (from Sarah)
+
+| Duration | Activity                                |
+| -------- | --------------------------------------- |
+| 10 mins  | 👋 Welcome + Introductions              |
+| 5 mins   | Review of WG Proposal!                  |
+| 20 mins  | Review of last year                     |
+| 20 mins  | Developing Principles & Ways of Working |
+
+| 5 mins | Action items & Next steps |
+
+## Welcome back + Introductions
+
+Time: 0:00-0:05
+
+(Please add your name and you can respond to the questions verbally during the introduction.)
+
+**Name (optional: pronouns) + How did you start getting involved with open source infrastructure (with The Turing Way or otherwise?)?**
+
+- [name=Danny] (he/him) - I think I saw things that bugged me in the formatting of the Turing Way, and saw that they were fixed in a new version, and the rest is history! 😅
+- [name=Brigitta] (she/her) - I started to contribute to open source as a GSoC student, gravitated towards the infrastructure parts over the years. During the pandemic joined one or two book dashes, and naturally ended up enjoying fixing infrastructure for TTW more than writing content.
+- [name=Anne] (she/her) -
+- [name=Jim] (he/him) - Wanting to self-host and manage multiple Raspberry Pis in a sensible way
+- [name=Bastian] (he/him) - Some self-hosting blogs and stuff and then wanting to run openSNP.org
+- [name=Sarah] (she/her) From the beginning of the Turing Way, working with Project Binder and JupyterHub, deploying "traditional" compute-based infrastructure
+
+## Review: What we've done so far
+
+Time: 00:10 - 00:55
+
+[Anne]
+
+Notes:
+
+- Instructions for building locally: https://github.com/alan-turing-institute/the-turing-way/pull/2922
+  - Worked with Outreachy interns to test documentation, which was great!
+- Planning documentation for infrastructure maintainers: https://github.com/alan-turing-institute/the-turing-way/issues/2809
+  - What has worked, what hasn't?
+- Flagging infrastructure work for Book Dash: https://github.com/alan-turing-institute/the-turing-way/issues/2988
+- Reviewing core principles from last year
+
+  - Availability & Commitment: has anything changed?
+    - [name=Jim] In principle, no change. In practice, I'm probably going to have less 'Turing time' to use for TTW.
+    - [name=Sarah] Low availability. I feel like I am in a position to be consulted and provide designs for solutions to problems, but I probably don't have time for implementations.
+    - [name=Brigitta] ad-hoc, availability for PR review is definitely there (I need to receive a direct github notification about it), less commitment for implementing new ideas
+    - [name=Bastian] No prior availability reported :wink:
+    - [name=Anne] There's a lot more that I wanted to do with everyone, but am being pulled in a couple of different directions! I could commit to a regular set time.
+    - [name=Danny] Unclear currently - I'm in the process of wrapping up my postdoc and deciding what comes next, and I'm currently planning my life only several days ahead at a time!
+  - Github organisation, github teams
+    - We got the ok! :thumbsup:
+    - ALS: How can we host a conversations about this transition in public?
+    - SG: Github teams -> each WG can be a team. Separating event planning from maintenance issues.
+    - BS: Hard to find issues that you can find in 10-15 minutes that I have. Labels is one thing. Project board can be helpful and directly being pinged on pull requests. Balance of pinging group & pinging individuals...
+    - SG: We can ping each other... but can people outside the WG know how to do it.
+    - JM: Can you assign a team to a PR or request a review from a team?
+    - ALS: We have slack channel... but should that happen in this context?
+    - What would be needed to flag a working group?
+      - SG: Currently is through ATI, but will need github organisation
+      - BS: First hurdle is to get the organisation
+      - JM: We'll just do what makes sense and worry about improving it later! Teams on Github had be a tree structure, can have sub-team of infrastructure maintainers.
+      - SG: Downside of pinging a team can be that no one is responsible...
+      - ALS: How can we be a buffer during this process?
+      - JM: Tagging, people who play that triage role... Sounds a bit risky, you have to have a lot of knowledge about who everyone is.
+      - SG: Pull request reminder bot... burden the robot!
+    - How can we start planning for a github organisation in 6 months?
+      - JM: We can do this?
+      - SG: Will dig into how the reminder bot is done
+      - BS: Getting org wide anything requires the hacking, not the other way around
+    -
+  - Communication: platform, cadence, method
+    - Infrastructure reminders on Slack channel
+      - BS: Every other week a summary of what is going on?
+      - JM: Monthly, weekly summary,
+      - BST: i would feel like having a bot do automated reminders in a separate channel can easily lead to notification fatigue (and a same vague responsibility)
+    - Github team: Can only add Turing folks to the Github team...
+  - Openess: sharing with TTW communinity
+  - Membership: who should be in this group?
+    - ALS: Maybe pause on thinking about this?
+
+- 1. Github teams
+  - Now:
+    - AAA & ALS: can see on Turing level
+    - JM: Can people be added as 'Outside Collaborators'? Jim tested it and it was not possible.
+  - Organisation: We'll need our own team.
+- 2. Notifications
+  - Github email digests
+  - Slack channel
+- 3. Accountability + Scheduling
+  - Meeting structures
+  - Book Dash & Collab Cafe
+    - Planning in the long term for a sprint of some sort?
+    - Once a quarter?
+  - Slack channel
+
+## Next steps
+
+Time: 00:55-01:00
+
+- Scheduling a monthly meeting
+  - AAA: Start with scheduling one month check-in
+  -
+- Schedule time
+  - Schedule monthly meeting
+- Github organisation
diff --git a/meeting-notes/2023-04-20-notes.md b/meeting-notes/2023-04-20-notes.md
@@ -0,0 +1,62 @@
+# 20-04-23 Infrastructure Working Group Meeting 3
+
+# Agenda
+
+**Time**: Thursdat, 20 April, 16:00 UTC+1 ([in your timezone](https://arewemeetingyet.com/london/2023-03-29/16:00))
+**Chair**: Anne
+**Scribe**: Otter.ai (from Sarah)
+
+| Duration | Activity                                       |
+| -------- | ---------------------------------------------- |
+| 10 mins  | 👋 Welcome + Introductions                     |
+| 5 mins   | Review Developing Principles & Ways of Working |
+| 20 mins  | Review PR                                      |
+| 20 mins  | Documentation                                  |
+| 5 mins   | Action items & Next steps                      |
+
+## Welcome back + Introductions
+
+Attendees: Sarah, Brigitta, Anne and Ale
+
+### Meeting discussions
+
+Sarah
+
+- Redirection of files around
+- Link checks
+
+PR Working group
+
+- How are we using this meeting?
+
+  - Fundamental work needs to happen offstream
+  - The Turing
+
+- Jim (how do good meetings look like):
+  Project Tracker
+  Quick overview of issues.
+  Higher level of prioritation. High level of conversation. Quick refresh of people opinions.
+
+- Anne (Open Roadmap)
+  Propose to have someone from Translation to guide us on how to organise the group
+  Translation and Location notes: https://hackmd.io/HQQQMlwvTIOtX5nHH9R4eg
+
+- Sarah (on inviting someone from the Translation group)
+  Sounds like a good idea.
+  Documenting what we have might be a good idea.
+
+- Brigitta: on building the roadmap.
+
+## Planning the documentation
+
+- Prepare templates and sessions for a Collaboration Space
+
+## Roadmap
+
+- Jim and Sarah are not certain that this might be a solution for this WG.
+
+**Next meetings will be the 2nd Thursday of the month from 4:00 pm to 5:00 pm**
+
+May will be a month full of Conferences for the
+Collaborations Workshops
+SciPy / mid July: Send stickers and cards to Brigitta
diff --git a/meeting-notes/20230511-notes.md → meeting-notes/2023-05-11-notes.md b/meeting-notes/20230511-notes.md → meeting-notes/2023-05-11-notes.md
@@ -1,15 +1,16 @@
 # 11-05-23 Infrastructure Working Group Meeting 4
 
 Time: Thursday, 11 May, 16:00 pm
-Attendees: Bastian, Jim and Alex. 
+Attendees: Bastian, Jim and Alex.
 
-There was no agenda as we have agreed that this was a prep meeting for the ones starting on the 2nd Thursday of the month. 
+There was no agenda as we have agreed that this was a prep meeting for the ones starting on the 2nd Thursday of the month.
 
-- We spoke about how we could support in structuring the infrastructure working group. 
-- Jim will be at the Book Dash (in May) and that was a good opportunity for him to work on the infrastructure team documentation. He wanted to speak to Malvika to answer some technical questions  
-- We spoke about the possibility of TTW having an Infrastructure custodian who can focus and guide all the technicalities of the space. This person should have authority to make decisions and make it evident for other contributors. 
-- Are the Collaborations Cafes the right space for the infrastructure team to work. Is it a focus time to go through PR?   
+- We spoke about how we could support in structuring the infrastructure working group.
+- Jim will be at the Book Dash (in May) and that was a good opportunity for him to work on the infrastructure team documentation. He wanted to speak to Malvika to answer some technical questions
+- We spoke about the possibility of TTW having an Infrastructure custodian who can focus and guide all the technicalities of the space. This person should have authority to make decisions and make it evident for other contributors.
+- Are the Collaborations Cafes the right space for the infrastructure team to work. Is it a focus time to go through PR?
 - Is is possible to bring more resources to the infrastructure team to be able to invest in more automations and structure?
 
 ### Actions:
-- Alex agreed to talk to Malvika about this points
+
+- Alex agreed to talk to Malvika about this points