1. Innovative solutions for a safer, better world BUILDING STRONG ® Version Control Subgroup Coastal and Hydraulics Laboratory 16 January 2013 Mitch Brown, Matthew Farthing, Chris Kees, Chris Massey, and Gaurav Savant

2. Innovative solutions for a safer, better world BUILDING STRONG ® What is Version Control?  System that manages evolution of a document or collection of documents ► Source code, configuration management  source control management  Simple : foo_v09.c, foo_v1.c  Complex

3. Innovative solutions for a safer, better world BUILDING STRONG ® What is Version Control? (2)  Management Software + Repository = VC infrastructure  Zero-th step in software engineering [Heroux et al, 2009]  First test to see if we (CHL) can develop a more rational, organized software development process

4. Innovative solutions for a safer, better world BUILDING STRONG ® Survey of VC use in CHL 1What version control system(s) are you using now and where is the repository located (internal/external)? 2What features do you like the most/least about the system you’re using. What features do you wish your version control system had or supported better? 3How important is it that the repository be accessible from outside of ERDC? 4Should CHL support and maintain a central repository resource? If so, how should it be paid for? 5How should we encourage (or even enforce) use of version control in the lab?

5. Innovative solutions for a safer, better world BUILDING STRONG ® Current Use 1VC infrastructure  CMS, CSTORM-MS, ADCIRC, STWAVE, ADH, SEDLIB, PTM,CH3D, PT123, and GSSHA use subversion (svn)  PROTEUS, CMB use git  External repositories: CMS, CSTORM-MS, STWAVE, (Aquaveo),CMB (Kitware), PROTEUS (github)  Internal repositories: PTM, CH3D, ADH 2Satisfaction with your VC software  Recovery of past code state, managing parallel development  Something is better than nothing  svn (signification user base, familiarity), git (distributed VC support) 3 Outside visibility is a high priority for many development efforts

6. Innovative solutions for a safer, better world BUILDING STRONG ® Recommendations  Require VC for lab-funded developments. Identify in code source release and development plan  CHL should host its own repository with RDE, CorpsNet, and external access.  RDE IT staff, basic support under current responsibilities.  Enterprise github server $5K for twenty users per year.  svn and git are the preferred VC software. They meet the current needs of CHL developers and offer reasonable flexibility as we move forward.  Approval to use another version VC platform may be requested from the MAT.

7. Innovative solutions for a safer, better world BUILDING STRONG ® Recommendations (2)  CHL should fund training in the use of version control for lab developers  Chris Massey would require roughly $3k to prepare svn training sessions.  Kitware half day course on git ≈ $5.8k.