[Fiware-lab-recovery-tf] URGENT response on FIWARE Lab status

Pietropaolo Alfonso Alfonso.Pietropaolo at eng.it
Wed Jun 24 22:23:38 CEST 2015


Dear Juanjo,
about the Action Plan probably there is not so much to explain, the fact that has not been touched for days is the reason why last week I asked for more participation and enthusiasm... Yesterday I couldn't attend the new weekly meeting (only 2 were in the call) but I don't think is a good excuse for task owners in order to not update the status of their own tasks.
I'm the coordinator of the task force, ok, i know, but if for any reason I'm out of office (Xifi review, vacation or others...) nothing prevent to put a "done" when a task is finished (I guess).
About the general status of the Lab, I don't think is totally abandoned. Probably the task force yes, is not so active like in the past, because the most critical period is passed. I totally agree with you that further discussions and actions should be taken (especially now that Xifi is over) but others several activities in the Lab are daily done, for instance I'm almost daily in touch with Manuel for help desk activities and Jira improvements, or I asked to fix a bug in the Sanity Check and it is planned in the next sprint, and so on... I mean, not all these activities are described in the TF Action Plan because i consider them normal activities in a project and not something to underline in the task force plan (if this is not the correct way to proceed let me know).

I'm not at work in these days and for the whole week till next Tuesday, tomorrow I will try to connect at the conference call even though could be very difficult for me.

Thanks,
Alfonso
________________________________
Da: fiware-lab-recovery-tf-bounces at lists.fiware.org [fiware-lab-recovery-tf-bounces at lists.fiware.org] per conto di Juanjo Hierro [juanjose.hierro at telefonica.com]
Inviato: mercoledì 24 giugno 2015 8.19
A: fiware-lab-recovery-tf at lists.fiware.org
Oggetto: [Fiware-lab-recovery-tf] URGENT response on FIWARE Lab status

Folks,

  I remind you that tomorrow 18:00 CET we have a meeting with the EC to check the status of the FIWARE Lab Recovery Plan.

  I'm worried about the status.   When I tried to sync up by means of simply checking the status of the FIWARE Lab Recovery Crash Plan:
https://docs.google.com/document/d/1BanhzbYZONjAflT3jpmMfl5wi-xp25RckrakqklJLow/edit?usp=sharing

  I have found a) it has not been touched since 9 days and b) apparently there is no follow-up of almost any action.   There are actions which should have been closed or, if there are pending, there should have been urgent remediation actions in place (e.g., #19), clear actions like #20x which I wonder now whether they have been finalized ...

  Taking a look at the infographic ... I still see 2026 users which I understand shouldn't be true if we were deleting the Trial users after the two-weeks experimentation period.  I also remind that I asked for evolving the tool so that it provides detailed info about Basic, Trial and Community Users as well as organizations when we expand to see the details.   Can someone tell me how many users do we have regarding each category?

  Also rather low traffic in the list, just last discussion about whether we should have daily meetings ...  Event the mailing list is not being moderated (and I'm not the only moderator).

  Gentlemen ... if you ask my honest opinion, this looks like almost totally abandoned.   I would need a response from Engineering on this matter reporting on the status of the FIWARE Lab and explaination about the status of follow-up tasks which seem to have been abandoned!

  Best regards,


-- Juanjo

______________________________________________________

Coordinator and Chief Architect, FIWARE platform
CTO Industrial IoT, Telefónica

email: juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com>
twitter: @JuanjoHierro

You can follow FIWARE at:
  website:  http://www.fiware.org
  twitter:  @FIWARE
  facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
  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/fiware-lab-recovery-tf/attachments/20150624/443a72f9/attachment.html>


More information about the Fiware-lab-recovery-tf mailing list

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