[Fiware] Start of the 2nd year reporting. We need work from ALL

[Uri Shani]

Done for IBM in WP13.



From:   MIGUEL CARRILLO PACHECO <miguel.carrillopacheco at telefonica.com>
To:     "fiware at lists.fiware.org" <fiware at lists.fiware.org>
Cc:     "'JAVIER DE PEDRO SANCHEZ'" 
<javier.depedrosanchez at telefonica.com>, JUAN JOSE HIERRO SUREDA 
<juanjose.hierro at telefonica.com>
Date:   21/12/2016 19:33
Subject:        [Fiware] Start of the 2nd year reporting. We need work 
from ALL
Sent by:        fiware-bounces at lists.fiware.org



Dear all,
As announced in the coordination call today, we have launched the 2nd year 
report. We have made available the links to edit it for all partners. They 
are here:

WP11
Global FIWARE Technical Coordination
https://docs.google.com/document/d/1eMgHbvaQBejfeXdxEBm1mwUoqIbIZByLe1pfOWZ-yig/
WP12
Cloud Hosting
https://docs.google.com/document/d/1j-HIjlqEpjPGn1TlEbxGRb8WzzKDQ_3zWOIqeBGhI5M/
WP13
Data/Media and Context Management
https://docs.google.com/document/d/1MbIgnZ--a8vPIYQVXYsUgPw8EmsfNFSdenfP9VKppGs/
WP14
IoT Services Enablement
https://docs.google.com/document/d/1dUrC_rAcy-RDZdDPdUz3XRrxNhA66TeAralQdzIPqPM/
WP15
Advanced Web-based User Interfaces
https://docs.google.com/document/d/1aQm0EeyGVH_oNSxKUfkN-AR007k8HfL7VyFjfHPtE9Q/
WP16
Apps/Service and Data Delivery
https://docs.google.com/document/d/1HZeUZFa1cPZ2eF-kjG_eNI5PtVPJzL2HHf-YHQDQZP0/
WP17
Security
https://docs.google.com/document/d/11DRpLGrJnyhrWECqka_o9uTWCmve16wkE3ycGwozzKw/
WP18
Advanced Middleware and Interfaces to Networks and Robotics
https://docs.google.com/document/d/1LDGy1ReFpLBcV9t0XfcyqM3XzjJlG5_VQz9hjydzlgY/
WP21
FIWARE Ops Tools
https://docs.google.com/document/d/1tz-Nb1xd_7eBOhsslXquFCUjE9c4TN0Gyq2FmqYeU9U/
WP22
FIWARE Lab Setup and Operation
https://docs.google.com/document/d/1QNFRaQWkm5J90J0xqjU6VKZuz_XmCOqPc2hUbC0on1k/
WP31
Sustainability Support Tools
https://docs.google.com/document/d/1Ahl4rDQYyJvMeBQxNZT2Gha8xgEbDZLvoIO4DPfGD_w/
WP32
Sustainability Model Definition and Activities
https://docs.google.com/document/d/1Oc7IKsf0oU6nGJhMdyubQVyfEvUA_gLIbcfd70maqXk/
WP33
Exploitation
https://docs.google.com/document/d/1SRsnaFzYfIzIEUTJUPSLfl6g0ER7GtMCOKS1Gf0gHcI/
WP41
Project Management
https://docs.google.com/document/d/1o9ojsHHuaYcvtxRhWpq3dGqgi-czSvP-f-KyPpqDjtE/
WP42
Communication, Collaboration and Dissemination
https://docs.google.com/document/d/1sCkzT6cpcaHEXbFqdbyqvAukBlkQBLGEHo3pczuV4Fc/
You are requested to report on your activity in the project in Year 2,  
from M14 (Oct/2015) till M28(Dec/2016). You cannot report activity before 
M14 or after M28. 
These links and the information within are FIWARE confidential
Deadline: 17/January
Important guidelines:
The WPLs are expected to check that the partners per task are the right 
ones according to the current DoW (amendment 2)
The WPLs are expected to do periodic backup of their part (weekly, at 
least!). This is more serious than you may think, someone may delete all 
by mistake and then we would have a problem.
The WPLs are expected to fill in the "general" parts of their WPs/chapters
The WPLs are expected to ensure that all is consistent, have good quality 
and that all is delivered on time (Jan, 17). If they throw at me things 
that are in bad shape, they will have a negative observation in the report 
from the coordination
The WPLs are expected to send reminders to the partners who failed to fill 
in their part.
All the partners have a clear entry in all the tasks where they 
contribute. 
If the do not have anything to report, they do not delete their entry. 
They state "Nothing to report in this reporting period". This is entirely 
unambiguous (deleting your entry leaves room to think that maybe it is an 
oversight and that we forgot this partner). 
If a given partner fails to provide their inputs, I will waste no time. If 
someone is not interested in claiming money from the EC, I respect it. In 
the cases of partners with no info (or those who disregard the previous 
bullet point and delete their entries), I will add this in red: "This 
partner did not contribute contents to this part despite the requests of 
the coordination"
We will request financial  info in January at a later stage
We will also start the creation of the Final Report soon (it is a 
different report from the one we are talking about in this message)
If it helps, this is the previous report as we delivered to the EC.(you 
may find change tracking but this is how we delivered it for reasons that 
are out of the scope of this interaction): 
https://drive.google.com/file/d/0B6GGeaQGro3fZEpzSkZQd21PWWs/view?usp=sharing 

Regards,

Miguel

-- 

Please update your address book with my new e-mail address: 
miguel.carrillopacheco at telefonica.com

----------------------------------------------------------------------
     _/          _/_/                     Miguel Carrillo Pacheco
    _/   _/     _/  _/   Telefónica       Distrito Telefónica 
   _/ _/_/_/   _/   _/   Investigación y  Edifico Oeste 1, Planta 6 
  _/   _/     _/  _/     Desarrollo       Ronda de la Comunicación S/N 
 _/          _/_/                         28050 Madrid (Spain) 
                                          Tel:  (+34) 91 312 94 15 

                         e-mail: miguel.carrillopacheco at telefonica.com

Follow FIWARE on the net

                 Website:  http://www.fiware.org
                 Facebook: https://www.facebook.com/eu.fiware
                 Twitter:  http://twitter.com/Fiware
                 LinkedIn: https://www.linkedin.com/groups/FIWARE-4239932
----------------------------------------------------------------------
__________________________________________________________________________________________

You can get more information about our cookies and privacy policies on the 
following links:
- 
http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy

- 
http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE


Fiware mailing list
Fiware at lists.fiware.org
https://lists.fiware.org/listinfo/fiware





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware/attachments/20161222/4a85dee5/attachment-0001.html>