EGEE JRA Organization meeting

Name: EGEE JRA Organization meeting
Start: 2003-10-28T10:00:00+01:00
End: 2003-10-28T17:00:00+01:00
Location: CERN

Tuesday 28 Oct 2003, 10:00 → 17:00 Europe/Zurich

600/R-002 (CERN)

600/R-002

CERN

Show room on map

Frederic Hemmer

Description

The morning session will be used to discuss Joint Research Activities in General.
The afternoon session will be used to discuss JRA1 more specific items (although relevant to JRA2 and JRA3)

- Overall JRA Overview¶
  
  Overview and organization of Joint Research Activities
  
  Objectives:
  Introduce general organization, status of the project, introduce people.
  
  Workout interrelations between activities (JRA{1,2,3} are intimately interrelated anyway).
  
  Workout membership of Architecture team, QA Group, Security Group.
  
  Assumptions: Technical Annex has been read at least for the JRAx part.
  - 1
    
    Overall JRA Overview¶
    
    Speaker: Bob Jones
    
    transparencies
  - 2
    
    JRA1 (Middleware) Overview¶
    
    Speaker: Frédéric Hemmer
    
    transparencies
  - 3
    
    JRA2 (Quality Insurance) Overview¶
    
    Speaker: Gabriel Zaquine
    
    transparencies
  - 4
    
    JRA3 (Security) Overview¶
    
    Issues to be discussed: VOMS
    
    Speaker: Fredrik Hedman
  - 5
    
    JRA4 (Network Service Development) Overview¶
    
    To be discussed: how will JRA4 code be integrated with the rest of JRA1 (tests, tools, nightly builds, etc...
    Also, this has not been referenced under JRA2
    
    Speaker: Javier Orellana
    
    more information
    
    transparencies
  - 6
    Interworking between JRA's¶
    
    a) Archtitecture Team¶
    
    Address Composition, meeting frequency and length
    
    Speaker: Bob Jones
    
    b) QA Group¶
    
    Items to be discussed:
    
    Integration procedure and associated checklist
    How to provide the 'EGEE developers' Guide" cf. EDG developers' Guide
    
    Release policy (cf. EDG release policy)
    
    Naming and coding convention (in case of new development)
    
    see http://eu-datagrid.web.cern.ch/eu-datagrid/QAG/QAGdocuments.htm
    Try to define composition, meeting frequency and length
    
    Speaker: Gabriel Zaquine
    
    c) Security Group¶
    
    Try to define composition, meeting frequency and length
    
    Speaker: Fredrik Hedman
  - 12:30
    
    lunch
- JRA1 Organization¶
  
  Objectives: identify list of tasks to be done, processes to be in place, documents to be released before project launch in April 2004.
  
  Attempt to identify possible events that could impact significantly JRA1.
  
  Identify people to be assigned in various working groups (QA, Security, EMT, Architecture) and their tasks.
  
  Identify meetings, their participation, frequency and location.
  
  Identify list of issues.
  - 7
    
    Tools - LCG Process Infrastructure (SPI)¶
    
    Alberto will describe the tools and processes in place for SPI (LCG Software Process Infrastructure)
    The idea is then to keep this in mind in the next two sessions to see what issues would be raised when adopting the SPI approach.
    
    Speaker: Alberto Aimar
    
    more information
    
    transparencies
  - 8
    
    Implementation Overview¶
    
    Items to be discussed: LCG-2 support, Middleware hardening, Common software organization, VDT/Globus, Containers, Unit Testing, Software Engineering Tools, People assignments. What will be part of the first release, who is going to be responsible.
    
    Speaker: Erwin Laure
    
    transparencies
  - 9
    
    Testing and Integration Overview¶
    
    Items to be discussed: Tools, Nightly builds, Nightly Tests, Testing process and validation rules (document needed).
    Site1/Site 2 tests. Which are the site, who is taking responsibility, what is the timing (PM3?)
    CVS, autobuild, autoinstall, testing, testbed needed (i.e. Integration testbeds presumably inherited from EDG; who will commit?)
    
    Speaker: Maite Baroso
    
    transparencies
  - 10
    
    EMT Organization¶
    
    Items to be discussed: this is mainly about processes.
    Which (documented processes) are needed. For example we need strict rules on interface definitions and freeze, as well as a process to make them change.
    How do you go from Release Candidate to manufacturing. Who are the members, how often do we need to meet.
    
    Speaker: All
  - 11
    AOB¶
    
    Speaker: All
    
    a) QA Industry example¶
    
    Visit of Mark Gilbert & Nikhil Shrikhande/ Microsoft on November 14, CERN. The developer lead and the program manager will go through how MS build (large) software (builds, checking tests, QA being separate from dev, specs, versioning, testing tools, etc) and see if there is interest to go further on some aspects.
    
    b) ARDA prototype activity¶
    
    The SC2 RTAG 11 (ARDA) Architectural Roadmap towards Distributed Analysis is being completed. This document (as well as HepCal) is supposed to form the basis of the requirements for EGEE Middleware. A likely outcome of this activity is that SC2 will recommend a prototype of ARDA to be build in the coming months. This could have important impact on JRA1 and JRA3, and clusters should be involved directly with it.
    
    transparencies