PTB Meeting

Tuesday 13 Jul 2010, 14:00 → 16:00 Europe/Zurich

CERN

Extraordinary PTB meeting

Starting Time: July 13, 2010 at 2:00 PM, Europe/Zurich
Duration: 2:00

 

Calling details:  skype test conferencing service (call mailmagnes in skype)

Screensharing: https://my.dimdim.com/arc-emi  (12345)

 

Proposed agenda:
----------------

0) Meeting notes / Actions follow up (5 min)

 

1) Feedback from Monday PEB meeting (5 min)

What is expected to be provided by the PTB.

 

2) Discussion of high level technical strategies ( 60 min)

What are the major objectives of the technical strategy irrespective of
the individual PT plans?

What is the relationship between the overall plan and the individual TA
plans, how do they complement each other? How is the plan organized?

 

3)  EMI components and product teams (50 min)

see EMI component table in v0.4 of the DNA1.3.1

 

4) AOB

Document DNA1.3.1 draft "post" v0.4 EMI_DNA1.3.1_draft.pdf

Extraordinary PTB meeting July 13, 2010 14:00 - 16:26 Present: Patrick, Massimo, John, Morris (left at four), Balazs (notes) not showed up: Laurence 0) Meeting notes / Actions follow up postponed for the next meeting 1) Feedback from Monday PEB meeting Balazs described the two input the PTB needs to deliver by Monday morning to the PEB: * list of technical objectives, approved by PTB * the list of the EMI component and product teams, approved by PTB 2) Discussion of high level technical strategies Balazs described the current objectives table of the draft. Agreement that every objectives must be linked to components (products!, not PTs), Completion time should be provided at least with a yearly granularity (M12, M24, M36). Balazs posted a long list, collected from the Dow. Patrick posted data area objectives, Massimo, John, Laurence, Morris has not sent anything yet. Thursday, 10-12 is booked for the discussion of the objectives. We'll go one by one. 3) EMI components and product teams Balazs explained the EMI Component table. Some changes were agreed (e.g. deployed -> in-production) Balazs will fill most of the table once the PT plans are approved by the area leaders. The component list will be approved (component by component) on Friday, 16 July, via an email voting. votes: yes, no, area leader vote 4) AOB * Infrastructure area workplan was submitted to internal review without being circulated or discussed in the PTB In the future, technical plan deliverables and milestones are asked to be circulated and approved first within PTB, before official internal release. * PTB members' availability in July: people are encouraged to use the out-of-office EMI wiki page Patrick (except next week), Massimo, Balazs, Morris, John will be available in July. No news from Laurence, he could already be on a vacation. * Milestones (what is the format, rules): postponed for later * Massimo proposed to consider the addition of the SA1 leader (Francesco) to the PTB. Discussion is postponed till the Autumn. ACTIONS: -------- * Balazs clarifies the release schedule with SA1. * Morris sends at least the names and a short description of the new JRA1 Product Teams: 9th July * all: send Balazs any kind of requirement list you can think of being useful for EMI * Area leaders: approve the PT plans. Please explicitly mention any major development items/products you consider out of scope for your area. deadline: Wednesday 14 July * Balazs fill component able by Thursday evening and sends it out for voting. * All: Vote on the EMI component list/PT list by Friday evening * John, Massimo sends technical objectives formulated according to the table by Wednedays evening *All: 10-12 Thursday: Tech objectives discussion meeting *Balazs sends the two tables to the PEB by Monday morning. *All: area workplans should be circulated and approved within PTB before it gets submitted to project office.