Welcoming new members to the nf-core core team
We are delighted to announce that five long-time contributors are joining the nf-core core team:
If you have spent some time around nf-core, you probably have already crossed paths with them. Collectively, they have contributed to pipelines, modules, subworkflows, tooling, reviews, hackathons, helpdesks, training, and the many quieter tasks that keep a community running. Joining the core team is a natural next step for each of them.
Why we’re growing the core team
nf-core keeps growing. More pipelines, more modules, more users, more questions, more events, more grants, more collaborations across more time zones than ever before. These all are very good news but as the community scales, the work of coordinating and sustaining it scales with it, and thus we need more core team members!
Bringing new people into the core team is how we keep up with that growth and how we stay a healthy and welcoming community. New members bring new perspectives, new expertise, and new energy. They help distribute responsibilities more evenly, reduce the risk of burnout, and open up more opportunities for mentorship and leadership across the community.
Passing the torch
Just as importantly, several of our current core team members are moving into new chapters of their careers. This is something to celebrate: nf-core has always been a place where people grow, learn, and take the skills they build here into exciting next steps. At the same time, it means we need to prepare for these transitions thoughtfully, making sure the knowledge, responsibilities, and relationships that keep nf-core running are shared with people who are ready to carry them forward.
How the core team can help you
A bigger core team also means more capacity to handle the day-to-day tasks that require elevated permissions. If you need something that requires core team involvement: pipeline proposals, repository transfers, AWS test data uploads, Zenodo activation, upload custom Docker containers for modules, getting access to the GitHub organisation, or a first release review. The #request-core Slack channel is the right place to ask. A full list of what the core team handles and how to request it is described in the core team tasks documentation and in the governance page.
Looking ahead
A growing community needs a growing core team, but it also needs all of you. If you have been thinking about contributing more (reviewing a PR, answering a question on Slack, writing a module, joining a special interest group, or helping out in a maintainers or documentation team, now is a great time. The path from “first contribution” to “core team member” is well travelled, and today’s announcement is proof of that.
Welcome Arthur, Anabella, Louis, Matthias, and Simon. We are very glad to have you. 🎉
