JRA1 - Middleware Development, Evolution and Integration (WP5)
D5.4.1: DJRA1.4.1 - Infrastructure Area Work Plan and Status Report (M3 - end of July 2010)
Documents
Draft version 0.1 - Workplan
Draft version 0.2 - Workplan
Final version for PEB - Workplan
Final version for PEB - Workplan review by Morris
Final Version ready for project-wide review
Tracking
2010-06-29 - Morris: Progress discussion with Laurence started
2010-06-29 - Morris: Wiki page created
2010-06-29 - Morris: Deliverable Template Location circulated
2010-06-29 - Laurence: Already started with docs, draft available end of week (2010-07-02)
2010-07-02 - Laurence: Send deliverable draft for review to the Infrastructure mailing list (see draft version 0.1)
2010-07-06 - Laurence: Send deliverable draft to
PTB (see draft version 0.2); still waiting for some inputs from PTs
2010-07-12 - Laurence: Send deliverable for review to the
PEB list (see final version for
PEB)
2010-07-28 - Morris: Upload of final version for
PEB to the official EMI deliverable page
2010-07-28 - Morris: Reviewed deliverable and uploaded the review to the page (see final version for
PEB reviewed by Morris)
2010-07-28 - Morris: Deliverable is rejected from JRA1 Leadership due to less internal discussions within the infrastructure area
- Reasons: see feedback and document review
2010-07-28 - Morris: Informed the
PEB and
PTB about the status of the deliverable and informed Laurence that the deliverable is rejected
2010-08-25 - Laurence: Provided a new version of the deliverable integrating the comments received
2010-10-04 - Morris: Confirmed that the deliverable is ready for project-wide review from the JRA1 perspective, see
EMI_DJRA1.4.1_draft_v3.doc
Feedback to the process
2010-07-28 - The documents should have the "Document Change Record" section filled and an updated teminology section with all the abbreviations
2010-07-28 - The deliverable should have been reviewed internally first within the infrastructure area before send it directly to
PTB and finally
PEB
2010-07-28 - Deliverables would benefit from figures that at least set the components and/or products in context.
2010-07-28 - Deliverables should provide dates as a date or at least a concrete month rather than "Spring 2011" and such like