[Fiware-apps] overview about current wave of deliverables

Heller, Markus markus.heller at sap.com
Mon Jan 20 12:40:02 CET 2014


Hi all,

For your information, I put this current list of deliverables here (from WPL/WPA Meeting Minutes 20.01).

Your actions and next deadlines (grey)


1)    Architecture Deliverable AND Open Specs at M36partners (this schedule here only applies for the few "M36 partners" aka partners voluntarily not extending activities or closing on M33)

The schedules will be sent to the general mailing list once the placeholders are there

Where: Private wiki - placeholder links links to be created shortly
Juanjo will send the list of GEis with the status in relation with the closures requested by the EC

The following schedule applies to Architecture for all partners.
Applicable to Open Specs for those who do not extend their activities. And those who will be closed in M33 by the EC. Partners in any of these two cases.

       24/Jan/2014 - First draft of contributions by chapter ready for peer review
        - edition in PRIVATE WIKI
        - WPL to generate word doc for review
       27/Jan/2014 - .docx first version of chapter ready
       03/Feb/2014 - Comments on first draft (.docx with traced changes)
       07/Feb/2014 - .docx second version of chapters ready for the review of the coordinator
    From 7 to 17, interactions with the coordinator to refine the docs.
    17/Feb/2014 - Final .docx version ready for delivery + delivery to the EC
    24/Feb/2014 - Public wiki updated 100% with new architecture & Open Specs contents

@ALL: Please send until Friday...


2)    Open Specs at General (just for partners extending activities up to M40)


Where: Private wiki - placeholder links links to be created shortly

It applies just to those partner whose developments were not stopped by the EC AND those who are staying until M40 (both conditions must be met)

    14/Mar/2014 - First draft of contributions by chapter ready for peer review
        - edition in PRIVATE WIKI
        - Generate word doc for review
    17/Mar/2014 - .docx first version of chapter ready
    24/Mar/2014 - Comments on first draft (.docx with traced changes)
    31/Mar/2014 - .docx second version of chapters ready for the review of the coordinator
    From 31/Mar to 28/April, interactions with the coordinator to refine the docs. (note the that Easter is in this interval)
    28/Apr/2014 - Final .docx version ready for delivery + delivery to the EC
    5/May/2014 - Public wiki updated 100% with new architecture & Open Specs contents

@ALL. Please contribute as usual, no coordination needed, until the deadline.


3)    3rd party (D2.5.2)


Where: Directly on WORD

In previous meetings and in response to a question from Markus, each chapter decides what to send. There isn't a centralised "theme" at present. After  a bit of discussion, we decided to consider the suggestions from Markus and incorporate all or part of them to the TOC, following a uniform layout.

Makus proposed a number of topics that could be added to the current text per chapter. These are not sections names, just thing to take into account . The suggestion by Markus was:

  *   1.Architecture Changes: Description of changes in Architecture during reporting period that helped somehow the uptake/enablement of 3rd parties.
  *   2. Licenses/T&C Status: Diagram/Table showing overview of all WP3 license software assets and T+C info open specs (like in M24 review) and text explaining this
  *   3.FI-WARE Catalog & FI-LAB / Testbedas Status: Diagram/Table showing current state of availability in FI-WARE Catalog and FI-LAB (BUT: Two columns, one is "submitted for approval / available for publication", the other column "approved and published" à because current pipeline status would otherwise work against WP3 interests
  *   4.Software Releases Status: Exec Summary-like short overview of Software Releases 2 and 3 (as in the reporting period)
  *   5.Example success stories: how the WP3 e.g. for some UC enabled them to work...(optional, or leave out here and refer to reports on UC successes reported somewhere in other deliverables?).

    17/01/2013 - new and final deadline to send contributions

FYI: This work has not started on your side as partner.
@Markus: I will organize this work and send around the request for your contributions....


4)    Roadmap (D2.4.3)

Where: Directly on public wiki.

When a feature  is not going to be developed (stopped or not) we do not delete them and we put a standard sentence:


  *   "These features will be considered in coming releases but not in R3.3 "

Deadline: 21/January

@ALL: Please update as GE owner the roadmap now until deadline 21.1.



5)    State of the art (D2.6.3)

Where: Directly on word, no wiki here.

Due on M36 - only change: executive summary per chapter + changes if strictly necessary

Deadline to send contributions from WPL to the coordinator:  March,14

Info: Markus told that he would write an executive summary. Having discussed internally, we might change this so that all partners give their own part of the executive summary.

@Markus: I will update you on this asap, deadline is not urgent.


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


More information about the Old-Fiware-apps mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy