Hi Carlos,
I suspect this issue could include "IoT Discovery". Since we have changed the name of the GE "Configuration Management" to "IoT Discovery", this needs to be reflected in all the documentation. I can do this, but your colleagues developing Orion need to be aware of this as well.
As WP architect, please can you confirm that I can go ahead with the renaming, and that they will also take this into consideration.
Best regards,
Tarek
From: fiware-bounces at lists.fi-ware.org [mailto:fiware-bounces at lists.fi-ware.org] On Behalf Of MIGUEL CARRILLO PACHECO
Sent: 09 June 2015 17:52
To: fiware at lists.fi-ware.org
Cc: fiware-chapter-leaders at lists.fi-ware.org; fiware-chapter-architects at lists.fi-ware.org
Subject: Re: [Fiware] [Fiware-chapter-architects] Chaos in the names of GEs
Dear all,
Juanjo is suggesting to resend to all the project so here we go. I am sure that each one of you is aware of where his/her GE is and how it is called but people visiting our pages face a complex environment of many GEs and we cannot call the same things in different ways. Consistency in names will be severely taken into account in the future.
In other words, we expect the same name for the same GE on the catalogue, JIRA backlog, architecture, rodamap, FIWARE Academy, sw delivery, open specs, etc. Ge owners please make sure now that this is the case ... sometimes we make this so hard to understand from outside!
The reference is the link in my previous message (read on ...) It will be used to check against it in internal reviews and any inconsistency will count negatively. In other words, we will apply negative karma to any occurrences of this from now on.
Regards,
Miguel
El 09/06/2015 a las 16:29, MIGUEL CARRILLO PACHECO escribió:
Dear all,
When I try to come to terms with the architectures I get lost because people change the name of the Ges and GEri quite happily not telling anyone.
The only reference is this sheet:
* https://docs.google.com/spreadsheets/d/1rA1E1-Qj866E203h0zcJM9twqt2pku7MS_VAZa9Ngqw
If you want changes or new ones you need to inform and get an approval before going ahead - not as a "fait accompli" after changing multiple wiki pages with it.
The GE names and GEri names must be the same everywhere. Not arbitrarily different ones in the roadmap, academy, architecture, open specs, catalogue, JIRA backlog, etc. I am part of this project and get constantly lost, let alone people from outside. Anyone can see that it is totally wrong. Inconsistencies in the names will be severely taken into account in the future.
For the time being I am prioritising those chapters that have something understandable , which is mainly the case of the Apps Architecture, already delivered.
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
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
_______________________________________________
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
--
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-iot/attachments/20150609/2ae8e7e3/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <https://lists.fiware.org/private/fiware-iot/attachments/20150609/2ae8e7e3/attachment.txt>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy