This documents outlines expectations and responsibilities of project members and contributors of The Turing Way project with regards to working on the project.
| Name | Role | % working on the project | Time period allocated to the project |
|---|---|---|---|
| Kirstie Whitaker | PI | ||
| Malvika Sharan | Community manager | 100% | Jan 2020 - May 2021 |
| Rachael Ainsworth | Research Associate | 100% | Apr 2019 - May 2019 |
| Rosie Higman | Research Data Librarian | 20% | Jan 2019 - Mar 2019 |
| Becky Arnold | Research Software Engineer | 100% | Dec 2018 - Mar 2019 |
| Louise Bowler | Research Data Scientist | 40% | Nov 2018 - Mar 2019 |
| Sarah Gibson | Research Data Scientist | 40% | Nov 2018 - Mar 2019 |
| Patricia Herterich | Data Librarian | 40% | Nov 2018 - Mar 2019 |
| Anna Krystalli | Research Software Engineer | 10% | Dec 2018 - Mar 2019 |
| Alex Morley | Mozilla Fellow | not paid by project | Nov 2018 - June 2019 |
| Martin O'Reilly | Principal Research Software Engineer | 10% | Nov 2018 - Mar 2019 |
We're always around for a chat in our public Gitter channel: https://gitter.im/alan-turing-institute/the-turing-way
In addition, you can reach the team members through their preferred way of communication:
- Kirstie Whitaker: Mention me on a Github issue or pull request (@KirstieJane), or tag me in Gitter,
@KirstieJane. Don't be afraid to nudge if I've not replied after a day or two! 💖 - Malvika Sharan: Not full time on the project until mid-January 2020, but available by email 1 day per week at msharan@turing.ac.uk
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 named team members above, or tag them in the Turing Way Gitter channel so others can answer if the folks you're looking for are not around.
- Rachael Ainsworth
- Becky Arnold
- Louise Bowler
- Sarah Gibson
- Patricia Herterich
- Rosie Higman
- Anna Krystalli
- Alex Morley
- Martin O'Reilly
As most team 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. You can join members of the core team 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 🚀
- Once completed, issues should be closed immediately. By adding "closes #issue" or something similar in a comment on a pull request, merging the pull request will close the issue automatically.
- The team will have a weekly catch up to go triage on open issues, update the project board and agree on priorities for the next week.
- Pull requests should be reviewed in a timely manner.
- When reviewing a pull request, please do not use the "request a change" function but comment on the change or make a pull request to the file that should be merged.
All The Turing Way team members commit to
- making the implicit explicit by documenting their work
- dedicating time to update contribution guidelines and other core documents needed to facilitate collaboration
- feed back on issues in open source software used throughout the Turing Way by opening an issue in those open source packages and trying to fix them (including documentation)