Dear Stefano, 2.2. it is true that changes in the catalogue migth occur, but only from ge > owners for their own ge. at least, if this is not implemented, please > davide take proper actions. > This is already the case. Only who created an entry can modify it. There is also a higher role (as your), given to very few people that can update every content and validate requests for publication. > 2.3. davide please create a report (only for catalogue regeistered users, > or even better only for catalogue administrators) that generates the table > miguel need. i do agree for him this importnat for the duties he has, e.g. > sending the list of ges to people asking that. this way the miguekl list is > always up-to-date We can create that ... I wait for the final decision on this ... if it helps in the next update of the production we will include the "Last Updates" page where to see the list of enablers recently updated (this is available also as REST APIs) BR Davide 2015-06-11 10:09 GMT+02:00 stefano de panfilis <stefano.depanfilis at eng.it>: > dear miguel, > > (i kept in my answer now only the people who will actually decide). > > 1. we do all agree that ge names cannot change withou a control process: > that's a given. > > 2. the point is to understand how to keep thinks in line now and at regime. > 2.1. my porposal is to follow more a customer oriented approach (miguel we > have to think this way, we are not a normal rtd project!!!), and now our > customers only know the catalougue, very few browse our forge if at all ... > (we have to improve our communication here): so the catalogue is the only > valid list! > 2.2. it is true that changes in the catalogue migth occur, but only from > ge owners for their own ge. at least, if this is not implemented, please > davide take proper actions. > 2.3. davide please create a report (only for catalogue regeistered users, > or even better only for catalogue administrators) that generates the table > miguel need. i do agree for him this importnat for the duties he has, e.g. > sending the list of ges to people asking that. this way the miguekl list is > always up-to-date > 2.4. if a change in name occurr, than a warning is generated to the ge > owner and miguel (only for notification) to verify all the name occurrences > through out the documentation > 2.5. at this point miguel can easily apply karma. > > 3. for newly developed ge, the miguel/manuel sheet is the reference and > the driver for ge names when these have to be published in the catalogue. > form this point we are back to point 2, i.e. natural ge evolution including > its name if this felt needed by the ge owner should be supported. indeed we > cannot block evolution becouse it is difficult to manage (i perfectly > second alex here), but of course we need tools to control the evolution > (defintively agree with miguel here). > > hope this a good solution for everybody, anyhow this must be a point for > this monday wpl meeting. > > ciao, > stefano > > 2015-06-10 11:39 GMT+02:00 MIGUEL CARRILLO PACHECO < > miguel.carrillopacheco at telefonica.com>: > >> Dear Stefano, >> >> Thanks for the support! >> >> I prefer to keep the google doc as the main reference. The doc shows all >> at a glance and the catalogue requires navigation to obtain a list. Also, >> the catalogue can be edited by many people and uncontrolled changes will >> occur. This doc is simple and easy to maintain (people continue asking me >> to add columns and I refuse to do it to make it simple and clear). Every >> time someone asks for the list of GEs and contacts, I can send the link to >> this one. >> >> *Each GE owner is expected to update all pages and resources to synch* *it >> *- *now, not in a months time*. So If I find a set of GE/GEris different >> from the ones here in different places, I will apply karma. And I may block >> deliverables as well. I will not buy "do not worry, it is the same one, we >> just changed the name" -> if you decide to change the name, you duly >> communicate it in advance. >> >> Regards, >> >> Miguel >> >> >> El 09/06/2015 a las 19:36, stefano de panfilis escribió: >> >> 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 >> >> >> -- >> >> 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 >> > > > > -- > 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 > > > _______________________________________________ > Fiware-chapter-leaders mailing list > Fiware-chapter-leaders at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-chapter-leaders > > -- Davide Dalle Carbonare IT Solution Architect Engineering Ingegneria Informatica S.p.A. - www.eng.it Mob: +39-346-3207983 @davdalle <https://twitter.com/davdalle> | linkedin <https://www.linkedin.com/in/davidedallecarbonare> | about.me <http://about.me/davidedallecarbonare> -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-chapter-architects/attachments/20150612/ac63b82f/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy