[Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap

[t.elsaleh at surrey.ac.uk]

Hello Tobias,

>From USurrey point of view, we have edited the Technical Roadmap deliverable wiki page to accommodate USurrey's Epics and Features headers to the table for the Backend Second Release.

One question, can we just link these headers to their corresponding original Epic/Features pages, or do we have to duplicate the content as an internal link?

Best regards,
Tarek



From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs
Sent: 15 August 2012 10:32
To: Juanjo Hierro; fiware-iot at lists.fi-ware.eu
Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap

Hi all,

I just created a first version of the Revised Technical Roadmap.

It might look nice at first glance, however the assignment of Features to Release number is nearly completely RANDOM, based on my GUESSING.

https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT_%28Resubmission%29

So please please, we need every partner to revise the page above, and I guess this is by today.

It is a task that every GE owner can fulfill within fifteen minutes, so I would say we will not run into editing conflicts.
Please send an email to this list when you are done editing, so that we have an overview.

As many people are on holiday, the big question is what to do with the GEs owners who cannot do this task in time. Rather remove the features, or rather keep the random assignment to releases?

Best regards
Tobias

From: fiware-iot-bounces at lists.fi-ware.eu<mailto:fiware-iot-bounces at lists.fi-ware.eu> [mailto:fiware-iot-bounces at lists.fi-ware.eu]<mailto:[mailto:fiware-iot-bounces at lists.fi-ware.eu]> On Behalf Of Juanjo Hierro
Sent: Mittwoch, 15. August 2012 11:04
To: fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>
Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap

Hi all,

  There were clear and precise instructions on how to deal with this deliverable since August 3rd.   Please find them enclosed.

  Despite also an example was provided at that time, you may already check the contributions from the other chapters for reference.

  It's basically a matter of adding a number of tables, which make reference to the Epics/Features in the FI-WARE Backlog.   In the case of the Things Management GEs, they can easily be created, and I could even do it myself, but I have no clear idea about the rest of GEs in the IoT chapter.

  Since we are in a rush and it will be rather difficult to organize parallel editing of the wiki at this point, I would kindly ask you to provide your input to such tables in some sort of spreadsheet and I can take care of the final editing of the page later tonight.   Could NEC provide the template for that spreadsheet and distribute it to the rest of the IoT team so that they can return them filled by EOB today ?

  Cheers,

-- Juanjo



-------- Original Message --------
Subject:

Instructions for resubmission of FI-WARE Technical Roadmap

Date:

Fri, 03 Aug 2012 10:02:26 +0200

From:

Juanjo Hierro <jhierro at tid.es><mailto:jhierro at tid.es>

To:

fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu> <fiware-wpl at lists.fi-ware.eu><mailto:fiware-wpl at lists.fi-ware.eu>, fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu> <fiware-wpa at lists.fi-ware.eu><mailto:fiware-wpa at lists.fi-ware.eu>



Dear colleagues,

  Please find here the instructions to be followed to generate a new version of the Technical Roadmap deliverable to be published on the public Wiki and be resubmitted to the EC.

  The instructions are pretty simple and the best way to explain them is by referring to the example I have created on the private wiki:
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Example_(Resubmission)_-_Reference_Example<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Example_%28Resubmission%29_-_Reference_Example>
  That example is based on the current contents of the Technical Roadmap linked to the Apps Chapter.    Based on that, the steps to follow are:

 *   Update the Introduction:

    *   We should make a reference to contents of the FI-WARE Architecture and Open Specifications part of the wiki, rather than the FI-WARE Product Vision (at the time at which the first version of the Technical Roadmap, the Architecture and Open Specifications didn't exist, but this is no longer the case)
    *   You should also refer to the page dealing with Release and Sprint numbering, with reference to calendar dates.
    *   All of this may be done by simple copy&paste from the reference example.

 *   Description of first Major Release:

    *   The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow).   Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki.
    *   You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that will be supported.   The table shall be preceded by the paragraph:

       *   For a more detailed description of features provided, you can refer to the following table which help to identify what Backlog Features will be supported for each FI-WARE GE:

    *   You will see that table in the reference example, with the details of some of the FI-WARE GEs.   I have based them on info available in the public part of the Apps Chapter Backlog available on the  public wiki.   Essentially, you just need to include the references to the Backlog Features that have been addressed in the first Release for each FI-WARE GE (note this list should also include Features supported by the baseline assets)
    *   When you distinguished between the delivery by end of July and by end of September, the above three points indeed apply per each (section for the release by end of July and section for the release by end of September)

 *   Description of second Mayor Release:

    *   The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow).   Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki.
    *   You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that have already been planned or the Epics that will be analyzed and further refine which it is foreseen will lead to specification of Features to be planned as part of the second release.   The table shall be preceded by the paragraph:

       *   For a more detailed description of features to be provided, you can refer to the following table which help to identify what Backlog Features have already been specified and planned for the second Major Release of FI-WARE (and indication of the minor release is provided). The table also contain Epics currently under analysis which most probably will lead to the identification of Backlog Features to be planned also in the second Major Release

    *   You will see that table in the reference example, with the details of some of the FI-WARE GEs.   I have based them on info available in the public part of the Apps Chapter Backlog available on the  public wiki.   However, since there were no Backlog Features still planned, I have just created some fictitious features to make the reference example complete.  If a FI-WARE GE does have Epics, but not Features, then write down "(not yet specified)" in the column about Features.

 *   Regarding links to Features/Epics.   They should be wiki references, as they appear in the reference example.   No problem if they do not resolve in the FI-WARE Private Wiki, they should work once translated into the public Wiki
 *   Description of Future Releases:

    *   I believe we can keep this part as it is now



  I have prepared a section with placeholders for your contributions at:

https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4

  Please get them ready by Tuesday 12:00pm CET.   It shouldn't be that difficult if you made a good exercise updating Epic/Features in the Backlog.

  During the rest of August, you should update the stakeholder field of each Epic/Feature in the backlog.    Please do it with the best of your knowledge.   Put "FI-WARE partners" if an Epic/Feature doesn't come from an UC project but was there within our original plans.    Add the name of a UC project if you already know they are looking for it (based, for example, on feedback from the educational sessions).   We will ask UC projects in parallel to review the Epics/Features on the wiki and add the name of their project in the plan to use the GE and wish to use the functionality linked to that Epic/Feature.

  Best regards,

-- Juanjo



-------------

Product Development and Innovation (PDI) - Telefonica Digital

website: www.tid.es<http://www.tid.es>

email: jhierro at tid.es<mailto:jhierro at tid.es>

twitter: twitter.com/JuanjoHierro



FI-WARE (European Future Internet Core Platform) Chief Architect



You can follow FI-WARE at:

  website:  http://www.fi-ware.eu

  facebook: http://www.facebook.com/pages/FI-WARE/251366491587242

  twitter:  http://twitter.com/FIware

  linkedIn: http://www.linkedin.com/groups/FIWARE-4239932


________________________________

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-iot/attachments/20120815/453a40e2/attachment.html>