I suppose you already talked about this in the meeting today (unfortunately I am flying to Madrid this afternoon and I am writing this e-mail while flying...)
Last Wednesday the EC called me for a meeting with Jesús, Peter, Arian and Ragnar to discuss about some ongoing activities in FIWARE.
Arian pointed out the reduction of deliverables and specifically the issue with the deliverable on the architecture.
I may miss the context, but I think he is right and this is an important deliverable. He also mentioned that some people that should be involved are precisely the founding members of the Foundation, such as Alex has mentioned in his e-mail.
In fact the document should be used to illustrate to the community the relationships between GE and the concept of the "platform", whatever it means to us. Clear criteria on what GEs should be/look like/fulfill could also be included here so that the process of selecting new GEs is clear and transparent.
My two cents.
Best regards, Nuria
From: fiware-chapter-leaders-bounces at lists.fi-ware.org [mailto:fiware-chapter-leaders-bounces at lists.fi-ware.org] On Behalf Of Alex Glikson
Sent: Monday, June 15, 2015 12:37 PM
To: MIGUEL CARRILLO PACHECO; JUAN JOSE HIERRO SUREDA
Cc: fiware-chapter-leaders at lists.fi-ware.org; fiware-chapter-architects at lists.fi-ware.org
Subject: Re: [Fiware-chapter-leaders] [Fiware-chapter-architects] Fwd: FW: Proposal for the simplification of the deliverables of FI-Core
I think Arian raises excellent questions in the context of D11.x. I also think that we, as a consortium, don't have clear answers, and didn't conduct a meaningful discussion to figure out whether we even have a consensus or not. It seems that the answers would be tightly related to the governance model being defined for the open source community. On the other hand, maybe the relevant group to reach such a consensus would be the (founding) members of the to-be-established Foundation, and not necessarily the FI-Core consortium.
In more practical terms, if we decide to keep D11.x, it seems that replicating the individual GE specifications there might be redundant, and we may need to focus on architectural guiding principles.
Regards,
Alex
====================================================================================
Alex Glikson
Manager, Cloud Infrastructure Solutions, IBM Haifa Research Lab
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: MIGUEL CARRILLO PACHECO <miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>>
To: "fiware-chapter-leaders at lists.fi-ware.org<mailto:fiware-chapter-leaders at lists.fi-ware.org>" <fiware-chapter-leaders at lists.fi-ware.org<mailto:fiware-chapter-leaders at lists.fi-ware.org>>, "fiware-chapter-architects at lists.fi-ware.org<mailto:fiware-chapter-architects at lists.fi-ware.org>" <fiware-chapter-architects at lists.fi-ware.org<mailto:fiware-chapter-architects at lists.fi-ware.org>>
Date: 15/06/2015 01:23 PM
Subject: [Fiware-chapter-architects] Fwd: FW: Proposal for the simplification of the deliverables of FI-Core
Sent by: fiware-chapter-architects-bounces at lists.fi-ware.org<mailto:fiware-chapter-architects-bounces at lists.fi-ware.org>
________________________________
Dear all,
Just to share Arian's reactions to our proposal to simplify the deliverables. His answer is in my opinion rather reasonable.
Maybe we do not have time to analyse it and comment on it today but I wanted to pass the info to all of you for the sake of transparency.
Regards,
Miguel
-------- Mensaje reenviado --------
Asunto:
FW: Proposal for the simplification of the deliverables of FI-Core
Fecha:
Fri, 12 Jun 2015 15:42:58 +0000
De:
Arian.ZWEGERS at ec.europa.eu<mailto:Arian.ZWEGERS at ec.europa.eu>
Para:
miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>
CC:
juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com>, manuel.escrichevicente at telefonica.com<mailto:manuel.escrichevicente at telefonica.com>, javier.depedrosanchez at telefonica.com<mailto:javier.depedrosanchez at telefonica.com>
Dear Miguel,
Background: this is a response to some oral statements during the FI-WARE review, where I expressed surprise that FI-Core had so many deliverables, while at the same time the FI-WARE project was complaining about too many deliverables.
Response:
- Overall, the reduction in the number and frequency of deliverables is good
- D11.2-4: this is probably the most significant change. See below.
- D11.5: drop D11.5.3. No change in schedule. Given the 1300 SMEs, the whole idea of the live demos (and its 200 PM effort) is to be reconsidered, as repeated before.
- D.1<y>.1.(1,2): OK to move 1st issue to May/15.
- D.1<y>.6.(1,2,3,4): OK to make it annual.
- D.1<y>.8.<j>.(1,2): OK to merge with D.22.1.(1,2)
- D.21.x.(1,2): OK to merge
- D.22.x.(1,2) : OK to merge
- D31.5.x: OK to make it annual
- D.32.1.(1,2): OK for Sept+Dec 2015, with a draft at the time of the first review
- D32.2 "Confidence-building framework": This is related to proposing processes to evaluate the suitability of contributions [of new enablers, by the open source community], based on a wide adoption by application developers, and the consistency of such contributions to be compliant with common rules. It also defines what the criteria in the "Acceptance" boxes in presentations about the Open Source Community would be. This cannot be skipped, but the information may be provided in other deliverables.
- D33.2 "Expansion beyond Europe": the proposal is to leave this to FI-Links completely. I guess this means only support to non-European entities in the contract (to be confirmed).
Regarding D11.x:
- Without an overall architecture and roadmap, this change basically means giving up on the "FIWARE is a COHERENT set of enablers" vision, let alone the "FIWARE is a platform" strategy. FIWARE would then be a set of enablers, without coherence.
- The integration / interoperability of GEs has always been a question mark. Without overall architecture guidance, interoperability of any combination of GEs is not per se designed in and integration of any set of GEs, if required, is an issue for anyone taking up the enablers. With no overall architecture, there are no sufficient mechanisms to assure the interoperability of any set of GEs, other than what perhaps can be done on chapter level, which will be partial at best and without any overall guidance.
- This will have consequences for how to sell FIWARE. What does it really mean to be a FIWARE enabler? FIWARE would become like a label for passing certain acceptance tests, but not much more than that.
- Then, how would the Open Source Community choose the "accepted FIWARE" specification of a certain functionality, if it can choose between specification A and B? Certainly, the fit of any specification with complementary, already accepted and to be defined FIWARE specifications would be a major criterion (in addition to overall functionality, and prerequisites such as sufficient quality, documentation, on FI-Lab, etc.). It looks like the Open Source Community (or the Technical Committee thereof) would make some arbitrary decisions here, not based on vision or grand design, but at best on legacy.
- Then, what would be the argument for not having both specifications A and B for a certain component/functionality? Would overlaps be allowed? If so, again, FIWARE is reduced to a label. If not, arbitrary and opaque decisions are around the corner.
- The consortium needs to ask itself what it means to be a FIWARE enabler. There are some 'existential' questions to be answered.
From: MIGUEL CARRILLO PACHECO [mailto:miguel.carrillopacheco at telefonica.com]
Sent: Thursday, May 21, 2015 11:07 AM
To: ZWEGERS Arian (CNECT)
Cc: JUAN JOSE HIERRO SUREDA; MANUEL ESCRICHE VICENTE; 'JAVIER DE PEDRO SANCHEZ'
Subject: Proposal for the simplification of the deliverables of FI-Core
Dear Arian,
After our interactions with you in the past FI-WARE review we have concluded that it makes complete sense to take your offer and improve the deliverables. We have been putting some time in discussing how to reorganize the FI-Core deliverables with the focus on simplification. What I am passing you now is just a proposal, some things you may agree with and some others may need to stay as they are. In any case, part of the deliverables at stake are ongoing work so coming to a swift conclusions would help us to minimize delays.
This is what we propose:
* https://docs.google.com/spreadsheets/d/1vEFqA7ZumHjgT1bcDl7nST_ZI7YfXILGTbjkIb-tgFU
We created a timeline with all the deliverables as they are now and added column D with our proposal of change. The level of detail in the proposal is not very high to make this manageable but we can send more details for those changes that you may want to get better explained.
We look forward to your reply.
Kind 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 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<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
________________________________
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_______________________________________________
Fiware-chapter-architects mailing list
Fiware-chapter-architects at lists.fi-ware.org<mailto:Fiware-chapter-architects at lists.fi-ware.org>
https://lists.fi-ware.org/listinfo/fiware-chapter-architects
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-chapter-architects/attachments/20150615/894b43c6/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy