Ya soy consciente.......pero como nadie va a responder, pues precisamente el deliverable de Kenneth es básicamente IBM _Openstack, y algo quizás de Thierry y Stefano en OW2..
Pero si el otro dia en el mail de explotación metí varios contactos de las nuevas empresas de FICORE (Createnet, DFKI, ZHAW, Conwet, RedIris, UPM.............) y faltan algunos
De todas maneras hay uno general donde estarán todos metidos tb no?, le diré que la mande tb a esa, fiware at lists.fi-ware.org<mailto:fiware at lists.fi-ware.org> o acabada en eu fiware at lists.fi-ware.eu<mailto:fiware at lists.fi-ware.eu>
Tobias Jacobs (Tobias.Jacobs at neclab.eu); alessandro.martellone at create-net.org; antonio.fuentes at rediris.es; estanislao.fernandez at telefonica.com; gianmario.bollano at telecomitalia.it; laura.pucci at eng.it; miguel.carrillopacheco at telefonica.com; De Lama Sanchez, Nuria <nuria.delama at atos.net>; pascal.bisson at thalesgroup.com; pierangelo.garino at telecomitalia.it; silvio.cretti at create-net.org; slusallek at dfki.de; stefano.depanfilis at eng.it; thierry.nagellen at orange.com; cyril.dangerville at thalesgroup.com; fdelavega at conwet.com; jsoriano at fi.upm.es; thomas.bohnert at zhaw.ch; toff at zhaw.ch; joel.riga at orange.com; stefano.depanfilis at eng.it; thierry.nagellen at orange.com; Donato Cohen, Malena (malena.donato at atos.net<mailto:malena.donato at atos.net>)
Juan Bareño
Research & Innovation
Client Manager - European Union Institutions-Iberia
T. +34 912 148 859
juan.bareno at atos.net<mailto:juan.bareno at atos.net>
Albarracín, 25
28037 Madrid - Spain
atos.net
[cid:image002.png at 01CF21D2.D8BA98F0]
From: MIGUEL CARRILLO PACHECO [mailto:miguel.carrillopacheco at telefonica.com]
Sent: Monday, September 14, 2015 10:19 AM
To: Bareno Guerenabarrena, Juan
Subject: Re: WP333 FICORE-Explotation_ DELIVERABLES on M13 (September) IMPORTANT!!
Juan
El flujo es este:
Kenneth -> leaders & architects -> cada uno responde a lo de su empresa (si hay suerte)
Y las empresas que no tengan leaders & architects, no responderán porque nadie se lo pedirá. No sé si lo ves, pero esto no es a nivel de chapter sino de socio!!! Habría que identificar un contacto para temas de explotación en cada empresa y hacer una lista, ya te digo yo ...
El 14/09/2015 a las 10:02, Bareno Guerenabarrena, Juan escribió:
Hi Kenneth
Below my answers, I would recommend you to use the JIRA and the mail, both together
I will forward to you the Standardization mail, that I will use as main reference. Additionally I will remark all the activities related to exploitation in the next coordination call on Wednesday
Best
Juan
Juan Bareño
Research & Innovation
Client Manager - European Union Institutions-Iberia
T. +34 912 148 859
juan.bareno at atos.net<mailto:juan.bareno at atos.net>
Albarracín, 25
28037 Madrid - Spain
atos.net
[cid:image002.png at 01CF21D2.D8BA98F0]
From: Kenneth Nagin [mailto:NAGIN at il.ibm.com]
Sent: Sunday, September 13, 2015 8:02 AM
To: Bareno Guerenabarrena, Juan
Cc: Alex Glikson; Ernoe.Kovacs at neclab.eu<mailto:Ernoe.Kovacs at neclab.eu>; ESTANISLAO MA FERNANDEZ GONZALEZ-COLAÇO; Donato Cohen, Malena; MIGUEL CARRILLO PACHECO (miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>); Tobias Jacobs (Tobias.Jacobs at neclab.eu<mailto:Tobias.Jacobs at neclab.eu>)
Subject: RE: WP333 FICORE-Explotation_ DELIVERABLES on M13 (September) IMPORTANT!!
I am working on the deliverable D33.4.1) Contribution to Open Source communities report:
This is a link to initial google doc draft:
https://docs.google.com/document/d/13VgQML1235lNAJGwpvkOAHmDKHJN_KibXffoCnmHf-k/edit#<https://docs.google.com/document/d/13VgQML1235lNAJGwpvkOAHmDKHJN_KibXffoCnmHf-k/edit>
Please note I have only added IBM's contributions. Other partners should add their contributions.
Once all relevant members have updated the google doc I will make the necessary changes to make it a word doc.
Each partner should include zero or more sub-sections with os community name that include description of contributions, URL to code, URLs to specific contributions, status (in progress, under review, merged, in release, etc).
What list should we use to advertise this task? I would use the following:
- fiware-chapter-leaders at lists.fiware.org<mailto:fiware-chapter-leaders at lists.fiware.org> ; fiware-chapter-architects at lists.fiware.org<mailto:fiware-chapter-architects at lists.fiware.org>, that have been used by Tobias in the standardization side, with the following remark to extend it as much as possible "As you will need the input of your chapter's partners to this, please distribute this information as soon as possible within your chapter".
Is there way to automatically generate jira issues to complete this task for this sprint? There is a Jira space for exploitation, but with limited participation....
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: "Bareno Guerenabarrena, Juan" <juan.bareno at atos.net<mailto:juan.bareno at atos.net>>
To: Alex Glikson/Haifa/IBM at IBMIL, Kenneth Nagin/Haifa/IBM at IBMIL
Cc: "Ernoe.Kovacs at neclab.eu<mailto:Ernoe.Kovacs at neclab.eu>" <Ernoe.Kovacs at neclab.eu<mailto:Ernoe.Kovacs at neclab.eu>>, ESTANISLAO MA FERNANDEZ GONZALEZ-COLAÇO <estanislao.fernandez at telefonica.com<mailto:estanislao.fernandez at telefonica.com>>, "Donato Cohen, Malena" <malena.donato at atos.net<mailto:malena.donato at atos.net>>, "MIGUEL CARRILLO PACHECO (miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>)" <miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>>, "Tobias Jacobs (Tobias.Jacobs at neclab.eu<mailto:Tobias.Jacobs at neclab.eu>)" <Tobias.Jacobs at neclab.eu<mailto:Tobias.Jacobs at neclab.eu>>
Date: 11/09/2015 03:19 PM
Subject: RE: WP333 FICORE-Explotation_ DELIVERABLES on M13 (September) IMPORTANT!!
________________________________
Hi
Please find here the status:
- 33.1.1 Atos, has sent the first version to complete, mainly Individual Exploitation Plans pending
- 33.2.1 TEF pending from an answer regarding F-LINK deliverable connection, any news??
- 33.3.1 NEC has sent the first version to complete
- 33.4.1 IBM Kenneth working on the deliverable, Kenneth could you confirm it?
Best
Juan
Juan Bareño
Research & Innovation
Client Manager - European Union Institutions-Iberia
T. +34 912 148 859
juan.bareno at atos.net<mailto:juan.bareno at atos.net>
Albarracín, 25
28037 Madrid - Spain
atos.net
[cid:image002.png at 01CF21D2.D8BA98F0]
From: Bareno Guerenabarrena, Juan
Sent: Tuesday, September 01, 2015 6:30 PM
To: 'Alex Glikson'; Kenneth Nagin
Cc: Ernoe.Kovacs at neclab.eu<mailto:Ernoe.Kovacs at neclab.eu>; ESTANISLAO MA FERNANDEZ GONZALEZ-COLAÇO; Donato Cohen, Malena; MIGUEL CARRILLO PACHECO (miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>); Tobias Jacobs (Tobias.Jacobs at neclab.eu<mailto:Tobias.Jacobs at neclab.eu>)
Subject: RE: WP333 FICORE-Explotation_ DELIVERABLES on M13 (September) IMPORTANT!!
Thanks Alex!
Please find here the status, I still miss some inputs from NEC people regarding Standardization deliverable, Tobias/Ernoe????
- 33.1.1 Atos, working on a TOC regarding sharing strategy an on a individual exploitation plan to complete by each partner involved
- 33.2.1 TEF pending from an answer regarding F-LINK deliverable connection
- 33.3.1 NEC ?????
- 33.4.1 IBM on track, Kenneth working on the deliverable
Best
Juan
Juan Bareño
Research & Innovation
Client Manager - European Union Institutions-Iberia
T. +34 912 148 859
juan.bareno at atos.net<mailto:juan.bareno at atos.net>
Albarracín, 25
28037 Madrid - Spain
atos.net
[cid:image002.png at 01CF21D2.D8BA98F0]
From: Alex Glikson [mailto:GLIKSON at il.ibm.com]
Sent: Thursday, August 27, 2015 4:27 PM
To: Bareno Guerenabarrena, Juan; Kenneth Nagin
Cc: Ernoe.Kovacs at neclab.eu<mailto:Ernoe.Kovacs at neclab.eu>; ESTANISLAO MA FERNANDEZ GONZALEZ-COLAÇO; Donato Cohen, Malena; MIGUEL CARRILLO PACHECO (miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>); Tobias Jacobs (Tobias.Jacobs at neclab.eu<mailto:Tobias.Jacobs at neclab.eu>)
Subject: Re: WP333 FICORE-Explotation_ DELIVERABLES on M13 (September) IMPORTANT!!
Dear Juan,
Kenneth will take care of coordinating 33.4.1 (and of consolidating IBM's input for 33.1.1).
Regards,
Alex
====================================================================================
Alex Glikson
Manager, Cloud Infrastructure Solutions, IBM Haifa Research Lab; FIWARE Cloud Architect
Email: glikson at il.ibm.com<mailto:glikson at il.ibm.com> | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112
From: "Bareno Guerenabarrena, Juan" <juan.bareno at atos.net<mailto:juan.bareno at atos.net>>
To: ESTANISLAO MA FERNANDEZ GONZALEZ-COLAÇO (estanislao.fernandez at telefonica.com<mailto:estanislao.fernandez at telefonica.com>) <estanislao.fernandez at telefonica.com<mailto:estanislao.fernandez at telefonica.com>>, "Tobias Jacobs (Tobias.Jacobs at neclab.eu<mailto:Tobias.Jacobs at neclab.eu>)" <Tobias.Jacobs at neclab.eu<mailto:Tobias.Jacobs at neclab.eu>>, "Ernoe.Kovacs at neclab.eu<mailto:Ernoe.Kovacs at neclab.eu>" <Ernoe.Kovacs at neclab.eu<mailto:Ernoe.Kovacs at neclab.eu>>, Alex Glikson/Haifa/IBM at IBMIL
Cc: "MIGUEL CARRILLO PACHECO (miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>)" <miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>>, "Donato Cohen, Malena" <malena.donato at atos.net<mailto:malena.donato at atos.net>>
Date: 26/08/2015 01:49 PM
Subject: WP333 FICORE-Explotation_ DELIVERABLES on M13 (September) IMPORTANT!!
________________________________
Dear Colleagues
For M13, end of September we must deliver the following 4 deliverables, with the following leaders as they are mentioned in the DOW, so please we should start to work on the TOCs and in ask for the required inputs for the rest of the partners (see each Task description below with all the partners involved)
* D33.1.1) Exploitation plans: This deliverable will describe the shared exploitation plan between FI-Core consortium partners and their relationships with the individual exploitation plans. [month 13]. Leader ATOS
* D33.2.1) Expansion beyond Europe: This deliverable describes actions put in place to expand the impact of FI-WRAE, FI-Lab and FI-Ops beyond Europe and the different external entities which have been involved in such dissemination activities. [month 13]. Leader TEF
* D33.3.1) Standardization relationships: This deliverable will describe the project-wide standardization plan will in order to identify the right targets, the right strategy and the selection of topics to be proposed into standardization bodies and the process to pursue these standardization contributions[month 13]. Leader NEC
* D33.4.1) Contribution to Open Source communities report: This document will describe relationships build with existing Open Source communities and detail FI-Core contributions to some of them. [month 13]. Leader IBM (Mainly Openstack contributions)
Please start to work on them for what I propose the following calendar:
* First TOC version to share with the rest of contributor partners by 4th of September Friday
* Three weeks for receive inputs and complete the document to have a first draft version to review by 25th September Friday
* Final delivery 2nd of October Friday
I will welcome any feedback on this and a confirmation on your side
Thanks for your collaboration
Best
Juan
Task 3.3.1: Shared and individual exploitation plans
This task includes two levels of exploitation plan. The direct exploitation from the project consortium partners in order to enhance their own products and provide better services to their customers will be the first one and commercial exploitation of project results by FI PPP Community and external stakeholders will be the second.
This task will therefore contribute to those FI PPP Programme level activities the perspective and needs of FI-Core and the FI-Core consortium. In order to pave the way for a successful exploitation and sustainability, FI-Core will work on setting up a shared exploitation taken into account the inputs from the WP3.2 on governance models. The definition of this shared exploitation plan will be carried out here in cooperation with other technical WPs as well as other projects of the FI-PPP Community. The share exploitation plan will take care of the IPR guidelines and the common Open Source framework that will be published for external stakeholders.
In addition, all FI-Core will provide their own classical exploitation plans which will be critical to involve them in the new expected structure. This new structure will potentially take the lead at the end of the programme on animation and coordination activities of increase business impact of FI PPP Community results.
ATOS (Leader), TID, ORANGE, TI, IBM, CONSOFT, ENGINEERING, THALES COMMUNICATIONS & SECURITY, THALES SERVICES, NEC, CREATE-NET, CYBERLIGHTNING, ADMINOTECH, ETXE-TAR, EPROS, NAVEATEC,UPM, ZHAW, DFKI, UNIVERSITY OF SURREY, RED.es, ILB, TRENTINO Network
Role of Partners:
* ATOS: Overall coordination
* TID, ORANGE, ENGINEERING, ATOS: Shared Exploitation Plan
* TID, ORANGE, ENGINEERING, ATOS ,TI, IBM, CONSOFT, THALES COMMUNICATIONS & SECURITY, THALES SERVICES, NEC, CREATE-NET, CYBERLIGHTNING, ADMINOTECH, ETXE-TAR, EPROS, NAVEATEC,UPM, ZHAW, DFKI, UNIVERSITY OF SURREY, RED.es, ILB, TRENTINO Network: Individual Exploitation Plans and commercial exploitation of project results by FI PPP Community and external stakeholders
Task 3.3.2: Expansion beyond Europe
This task aims at building relationships with relevant international communities especially in Asia and in America to push the adoption of European Technologies but also to integrate new technical challenges or improve Open Specifications based on new generic requirements.
Recent manifestation of interest from countries as Brazil to be integrated in FI-Lab are good opportunities to support the adoption of FI PPP Community results through the world and in many case to propose some of the results as concrete implementation which could be de factor standard if adopted by a large community.
This task will organize the industrial dissemination and exploitation process to countries beyond Europe to organize this first adoption
TID (Leader), ORANGE, TI, ENGINEERING, ATOS, NEC, CREATE-NET, ADMINOTECH, ETXE-TAR, EPROS, UNIVERSIDAD REY JUAN CARLOS, ZHAW, DFKI, and UNIVERSITY OF SURREY ,
Role of Partners:
* TID: Overall coordination
* TID, ORANGE, TI, ENGINEERING, CREATE-NET, ADMINOTECH, ETXE-TAR, EPROS, UNIVERSIDAD REY JUAN CARLOS, ZHAW, DFKI, and UNIVERSITY OF SURREY : Integrate new technical challenges or improve Open Specifications based on new generic requirements.
* ATOS, NEC: Organize the industrial dissemination and exploitation process
Task 3.3.3: Contribution to standardization
The objective of this task is two-fold. First, a project-wide standardization plan will be developed in order to identify the right targets, the right strategy and plan the standardization activities in accordance to the overall project planning and evolution. This standardization plan will take care of the Standardization Working Group activities which provide the consensus from the FI PPP community point of view.
This includes also a selection of topics to be proposed into standardization bodies in close cooperation with the other technical work-packages and a selection of standardization organizations. Furthermore, participation within identified standardization organizations will be established and actively maintained.
These standardization plans will be supported by the generation and improvement of existing and new Open Specifications and the development of reference implementations by the technical WPs. This is the second objective of this WP that will centralize all efforts required to generate and pursue these standardization contributions.
NEC (Leader), TID, ORANGE, TI, THALES COMMUNICATIONS & SECURITY, THALES SERVICES, CYBERLIGHTNING, ADMINOTECH, ETXE-TAR, EPROS, UPM, DFKI, ILB, TRENTINO Network
Role of Partners:
* NEC: overall coordination
* NEC, TID, ORANGE, THALES COMMUNICATIONS & SECURITY, THALES SERVICES: Define a project-wide standardization plan
* NEC, TID, ORANGE, TI, THALES COMMUNICATIONS & SECURITY, THALES SERVICES, CYBERLIGHTNING, ADMINOTECH, ETXE-TAR, EPROS,UPM, DFKI, ILB, TRENTINO Network: The generation and improvement of existing and new Open Specifications
Task 3.3.4: Involvement in Open Source communities
This task aims at monitoring the dissemination of FI-Core results in some relevant Open Source Communities. Based on existing results from FI-WARE related to existing Open Source communities, it is critical that the contributions provided by FI-Core partners and in a middle term by partners involved in the new entity which should emerge from the governance model work done in WP3.2.
Involvement in Open Source communities is based on dedicated contributions which will be the results of
Collaborative work done in the technical WP. These collaborative results have to be identified as a result from FI-Core, supported by the FI PPP Community more than the contribution of a single partner.
This task aims at defining the process to validate the content which will be submitted to the different communities Open Source where FI-Core results are relevant and to monitor effectively their integration or adoption by the Open Source Communities themselves.
IBM (Leader), TID, ORANGE, TI, ENGINEERING, THALES SERVICES, ATOS, NEC, CREATE-NET, CYBERLIGHTNING, ADMINOTECH, ETXE-TAR, OKF, EPROS, NAVEATEC, Universidad Rey Juan Carlos, UPM, ZHAW, DFKI, ILB, TRENTINO Network
Juan Bareño
Research & Innovation
Client Manager - European Union Institutions-Iberia
T. +34 912 148 859
juan.bareno at atos.net<mailto:juan.bareno at atos.net>
Albarracín, 25
28037 Madrid - Spain
atos.net
[cid:image002.jpg at 01D0EED8.04186A80]
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional.
Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes.
Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional.
Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes.
Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional.
Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes.
Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.
--
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 483 26 77
e-mail: miguel.carrillopacheco at telefonica.com<mailto: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
----------------------------------------------------------------------
________________________________
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
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional.
Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes.
Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware/attachments/20150914/da46cb5e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 4687 bytes
Desc: image001.png
URL: <https://lists.fiware.org/private/fiware/attachments/20150914/da46cb5e/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 4607 bytes
Desc: image002.jpg
URL: <https://lists.fiware.org/private/fiware/attachments/20150914/da46cb5e/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy