[Fiware-apps] WPL/WPA Meeting Update & Todo's for WP3 members

[Heller, Markus]

Dear WP3 members,

As you might have heard already, I have taken over WP3 lead from Axel Fasse now. First, I would like to say "hello" to you all, I am looking forward to work with you all in the future.


I would like to update you on some items from this WPL/WPA-meeting that might be relevant for you from my perspective:


1)      FI-WARE Backlog Deliverable Items for Release 2:

TID announced that a "snapshot" of the complete backlog is taken on 30.April and that this snapshot is reported to EC as a deliverable without further modification by TID.



I would like to remind that you all update your backlog items to reflect your work properly prior to 30.4. (as backlog items serve as one basis for budgeting).
Please note that as usual this remains the sole responsibility of each partner to update their backlog items on their own (so no WP3 lead coordination etc. here).



For WP3, we currently check the current state of the WP3 backlog to see who has already updated the backlog. Please all check that you do this before the snapshot deadline.



2)      WP3 Software deliverables for release 2.2

We have communicated in the WPL/WPA call, that all our WP3 software deliverables for release 2.2 have been finalized and submitted for review by TID. Thanks for your contributions.


3)      FI-WARE Technical Roadmap



The technical roadmap will be resubmitted at end of April, two things are relevant for us:
a) Pablo (TID) to update all features for release 2.3 as discussed.
b) IMinds to introduce features for release 2.3 as discusses, if possible.

Link: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Applications/Services_Ecosystem_and_Delivery_Framework


4)      FI-WARE Architecture Release 2

TID announced that architecture deliverable will be submitted on a chapter basis and they are reviewing the complete documents within this week, not submitted yet.


5)      FI-WARE Open Specifications

As Miguel announced via fiware@ we will have one review of the open specifications.


We have assigned you as reviewers to the Cloud chapter. Please check if you have any time problems to start with peer review of Cloud Chapter parts on 30.4. (as listed below).
We will notify you when the Cloud Chapter has compiles the deliverable earlier than planned.



FYI Copied plan dates for review (from Miguels Mail to fiware@):
·         29/April/2013 - this day EOB I will expect the doc version of your chapter uploaded and ready on the open Specs cockpit
·         30/April/2013 - start of the peer review
·         08/May/2013 - end of the peer review. At the end of this day, the cockpit has links to all the reviews stored on the private project(a word doc tracking the changes).
·         10/May/2013 - end of incorporation of comments. This is done directly on thew wiki. At the end of this day, the Open specs cockpit has the new versions of the docs, with all changes incorporated. This docs must be re-generated from the wiki by the WPL
Open spec cockpit assignments: https://docs.google.com/spreadsheet/ccc?key=0AmxBgS-lWT4vdHYxYTVOZ3FrNEprZXRBZk80TGRLMGc#gid=0


6)      State of the Art Analysis Deliverable

A timeline for this deliverable has been announced. Please note the highlighted role of academic partners as main contributors for this state of the art deliverable, as was discussed in WPL/WPA meeting.


>From the DoW :
"A special deliverable on state-of-the-art emerging technologies will be produced every year. The R&D centers will be in charge of this task"
·         TID will create the skeleton of the deliverable based on the section "B.1.2 Progress beyond the State of the Art" in the original DoW.
·         Then this will be distributed to the WPLs for changes (that should be deep)
·         This will be  edited directly on the Word document as the result will not go to the wiki
·         Need to agree on a schedule & to appoint a lead editor

TID to create the TOC + original doc based on the one in the DoW

AP for each WP to organize themselves and distribute the work between partners (mainly for Academic partners but not only them)
·         April, 23 - Skeleton ready
·         May, 7 - Contributions from chapters
·         May, 10  - Peer Review ready (academia partners)
·         May, 17 - Feedback incorporated
·         May, 20 - Delivery
Please contact me if you have any further questions or need additional information on this.

Best wishes
Markus


Dr. Markus Heller
Senior Researcher
SAP AG
Vincenz-Priessnitz-Str. 1
76131 Karlsruhe / Germany

T +49 6227 7-52673

Pflichtangaben/Mandatory Disclosure Statements: www.sap.com/corporate-en/impressum<http://www.sap.com/corporate-en/impressum>

Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.

This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20130423/f38ecf1c/attachment.html>