-------
# NOTES

### Clarifying responsibilities

### Core Delivery Team
- Kirstie Whitaker
- Malvika Sharan
- Alexandra AA
- Anne Lee Steele
- Arielle Bennett - funding, budgeting

###
### Reviewing previous points [WIP]

- [Proposal] Access-centered Guide
- Status: Proposed
- What would be useful for everyone's crowdsourced tasks... what decisions are held within The Turing Way project? what types of decisions can peopl emakde?
- Can I open up a PR
- Can I promote my own particular project
- What do we do around Quarto vs JupyterBook
-
-

Prompted discussion [Malvika]
- 1-2-4 Librating Format (https://www.liberatingstructures.com/1-1-2-4-all/): Start alone, then in pairs, (then four?), and finally as a whole group

* What work you have been doing that are not represented in the current working groups?
* What is useful about about the working groups? What is unclear? Is the working group model fit for the governance work? If not then what should these be?
* What resources does your working group need and what resources you need to engage meaningfully in The Turing Way?
* What is currently unclear for you about the governance process? What decisions related to your work in The Turing Way you would like to be made? Where do you 'struggle' or are unsure about taking a decision in your work?
* Where do you need the leadership of the Turing Way to step in? What other processes from The Turing Way community/book/project we should clarify?
* Reflections, sharing and feedback

## Notes from the discussion

* Lack of governance framework that working groups can use to make decisions or to decide NOT to use it but a starting point.
* Danny: Discussing infrastructure working group with Christian -
* What are the issues? Nobody with time/confidence/permission to determine long-term priorities
* What (IMO) would the long terms priorities be?
* Discussing with other users of the Turing Way what the unmet infrastructure needs are (what's on the wish-list?),
* and (_potentially related_) getting more involved in contributing to upstream projects
* Prioritization of projects from leadership would help guide working group activities
* How can the WG be pathways for new contributors to get involved? Clear direction from leadership on what is the appropriate way for new people to get involved with governance would be very helpful (we don't want to lose excited newcomers!)
* Some volunteers sound tired / overworked (but also, bookdash!). Would love to know how best to support them
* Is the community working on problems and delivering outputs that they are strongly passionate about and engaged in? How dynamic/fluid is TTW to adapting community to wants, needs and aims of community members?
* Some of the updates could have been an email/recording to save more time for discussion +1+1
* More clarity/direction in terms of what decisions can be made by the working group
* More clarity in terms of what is expected from the leadership by these working groups?
* Longer term: differences between paid members and volunteers and how this could have an effect on working group dynamics
* Would need more clarity of which decision making powers are part of the WGs and which ones aren't +1
* Lack of clarity for decision making processes generally e..g when conflicts of opinion do arise and can't be resolved within eg WG
* Some sense for formal structure to delegate authority could help "get stuff done". Does this clash with a community led project?
* How formalised is the decision making process? https://medlabboulder.gitlab.io/democraticmediums/
* How do we identify the need for dedicated time over volunteer time? Is there a process for requesting that?
* Translation group is "independent enough" to have tried a governance model and, currently, it's basically making sure that each language works the way that suits them best. So it's explicit that everyone can decide (which is different to not having any governance, I imagine). However, our written documentation was proposed as preliminary and shared among the co-leads but never made public/official or discussed in detail between us or the team, so the "actual governance model" is transmitted orally during the onboarding process and the emphasis may change depending on who's talking (no big problem about this). Being named co-leads was great as recognition but our own offboarding if we have too much work has been unclear.

Have questions or feedback to organisers? Have ideas for how you would you like to get/stay involved? Please add them here.
(2-3 min silent note taking)

Thank you for joining us! Questions and Reflections
Wrap up and next steps [Anne+Malvika]
Please add your questions/reflections from The Turing Way

**Not sorted**: Kirstie, Malvika, Arielle, Alex, Anne

#### Identifying key needs for Volunteer Working Groups

*Review this document that includes a draft information of your group. In particular, focus on your 'urgent needs' section: both strategic and operational.*

* Group 1 - Translation and Localisation Team: https://docs.google.com/document/d/1_Ofh0i8O5sFyNULi1UqI1Bhk57k8ucFsQuVcasyErN0/edit
* People: Batool, Andrea, Camila,
* Group 2 - Infrastructure Maintainers Team: https://docs.google.com/document/d/162ZaTNMxnH2PyTsJ44ResoXNlDxyxjigyfwDQAHuhtc/edit
* People: Danny, Sarah, Jim, Bastian

#### Reviewing sample structures needed for Working Groups

*These two groups will explore and revise a proposed structure for their working group: ask lots of questions in the document, and take notes if something is unclear*

* Group 3 - Trainers & Mentors WG: https://docs.google.com/document/d/1BIhrCLFOJVuopUNiOfd2OkDObMsX_2z_ALIUNQYW56o/edit?usp=sharing
* People: Eirini, Emma, Alden
* Group 4 - Reviewers & Editors WG: https://docs.google.com/document/d/1CZlkzBrez4YOwpGyFUGJygeXkglufVFuoqAvng6OuA4/edit#
* People: Esther, Hari, Jen, Vicky
* [No group currently] – Accessibility WG

#### Templating support for External Collaborators

*This shared group will discuss and answer the questions below (don't forget to take notes!), related to needs & priorities for groups that are external collaborators with The Turing Way*

* Group 5: Environmental Data Science Book, Turing Commons, Netherlands eScience Center, VU Amsterdam
* People: Alejandro, Chris, Carlos, Lena

Questions:
* What is your status and short description of your collaboration with TTW?
*
*
*
* What are the differences & similarities between your collaborations?
*
*
*
* What support do you require to enable this collaboration?
*
*
*

#### Supporting onboarding for volunteer & Turing staff for project

*This shared group will discuss and answer the questions below (don't forget to take notes!), related to needs & priorities for groups that are external collaborators with The Turing Way*

* Group 6: New staff members with TPS members to TPS & TTW Community Members
* People: Arron, Gabin, Cassandra, Shakir, Sophia

Questions:
* How have you been engaged in The Turing Way so far?
*
*
*
* What would be helpful in preparing you in order to join a working group and/or team?
*
*
*

#### FAQ
- If you are a part of two working groups, choose the one is that is most relevant for your ongoing work.
- If you have been put into the wrong group, please flag for Alex & Anne, and we will put you into a different group
-

### Gathering references & suggestions for governance (5 min)

We would like to review 2-3 existing governance document that could enlighten our process.

**What examples of project governance documents that you could be useful for The Turing Way?*** (3min)
* Examples (Note: they don't have to be only open source digitally-focused projects!)
* Kubernetes: https://github.com/kubernetes/community/blob/master/governance.md
* Decidim: https://meta.decidim.org/assemblies/our-governance
* Open Life Science: https://docs.google.com/document/d/1pD_P8oKLenyxCM39PZxu3X8a6hZQ4jZi-fA-xBB3DXQ/edit#heading=h.gjdgxs
-
-
-
-
-
-

***Please fill out the survey if you haven't already: https://forms.gle/dEyWZpcMUEVbpGYm7***

## Reviewing previous core team decisions (5 min)

Reviewing previous core team tasks. We will not be able to move forward on these points – yet.

[ Alexandra ]

**Status: Stalled**
- Switching to ReadTheDocs (from Netlify)
- Creating processes with Infrastructure Maintainers WG.
- Organising the Github Repository - Github organisation vs new repositories
- All-Contributors-Bot - updating for new translation roles
- Emerging interest groups:
- Translation & Localisation: ACC stepping out and new member joining
- Accessibility: transitioning into WG, some members not part of core team
- Environmental Sustainability: New partnership emerging with Environmental Data Science Book
- Membership to Core Team
- Developing structure proposals
- Account permissions
- Infra WG wanting Github team - not possible under ATI Organisation
- Translation & Localisation team wanting to use main org for translation - not possible under ATI Organisation

### Closing & Next steps (5 min)

[ ]

*
*
*

#### Reviewing reflections from 2022 (if applicable - from June 2022)

What affects your ongoing and future participation in *The Turing Way*? What support looks like for you in *The Turing Way* -- What should be maintained/retained? What should we include/strengthen going forward?

* Lena - I personally learn a lot from the Turing Way and enjoy contributing. If my organisation commits to contributing than I have an even stronger motivation to do so. It's important to have sustainability: some security that the resource stays available. FOr my organisation, it woudl be good if we could involve more diverse researchers into the Turing Way, like humanities or social sciences doing qualitative research.
* Sample response
* Arron - I work better being able to block out half days or even a whole day and so I'm going to try and sort out meetings to allow for this. I also really enjoy co-working (I'm in Wales 😥) so if anyone else likes to work that way I'm more than happy to work together. My experience is mainly around analysis of healthcare data i.e. in secure environments so anything around security, hosted environments and data science tools really interests me - hit me up if that's your thing too!
* Sarah - Time. As always. It's inevitable. For the near future, my participation will look like a collaboration between The Turing Way and myself as JupyterHub Community Strategic Lead to develop strategy in the JupyterHub community by drawing on the Turing Way's learnings, and contributing anything new upstream. Support for this probably looks like brainstorming meetings with community/strategy experts. But it's difficult for me to participate in things like Collaboration Cafe/Book Dash because I need to be interruptible as a legacy member with a lot of context and expertise to share with newcomers. So these meetings are not conducive for me focusing on new/deep work.
* Batool - I think my participation is mostly to affected by awful time management skills. I like how I can block some time I the collaboration cafe for some work but this also get affected by other unexpected commitments.
* Achintya - I think I enjoy reviewing more than writing and so my contributions tend to be focused on reviewing PRs. But the main factor is time: I have a couple of half-baked branches sitting on my local machine that I haven’t had time to work on for a while. Don’t really have an opinion of what needs to be retained etc.
* Hari - The specifics of contributing to the Turing Way are quite different from other day-to-day requirements of my role, so I think it's the clearly earmarking time for being involved - I also think the lack of time sensitivity for a lot of Turing Way contributions makes it easy to become an eternal 'Important not urgent' i.e. 'if I have time' task... but actively setting aside time/a window to engage with Turing Way contributions would help. In terms of what to do going forwards, I feel like some more guidance/direction on what contributions could look like (even maybe active coworking sessions where some easy 'Good first PR approval' tasks, or topic area ideas for chapters and ongoing collaborative content creation docs could be cool, so if you do have the spare time you can join a call/find a place easily where there's lots of actionable stuff to do )
* Andrea: Time, with timezones and different time availabilities we are having trouble working async and the decision making process is either slow or relies on very few people.
* Vicky- Time as always! I think I'm running out of things to contribute publishing content wise so need to think about what other content I could work on, especially since I don't have a data science background. I would like to link in the Turing-Roche partnership work but don't think I'm at a point for this yet.
* Alden - I find it can be difficult to know where to start, there are so many topics and issues, and it's something I come back to sporadically when I have some extra time, so maybe it would help to create a structure for myself with some contributions I'd like to make so that I don't have to search around for what needs to be done each time I sit down to work on it
* Alejandro - Time, busy in my postdoc research and family stuff 👼. I see myself participating Translation team meetings and contributing with creation/revision of new content/PRs in future book dashes. I'd suggest maintaining the community coworking meetings and novel events (firechats are amazing!). It would be great to share and improve metrics measuring the impact of TTW in research/education and private sectors.
* Emma - Being very busy on other projects does affect my time so going to regular co-working session does help me to get things done. Regular co-working and bookdash - bookdash is the most productive time for me, even the weeks leading up to it as I tend to prepare and so work more on the parts I am writng. I wonder if we can also plan book sprints - to block 1 day occasionally?
* Esther - I think I'm mostly hampered by work load to contribute, I don't think that there's a lot to be done there in terms of support :) I use the regular co working sessions as a blocker to really spend some time on the Turing Way, perhaps shorter sprint sessions could help so that I'm forced to block off time.
* Carlos - Time planning - booking time with people at the eScience Center is sometimes a bit of a nightmare (when I try to get people to join an event a month in advance they tend to already have planned a sprint to work on other projects, etc). I think if we were able to at least block times far in advance (ideally like a year) that would help a lot.
* Jen - defining a long-term goal as a RAM team (vetted by . the Core Team) I think will be helpful for us. That way we have a big picture to work towards as we make small, incremental progress each month/ tackle bigger chunks during Book Dashes. I think it is essential for us to regularly check-in with other TTW folks though to make sure we are moving in the right direction

### Future plans

What would you like to work on in the coming year? What support can we provide to help achieve your goals, and continue your participation in The Turing Way?

* Sarah - The JupyterHub Community Strategic Lead is a two year project with in-kind contribution with the Turing Way. So... _that_. As mentioned above, support looks like brainstorming and strategic thinking with other community/strategy experts so I'm not isolated in my work, and also cos the Turing Way has also thought through a lot of this stuff already.
* Arron - I would really like to produce content around working within secure, air-gapped environments and ensuring we can remain as collaborative as possible. I am also interested in accountability of Machine Learning and so trying to present best practices to do this is something I'd really like to work on!
* Achintya - I want to spend some time closing that lond-standing PR on communications/outreach, and also want to collaborate with Arron on the packages chapter. Plus I need to put in my case study from the ASG white papers… I’d also love to help onboard new members with using GitHub effectively, which I think I do fairly well.
* Hari - As the RAM role is so new at Turing (and apparently within the world) I really want to get a sense of what specifically a RAM does that is different and especially value-add than other roles, and then provide documentation/guidance on how to implement those skills. Not entirely sure what this looks like yet but a project to think about! Also encompassing pedagogy in some explicit way to TTW feels v applicable and important, would be cool to explore this too!
* Lena - I have a personal dream project of making a tesaurus for the Turing Way. This is my dream of learning semantics and doing somethign useful at the same time. For my insitution, I want to work on our guidlines and make sure they are organised and follow some template. The idea is to refer to the Turing Way for generic stuff and only have VU Amsterdam relevant information as our own resource
* Alden - finish the chapter that the RAMs started during the book dash, continue to support general TTW infrastructure (I helped install a bot to check for inclusive language, which was fun and felt helpful). I have a notion of working on some French translation, would probably not be the most efficient translator and I don't know if we already have things translated to French?
* Vicky - A case study on the collaborative workshops I ran for the partnership
* Esther - I would like to revise some of the RDM content and add some more recent resources to existing pages. Maybe transfer the Open stuff to the communications chapter. We're working on a research infrastructure paper and I would like to contribute insights from this back to the chapter that was set up by Arielle.
* Emma - Just finishing those sensitive data chapters would be good and then developing them more in line with the current work that I am doing.
* Alejandro - Get live & disseminate the translated version of TTW. SOS, support in the deployment and maintenance of TTW translated content in Netlify.
* Carlos - I would like to increase our contribution to all content related to research software. However, for this I know we need more resources -- the most important one being people's time.
* Jen - create materials through RAM role that can be resources/links in TTW like the reproducible-research-template some folks made awhile back. Hope this can help more of our colleagues who don't currently use/know of TTW engaged and invovled with our work
* Batool - I'd love to continue to do my work and make it reachable to the wider community in the Arab regions. I'd like (with the Translation team) to produce documentation of localisation that not only can be reused by other communities
* Andrea - I would love to see the translation team work out in the open and advancing with independent teams for languages. Time and other commintments ($) are constraints but the fellowship put this in priorities for the year. I would like to help implementing a culture of following accessibility practices to the current content and the ways of contributing.