Table of Contents
Developers’ meeting
The next developers’ meeting will be 8-10 July 2025 at The Cosener’s House, Abingdon-on-Thames.
Source code
Bulletin board
- ccp4-dev – Mailing Lists
Miscellaneous
- Status of CCP4 server certificates
- A quick guide to using Bazaar [pdf] (April 2014)
- Users guide and Developers Guide to Missing Number Flags in MTZ files (old)
- Repository of X-ray crystallographic datasets from Structural Genomics consortia
- Test Data at Autostruct/CCP4
- CCP4i Developers Resource page
- Templates for using CCP4 library routines (September 1998)
- How to Write CCP4 Documentation [pdf] (February 1998)
- Information for CCP4 RAL Staff (restricted access)
Bugs and features
The usual way to report bugs or request new features is by email to ccp4@ccp4.ac.uk.
However, developers may take a more active approach by submitting reports and requests on the CCP4Forge site. If a tracker for the component in question is already set up, please use it. Otherwise, use one of the general trackers for series-65.
After the requested changes have gone out to nightly builds and are tested, an update request should be placed on the updates tracker, as described on the Project Home Page under the section Updates Tracker.