EPICS Code Management
Most of the infrastructure already exists for EPICS:
- Central source code CVS repository at APS.
- Secure-shell access to the repository for trusted individuals.
- Web-sites, although many documents need maintaining.
- Tech-talk mailing list for discussions and problem resolution.
We should continue using these for hardware support, but need:
- Active module owners and peers for each hardware support collection.
- Central module directory web-site with links to the ...
- Web-sites for each hardware support collection, containing at least:
- Module source code.
- Contact information for the module owner.
- Some documentation for each support layer?