![]()
Documents:
![]()
Chair: Fons Rademakers (chair)
Mandate:
| Define a process for managing LCG software. Specific tasks to include: | |
| Establish a structure for organizing software, for managing versions and coherent subsets for distribution | |
|
Identify external software packages to be supported | |
|
Identify recommended tools for use within the project – to include configuration and release management | |
| Estimate resources (person power) needed to run an LCG support activity |
Timescale:
|
1 months for the initial report | |
|
2 months in total for the final report to SC2 |
Makeup: Experiment representatives, IT/API, and additional members at chiar's discretion
Members and experts: Marco Cattaneo, Gabriele Cosmo, Simon George, Fons Rademakers (chair), Stephan Wynhoff
Guidance:
| Procedures and tools will be specified | |
| Will be used within project | |
| Can be packaged and supported for general use | |
| Will evolve with time |
Additional constraints
| The RTAG does not make any recommendations on how experiment internal software should be developed and managed | |
| However, if an experiment specific program becomes an LCG product it should adhere to the development practices proposed by this RTAG |