I'm excited to let you know that OpenDerby is part of Mozilla’s Global Sprint https://mozilla.github.io/global-sprint/ on June 1st and 2nd, 2017. This is a fast-paced, fun two-day collaborative work event where we’ll come together online and in person to work and hack on open projects.

WELCOME SPRINTERS! To contribute, check out our Issues tracker. We’re looking for R, Python and Git content and links, open data, and OpenDerby organizers.

Open Derby solves an unanswered science problem in open collaboration. Participants will combine open data, Github, and Jupyter/R-markdown in an open notebook to ensure their findings are reproducible and openly available.

We've written a short manual explaining what OpenDerby is, and how you can adapt it for your own open needs.

• Why do open science?
• What is an Open Derby?
• How to run an Open Derby
• Research questions for Derbies
• Open resources

The derby concept is targeted at any research group, from coding clubs to academic labs, who want to:

1. Adopt open science tools for their own research
2. Learn how to collaborate openly
3. Support open science with an open notebook publication

We expect that most derbies will be run for graduate students who are interested in learning open science tools, but we encourage post-docs and PIs to take a leadership role.

In addition to learning new skills and gaining a publication, graduate students may also use Open Derby for course credit (though this will depend on the university curriculum)

Anyone can run their own Open Derby! We do suggest that the lead organizer is a senior PhD student, post-doc, or PI who already has some experience with using Github. All participants should also have a basic understanding of coding in R or Python.

More details on running your own event
Copy our Open Derby checklist for your own event

Although each derby will be unique, we encourage participants to share their open insights:

• which tools worked well for your lab group?
• how did you write the manuscript?
• did you find any interesting datasets?
• what did you publish?!

To learn more about contributing, check out our Issues tracker and see our contributor code of conduct..