06.02.2012 Project Executive Board Conference Call

From IMarine Wiki

Jump to: navigation, search

Contents

Agenda

Time: Monday February 6, 2012, 15:00 - 17:45 Europe/Rome

  • assessment of the actions identified in the previous PEB conference call;
  • assessment of the January WP reports prepared by each WP leader. Each WP leader has to prepare a concise report on major achievements, on issues and deviations from the plan (highlighting the identified countermeasures identified to solve the issue), and on the plan for the next short reporting period. In particular, cross-activities and cross-partners issues and results should be emphasized.
  • assessment of the status of deliverables;
  • assessment of the status of milestones.

Participants

TD WP1 WP2 WP3 WP4 WP5 WP6 WP7 WP8 WP9 WP10 WP11
P. Pagano L. Nguyen D. Castelli A. Ellenbroek H. Hanahoe A. Manzi L. Candela G. Giammatteo M. Simi G. Coro G. Farantatos G. Kakaletris

Main Discussions and Actions

Jan. PEB Actions Status

  • A template for documenting technical milestones produced by WP8, WP9, WP10, and WP11 will be circulated by the TD;
    • A template is available at gCube Wiki
    • The TD quickly described it. It should satisfy the needs of WP8-WP9-WP10 and partially WP11;
    • This should be used for, e.g. MS33, MS34;
    • These pages should be created and concur to "gCube features";
    • G. Kakaletris says that guidelines for the following aspects should be included:
      • standards should be highlighted (e.g. one of the key features might be dedicated to highlight this);
      • metrics on performance should be included (e.g. in key features);
    • Discussion should continue by emails and the template should be finalised soon;
    • The TCom mailing list will be used to propose enhancements and in one week time the final version should be ready;
  • TD should send an email reporting the major issues affecting the current version of the Monthly report, e.g. lack of contributions.
  • TD should describe the procedure for documenting milestones achieved;
    • DONE


  • The template for documenting technical milestones should be discussed through the TCom mailing list and finalised in one week;

M3 (Jan '12) Activity Report

On WP1 report:

  • the work focuses on the Quality Plan;
  • there is one deviation wrt the bi-monthly effort report;
    • if the missing contributions are expected by "new" partners, personal reminder should be sent;
    • this problem should be discussed also by the SB;

On WP2 report:

  • apart from what is in the Wiki, a number of MoU have been produced;
    • one of these MoU is about myOcean. However, this activity is not complete yet since it seems that there is no policy regulating the kind of interaction iMarine is planning;
    • is there any member in the consortium that might help (apart from Terradue);
  • DG-MARE decided to participate in the iMarine Board;
    • this is very important (also from the EC point of view);
    • a meeting with this Unit will be organised after the iMarine Board meeting to establish a more precise working strategy;

On WP3 report:

  • the work is on finalising D3.1 which governs the operation of the CoP;
  • 2 upcoming milestones MS7 and MS8;
  • there are some partners that are not reacting, namely FIN (unreachable), IRD, UNESCO, and CRIA;
    • this is quite evident, e.g. by reading WP3 monthly report;
    • this is a problem since a lot of tasks and activities depend from WP3 activities;
    • a recovery plan should be defined;
    • the next TCom meeting is very important, community should be prepared for it;
    • Anton asks for a different approach, e.g. WP8-11 should create descriptions of the Technological results achieved so far;
      • Anton will create a template for this;
  • the TD highlight the fact that the majority of Wiki pages expected by WP3 are almost empty:
    • this is a consequence of a difficulty in (i) collecting partner' contributions and (ii) business cases identification;
  • plan:
    • Anton roughly discussed about FAO resources activities;
    • CNR might contribute to the analysis of BC once they are ready;

On WP4 report:

  • the major issues are the newsletter production and the channel finalization;
    • TD: is TRUST-IT happy with the content that has been produced so far?
    • the information produced so far is almost ok as well as the Channel content (if we take into account the project phase) although it might be enhanced;
  • two points have been raised by Anton: (i) user interface design and (ii) ???;
    • A.E.: there are two UIs: the channel (too much information) and the VREs (they should look more professional);
    • D.C.: it is fundamental to clarify the request to TRUST-IT;
    • ACTION: this discussion should be part of tomorrow SB. Anton should prepare a bullet list of aspects that should be enhanced;
  • if a news feed will be in place, the target audience should be clearly identified;

On WP5 report:

  • D3.1 has been completed as well as M25 and M27;
  • Deviations: the part on policies definition is not complete (it will be ready by March, i.e. it should be ready for the iMarine meeting);
  • the infrastructure will be upgraded to 2.7.3;
  • the "support team" weekly conference call will restart (it might be weekly or bi-weekly);

On WP6 report:

  • the major problems are the lack of requirements driving VREs creation or development stemming from WP3;
    • A.E. gives a quick report on ICIS (e.g. the full life cycle should be supported), SPREAD, VTI and "Modelling";
    • a dedicated phone conference should be organised.

On WP7 report:

  • D7.1 is still under development;
  • the major deviation if for the "Testing Infrastructure";
  • gCube 2.8.0 is under planning, the components should be identified;
  • On Maven transition:
    • not all partners are aware of it, the should be informed;
  • maintenance release production performance should be enhanced;

On WP8 report:

  • the most consuming activity is on Resource Model which is ready for release;
  • the integration of this model in the core services is in place;
  • the migration to Maven is causing changes in the Software Repository component;
  • Re plan:
    • new software repository will be finalised during February and presented at the TCom;
    • the two expected milestones will be produced;
    • the implications of the new SW repository should be discussed with the rest of WPs;

On WP9 report:

  • Gianpaolo summarises the achievements documented in the activity report;
  • A.E. asked to be in CC for tickets documenting activities;
  • Terradue activity is not actually documented, this should be reported in TRAC tickets;

On WP10 report:

  • Gerasimos summarises the achievements documented in the activity report;
    • FORTH report has not been produced with the expected strategy, i.e. they put a document on BSCW;
    • FORTH is not yet collaborating with FAO on semantic aspects;
    • Overall, collaboration should be promoted;

On WP11 report:

  • Activity is progressing, including a methodology for producing the expected results;
    • several working groups have been/will be developed;
  • dependencies between this WP and the rest have been identified;
  • the expected deliverable is under development;


  • the following items should be part of the SB meeting:
    • lack of effort reporting;
    • User Interfaces problems and enhancements;
  • A.E. should prepare a bullet list of aspects that should be enhanced wrt the channel;
  • All should reinforce the TRAC exploitation, e.g. by documenting ongoing and future development activities. It should be a duty of WP Leaders to promote this approach;

Deliverables status

Some delay has been accumulated wrt:

  • D1.1 Quality Plan
    • this will be finalised soon;
  • D7.1 Software Release Procedures and Tools
    • this is under review;
  • D3.1 EA-CoP Operation
    • this is started recently, it is of type other and will be finalised soon;
  • D6.2 Applications and Tools Development Plan
    • this is started recently, it is of type other and will be finalised soon;


Milestones status

All planned milestones have been achieved.


N/A

AOB


Agreed Actions Summary

  • The template for documenting technical milestones should be discussed through the TCom mailing list and finalised in one week;
  • The following items should be part of the SB meeting:
    • lack of effort reporting;
    • User Interfaces problems and enhancements;
  • A.E. should prepare a bullet list of aspects that should be enhanced wrt the channel;
  • A.E. should create a template for describing the technological results achieved so far and agree on this with the TD;
  • All should reinforce the TRAC exploitation, e.g. by documenting ongoing and future development activities. It should be a duty of WP Leaders to promote this approach;
  • Next PEB Conference Call will take place the 5th March 2012, 17:00 CET through the webconference facility;
Personal tools