[Fiware-wpl] R: Taking care of the FI-WARE General Support Tracker

[Garino Pierangelo]

Hi Juanjo,

It looks like UCPs are using not only the General Support tracker but still add a number of tickets in the FI-WARE Theme/Epic/Feature Requests<https://forge.fi-ware.eu/tracker/?atid=163&group_id=7&func=browse> tracker.
For I2ND we got additional tickets in August from FINSENY project, and some of them are out of scope for the chapter (and others for the project too presumably).

Since this point is not so clear, shouldn't tickets in this tracker be added only as a conclusion of the analysis of FI-WARE + UCPs (e.g. via the general support tracker discussions) about possible inclusion of requested functionality in the FI-WARE backlog later?


BR
Pier

P.S: just a minor correction to the list of valid ticket status you reported: the 'ToBeChecked' status is actually named 'CheckSolved' in the tracker.







Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro
Inviato: giovedì 30 agosto 2012 07:51
A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Oggetto: [Fiware-wpl] Taking care of the FI-WARE General Support Tracker

Hi all,

    Now we face a critical point at which we should demonstrate quick response to any request for support by any UC projects.   We may foreseen that many request will come as a result of making FI-WARE GEs available on the Testbed and UC projects trying to experiment with them.

  As per agreement with UC projects, most of the interaction should now be handled through the FI-WARE General Support tracker at:
https://forge.fi-ware.eu/tracker/?group_id=7
  I have asked Axel and Carlos, as the dedicated team that was designated to monitor interaction with UC projects, to make sure that proper monitor of the status of this tracker is in place so that Chapter Leads and Chapter teams take care of tickets.    Note that some tickets may also require actions by members of the Testbed team or the team working on Development Tools.

  A very basic workflow has been defined to start working.   We will see how this evolves but I believe we should keep it as simple as possible.   Currently, valid status are:

 *   Open: it means that the ticket remains unassigned it has been formulated (or reformulated)
 *   Assigned: it means someone is taking care of it
 *   ToBeRevised: it means that the original ticket was wrongly formulated and has to be reformulated or closed
 *   ToBeChecked: it means that the one that was assigned to take care of it now thinks is solved but this has to be verified
 *   Closed: it means that the ticket was closed

and valid transitions are defined at: https://forge.fi-ware.eu/tracker/admin/?group_id=7&atid=162&workflow=1

  Don't wait until Axel or Carlos pursues you to handle a ticket and be proactive checking regularly what you could assign to you !

  I have kindly asked Axel and Carlos to brief us during our next follow-up confcall about status of the tracker, APs that we should put in place to move forward, etc.

  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
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

[cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non è necessario.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20120831/45c4cc80/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo Ambiente_foglia2.jpg
Type: image/jpeg
Size: 677 bytes
Desc: logo Ambiente_foglia2.jpg
URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20120831/45c4cc80/attachment.jpg>