Dear all, The situation in IoT is critical. The process goes like this: * The GE owner creates the manuals and delivers the sw * The WPL iterates with his team and deliver something that is compliant with the guidelines. If he has doubts, he asks the coordination for instructions/feedback. * The WPL delivers to the coordination for a final check, ensuring fluent communication with them. He sends reports when asked and trigger new reviews if iterations are needed. Obviously, this was not the procedure followed in WP5 and as a consequence and unfortunately, the WP has been stalled for months. This is the general status thanks to the commitment of the respective WPLs: * WP3 - Delivered on 02.07.2014 * WP4 - Delivered on 02.07.2014 * WP5 - not delivered, the communication link between the WPL and the coordination broken for months. * WP6 - Delivered on 11.07.2014 * WP7 - Delivered on 11.07.2014 * WP8 - still iterating but the WPL is responsive * WP13 - Delivered on 26.06.2014 I am basically blind in WP5 and I have not received status reports in ages. Just to clarify, talking to the individual GE owners is exceptional and not part of my duties in the case of these deliverables. If I am going to do it in some cases it is simply because someone has to do it or else we will deliver in year 2016. The reviews and further details are on: * [1] https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdGlvRWJrQl96M1VNTHBlc3hvUGF0Zmc#gid=4 I will leave the User Manuals for the moment, my colleague Manuel is the one who normally takes care of them. Go to [1], read comments on the google doc and also read the following text. So far I could re-review these (I will continue next week when I can): IoT broker * UTP: Accepted. I fixed a small thing in a few features to make it consistent with the roadmap. Also, one figure does not work on the private wiki but it is minor, the image exists on the public wiki and it will work once ported. * INS: temporarily rejected. Details in a private message * SW: please fix the release number of the sw in R3.2. The R3.3 seems ok - but there is a pending clarification on the release to deliver (again, this is in a private message). IoT discovery * UTP: Accepted now. I fixed a comment that had been ignored. * INS: rejected (easy to fix). Reference to a non existent file name. Once fixed it will be approved. Details sent in private to Tarek by e-mail. Gateway Device Manager - OPEN MTC * Comments ignored in all manuals and SW. No action in months and months after direct warnings to the GE owner in the past. This is enough. I will add a negative comment from the coordination in the periodic report, recommending consequences in the acceptance of costs. Gateway Data Handling - SOL/CEP * Reading the roadmap I see that this is actually not in R3. I created this online sheet and the links on the private wiki very long ago and asked the WPL to check and keep me informed of whether it was valid. This has been marked as "not delivered" for months but it seems that the links should have never been there. I moved it to "N/A" as it seems out of the release. As I say, I will try to look into others (IDAS, ZPA, EPCGE and Esper4FastData) next week when I have the time. Best regards, Miguel -- Please update your address book with my new e-mail address: miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com> ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telefónica Distrito Telefónica _/ _/_/_/ _/ _/ Investigación y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com> Follow FI-WARE on the net Website: http://www.fi-ware.org Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20140808/3291e77c/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy