Developer Info

• OPeNDAP's GitHub repositories: OPeNDAP's software is available using GitHub in addition to the doenloads from our website.
• Continuous Integration builds: Software that is built whenever new changes are pushed to the master branch. These builds are done on the Travis-CI system.
• test.opendap.org: Test servers with data files.
• We use the Coverity static system to look for common software defects, information on Hyrax is spread across three projects:
  • The BES and the standard handlers we distribute
  • The OLFS - the front end to the Hyrax data server
  • libdap - The implementation of DAP2 and DAP4

Developer Guidelines and Information

The OPeNDAP FAQ has a pretty good section on developer's questions.

General development information

These pages contain general information relevant to anyone working with our software:

• Git Hacks and Tricks: Information about using git and/or GitHub that seems useful and maybe not all that obvious.
• Migrating source code from SVN to git: How to move a large project from SVN to git and keep the history, commits, branches and tags.
• Eclipse - Detailed information about running Eclipse on OSX from the Mozzilla project. Maybe a bit out of date.

OPeNDAP Workshops

• The APAC/BOM Workshops: This workshop spanned several days and covered a number of topics, including information for SAs and Developers. Oct 2007.
• ESIP Federation Server Workshop: This half-day workshop focused on server installation and configuration. Summer 2008
• Server Functions: This one-day workshop is all about writing and debugging server-side functions. It also contains a wealth of information about Hyrax, the BES and debugging tricks for the server. Spring 2012. Updated Fall 2014 for presentation to Ocean Networks Canada.

OPeNDAP Development process information

These pages contain information about how we'd like people working with us to use our various on-line tools.

• Hyrax GitHub Source Build This explains how to clone our software from GitHub and build our code using a shell like bash. It also explains how to build the BES and all of the Hyrax 'standard' handlers in one operation, as well as how to build just the parts you need without cloning the whole set of repos. Some experience with 'git submodule' will make this easier, although the page explains everything.
• How to use Eclipse with Hyrax Source Code Assuming you have cloned our Hyrax code from GitHub, this explains how to setup eclipse so you can work fairly easily and switch back and forth between the shell, emacs and eclipse.
• Making a Source Release. Once software is ready for distribution, use this checklist to make sure you do all of the steps needed to make a source release.
• How to configure a CentOS machine for production of RPM binaries - Updated 12/2014 to include information regarding git.
• Making RPM Distributions. Follow these steps to create an RPM distribution of the software.
• Making a Release of OLFS. Follow these steps to create the three .jar files needed for the OLFS release. Includes information on how to build the OLFS and how to run the tests.

Software process issues:

• How to add timing instrumentation to your BES code.
• How to write unit tests using CppUnit
• How to use valgrind with unit tests
• How to copyright software written for OPeNDAP
• Managing public and private keys using gpg
• How to Setup Secure Email and Sign Software Distributions
• How to Handle Email-list Support Questions
• Security Policy and Related Procedures
• Software version numbers
• Development Guidelines

Old information

Note: The following is all about using Subversion and is out of date as of November 2014 when we switched to git. There are still good ideas here...

• How to merge code
• Using the SVN trunk, branches and tags to manage releases.
• Making a Branch of Shrew for a Server Release. Releases should be made from the trunk and moved to a branch once they are 'ready' so that development can continue on the trunk and so that we can easily go back to the software that mad up a release, fix bugs, and (re)release those fixes. In general, it's better to fix things like build issues, etc., discovered in the released software on the trunk and merge those down to the release branch to maintain consistency, re-release, etc. This also means that virtually all new feature development should take place on special feature branches, not the trunk.
• Hyrax Package for OS-X. This describes how to make a new OS/X 'metapackage' for Hyrax.
• Making Windows XP distributions. Follow these directions to make Windows XP binaries.
• Making a Matlab Ocean Toolbox Release. Follow these steps when a new Matlab GUI version is ready to be released.
• Eclipse - How to Setup Eclipse in a Shrew Checkout This includes some build instructions
• How to configure a Linux machine to build Hyrax from SVN
• How to configure a SUSE machine for production of RPM binaries
• How to configure an Amazon Linux AMI for EC2 Instance To Build Hyrax
• Notes from setting up Hyrax on our new web host
• Subversion 1.7 documentation -- The official Subversion documentation; PDF and HTML.
• OPeNDAP's Use of Trac -- How to use Trac's various features in the software development process.