Package Submission


Users are welcome to contribute new packages to Bioconductor. Packages must meet a checklist of standards of functionality, documentation, and interoperability. See Contact information to obtain instructions for submitting new packages.

Authors receive initial feedback in 1 to 3 weeks. Packages will be checked for adherence to the Bioconductor package guidelines and the checklist below by a member of Bioconductor team. Package developers should consult the full Bioconductor Package Guidelines. Submission implies commitment to package maintenance across multiple release cycles.


Packages must satisfy the following checklist:

Packages should also conform to the following:

[ Back to top ]

From submission to acceptance


Following acceptance of a package:


If the developer had made an error and not bumped the version from 0.99.1 to 0.99.2, then the package would be built by the nightly build process, but the new version would not propogate to the public repository. biocLite("DemoPackage") would return the old version 0.99.1 of the package.

[ Back to top ]

Additional Support

We are eager to enhance the quality and interoperability of Bioconductor software and will provide additional support when requested by package developers. Example areas of assistance include use of appropriate S4 structures, specific guidance on efficient implementation, guidance on code structure, and critical assessment of package documentation and structure. Use the bioc-devel mailing list or the Contact information below to obtain additional support.

[ Back to top ]

Contact Information

To submit a package or obtain additional support, contact Sonali Arora (email: bioconductorseattle NEAR gmail POINT com)

[ Back to top ]

Source Code & Build Reports »

Source code is stored in svn (user: readonly, pass: readonly).

Software packages are built and checked nightly. Build reports:


Development Version »

Bioconductor packages under development:

Developer Resources:

Fred Hutchinson Cancer Research Center