[Fiware-data] Minutes of Data/Context Management Chapter weekly follow-up confcall

[Juanjo Hierro]

Hi,

  Please find bellow the minutes of our follow-up confcall yesterday.

  I couldn't close all my assignments yesterday morning, so I will try to get them done asap (check minutes)

  Best regards,

-- Juanjo


Attendees:

 *   Guy (IBM)
 *   Boris (TI)
 *   Markus (Siemens)
 *   María (UPM)
 *   Juanjo (TID)

1. Briefing on status of FI-WARE High-level Description (Product Vision) deliverable

  Juanjo briefed about the status of the FI-WARE High-level Description:

 *   The deliverable was officially released to the EC on August 15th.   You can find it at:
    *   https://forge.fi-ware.eu/docman/view.php/7/309/FI-WARE+High-Level+Description+v1.0+11-08-15.doc
 *   Now is under a formal/legal review process until August 29th (partners could object to publish part of its contents according to the Consortium Agreement that will be signed)
 *   After August 29th, it will be made publicly available and distributed to the UC projects

  Next step will be to transform it into contents of the Wiki.   From then on, updates will take place directly on the Wiki.   Therefore, second release of the FI-WARE High-level Description will consist on reminding the EC that they can get access to updated contents on the Wiki page.

2. Briefing on FI-PPP AB meeting and overall FI-PPP progress

  There was a face2face meeting of the FI-PPP AB on 11-12 of July in Madrid.   The FI-PPP AB includes 2 architects/technical-leads of all FI-PPP projects.   FI-WARE has two representatives: Juanjo Hierro (TID) and Thomas Bohnert (SAP).   Juanjo as Chief Architect of FI-WARE and chair of the FI-PPP AB.    This body is in charge of keeping projects synchronized in terms of planning, technical vision, etc.   It will be a forum where requests for entries in the FI-WARE Backlogs will be analyzed and issues resolved by consensus.

  The template for entries in the different project backlogs and particularly the FI-WARE backlog was indeed approved by the FI-PPP AB in the July meeting.

  There was a virtual FI-PPP AB meeting on August 25th.   Overall progress of the different projects was shared.   Regarding Use Case (UC) projects, more or less they are finalizing capturing of end user requirements for the application scenarios they wish to prototype.   For those UC projects that have adopted Agile themselves (not all), user requirements are mapped into User Stories in Backlogs that belong to those projects.   Now they are in the process of analyzing these requirements and finding out how they can be resolved from a technical point of view.   This process may lead to definition of requests for features to be provided by "Platform Enablers" they may wish to use.   These requests for features will be provided following the template for backlogs that was approved and will be provided as input to FI-WARE in the form of either Themes, EPICs or User Stories (term "user" doesn't map to "end user" really but to "applications" or even "application developers").   FI-WARE has to analyze this input an final decisions will be agreed regarding what should be transformed into an actual entry in the FI-WARE backlog or what has to be addressed as a specific development out of the scope of FI-WARE.

  Two tracker systems will be implemented to manage the communication with UC projects.   They will be based on the tracker facility of FusionForge.   One will deal with "Global Technical Support" and will be used, for example, to clarify doubts on the FI-WARE High-level Description.   The other one will have to do with managing the process of creation of entries in the FI-WARE Backlog.    Tickets in the tracker system will be issued by UC projects whenever they request a feature related to a platform enabler.

  Thomas and Juanjo are designing the management process for communication with UC projects and are dealing with the settings of the two trackers.   We expect to provide a demo by September 2 to FI-WARE WPLs and WPAs to get their feedback.   Then do the final tuning expecting that the tracker be configured by September 19 at the latest.


3. FI-WARE Data Backlog

  We checked the status of contributions.   Backlog entries have been produced for the main GEs for which an asset and provider had already been identified:

 *   CEP GE - IBM
 *   BigData Analysis GE - TID
 *   Publish/Subscribe Broker GE - TI
 *   Semantic Annotation Tool - TI
 *   Semantic Infrastructure GE - ATOS
 *   Multimedia Analysis GE - Siemens
 *   Query Broker GE - Siemens
 *   Localization GE - Thales

  All the contributions received so far have been placed under a FI-WARE Data Backlog folder.

  Juanjo will perform an overall analysis of the contributed entries and will circulate an email with some hints and comments.  Then each partner has to check this and develop any update that may be needed.

  All partners are requested to carry out a peer review of the entries of the rest of partners, starting on Monday August 29th and closing on September 2nd EOB (they should send comments before that deadline).   Then responsible of each GE will perform the necessary revision afterwards.   Goal is to get a first consolidate set of entries for the Data/Context Management Backlog by September 7-8.


4. Call for specific topic confcalls

   We should try to make as much progress as possible regarding some pending discussions before the f2f plenary meeting in Turin.   In some cases, scheduling dedicated confcalls.   Following is a list of pending topics we identified:

 *   Publish/Subscribe Broker specifications: We have discuss in detail how to approach the specification of the final interfaces to be supported.   However, Boris mentioned that we won't be able to make progress on this until Carlo (TI) comes back from his holidays.   We agreed to config a confcall involving TI, Orange and TID during the week starting September 5th.
 *   Localization Service: we need to setup a confcall involving Thales who unfortunately didn't attend the follow-up confcall.   Juanjo to setup a doodle to find date.
 *   Relationship betwen Query Broker and Publish/Subscribe query mechanisms: Boris to send an email summarizing position on the matter.   We'll try to keep the discussion over the email and try to reach consensus prior f2f meeting in Turin.   No confcall identified for the time being.
 *   Additional Thales assets: Juanjo to analyze and send mail with results of the analysis.

5. Other stuff

   There is a delay in setting the new version of the blogs/website infrastructure.   This is delaying the start of activities dealing with provision of contents in both the website and blogs.   Juanjo mentioned that he expects to see progress prior Turin.   He will keep the team informed.


________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20110827/ee121866/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jhierro.vcf
Type: text/x-vcard
Size: 429 bytes
Desc: not available
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20110827/ee121866/attachment.vcf>