[Fiware] Reminder: all to edit the 2nd Year Periodic Report now

MIGUEL CARRILLO PACHECO miguel.carrillopacheco at telefonica.com
Wed Jan 11 08:58:53 CET 2017


Dear Kenneth,

The information you want is reachable following the link in the part 
"Important Guidelines" at the end of my first 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/"

The per-WP sections are what you are looking for.

Regards,

Miguel
El 10/01/2017 a las 9:22, Kenneth Nagin escribió:
> It would be very helpful if you provided links to last period's WP 
> reports so that we use what as written and make the appropriate changes.
> BTW I looked in forge and found the periodic report under 
> deliverables, but it is not in the same format at all.
>
> Best Regards,
>
> Kenneth Nagin
> Ph: +972-4-8296227
> Cell: 054-6976227
> Fx: +972-4- 8296114
> http://researcher.ibm.com/view.php?person=il-NAGIN
>
>
>
>
>
>
> From: MIGUEL CARRILLO PACHECO <miguel.carrillopacheco at telefonica.com>
> To: "fiware at lists.fiware.org" <fiware at lists.fiware.org>
> Cc: JUAN JOSE HIERRO SUREDA <juanjose.hierro at telefonica.com>, "'JAVIER 
> DE PEDRO SANCHEZ'" <javier.depedrosanchez at telefonica.com>
> Date: 09/01/2017 11:23 AM
> Subject: [Fiware] Reminder: all to edit the 2nd Year Periodic Report now
> Sent by: fiware-bounces at lists.fiware.org
> ------------------------------------------------------------------------
>
>
>
> Dear all,
>
> Once the Christmas season is over, it is time to resume the work to 
> create the *2nd Year Periodic Report*. This is basically justifying 
> our work and demonstrating the EC that we've done what we were 
> expected to do - if not, they will not pay us! :)  A big thank you 
> goes to the cloud team who notified that they had completed their part 
> already.
>
> Each company has an entry in the tasks where they have efforts. Your 
> chapter leaders will ask you to contribute, but you have the links so 
> please, *_each one of you check and fill in your parts of the docs_* 
> linked at the end of this message even if you do not get directions 
> from him. Please DO NOT DELETE any entries, if you have no activity in 
> the period, you express this with a  short sentence.
>
> Note that 3 WPs will not have a chapter leader following up so please 
> do not forget to check your entries for:
>
>   * WP18 Advanced Middleware and Interfaces to Networks and Robotics
>     (the leader left the consortium long ago)
>   * WP32 Sustainability Model Definition and Activities (Orange is
>     theoretically the leader but ... )
>   * WP42 Communication, Collaboration and Dissemination
>
> You have until Jan, 17. Then we will start adding the usual "/This 
> partner did not contribute contents to this part despite the requests 
> of the coordination/" in the empty entries and send it to the EC once 
> finished. There are hundreds of entries and we cannot follow up on 
> each one of them.
>
> Regards,
>
> Miguel
>
>
> El 21/12/2016 a las 18:33, MIGUEL CARRILLO PACHECO escribió:
>
> 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_ 
> <mailto: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_ 
> <mailto:miguel.carrillopacheco at telefonica.com>
>
> Follow FIWARE on the net
>
> Website: _http://www.fiware.org_ <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_ <mailto:Fiware at lists.fiware.org>
> _https://lists.fiware.org/listinfo/fiware_
>
>
>
> -- 
>
> 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 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_ 
> <mailto:miguel.carrillopacheco at telefonica.com>
>
> Follow FIWARE on the net
>
> Website: _http://www.fiware.org_ <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
>
>
>
>

-- 

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
----------------------------------------------------------------------

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


More information about the Fiware mailing list

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