This document provides details about the project members and contributors working (or previously worked) on The Turing Way in a paid capacity, organisational agreement, in-kind contributions or grant proposal-based collaboration. It further outlines expectations and responsibilities with regard to working on the project.
| Name | Affiliation | Full-Time Equivalent on the Project OR Community Roles | Time period allocated to the project | Previous roles |
|---|---|---|---|---|
| Kirstie Whitaker (@KirstieJane) |
PI, The Alan Turing Institute | - | Oct 2018 - Present | - |
| Malvika Sharan (@malvikasharan) |
Co-lead investigator, The Alan Turing Institute | - | Jul 2021 - Present | Previously: Community manager, Jan 2020 - Jun 2021 (100%) |
| Anne Lee Steele (@aleesteele) |
The Turing Way Community Manager, The Alan Turing Institute | 100% | March 2022 - Present | - |
| Emma Karoune (@EKaroune) |
Senior Community Manager, The Alan Turing Institute | 10% | Jan 2021 - Present | - |
| Arron Lacey (@arronlacey) |
Senior Community Manager, The Alan Turing Institute | 10% | Nov 2021 - Present | - |
| Achintya Rao (@RaoOfPhysics) |
Community Manager, The Alan Turing Institute | 10% | Nov 2021 - Present | - |
| Vicky Hellon (@vhellon) |
Community Manager, The Alan Turing Institute | 10% | Nov 2021 - Present | - |
| Aida Mehonic (@AidaMehonic) |
Research Application Manager, The Alan Turing Institute | 10% | 2021 - Present | - |
| Alden Conner (@aldenc) |
Research Application Manager, The Alan Turing Institute | 10% | 2021 - Present | - |
| Arielle Bennett (@Arielle-Bennett) |
Project Manager, The Alan Turing Institute | 10% | 2021 - Present | - |
| Jennifer Ding (@dingaaling) |
Research Application Manager, The Alan Turing Institute | 10% | 2021 - Present | - |
| Sophia Batchelor (@BrainonSilicon) |
Community Manager, The Alan Turing Institute | 10% | 2022 - Present | - |
| Hari Sood (@harisood) |
Research Application Manager, The Alan Turing Institute | 10% | 2022 - Present | - |
| Eirini Zormpa (@eirini-zormpa) |
Community Manager, The Alan Turing Institute | 10% | 2022 - Present | - |
| Carlos Martinez-Ortiz (@c-martinez) |
RSE community manager, Netherlands eScience Center | in-kind contribution | Feb 2020 - Present | - |
| Esther Plomp (@EstherPlomp) |
Data Steward, Faculty of Applied Sciences at Delft University of Technology | in-kind contribution | Feb 2020 - Present | - |
| Sarah Gibson (@sgibson91) |
Open Source Infrastructure Engineer, 2i2c & JupyterHub Community Development | in-kind contribution | - | Prevously: Research Data Scientist, Nov 2018 - Aug 2021 (40%) |
| Callum Mole (callummole) |
Research Data Scientist, The Alan Turing Institute | Turing Binder Federation Membership - Project Contact | 2021 - Present | - |
| Luke Hare (lukehare) |
Research Data Scientist, The Alan Turing Institute | Turing Binder Administrator | 2021 - Present | - |
| Camila Rangel-Smith (crangelsmith) |
Senior Research Data Scientist, The Alan Turing Institute | The Turing Way Translation and Localisation Co-Lead | 2020 - Present | - |
| Batool Almarzouq (BatoolMM) |
Postdoctoral Researcher, KAIMRC and Honorary Research Fellow, The University of Liverpool | The Turing Way Translation and Localisation Co-Lead | 2020 - Present | - |
| Alejandro Coca Castro (acocac) |
Postdoctoral Research Associate, The Alan Turing Institute | The Turing Way Translation and Localisation Co-Lead | 2021 - Present | - |
| Andrea Sánchez-Tapia (AndreaSanchezTapia) |
Independent researcher | The Turing Way Translation and Localisation Co-Lead | 2021 - 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 |
|---|---|---|---|
| May Yong (@myyong) |
Senior Research Software Engineer | 40% | Oct 2021 - Jan 2022 |
| Lydia France (@LydiaFrance) |
Research Data Scientist | 50% | 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 |
All The Turing Way project 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): theturingway@gmail.com. You can also contact Malvika by emailing msharan@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.