• Why sharing code is not sufficient?

  • How to share computational environment?

  • What is Binder?

  • How to binderize my python repository?

  • How to publish my python repository?


  • Learn about reproducible computational environments

  • Learn to create and share custom computing environments with myBinder

  • Learn to get a DOI from zenodo for a repository.

Why isn’t enough to share your code?

Before we work in group and write our thoughts on why we need more than sharing our codes for reproducible research, let’s take an example from geospatial analysis where the first import in the code would be (please note that it is not necessary to install any of the packages mentioned below):

from osgeo import ogr, osr, gdal

Depending on how you install this python package, it may be necessary to have libgdal and its development headers already installed on your system; with information on the version you have used, etc.

Binder-1 (10 mn)

Lea is a PhD student in computational biology and after 2 years of intensive work, she is finally ready to publish her first paper. The code she has used for analyzing her data is available on github but her supervisor who is an advocate of Open Science told her that sharing code is not sufficient.

  1. Why isn’t enough to share your code?

We form small groups (4-5 persons) and discuss in groups. If the workshop is online, each group will join a breakout room.

Each group write a summary (bullet points) of the discussion in the workshop shared document (the link will be provided by your instructors).


Binder allows you to create custom computing environments that can be shared and used by many remote users. It uses repo2docker to create a container image (docker image) of a project using information contained in included configuration files.

Repo2docker is a standalone package that you can install locally on your laptop but an online Binder service is freely available. This is what we will be using in the tutorial.

How can I share my computing environment with myBinder?

The main objective of this exercise is to learn to fork a repository and add a requirement file to share the computational environment with myBinder.

Credit: Juliette Taka, Logilab and the OpenDreamKit project (2017)

Binder-2 (15 mn)

  1. Fork the following github repository. In the top-right corner of the page, click Fork.
  2. Follow instruction given here to share the forked repository via Binder.

How can I get a DOI from Zenodo?

Zenodo is a general purpose open-access repository built and operated by CERN and OpenAIRE that allows researchers to archive and get a Digital Object Identifier (DOI) to data that they share.

Binder-3 (optional)

Everything you deposit on Zenodo is meant to be kept (long-term archive) so we recommend to use a repository you really wish to archive for this exercise.

  1. Link GitHub with Zenodo:

  • Go to

  • Log in to Zenodo with your GitHub account. Be aware that you may need to authorize Zenodo application (Zenodo will redirect you back to GitHub for Authorization)

  • Choose the repository webhooks options

  • From the drop-down menu next to your email address at the top of the page, select GitHub.

  • You will be presented with a list of all your Github repositories

  1. Archiving a repo:

  • Select a repository you want to archive on Zenodo.

  • Toggle the “on” button next to the repository ou need to archive.

  • Click on the Repo that you want to reserve.

  • Click on Create release button at the top of the page. Zenodo will redirect you back to GitHub’s repo page to generate a release

  1. Trigger Zenodo to Archive your repository

  • Go to GitHub and create a release. Zenodo will automatically download a .zip-ball of each new release and register a DOI.

  • If this is the first release of your code then you should give it a version number of v1.0.0. Add description for your release then click the Publish release button.

  • Zenodo takes an archive of your GitHub repository each time you create a new Release

  1. To ensure that everything is working:

  • Go to, or the Upload page (, you will find your repo is listed

  • Click on the repo, Zenodo will redirect you to a page that contains a DOI for your repo will the information that you added to the repo.

  • You can edit the archive on Zenodo and/or publish a new version of your software.

  • It is recommended that you add a description for your repo and fill in other metadata in the edit page.

  • Your code is now published on a Github public repository and archived on Zenodo.

  • Update the README file in your repository with the newly created zenodo badge.