[Fiware-data] Urgent: Tickets to address from the UCs

[CARLOS RALLI UCENDO]

Dear Colleagues,

Sorry my mail isn't working fine and this mail was not sent yesterday as planned :-(

As discussed in our call, we need to address these tickets ASAP to ensure we improve our cooperation with UCs and we -as Data WP- are not highlighted for this in the review.

---> The tickets are:
1) Tickets pending at caretakers level: None
1) Tickets pending at WP level: None
3) Tickets assigned and pending to be solved:
*****  Data/Context:
 1932 (20/Jun) - Tali - SAFECITY UC project F2F meeting with CEP GE
 1957 (25/Jun) - Tali - Sliding window requirements
 2058 (10/Jul) - ATOS - Semantic Application Support interconnectivity request
    Mauricio, I'm re-assigning this ticket from Chema to you or Ivan, Ok?
 2059 (10/Jul) - Fabio - Semantic Annotation interconnectivity and new features
 2207 (26/Jul) - Thomas - initiating discussion about data processing in OUTSMART
 2690 (14/Sep) - Tanguy - Location GE simulated geography
 2691 (14/Sep) - Tanguy - Location Server GE Service endpoint access

4) ToBeRevisedTickets:
*** Data/Context:
 1794 (14/Jun)  - Carlos Ralli - What capabilities does Data&Context offer wrt. data uncertainty?
5) Checksolved Tickets:
*** Data/Context: None

---> Addressing these tickets means:
1) If the ticket issue has previously been addressed through other channels (mail, calls, meetings, Educational Sessions, etc): send the following msg to the issuer "This ticket as solved by the means of [...] and therefore we will proceed to close this ticket." Then move the ticket to the state "Checksolved". After some 2-3 days, check there is no answer and move the ticket to "closed" .
2) Meaningless tickets at this point:send the following message to issuer: "This ticket is not meaningful anymore because [...] so it will be closed if no objection is received". Then move the ticket to the state "Checksolved". After some 2-3 days, check there is no answer and move the ticket to "closed" .
3) Tickets not clear enough: send a question to the issuer and propose to close this one and open a new one if it really needs refinement. If needs to be reassigned, ask in the mailing list before and once agreed please proceed and also communicate to issuer with a message.
4) Tickets that need sometime to be solved: Send a message to issuer that you are taking care because we are speeding up our feedback to UCs and please consider this as a priority because for the review time


Thanks a lot for your cooperation.
Best regards,
------------------------------------------------------------------------------------------------------------------------
Carlos Ralli Ucendo (ralli at tid.es)
Cell: +34696923588
Twitter: @carlosralli
Product Development & Innovation (Telefónica Digital)
Telefónica I+D SAU
Madrid, Spain
------------------------------------------------------------------------------------------------------------------------
Follow FI-WARE project (Future Internet Services Core Platform):
Website:  http://www.fi-ware.eu
Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
Twitter: @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-data/attachments/20121026/d36d82c4/attachment.html>