April 26 Steering Committee Meeting Notes

constititution-level-resources/meeting-notes/20260128-meetings-notes.md

@@ -0,0 +1,17 @@
+# 28-01-2026
+
+Attending: Jim, Léllé, Liz, Precious
+
+Apologies: Emma, Arielle, Kirstie, Malvika, Sara
+
+## Actions & Decisions 
+* None taken
+
+## Notes
+
+   * Is there a process for stepping down from a role, temporarily or permanently?
+       * We don't think so currently
+       * although, we adopted the principle that although we commit to terms, we don't block people from standing down for whatever reason
+       * In specific: Léllé want to step down in the near future. May be an opportunity to test how this works. Sara would be well positioned to step into this role
+   * Feeling was too many people were absent to make progress on the SC priorities for this year
+   * No items which would be beneficial to cowork on, so we closed the meeting

constititution-level-resources/meeting-notes/20260211-meetings-notes.md

@@ -0,0 +1,55 @@
+# 11-02-2026
+
+## Attending:
+* Kirstie
+* Malvika
+* Liz
+* Emma
+* Sara
+* Jim
+* Precious
+
+### Apologies: 
+* Arielle
+* Lelle
+* Batool
+
+## Actions & Decisions
+* ACTION: EK share the turing template for comms plan.
+* DECISION: Focus next meeting on strategic comms plan 
+
+## Agenda
+* Updates - how are you feeling and how is your working / delivery group doing?
+* Goals for 2026
+
+## Notes: 
+* **Updates - how are you feeling, and how is your working / delivery group doing?**
+  * Emma: Time is an issue to get some writing done. Book Dash WG has lost a few members- need to recruit more. But we do have some funding for book dash, that's good news. Book Dash Date is set, but no issue made yet. 
+  * Sara: **CMWG** - restarting again, after a break it takes us a while to revamp our routine and group. Might need to put this into the plans. But positive going forward - switched our meeting to the afternoons to accomodate more people. Onboarding new members. 
+  * Malvika: Added in reproducibility training at St Jude. Might be onboarding Oscar as co-chair - can we do this? If we give him a bit more agency, he would step up and take on more responsibility.
+  * KW - is this a new process to create a working group, and have a chair/co-chair.
+    * MS - We did an issue and established a regular meeting. 
+    * Move meeting maybe to Collab cafe, so more people can join.
+  * Liz: just me, attending collab cafe (1st of month) to be more accessible to others. I am focusing on the goverance stuff now. Would like to work with funding wg and could support bringing people with lived experience to those discussions.  
+  * KW: Time has been an issue, plus the way to find a connect UC Berkeley with the Turing Way. There's a lot of content in the Turing Way that can overlap with the plenty OSPO work going on.  
+    * An angle that may be helpful for 2026 is linking individual chapters of the Turing Way to people, as opposed to the whole Turing Way book.
+    * The Turing Way is an example of Jupyterbook, and can be highlighted as a great example.
+  * MS: What does it look like to have the Turing Way be part of more organisations strategically? What is the value proposition for these organisations to adopt the Turing Way? 
+       * MS - need for promoting TTW
+  * Jim: IWG - same has always been, pressed for time and trying to do the most sensible things. We have a project board and making good use of that. We want to do some work on translation, but have not heard from translation group lately - we will look into Crowdin. We meet once a month. I bit of friction has been - one member that has not come to a meeting has not agreed with us and done something else. 
+       * I was happy at the end of last year that KW said we should look after what we have and not add more. Hard to find time to contribute. Maybe we can't have all the things we want - maybe we want to be more strategic about what we do. 
+  * Precious - Jan went quick! DSWB - have been using resources from TTW. We have a workshop coming up - want to have some contributions into book. Personally, I will be travelling alot this year. 
+       * KW - is there any reports that name us or cite us? PO - not at the moment. 
+               * Correcting to say the Turing Way is listed here as a resource for DSWB: [https://dswb.africa/open-science/](https://dswb.africa/open-science/)
+* **Goals for this year/2026** - [https://github.com/the-turing-way/governance/issues/45](https://github.com/the-turing-way/governance/issues/45)
+  * Comms plan
+  * each month have a theme and have 4 posts around the theme
+    * EK - needs to be strategic - were do we want to be speaking and to who?
+* Curation - consolidating what we have
+* Governance to be visible
+   * MS: let's just focus on one thing, that's consistent: maybe Collab cafe, one issue or chapter to curate. 
+   * OSPO - challenges we have had is - I don't know how to promote our events. 
+       * if our strategic friends - know to repost automatically our posts, etc. 
+* Promoting TTW
+* Partnership framing
+* SV - Updating documents on giv and ways of working: [https://github.com/the-turing-way/the-turing-way/pull/4371](https://github.com/the-turing-way/the-turing-way/pull/4371)

constititution-level-resources/meeting-notes/20260225-meetings-notes.md

@@ -0,0 +1,42 @@
+# 25-02-2026
+
+## Attending: 
+* Batool
+* Kirstie
+* Emma
+* Lelle
+* Jim
+* Liz
+* Arielle
+
+### Apologies: 
+* Malvika
+* Sara
+* Precious
+
+## Agenda:
+
+* Community forum
+
+## Actions & Decisions
+* DECISION: Community forum in March 2026 will be focused on showcasing the SSI fellows involved in the community, roles were assigned across the committee
+* DECISION: Next SC meeting on 11 March will be co-working with no agenda
+
+### Notes
+* LD is stepping down due to personal reasons
+  * SV will continue to lead the community management working group 
+   * AB suggested updating the contributor record [https://book.the-turing-way.org/afterword/contributors-record/](https://book.the-turing-way.org/afterword/contributors-record/) 
+       * EK suggested creating checklist to update documentation/source of truth about governance and maybe social media post to thank those who step down
+       * Having co-chairs makes working groups easier in terms of capacity and offboarding, etc.
+       * Issue for writing and updating guidance here: [https://github.com/the-turing-way/the-turing-way/issues/4550](https://github.com/the-turing-way/the-turing-way/issues/4550)
+* Community forum -  [https://github.com/the-turing-way/governance/issues/47](https://github.com/the-turing-way/governance/issues/47)
+  * Possible topics
+    * Plans for 2026
+    * Invite people from other communties - creating community of communities (e.g. HiddenREF, SSI, RSE, ..etc)
+           * Maybe SSI fellows focused showcase - Cass, Andre, Anne, Johanna, Sara, Precious
+               * Extend invite to other fellows to attend. 
+       * We decided SSI fellow showcase, 3 mins lightning talks.
+           * Emma will be chairing
+           * Lelle/ CM WG will be creating the Zoom link
+           * Batool will create frampad and help with breakout rooms
+* Next call on 11th of March will be co-working call, optional - no agenda

constititution-level-resources/meeting-notes/20260311-meeting-notes.md

@@ -0,0 +1,44 @@
+# 11-03-2026
+
+## Attending: 
+* Kirstie
+* Jim
+* Liz
+* Arielle
+* Malvika
+* Sara
+* Precious
+
+### Apologies: 
+* Batool
+
+## Agenda:
+* Governance and Ways of Working PR: [https://github.com/the-turing-way/the-turing-way/pull/4371](https://github.com/the-turing-way/the-turing-way/pull/4371)
+  - Jim is removing the Way of Working file to a different PR and merge the information in the FAQ page: [https://book.the-turing-way.org/communication/binder/#binder-faqs](https://book.the-turing-way.org/communication/binder/#binder-faqs) 
+* Sara is adding new members in the maintenance level list in Governance roles
+* Jim suggested to automate the way we show people's role in the Governance Role - but this will be in a different PR after we merge this PR (minus the Ways of Working)
+
+## Actions & Decisions
+* ACTION: Remove 'ways of working' document
+* ACTION: Work on governance files to update and reflect roles of people
+* DEICSION/ACTION: All SC to reivew 
+           * [https://github.com/the-turing-way/the-turing-way/issues/4554](https://github.com/the-turing-way/the-turing-way/issues/4554)
+           * [https://book.the-turing-way.org/foreword/guiding-principles/](https://book.the-turing-way.org/foreword/guiding-principles/)
+           * [https://github.com/the-turing-way/the-turing-way/pull/4371/changes](https://github.com/the-turing-way/the-turing-way/pull/4371/changes)  
+## Notes 
+* [https://github.com/the-turing-way/the-turing-way/pull/4371](https://github.com/the-turing-way/the-turing-way/pull/4371)
+  * What should we have in the ways of working document? 
+    * Jim: Have the FAQs in the Ways of Working document
+    * MS: +1 to Jim. It reduces the redundancy of finding the information at different places. 
+    * Kirstie: Do we delete the waysofworking.md? 
+    * MS: We would move the information away from the Waysofworking. We can save it as history, but have the information on it placed in the proper locations. 
+    * Kirstie: We can have it as a chapter in the handbook to highlight the journey of starting with a lighter document, building it up due to the growth of a community, and making it into something larger. The initial document can then be deleted, as all the information on it can now be found somewhere else. 
+    * Kirstie: Are there other documents we would need to delete?
+    * Jim: A little unrelated, but we can work on markdown to structure roles so it can easily be updated. We could have a tag to highlight whoever may be the chair at the time to link to the profiles page. 
+    * Sara: Do we update the governance roles file?
+    * Jim: We can update the files to include the names of the individuals in the roles.
+    * Malvika: Supporting to pull out the WoW in different PRs, resolve any comments, and merge the remaining files. Also, update the roles/individual names on the governance roles document.
+               * Action Items:
+                   * Remove the waysofworking document
+                       * Profile file needs to be updated. 
+                       * Work on governance files to update and reflect roles of people. 

constititution-level-resources/meeting-notes/20260408-meetings-notes.md

@@ -0,0 +1,59 @@
+# 08-04-2026
+
+## Attending: 
+* Arielle
+* Emma
+* Jim
+* Liz
+* Precious
+* Kirstie
+* Malvika
+
+### Apologies
+* Oscar
+* Batool
+
+## Agenda
+   * Code of Conduct discussion
+
+## Actions & Decisions
+* **ACTION:** SC to review the PR [https://github.com/the-turing-way/.github/pull/3](https://github.com/the-turing-way/.github/pull/3)
+* **ACTION:** SC to update CoC to make it suitable for handover to a committee
+* **DECISION:** CoC discussion to continue next meeting 
+
+## Notes 
+* Code of conduct - current state
+  * Originally taken from carpentries - have there been any updates?
+    * [https://docs.carpentries.org/policies/coc/](https://docs.carpentries.org/policies/coc/)
+    * Carpentries has a committee with a chair, has an executive council liaison to act as a 
+    * For Turing Way - need to separate Kirstie and Malvika as previous project leads from Coc Committee
+* [https://www.contributor-covenant.org/version/3/0/code\_of\_conduct/](https://www.contributor-covenant.org/version/3/0/code\_of\_conduct/)
+  * Report handling could be improved - was worked on in 2023 but dropped due to capacity issues 
+  * SC does not feel like there are serious issues with the content of the CoC but need to set up and recruit committee
+  * There was some effort in 2024 to update CoC, it is held in the .github repo ([https://github.com/the-turing-way/.github)](https://github.com/the-turing-way/.github)) so that the CoC could be applied to all repositorys (except those that have their own CoC)
+* Forming the committee
+  * We may want to exclude very senior (chair) members as there could be conflicts
+  * Should SC members be eligible for CoC committee?
+       * Most likely,
+           * CoC events will not happen often
+           * When they do, it is important to action them quickly and appropriately
+       * Pulling from maintenance level may be a good idea. CoC committee members need to have good knowledge of the community and also need to make a commitment.
+       * Some reports are easier than others, it may be clearly no violation or cleary a violation. More subtle cases can be difficult and require good knowledge of the CoC and community norms
+       * Sketch
+           * 1 member from SC (ex officio)
+           * 1 member from community management (ex officio)
+           * pool of members from community or maintenance levels
+           * Ombudsperson (external to The Turing Way community)
+  * An area where it can be difficult to get experience
+  * Definitely need members on the CoC committee with experience
+  * Should aim to have places for training
+  * What constitutes a CoC report ?
+  * Arielle is in favour of us utilising the CoC as a tool to improve the community! 
+  * We're digging into discussions about how we handle CoC reports
+  * As part of review, checking that the intention of the CoC process is clear,
+    * "If you have been made to feel uncomfortable use this", false positives are fine, we would rather have reports than potential miss a CoC violation
+* **Next steps!**
+  * Committee
+  * Documentation
+    * Clarify responsibilities of CoC Committee, and the SC
+    * Understanding how the community wants to meet the space - delegated to the committee?