EGEE JRA Organization meeting
The afternoon session will be used to discuss JRA1 more specific items (although relevant to JRA2 and JRA3)
-
-
10:00
→
14:00
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.- 10:00
- 10:20
- 10:40
-
11:00
JRA3 (Security) Overview 20mIssues to be discussed: VOMSSpeaker: Fredrik Hedman
- 11:20
-
11:40
Interworking between JRA's 1h
-
Archtitecture Team 20mAddress Composition, meeting frequency and lengthSpeaker: Bob Jones
-
QA Group 20mItems 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)
Try to define composition, meeting frequency and lengthSpeaker: Gabriel Zaquine -
Security Group 20mTry to define composition, meeting frequency and lengthSpeaker: Fredrik Hedman
-
-
12:30
lunch 1h 30m
-
14:00
→
17:00
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.-
14:00
Tools - LCG Process Infrastructure (SPI) 30mAlberto 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 -
14:30
Implementation Overview 35mItems 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
-
15:05
Testing and Integration Overview 35mItems 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 -
15:40
EMT Organization 40mItems 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 -
16:00
AOB 20mSpeaker: All
-
QA Industry example 5mVisit 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.
-
ARDA prototype activity 20mThe 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.
-
-
14:00
-
10:00
→
14:00