EMI SA2 Weekly Meeting

Name: EMI SA2 Weekly Meeting
Start: 2010-06-16T10:30:00+02:00
End: 2010-06-16T12:00:00+02:00
Location: CERN

Wednesday 16 Jun 2010, 10:30 → 12:00 Europe/Zurich

CERN

Description

Meeting Access Information:
- Meeting URL
http://evo.caltech.edu/evoGate/koala.jnlp?meeting=e8eteDvBvDataDa9I8
- Phone Bridge
ID: 62440
- Phone Bridges Numbers
http://evo.caltech.edu/evoGate/telephone.jsp

NOTE: THE MEETING IS RECORDED (for minutes-taking only purposes, then the files are deleted)

- 10:30 → 10:40
  
  Action List Review 10m
  
  Emi Sa2 Action List
- 10:40 → 11:10
  Task Reports and Progress 30m
  
  In this first meeting we will discuss on who is working on which task(s).
  - TSA2.1 – Work Package coordination 5m
    
    + Status and Progress - Mailing lists for each task created, can include people external to SA2. Contact me in case of problems to include people - Followed a few of the tasks kick-off + PEB Report - CERN accounts should being solved. Who still has no news about it? - Milestones and deliverable before M3 moved of 1 month - Announced that the EMI repository is available. PEB agreed that the 3 middleware should be added to the repository as they are, in 3 separate areas. A proposal and instructions is needed in a wiki page (task 2.4) +Issues to Discuss None + Step for Next Week - Deliverable DSA2.1 - M2 - DSA2.1 - Quality Assurance Plan (task 2.2) Reviewers: Francesco Giacomini (SA1), Andrea Ceccanti (JRA1) - M3 - DSA2.2.1 - QA Tools Documentation (task SA2.4) Reviewers: to be defined
    
    SA2 Internal Wiki
    
    Sa2 Meetings
  - TSA2.2 – Quality Assurance Process Definition and Monitoring 5m
    
    + Status and Progress - First draft of Software Quality Assurance Plan created: https://twiki.cern.ch/twiki/bin/view/EMI/TSA22#Software_Quality_Assurance_Plan - Feedback is being collected from WP leaders + Area leaders + Issues to Discuss - None + Steps Next Week - Understand the scope of the Quality Assurance Plan after collecting feedback from WP leaders + Area leaders - Start working on each specific section to define it in more detail when scope is defined
  - TSA2.3 – Metrics and KPIs Definition and Reporting 5m
    
    + Status and Progress SA2.3 kick-off meeting was quite loose/unstructured but was satisfactory. 1. The metrics survey has now been returned by all partners to Gianni and has been summaried by Gianni. 2. Eamonn contacted members of Cross-grid to obtain access to the project documentation. This has been studied, not a huge amount of extra insight has been added. 3. Alberto set up SA2.3 list and area leaders list. + Issues to Discuss Currently no issues to discuss, since a large amount of background reading and planning is still required. Query to area leaders will help with decision making process on planned metrics. We are still weighing up what can be obtained against what is actually useful for pushing quality over the next 3 years. + Steps Next Week Action points from SA2.3 meeting and progress so far (in braces): 1. Look at Sonar in addition to A-QCM (to be done). 2. Gianni to look at security plugins at CERN (in progress). 3. Eamonn will look at ISO standards on the web. TCD has free access to all IEEE publications (in progress). 4. Eamonn will contact area leaders about what metrics they see as being useful to their overall tasks (e-mail reviewed, to be sent). 5. We need a draft of metrics for a proposal in one weeks time to go into the deliverable due to be completed in two weeks time (in progress). 6. Alberto will contact SA2.5 partners by e-mail with Eamonn in CC.
  - TSA2.4 – Tools and Repositories Selection, Maintenance and Integration 5m
    
    + Status and Progress - Tool Inventory completed at 90% - https://twiki.cern.ch/twiki/bin/view/EMI/TSA24 - Missing ARC and APEL - Preparing summary document - Discussions with users/stakeholders about the tool integration - A proposal will be prepared during next days - The EMI Repository is in place - http://emisoft.web.cern.ch - Linked by eu-emi.eu - According to project requirements - Permission granted to the release manager - SA2.4 Mailing list has been created and people invited - Going towards an EMI-dedicated ETICS infrastructure - Import script for externals - Configuration validator + Issues to Discuss - Situation about CERN Accounts - I'd like to know what commitment I can expect from different people/partners + Steps Next Week - ETICS private Installation for EMI - Jira migration under our administration - Document: SA2.4 Plan draft
  - TSA2.5 – QA Implementation Review and Support 5m
    
    + Status and Progress Task SA 2.5 has not started + Issues to Discuss Activities before first reporting period Activities after first reporting period > + Steps Next Week -ask team leaders to assign persons to this task -update wiki page -first task meeting
  - TSA2.6 – Testbeds Setup, Maintenance and Coordination 5m
    
    + Status and Progress - A draft model of requirements, actual resources, problems and implementation proposal for Testbeds was provided. 11 subtasks were defined, we're still missing for a couple of assignee for these subtasks. - we had a meeting on 14th to discuss the draft with minutes and actions defined at https://twiki.cern.ch/twiki/bin/view/EMI/TSA26 - According to what discussed in the meeting a mail with feedback requests was sent to JRA1/SA1 and SW area Leaders. All main issues to discuss were mentioned in the mail and a meeting for Thursday (10:30 or 14:30) was proposed. There was a request for postponing the meeting to next week. This will depend on the deadline for the proposal. + Issues to Discuss - Deadline for the quality plan (deliverable DSA2.1) and contribution expected from sa2.6 (will the draft written be included in the quality plan once updated with developers' feedback)? Patrick is asking me to postpone the meeting to next week, could it be done? + Steps Next Week - collect feedback from developers and integrate the draft accordingly
- 11:10 → 11:30
  Issue and Topics to Discuss 20m
  - Task Tracking tools (Savannah?), WIki, Audioconf 5m
  - Definition of sub-tasks? 5m
    
    Example: repository, bug tracker, build tools, etc etc?
  - Deliverable DSA2.1 - Software Quality Plan 5m
  - AOB