Reporting a problem
If something on bioconductor.org is broken, slow, missing or different from before, report it, however small. Everything goes through one place, the issue forms in the bioc-infrastructure repo, so you don’t need to know which part of the system is at fault.
Where to report
| Problem | Where |
|---|---|
| A package won’t install, can’t be found, or a download fails | Package install problem form: the command you ran, the full output, your setup, and where you install from (bioconductor.org or a mirror) |
| A page, download, redirect or file on bioconductor.org doesn’t work | Something’s broken on bioconductor.org form: the URL, what happened and what you expected, how you accessed it, the output or a screenshot, and when you noticed |
| A suspected security problem | Email, never a public issue; see Security |
| Questions about these docs, corrections, anything else | bioc-infrastructure issues, or email seandavi@gmail.com |
| How to use a package | The Bioconductor support site |
| The wording of a page on bioconductor.org | Bioconductor/bioconductor.org issues; the prose still lives there |
A page that looks out of date may be a stale copy at the edge. The edge cache page shows how to tell from the response headers; report it either way, with those headers if you have them.
How triage works
- Both forms add the
reportlabel, which means “incoming, not yet triaged”. - One person triages reports by hand: Sean Davis, who operates the new stack (operations). No response time is promised and there is no on-call rotation.
- A report is moved to the repo that owns it (bioc-edge for serving, caching and the sync; bioc-website for how pages render; bioc-registry for the registry), or fixed with a linked pull request and closed here. For example, #47 (the About page showing HTML as code) was filed on 2026-09-29 and closed the same day by bioc-website#32.
On 2026-09-30, three reports were open (label:report). A written triage protocol and automated first-pass triage are planned in bioc-infrastructure#43, not built.
Security
Report vulnerabilities privately by email to Sean Davis (seandavi@gmail.com), as bioc-edge’s SECURITY.md describes. It says to expect a reply within a few days and asks you to allow time for a fix before public disclosure. The same route applies to problems found in the legacy bioconductor.org infrastructure; the maintainer coordinates disclosure with the Bioconductor core team. Don’t open a public issue for either.