Merge pull request the-turing-way#2 from pherterich/pherterich-patch-1

Create ways_of_working.md

ways_of_working.md

@@ -0,0 +1,47 @@
+# Ways of working
+
+This documents outlines expectations and responsibilities of project members and contributors of the Turing Way project with regards to working on the project.
+
+## Project team
+|Name | Role | % working on the project | Time period allocated to the project|
+|---|---|---|---|
+| Kirstie Whitaker| PI  |   |   |
+| Becky Arnold| Research Software Engineer |100% | Dec 2018 - Mar 2019 |
+| Sarah Gibson |Research Software Enginner | 50% | Nov 2018 - Mar 2019 |
+| Louise Bowler | Research Software Engineer | 50% | Nov 2018 - Mar 2019 |
+| Patricia Herterich | Data Librarian | 40% | Nov 2018 - Mar 2019 |
+| Rosie Higman | Research Data Manager | 20% | Jan - Mar 2019 | 
+| Anna Krystalli | Research Software Engineer | 10% | Dec 2018 - Mar 2019 |
+| Alex Morley | PhD Candidate in neurosccience | not paid by project |    |
+| Martin O'Reilly | principal Research Software Engineer | 10 % | Nov 2018 - Mar 2019 |
+
+## Communication
+We're always around for a chat in our public gitter channel: https://gitter.im/WhitakerLab/the-turing-way
+
+In addition, you can reach the team members through their preferred way of communication:
+- Kirstie Whitaker:
+- Becky Arnold:
+- Sarah Gibson:
+- Louise Bowler:
+- Patricia Herterich: if you need a quick answer, ping me on Twitter (https://twitter.com/PHerterich)
+- 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.
+
+## Project management
+### Issues
+- Once completed, issues should be closed immediately. By adding closes #issue or [something similar](https://help.github.com/articles/closing-issues-using-keywords/) 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
+- 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. 
+
+## Committments
+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 opeing an issue in those open source packages and trying to fix them (including documentation)