Tracking tools

This wiki will help the IT-SDC-MI group decide the structure that should be used for the tracking tools

Basic assumption:

• Jira will be used to keep track of development and deployment
• Jira will be open to end users to see the status and comment
• GGUS/SNOW will be supported

The main discussion now is to decide if there should be a single project (with each application as a different component), or different projects per application. Other alternatives (like one project per rpm, or one project per category) have already been discussed and discarded (see Tracking Tools Presentation.

Jira concepts:

• Category: Project belong to a category. This is used only for the initial page. Current categories: ATLAS, ATLAS ADQ, IT Databases, IT Services, IT infrastructure
• Project:: Basic unit of jira. Roles, versions, notifications and workflows are defined at the project level. Current projects: AI, AI Monitoring, ATLAS simulation, Big Brother, CERN mobile web pages...
• Component: Projects can be divided into components. Examples: for AI has 45 component (cli, boson, archive, apollo...), GEANT has 3 components (framework, physics, navigation), lcgutils has 12 components (davix, gfal 1.0. gfal 2.0)
• Version: Originally, assignated to a project. Several projects put in the version the component name to which it applies

IT-SDC-MI applications

This table contains the applications that will be considered, and their current leader

Use cases

This table presents several use cases, and how they will be solved in the two approaches (one single project, one project per application)