Skip to main content

Getting involved in the community

Bioconductor depends on contributions from people with many different roles and levels of involvement. Some help guide the project through its core team, advisory boards, or committees; others contribute by maintaining packages, reviewing new submissions, supporting users, organizing events, or joining working groups. These contributions strengthen both the project’s technical foundations and its welcoming, collaborative community.

This section introduces the groups and activities through which people help sustain Bioconductor, with links to learn more, get involved, or take on a formal role. Participation does not require a leadership title: sharing your skills, experience, and time in ways that suit you is a valuable contribution.

Core team

The Bioconductor core team supports the project’s day-to-day operation and development. Its work includes maintaining project infrastructure, coordinating releases, and helping the community resolve technical and organizational issues. Core team members bring experience from across the project, including software, infrastructure, and community support.

Members of the core team are listed on the Bioconductor Core Team page.

The core team is one way to take on a formal role, but it is far from a prerequisite for contributing. Package authors and maintainers, educators, users who answer questions, and people who help organize community activities all make valuable contributions. Many people participate in these ways without a formal appointment.

TipContact

Reach out to the core team at .

Community Advisory Board (CAB)

The Community Advisory Board supports the Bioconductor mission by coordinating training and outreach, and by helping users and developers participate productively and respectfully at every experience level. The board also helps connect community members with events and opportunities to contribute. CAB membership and governance are described on the Bioconductor CAB page, which also provides contact information and updates about membership.

TipContact

Reach out to the Community Advisory Board on the #community-advisory-board channel on the Bioconductor community chat or at .

Technical Advisory Board (TAB)

The Technical Advisory Board develops strategies for the long-term technical suitability of Bioconductor’s core infrastructure. This includes package addition and distribution, user and developer support, and tools for the broader developer community. The TAB also identifies technical and scientific aspects of funding strategies that support Bioconductor’s long-term viability. See the Bioconductor TAB page for its governance, current membership, meeting information, and contact channel.

TipContact

Reach out to the Technical Advisory Board on the #tech-advisory-board channel on the Bioconductor community chat.

Code of Conduct committee (CoC)

The Bioconductor website maintains a Code of Conduct page that redirects to the multilingual Project-wide Code of Conduct statement for Bioconductor which is progressively being transfered to the Code of Conduct section of this handbook.

TipContact

Reach out to the Code of Conduct committee at .

Working groups

Bioconductor working groups bring community members together around a shared topic or a defined set of short-term goals. They can focus on areas such as training, package development, data interoperability, events, or community support. Groups work toward agreed deliverables and may disband when their goals are complete; committees generally provide longer-term guidance or support.

The Bioconductor Working Groups site lists active groups, groups seeking participants, and inactive groups, along with their aims and contact channels. You can also propose a new group by submitting a pull request to the working groups site with its purpose, lead, initial members, relevant links, and initial goals. Proposals are reviewed by the Technical Advisory Board and/or Community Advisory Board.

TipContact

If you would like to join an active group, contact its lead through the Bioconductor Zulip channel listed on the Bioconductor Working Groups site.

Developer forum

The Bioconductor Developer Forum is a regular platform for users and developers to present existing infrastructure, discuss future developments, and consider changes that may affect the project. Meetings encourage informal, technical presentations and discussion, and help share institutional knowledge, package work, sustainable development practices, and upstream changes.

Attendance is open to all Bioconductor users and developers, regardless of background or experience. The forum usually meets on the last Thursday of each month at 4pm UTC for about an hour; check the Developer Forum page for the current schedule and announcements. Past meetings are available through the Bioconductor YouTube channel and the course materials page.

TipContact

To propose a presentation, contact the organizer listed on the Developer Forum page.

New package review

Every package submitted to Bioconductor goes through community peer review before acceptance. Reviewers assess whether a package is suitable for Bioconductor and is usable, well documented, maintainable, and interoperable with the wider ecosystem. The process is collaborative: reviewers provide actionable feedback and work with submitters to address issues.

Package authors can learn about submission requirements and the review process in the Bioconductor package submission guide. Community members who actively maintain a Bioconductor package can volunteer to review submissions. Reviews typically take 30 minutes to 1.5 hours, and assignments are distributed among active reviewers. New reviewers are onboarded with at least one paired review. See Review Expectations and Volunteer to Review for details.