Contact us#

Email: penchord@exeter.ac.uk

Address: South Cloisters, University of Exeter, St Luke’s Campus, Heavitree Road, Exeter, EX1 2LU, UK

South Cloisters photograph

Contributing to this site#

We welcome contributions to this book. In each case credit will be given. Please do not feel you need to be an expert to contribute all views and feedback are greatly appreciated. You can contribute in the following ways:

Typographical and grammatical errors#

If you spot a typo, spelling mistake, poor grammar (no matter how minor), or just feel a sentence/paragraph could be rewritten to improve clarity, I would greatly appreciate you reporting it. You can do that by raising a Github issue via the repository. The url is penchord/web#issues

When you submit an issue please provide:

  • Link to page of book with the error

  • Original sentence(s) that contain the error

  • Suggested fix

  • Label the problem as documentation.

Reporting bugs#

If you find a bug in any of the code examples including solutions to exercises please report via Github issues. Please provide the following:

  • The operating system and version you are using.

  • Details of your python dependencies or virtual environment if you are using one. (if using conda please provide a environment.yml file - see the conda exercises for help )

  • Steps to reproduce the problem including the url.

  • Please label the problem as bug

  • Optional: recommended fix.

Note: Before reporting a bug please check that the Jupyter notebook cells have been been run in order. I recommend selecting ‘Reset Kernel and Clear All Outputs’ from the Kernel menu and rerunning the notebook to confirm.

Submit general feedback or request new content#

The book will evolve over time. I’d greatly welcome feedback, via Github issues, on the book including requests for new new topics, chapters, or expanded sections on current content such as cases studies or package functionality.

Requests#

For new content requests please

  • Detail the requested content including description and lists of any relevant packages

  • Provide a case why this content relevant to health data scientist

  • Optional: provide an example

  • Label the issue an an enhancement

General feedback#

For anything I’ve not covered here please submit a Github issue labelled as feedback

Code of conduct#

If you wish to contribute in any of the above ways, including responding to feedback from others, then I ask you to follow the contribution code of conduct for this book.

  • Demonstrating empathy and kindness toward other people

  • Being respectful of differing opinions, viewpoints, and experiences

  • Giving and gracefully accepting constructive feedback

  • Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience

  • Focusing on what is best not just for us as individuals, but for the overall community

These guidelines are adapted from the Contributor Covenant

GitHub flow#

This guide explains how to follow GitHub flow to collaborate on projects, which includes:

  • Creating a branch

  • Making changes

  • Creating a pull request

  • Addressing review comments

  • Merging a pull request

  • Deleting a branch