dear miguel, i must only agree with you!!! however i think that it is better to take as reference the catalogue that is the main fiware window and which is certainly the place where our customers go first and more often. so my suggestion is: - that you update the file in the google do - that everybody updates the ge names along all the pages (academy, forge, docs, whatever ...) accordingly - you keep karma based on this! ciao, stefano 2015-06-09 18:51 GMT+02:00 MIGUEL CARRILLO PACHECO < miguel.carrillopacheco at telefonica.com>: > 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 > > ---------------------------------------------------------------------- > _/ _/_/ 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 > > 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 listFiware-chapter-architects at lists.fi-ware.orghttps://lists.fi-ware.org/listinfo/fiware-chapter-architects > > > -- > > 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 483 26 77 > > 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 > ---------------------------------------------------------------------- > > > ------------------------------ > > 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-leaders mailing list > Fiware-chapter-leaders at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-chapter-leaders > > -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-06-8759-4253 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 skype: depa01 twitter: @depa01 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-chapter-architects/attachments/20150609/9b216efb/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy