EMI SA2 Weekly Meeting 20100602

Meeting Information

• Indico Agenda: http://indico.cern.ch/conferenceDisplay.py?confId=97027
• Action List: link_to_action_list
• Mailing List Archive

Actions:(by next meeting)

Action: A.Aimar - Learn/setup EVO conferencing for the WP.

Action: A.Aimar - Prepare wiki page describing how to use the infrastructure, wiki, mailing list, indico, etc...

Action: A.AImar - Publish the members of the mailing list

Action: Partners send the representatives for the TSA2.2 task (QA Process Definition and Monitoring)

Action: Testbeds survey should be completed and sent to D.Dongiovanni by end of the week. Danilo will send a first proposal by end of next week

Action: G.Pucciani will set up a first task tasked in Savannah.

Action: All partners should send clarifications about who participates to each task.

Minutes

Participants:(in the disorder, mail me if I have forgoteen your name)

Marek Kocan, Jozef Cernak, , Danilo Dongiovanni Gianni Pucciani, Tomasz Wolak, Maria Alandes Pradillo, Andres Abad Rodriguez, Alberto Resco Perez, Bjoern Hagemeier Anders Waananen, Eamonn Kenny, Alberto Aimar

Task Reports and Progress

In this first meeting we will discuss on who is working on which task(s). Material: Sa2-Subtasks.Pdf fileSa2-Tasks.Pdf file

Alberto A proposed to go through each SA2 task define who participates and leads the task.

---

TSA2.1 – Work Package coordination (Task leader: CERN, all partners participate to the meetings and reviews)
This task deals with the regular coordination of the Work Package, reporting and review of milestones and deliverables.

• A.Aimar will be the Task Leader
• Phone conferencing: Will investigate whether EVO can replace the CERN phone audiconferencing system
• Agendas: The WP will use the Indico system for its meetings here is the link: http://indico.cern.ch/categoryDisplay.py?categId=3001
• EMI SA2 mailing list is available: http://mail.eu-emi.eu/mailman/listinfo/emi-sa2/

the [emi-sa2] prefix is added automatically but tasks should add an additional prefix to more easily identify where the email belongs to. Later one can make a different list for tasks and subtasks. A.Wannaanen commented that JRA1 is doing separate lists but he advised us not to do too many mailing list at the beginning. Was agreed to keep a single mailing list for now.

• Wiki for EMI SA2: https://twiki.cern.ch/twiki/bin/view/EMI/EmiSa2-internal

If anyone has problems to access or modify the information in the infrastructure contact Alberto A for help.

Actions:
A.Aimar - Learn/setup EVO conferencing for the WP.
A.Aimar - Prepare wiki page describing how to use the infrastructure, wiki, mailing list, indico, etc...
A.AImar - Publish the members of the mailing list

---

TSA2.2 – Quality Assurance Process Definition and Monitoring (Task leader: CERN. Participants: CINECA, INFN, UPJS)
This task deals with the definition of a standard compliant software engineering process and the continual activity of monitoring its correct application within the activities of the EMI project. The success criteria of this task are the availability of an agreed, documented and regularly updated process and the minimization of deviation in its application by the project members

• DSA2.1 Software Quality Plan is for M1 will be probably given a bit more time.
• Partners are invited to send the names of the repreatnatives for this task
• CERN is the Task Leader and will likely be represented by Maria Alandes Pradillo (only some internal clarifications still needed).

Action:

• Partners send the representatives for the TSA2.2 task (QA Process Definition and Monitoring)

TSA2.3 – Metrics and KPIs Definition and Reporting (Task leader: CERN. Participants: TCD)
This task deals with the definition and continual collection and reporting of software quality metrics according to the A�QCM model or other suitable models. This task provides information to the Project Executive Board and other project This task provides information to the Project Executive Board and other project decisional bodies on the status of the software as an instrument to take corrective actions. The success criteria of this task are the regular production of reports and their use to identify improvement areas

• E.Kenny asked about the status of A-QCM in ETICs and whether will be used.
  A.Aimar replied that several A-QCM Metrics are in the next ETICS release but will have to be evaluated. Clearly having them in the build tool is an advantage compared to other metrics. A-QCM is based on standard metrics from ISO recommendations and common tools. One of the activity will be to check whether metrics currently available are suitable. The task will have to do the assessment.
• E.Kenny noted that the challenge of this task is to find useful metrics to really improve the software.
  

A.Aimar added that the challenge will be to select the tools and extract the information, SA2 is not going to write any tool just integrate them.

• A.Aimar asked to TCD whether they would accept to be Task Leader and this was accepted by E.Kenny. A.AImar wil communicate it to the Project Office.
• A.Aimar asked whether other partners want to participate to the task. No volunteers.
• G.Pucciani expressed interest to participate to the 2.3 task.
• Task Leader is Eamon Kenny

TSA2.4 – Tools and Repositories Selection, Maintenance and Integration (Task leader: CERN. Participants: CINECA, GRNET, INFN, UPJS)
This task deals with the definition and when necessary maintenance of the tools required to support the QA process. The task includes any supporting activity to software providers to integrate required information to and from other tools maintained outside the EMI project. The task also include the setup and maintenance of repositories for storing the EMI software packages, tests, build and test reports and metrics generated during all software development activities within EMI.

• Task Leader Lorenzo Dini (CERN)
• This task includes many technical activities (build, test, trasking, QA, etc) and maybe could be divided in subtasks, will be to the TL to decide.
• The overlap with QC in SA1 was discussed. Quality control in SA1 is done in using the SA2 tools, metrics, reports. The actual quality control, tests etc is done in SA1.

TSA2.5 – QA Implementation Review and Support (Task leader: UPJS. Participants: CERN, INFN, TCD, UPJS)
This task includes review activities of the QA, test and certification implementations done by the Product Teams, such as sample review of test plans and tests, compliance with packaging and porting guidelines, validation of and tests compliance with packaging and porting guidelines validation of documentation, etc. The task also includes supporting the Product Teams in effective design and implementation of tests to be used with testing tools such as ETICS. The success criterion for this task is the correct usage of tools and procedures by all project members to be measured by regular surveys and verifications

• Task Leader Jozef Cernak

TSA2.6 – Testbeds Setup, Maintenance and Coordination (Task leader: INFN. Participants: CERN CESNET FZJ)
This task consists in the setup and maintenance of distributed testbeds for the project continuous integration and testing operations and the coordination and provision of larger�scale testbeds from collaborating resource providers. The success criteria for this task are the availability and reliability metrics of the execution nodes.

• Task Leader is Danilo DOngiovanni (INFN)
• Task started and actions, minutes and available in this wiki web
• ARC would like to be participant of task 2.6
• A deadline for the answer to the survey is needed. Was agreed that the answer should be provided by end of the week.

Action: Testbeds survey should be completed and sent to D.Dongiovanni by end of the week. Danilo will send a first proposal by end of next week

Issue and Topics to Discuss 25'

• Task Tracking tools. Was agreed that for now we create a SA2 project ijn savannah and follow the tasks in there.

Action: G.Pucciani will set up a first task tasked in Savannah.

• WIki, Audioconf 05'

Action: A.Aimar document how to connect to mailing list, wiki and audioconf

• Definition of sub-tasks? For example: repository, bug tracker, build tools. TSA2.4 is one where is it quite obvious.

• Participation to the tasks

Action: All partners should send clarifications about who participates to each task.

• Deliverable DSA2.1 - Software Quality Plan

• AOB
  • Timesheets for May will be filled with the ones of June, when PPT will be ready

Next Steps:

-- AlbertoAimar - 03-Jun-2010