ESMA Git Policy

Management Policy for the ESMA Git Repository

This document is to establish firm policies for the management of the ESMA repository under Git. For now we are just collecting various thoughts/opinions about existing practice that must be addressed by the document. After some accumulation, I’ll attempt to provide some structure for further refinement.

It is also worth noting that GFDL has a significant amount of documentation about aspects of their policy that might serve as good starting points for elements of our own.

Topics

- Roles and responsibilities
  - Committee to approve/change this document
  - End users
  - Gatekeepers
  - Administrators (super users)

-Commit rules
- Regression testing
   - Including how to evolve the regression tests
- Branch and release naming/tagging
- Externally shared components
- Issue tracking and monitoring
- Misc
  - E.g. special directory on discover for sw dev due to inode limitations