Program Syllabus

Niklas Morberg (CC BY-NC 2.0)

Table of content

  1. The program
  2. Timeline
  3. Goals and Learning Objectives
  4. Schedule
  5. Community Participation Guidelines
    1. Diversity Statement
    2. Reporting Issues
    3. Attribution & Acknowledgements

The program

Purpose: Training for early stage researchers and young leaders interested in furthering their Open Science skills

Outcome: Ambassadors for Open Science practice, training and education across multiple European and international bioinformatics communities.

Process: A 15-week mentoring & training program, based on the Mozilla Open Leader program, helping participants in becoming Open Science ambassadors by using three principles:

  1. Sharing essential knowledge required to create, lead, and sustain an Open Science project.
  2. Connecting members across different communities, backgrounds, and identities by creating space in this program for them to share their experiences and expertise.
  3. Empowering them to become effective Open Science ambassadors in their communities.


  • October 25, 2019: Opening of the applications
  • 27 November, 2019: 8am PST / 11am EST / 4pm GMT: Pre-application webinar - learn more and register now
  • December 8, 2019: Closing of the applications
  • December 20, 2019: Successful applicants announced
  • January 2020: Start of the 15-week program
  • April 2020: Conclusion of the 15-week program

Goals and Learning Objectives

The vision of Open Life Science program is to strengthen Open Science skills for early stage researchers and young leaders in life science.

At the end of the program, our participants will be able to:

  • Describe and define the terms openness and open science
  • Give original examples for the types of openness in science
  • Design
    • Illustrate the need for a project, its vision, and its goals
    • Embrace and communicate the benefits of Open Science and how to strategically apply different open practices to their work
    • Identify the public resources to share their data
    • Identify the different type of Open Access and associated journals
  • Build
    • Start any project with openness in mind from day one
    • Setup a project repository on GitHub using best practices for enabling collaboration
    • Choose and apply open licenses appropriately
  • Empower
    • Create and enforce a safe working environment
    • Promote the values of Open Science to empower others to lead and collaborate
    • Include a broad range of contributors in their work
    • Communicate their work and vision in a 2min demo of elevator pitch
  • Lead an open project in science


Week Call type, length & date Topic Rough Agenda
1 Mentor (30 min) Meet your mentor! Meet each other and discuss general
      working practices and project goals
2 Cohort (90 min) Welcome to Open Life Science! Meet other members of your cohort
      Share project vision
      Intro to working openly (open canvas)
3 Mentor (30 min)   Discuss assignments from the cohort
      call & concrete implementations
4 Cohort (90 min) Tooling and roadmapping for Working with GitHub as a community hub:
    Open projects Markdown as a tool to make websites,
      Licence, Goals and Roadmap,
      Contributors, Code of Conduct
5 Mentor (30 min)    
6 Cohort (90 min) Developing Open Projects Open Science I: Project Development
      Open - Source, Software, Hardware, Data
7 Mentor (30 min)    
8 Cohort (90 min) Sharing Open Project Open Science II: Knowledge Dissemmination
      Preprint publications, DOI and citation,
      Open Education & Training
9 Mentor (30 min)    
10 Cohort (90 min) Designing for inclusivity Personas and pathways for contributors
      Implicit bias & mental health care,
      Community interactions & Ally-skill
11 Work on your own: No Call    
12 Mentor (30 min)   Invite an expert with mentor
13 Cohort (90 min) Project Review: Closed-group call practicing final demos
    preparation and practice Cohort offers feedback and improvement,
      feedbacks and suggestions
14 Mentor (30 min)   Preparing for the final demos
15 Cohort (90 min) Final presentations & Open and Recorded call
    congratulations! 2-minute demos of each project
      Audience: entire community & public

Community Participation Guidelines

As a community we welcome everyone, and encourage a friendly and positive environment.

This code of conduct outlines our expectations for participants within the community, as well as steps to reporting unacceptable behavior. We are committed to providing a welcoming and inspiring community for all and expect our code of conduct to be honored. Anyone who violates this code of conduct may be banned from the community.

Our open source community strives to:

  • Be friendly and patient.

  • Be welcoming: We strive to be a community that welcomes and supports people of all backgrounds and identities. This includes, but is not limited to members of any race, ethnicity, culture, national origin, colour, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion, and mental and physical ability.

  • Be considerate: Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and you should take those consequences into account when making decisions. Remember that we’re a world-wide community, so you might not be communicating in someone else’s primary language.

  • Be respectful: Not all of us will agree all the time, but disagreement is no excuse for poor behavior and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It’s important to remember that a community where people feel uncomfortable or threatened is not a productive one.

  • Be careful in the words that we choose: We are a community of professionals, and we conduct ourselves professionally. Be kind to others. Do not insult or put down other participants. Harassment and other exclusionary behavior aren’t acceptable. This includes, but is not limited to: Violent threats or language directed against another person, Discriminatory jokes and language, Posting sexually explicit or violent material, Posting (or threatening to post) other people’s personally identifying information (“doxing”), Personal insults, especially those using racist or sexist terms, Unwelcome sexual attention, Advocating for, or encouraging, any of the above behavior, Repeated harassment of others. In general, if someone asks you to stop, then stop.

  • Try to understand why we disagree: Disagreements, both social and technical, happen all the time. It is important that we resolve disagreements and differing views constructively. Remember that we’re different. Diversity contributes to the strength of our community, which is composed of people from a wide range of backgrounds. Different people have different perspectives on issues. Being unable to understand why someone holds a viewpoint doesn’t mean that they’re wrong. Don’t forget that it is human to err and blaming each other doesn’t get us anywhere. Instead, focus on helping to resolve issues and learning from mistakes.

Diversity Statement

We encourage everyone to participate and are committed to building a community for all. Although we will fail at times, we seek to treat everyone both as fairly and equally as possible. Whenever a participant has made a mistake, we expect them to take responsibility for it. If someone has been harmed or offended, it is our responsibility to listen carefully and respectfully, and do our best to right the wrong.

Although this list cannot be exhaustive, we explicitly honor diversity in age, gender, gender identity or expression, culture, ethnicity, language, national origin, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, and technical ability. We will not tolerate discrimination based on any of the protected characteristics above, including participants with disabilities.

Reporting Issues

If you experience or witness unacceptable behavior, or have any other concerns, please report it by contacting the organisers - Bérénice, Malvika and Yo. (

To report an issue involving one of the members, please email one of the members individually (,,

All reports will be handled with discretion. In your report please include:

  • Your contact information.

  • Names (real, nicknames, or pseudonyms) of any individuals involved. If there are additional witnesses, please include them as well. Your account of what occurred, and if you believe the incident is ongoing. If there is a publicly available record (e.g. a mailing list archive or a public IRC logger), please include a link.

  • Any additional information that may be helpful.

After filing a report, a representative will contact you personally, review the incident, follow up with any additional questions, and make a decision as to how to respond. If the person who is harassing you is part of the response team, they will recuse themselves from handling your incident. If the complaint originates from a member of the response team, it will be handled by a different member of the response team. We will respect confidentiality requests for the purpose of protecting victims of abuse.

Attribution & Acknowledgements

This code of conduct is based on the Open Code of Conduct from the TODOGroup.