In 2023-2024, The Turing Way adopted three institutional "levels", described in the Foreword of The Turing Way book.
- The “Community level" ("Operational-level”) norms that influence the everyday decisions and actions made by community members such in participating in the community and contributing to the book.
- The "Maintenance" (“Collective choice") norms that allow different groups of people to come together to work on and promote specific area/initiative in the project as well as define/change process to make operational level participation easier. In The Turing Way it happens through formal and informal Working Groups (WGs).
- The "Constitutional-level" norms are followed by project leaders who are allowed to change/approve collective choice rules and establish procedures for those decisions. They also are responsible for the project-related responsibilities that affect the whole of the project, community and their sustainability.
This document lists members at the "Maintenance" and "Constitutional" levels in The Turing Way.
It further outlines expectations and responsibilities for all of them with regard to working on the project.
| Name | Position; Affiliation | Project Role | Role length | Previous roles in The Turing Way |
|---|---|---|---|---|
| Kirstie Whitaker (@KirstieJane) |
Programme Director for Tools, Practices and Systems (TPS); The Alan Turing Institute | Founder & Project Lead - Constitution Level | Oct 2018 - Present | - |
| Malvika Sharan (@malvikasharan) |
TPS Senior Researcher - Open Research & Lead of Research Community Management Team; The Alan Turing Institute | Co-Lead - Constitution Level | Jul 2021 - Present | Previously: Postdoctoral Research Associate - Community Manager, Jan 2020 - Jun 2021 |
| Anne Lee Steele (@aleesteele) |
Research Community Manager; The Alan Turing Institute | The Turing Way Community Manager - Maintenance Level | March 2022 - Present | - |
| Arielle Bennett (@Arielle-Bennett) |
Programme Manager; The Alan Turing Institute | Project Manager and various maintenance level roles | 2021 - Present | Previously: Project Manager, The Alan Turing Institute |
| Name | Position; Affiliation | Community Role(s) | Role length | Previous roles in The Turing Way |
|---|---|---|---|---|
| Alexandra Araujo Alvarez (@alexandraaaj) |
Senior Research Community Manager, BridgeAI; The Alan Turing Institute | Various maintainer level roles | February 2023 - April 2023 | Research Project Manager, Feb 2023 - Apr 2024 (100%) |
| Liz Hare (@LizHareDogs) |
Qualitative Geneticist, Dog Genetics LLC | The Turing Way Accessibility WG member | 2023 - Present | - |
| Emma Karoune (@EKaroune) |
Senior Researcher - Community Building; The Alan Turing Institute | Book Dash WG member | Jan 2021 - Present | Verious maintainer level roles |
| Esther Plomp (@EstherPlomp) |
Data Steward, Faculty of Applied Sciences at Delft University of Technology | Book Dash WG member and various community roles | Feb 2020 - Present | Various maintainer level roles |
| Batool Almarzouq (BatoolMM) |
The Alan Turing Institute, The University of Liverpool | Translation and Localisation WG member | 2020 - Present | Various maintainer level roles |
| Melissa Black (melibleq) |
Independent Researcher | Translation and Localisation WG member | 2023 - 2024 | - |
| Andrea Sánchez-Tapia (AndreaSanchezTapia) |
Data Scienst, Global Fisheries watch | Translation and Localisation WG member | 2021 - Present | Various community roles |
| Alejandro Coca Castro (acocac) |
Research Fellow, The Alan Turing Institute | Environmental Data Science book Co-Lead | 2021 - Present | The Turing Way Translation and Localisation Co-Lead, 2021 - May 2023 |
| Sarah Gibson (@sgibson91) |
Open Source Infrastructure Engineer, 2i2c & JupyterHub Community Development | in-kind contribution, The Turing Way Infrastructure Maintainers Co-lead | 2019 - Present | Prevously: Research Data Scientist, Nov 2018 - Aug 2021 (40%) |
| Danny Garside (@da5nsy) |
Postdoctoral Visiting Fellow, National Institutes of Health (NIH) | The Turing Way Infrastructure Maintainers Co-lead | 2021 - Present | - |
| Jim Madge (@JimMadge) |
Senior Research Software Engineer, The Alan Turing Institute | The Turing Way Infrastructure Maintainers Co-lead | 2022 - Present | - |
| Brigitta Sipőcz (@bsipocz) |
Research Software Engineer, Caltech/IPAC -- NASA/IPAC Infrared Science Archive | The Turing Way Infrastructure Maintainers Co-lead | 2022 - Present | - |
| Johanna Bayer (@likeajumprope) |
Post Doctoral Fellow (CNS) | Infrastructure WG member | 2023 - Present | GSOC Co-Mentor 2023 |
| Carlos Martinez-Ortiz (@c-martinez) |
RSE community manager, Netherlands eScience Center | Book Dash WG member | Feb 2020 - Present | - |
| Susana Roman Garcia (@Susana465) |
PhD researcher, University of Edinburgh | Book Dash WG member | 2024 - Present | - |
The following people are no longer paid to work on the project (although they remain very valuable members of the community!) You can request contact information through the project members above, or tag them in the GitHub issues and Pull Requests so others can answer if the folks you're looking for are not around.
| Name | Role | Full-Time Equivalent (or %) on the project | Time period allocated to the project |
|---|---|---|---|
| Arya A. (@arya1302) |
Google Summer of Code (GSoC) 2023 intern | 50% | Apr 2023 - Sep 2023 |
| Lydia France (@LydiaFrance) |
Research Data Scientist | 50% | Oct 2021 - Jan 2022 |
| May Yong (@myyong) |
Senior Research Software Engineer | 40% | Oct 2021 - Jan 2022 |
| Federico Nanni (@myyong) |
Senior Research Software Engineer | in-kind | Oct 2021 - Jan 2022 |
| Iain Stanson (@Iain-S) |
Research Software Engineer | 30% | Nov 2021 - Jan 2022 |
| Paul Owoicho (@paulowoicho) |
Google Season of Docs - Technical Writer | 100% | Sep 2020 - Dec 2020 |
| Rachael Ainsworth (@rainsworth) |
Research Associate | 100% | Apr 2019 - May 2019 |
| Rosie Higman (@rosiehigman) |
Research Data Librarian | 20% | Jan 2019 - Mar 2019 |
| Becky Arnold (@r-j-arnold) |
Research Software Engineer | 100% | Dec 2018 - Mar 2019 |
| Louise Bowler (@LouiseABowler) |
Research Data Scientist | 40% | Nov 2018 - Mar 2019 |
| Patricia Herterich (@pherterich) |
Data Librarian | 40% | Nov 2018 - Mar 2019 |
| Alex Morley (@alexmorley) |
Mozilla Fellow | in-kind contribution | Nov 2018 - June 2019 |
| Anna Krystalli (@annakrystalli) |
Research Software Engineer | 10% | Dec 2018 - Mar 2019 |
| Martin O'Reilly (@martintoreilly) |
Principal Research Software Engineer | 10% | Nov 2018 - Mar 2019 |
| Camila Rangel-Smith (crangelsmith) |
Senior Research Data Scientist, The Alan Turing Institute | The Turing Way Translation and Localisation Co-Lead | 2020 - 2023 |
All members commit to
- making the implicit explicit by documenting their work
- abiding by the Code of Conduct in all community platforms and spaces where they represent The Turing Way
- following the contribution guideline and keeping it up to date
- recording any new updates, exceptions or useful knowledge in project management and core documents needed to facilitate collaboration
- dedicating their time and expertise in fixing open issues either directly via GitHub or providing mentorship and support to community members and project contributors
- feedback on issues in open source software used throughout The Turing Way by opening an issue The Turing Way GitHub repo or other open source projects where this issue can be fixed
- documenting and sharing any conversation from closed spaces (such as email, Slack or 1:1 meeting) in a GitHub issue that could be useful for the community or community members in enabling their work in The Turing Way
You can reach out to all members by tagging them on GitHub issues or Pull Requests or on Slack.
You can reach the lead investigators of the project through their preferred way of communication: You can mention Malvika Sharan (@malvikasharan) and Kirstie Whitaker (@KirstieJane) on a Github issue or pull request, or tag in Slack. In addition, you can reach The Turing Way by email (managed by the community manager): turingway@turing.ac.uk.
Please join the project members and the wider Turing Way community at our twice-monthly Collaboration Cafes, which are great places to discuss ideas for new contributions and to get started with making them. 🚀
Talks, presentations and recordings from different events are posted on our YouTube channel regularly.
The project members triage on open issues, review Pull Requests or address any questions raised on GitHub asynchronously. As most members do not work full time on the Turing Way, it might take some time until your query or contribution is addressed - especially if expert knowledge is needed. Don't be afraid to nudge if they've not replied after a few days! 💖
Project members will:
- monitor open issues and Pull Requests on the project's GitHub repository to identify if feedback, comment or connections can help address any concern or build on any suggested ideas/features.
- whenever possible, post about the issues and Pull Requests in public forums (newsletter, Slack, Twitter) to facilitate participation from new members in the community.
- review or assign a reviewer to open Pull Requests for review. This should be taken as an opportunity to connect contributors with specific interests, availability or technical skills that could be useful for the ongoing work.
- connect issues and Pull Requests where possible (for example, by mentioning 'Fixes #[issue number]' in the Pull Request description). By adding "closes #issue" or something similar in a comment on a pull request, merging the pull request will close the issue automatically.
- once completed, approve Pull Requests (for the contributors to merge them) and/or close issues immediately (if not linked to specific Pull Request) with a comment describing how it was addressed.
- when reviewing a pull request or commenting on issues, be specific, describe your ideas clearly, comment to request changes or make a pull request to the file that should be merged (please do not use the "request changes" option when reviewing Pull Requests).
- use your interactions on GitHub or other community spaces to provide support, mentorship and acknowledgement to our community of contributors.