PTB Meeting

Tuesday 24 Jan 2012, 10:00 → 12:00 Europe/Zurich

lund.room.1 (Teleconference)

PTB meeting, 10:00-12:00, 24 January, 2012 Calling details: skype conference call with lund.room.1 Proposed agenda: ---------------- 0) Follow up, Actions i) Deliverable planning

-----------------------------------------
PTB meeting, 24 February 2012, 10:05-10:51

Present: Marco, John, Balazs, Laurence
Excused: Patrick, Jon


i) milestones

JRA1: MJRA13 (January!), MJRA111 (February), MJRA119 (February), MJRA112 (April)
MJRA17 (April)

Jon will monitor, take care of those

ii) preparation of EMI Year 3 development plan:


-Requirement status checking (including unfinished Y2 objectives): 2 February
-Requirement gathering, v6 (WLCG-TEG, EGI-TCB): no PTB meeting
-requirement analysis and prioritization: v7: 14 and 16 February
-Year 3 objectives:  v8, 21,22,23 February.
-Writing things down, cleaning notes, trackers, drafts (Balazs), no meeting: v9
-EMI-3 product portfolio agreement (consolidations): v10, 6 March
-DNA1.3.3 ready for review v12 (23 March)


The final agreed plan will be recorded in the DNA1.3.3 and the area workplans (DJRA1-4)


iii) format, content of the deliverables.

- DNA1.3.3 may need to contain some "architecture" like section

"a technology overview, list of tool requirements, high level (schematic) and intermediate level (technical) architectural designs, interface designs and interaction protocol definitions"

- area deliverables should be/contain:

"Increase the level of detail in technical deliverables, using examples only
of the work done; full technical designs are not required."

"The software design and development methodology is not yet visible and more
detail of the technical planning in deliverables has to be exposed."

- special suggestion for the security area workplan that John may consider:

"An alternative approach, starting from the perspective of attempting
to understand the threat surface presented by the EMI software stack, followed
by a consideration of “what it means to be secure in the grid” might reveal a
number of additional dynamic and behavioural security issues that could
additionally need to be resolved."

- while everybody should remember that

"Reduce the number of deliverables and improve their coherence as suggested
elsewhere in this review report. Reduce the number of actual printed pages of
the various reports"

- please remember the new deliverable template as well!