Governance
nf-core is committed to being an open, inclusive, productive, and open-source community. Anyone interested in the project can join the community and contribute to the project. All community members must comply with the Code of Conduct (CoC) at all times.
To help manage the project, nf-core has teams that are made up of community members that oversee core activities.
Loading graph
This page describes the structure of the nf-core community, including how governance teams are elected, their responsibilities, and how decisions are made.
Steering committee
Changes impacting the community require decisions informed by extensive experience with the nf-core project and the larger ecosystem. The steering committee is responsible for overseeing the running of the nf-core project.
The steering committee is made up of representatives from the core team and outside advisors who are familiar with the project. The steering committee is not a fixed size with its members being elected by the current steering committee. The steering committee will meet regularly to discuss the project, funding and personnel.
Responsibilities
- Guiding project initiatives
- Making decisions about the project, funds, and personnel
Members
Core team
The core team ensures the day-to-day running of the nf-core project and oversees the activities of governance teams.
The core team is made up of community members that have demonstrated a continued commitment to the nf-core community. New members will be invited to join the core team based on contributions, experience, and engagement with the community. The core team will aim to have representation from different genders, geography, and employers (e.g., academia, clinical and industry). Significant community decisions will be made by vote with any decision without a clear majority being passed to the steering committee to resolve. Core team members will appear as organization members on the GitHub organization and have administrator access to repositories.
Responsibilities
- Day-to-day community decisions
- Attendance at the core team annual meeting
- Regular attendance at monthly core team meetings
- Sub-roles within the nf-core governance teams
- A strong community presence
Members
Alumni
Safety
The nf-core community should feel comfortable contributing to the project without the risk of harassment or abuse. The safety team is responsible for ensuring the community is a safe place and responding to instances of misconduct.
The safety team is made up of community members who have displayed integrity, strong communication, and a genuine concern for community welfare. The safety team is elected by the core team, is not a fixed size, and will scale as the community grows. The safety team is not a part of the core team and can report directly to the steering committee.
Responsibilities
- Be responsible for the nf-core code of conduct
- Be available for nf-core events (online or in person)
- Promptly respond to reports of misconduct and escalate to the core team or steering committee as necessary
Members
Infrastructure
Tooling is a fundamental part of the nf-core community. The infrastructure team is responsible for the development and implementation of the nf-core tooling framework.
The infrastructure team will have one or more leads who are responsible for overseeing infrastructure efforts. The infrastructure team is elected by the core team, is not a fixed size, and will scale as the community grows. The infrastructure team will have administrator access to repositories.
Responsibilities
- Development and maintenance of nf-core tools, website, and mega tests
- Regular attendance at maintenance team meetings
Leads
Members
Outreach
Outreach is an important part of any community project.
The outreach team is responsible for overseeing the organization and running community outreach efforts, including, but not limited to, hackathons, and the #bytesize seminar series.
The outreach team will have one or more leads who are responsible for overseeing outreach efforts. New members will be invited to be a part of the outreach team based on experience and outreach activity. The outreach team is not a fixed size and will scale as the community grows. The outreach leads will have access to community social media and YouTube accounts (e.g., Twitter and YouTube).
Responsibilities
- Organizing and running the
#bytesizeseminar series - Leading the organization of hackathons, training sessions, mentorship program, and other outreach events
- Creating and sharing community content
- Regular attendance at outreach team meetings
Leads
Members
Alumni
Maintainers
nf-core test data, modules, and pipeline repositories require regular upkeep and maintenance. The maintainer’s team takes an active role in managing nf-core repositories in collaboration with the wider nf-core community.
The maintainer’s team will have one or more leads who are responsible for overseeing maintenance efforts. New members are invited to be a part maintainers team by current maintainers based on experience and activity in the community. The maintainer’s team is not a fixed size and will scale as the community grows. nf-core maintainers will have write access to repositories.
Responsibilities
- Respond to
#github-invitations - Review module, subworkflow, and pipeline release pull requests
- Manage repository access for community developers
- Manage test data
- Enable and promote nf-core community values
Leads
Friederike Hanssen
James A. Fellows Yates
Maxime U. Garcia
Members
Adam Talbot
Anders Sune Pedersen
Anders Jemt
Christopher Mohr
Daniel Lundin
Edmund Miller
Júlia Mir Pedrol
Gisela Gabernet
Harshil Patel
Jasmin Frangenberg
Jon Manning
Jose Espinosa-Carrasco
Louisa Perelo
Matthias De Smet
Matthias Hörtenhuber
Moritz E. Beber
Nicolas Vannieuwkerke
Ramprasad Neethiraj
Rob Syme
Simon Pearce
Sofia Stamouli
Jonas Scheid
We thank all the institutions and companies of the maintainers team for their support of nf-core.
Responsibilities
- Engaging with local, national, and international Nextflow and nf-core community
- Writing or sharing tweets, blogs, articles, and technical documentation
- Running nf-core events such as user group meetings, hackathons, workshops, and more
- Speaking about nf-core at meetings and events
- Acting as a local liaison for new community members