Contributing to our materials#

The Data Ethics Club repository is a hub of information where we collect the discussions we’ve had as a group, our reading list, information about our past or upcoming meetings, and advice on running your own online journal club.

The Data Hazards project is always welcoming new contributors! This page gives you an overview of how you can get involved. You can see all of our wonderful existing contributors on the front page of this website.

We strongly welcome first-time GitHub users and are very happy to provide support if you would like to learn how to edit the repository. Please just get in touch by email if that is the case.

What kinds of contributions are we looking for?#

We’re open to any suggestions on how to improve the Data Ethics Club resources, from increasing accessibility to changing the structure of our content.

That said, we are particuarly open to additions for our reading list - the data ethics landscape is pretty huge and so its a group effort keeping on top of new pieces and issues to consider. We welcome videos, blog posts, white papers or journal articles relating to ethics and data science - these can cover anything from be the impact of algorithms on the people who are deploying them, to the ethics of surveillance and buying/selling personal data, to a more technical paper on the specifics of an explainable AI algorithm.

Usually if you are contributing to the reading list we will ask you to also provide three discussion points about the piece to help guide our discussion if we read (or watch/listen to) it for a Data Ethics Club meeting. You can look at our past meetings for an idea of the kinds of questions we consider.

Choosing accessible reading

Our aim with Data Ethics Club is to provide an [accessible][] and interdisciplinary space where people can think about data science and ethics and discuss it together.

With this in mind, we have the following guidelines for choosing reading:

  • Materials should be short enough to read/watch/listen to in an hour (maximum). If you suggest a longer piece, we will include it in the reading list, but won’t include it in a meeting until we’ve identified a smaller part of the piece to discuss.

  • Try to avoid closed access articles.

If you have further suggestions for choosing accessible reading, we’d love to hear them via GitHub or email

How can I contribute?#

We accept contributions in a variety of ways. You could:

We welcome any form of contribution so don’t worry if you do not use GitHub, just get in touch with us however works for you and we’ll be happy to hear from you.

Writing accessible content

We want the content on our website to be [accessible][accessible]. For this reason, we:

  • Use alt text on all images. See a guide to writing alt-text here.

  • Check any images included on the site for colour-blind friendliness.

If you have further suggestions for writing accessible content, we’d love to hear them via GitHub or email

Credit for contributors#

While there is a smaller group of people who send the emails and welcome people to the event, Data Ethics Club wouldn’t be what it is without any one of its contributors. Whether they have made suggestions to our reading list, Pull Requests to our GitHub repository, or firey hot takes in our discussions: thank you to each and every one of them!

We try to record all of these contributions, and you can see our contributors on the website home page. When you suggest something to us please let us know your GitHub username or a link to your personal site so that we can credit you, if you’d like us to. If you have not been properly credited, please let us know via email, or by commenting on this GitHub issue and tagging one our GitHub usernames (e.g. @NatalieZelenka).

Contributing via Pull Request on GitHub#

Here we have some guidelines for making your first GitHub contribution to Data Ethics Club a good experience.

If you think of something you’d like to work on, then first:

  1. Check if there is an existing issue describing the issue. If not, make a new one :).

  2. Comment on the issue before you start working to let us know you’ll be working on it, this helps us not to repeat work and gives and opportunity to discuss how to make your contribution most useful.

  3. Fork this repository to your own GitHub account

  4. Check that you are happy with the changes by building the site locally.

  5. Then, once you’ve made your changes, submit a pull request: we’ll review it as quick as we can 😄.

Build the site locally#

In order to build the site locally, you’ll need to run the following from your root directory: sphinx-build site/ site/_build/

These require some Python packages to run. You may want to set up a virtual environment first, so that you don’t install these packages system-wide. Then you can install the packages using pip install -r requirements.txt