Hi Monica, hi all, Tomorrow I will start working with the comments/suggestions received from our reviewer to improve our deliverable. I will get back to you individually and ask for help if needed. Nevertheless, *Each GE owner should also have a look at the review of that GE section made by Sergio Garcia from TID and update it accordingly*. The link to the review is: https://forge.fiware.org/docman/view.php/59/5134/D.16.1.1+FIWARE+Architecture+-+APPS+v0.3-sergioreview.docx Please, send me your changes by this Friday so that I can create a consolidated doc on time. PLEASE ACTIVATE THE CHANGE CONTROL FEATURE OF WORD TO EASE MY TASK and keep Aitor on cc because next week I will be on vacations with limited access to my inbox... He will help me to finish this task ;-) BTW... I've just submitted my review of the Data (1.3) chapter. On time :-) BR, Javier 2015-05-18 14:48 GMT+02:00 Monica Franceschini <monica.franceschini at eng.it>: > Hi Javier, > I'm currently attending the chapter's leaders call. Miguel is wondering if > the architects are already working on the issue reported below, because he > didn't receive emails on it. > Is it everything ok for you? We're asked to check as wp leaders... > Thank you for your kind reply! > Monica > > > -------- Messaggio Inoltrato -------- Oggetto: [Fiware-chapter-leaders] > [IMPORTANT] Guidelines for the Architecture Document Data: Wed, 13 May > 2015 17:21:21 +0200 Mittente: MIGUEL CARRILLO PACHECO > <miguel.carrillopacheco at telefonica.com> > <miguel.carrillopacheco at telefonica.com> A: > fiware-chapter-architects at lists.fi-ware.org > <fiware-chapter-architects at lists.fi-ware.org> > <fiware-chapter-architects at lists.fi-ware.org> CC: > fiware-chapter-leaders at lists.fi-ware.org > <fiware-chapter-leaders at lists.fi-ware.org> > <fiware-chapter-leaders at lists.fi-ware.org>, Javier Soriano > <jsoriano at fi.upm.es> <jsoriano at fi.upm.es>, Torsten Spieldenner > <Torsten.Spieldenner at dfki.de> <Torsten.Spieldenner at dfki.de>, > gilles.privat at orange.com <gilles.privat at orange.com> > <gilles.privat at orange.com>, CARLOS RALLI UCENDO > <carlos.ralliucendo at telefonica.com> <carlos.ralliucendo at telefonica.com>, > Thomas Michael Bohnert <thomas.bohnert at zhaw.ch> <thomas.bohnert at zhaw.ch>, > DANGERVILLE Cyril <cyril.dangerville at thalesgroup.com> > <cyril.dangerville at thalesgroup.com> > > > Dear all, > > I made an effort to write a very detailed message with all the info you > may need to do this orderly. Please read it carefully, stick to it and we > will save loads of work. > > We have been neglecting a number of tasks in the mayhem of the review > preparation but it is time to put ourselves back together. This is the > first action of a stream of work fronts that will be soon reactivated. The > instructions sent months ago were to edit all in the public wiki but it > seems that not all chapter did it like this. We do not mind, we intended to > simplify your work and this is your choice, it will simply require an extra > effort on the architects but if you want to do it like this. I remind you > that the SAP tool cannot be used in the current project. > > Something I would like to stress is that I will edit the public wiki to > reflect R3 and R4 in separate pages. I will instruct you once it is > organized. > > Going to the subject of this message... as reminded in last monday's call, *the > architecture is the main task of the architects in FIWARE. They will take > full responsibility and they are fully accountable* for it (e.g.: karma, > cost rejections etc.) for whatever happens here if something approved by > them goes wrong. Leaders can help but their role here is supportive, not > central. > > We are going to finish the Architecture Deliverable for R4. Steps: > 1) *Architects* to take the templates and create a doc doing copy-paste > from the wiki pages. I would not go for the approach suggested by Alex as > saving on the hard disk and importing is too painful. In my experience, > direct copy-paste from wiki pages on the browser goes reasonably well. Up > to you. Before you ask, I am afraid that the tool to generate docs is not > yet finished. > > Template doc linked from the usual location : > > - > https://docs.google.com/spreadsheets/d/1cq-YRQTChw4WRpaRbMPIxOXEPQHiXR-fX0n-T9ncytU/edit#gid=0 > > If you want to have examples of past deliverables sent to the EC, they are > here (tab "Submitted deliverables"): > > - > https://docs.google.com/spreadsheets/d/1IK04LaNl5fGgyEZHs2scAMF3QoEQK-lPVqImaXRBKJQ/edit#gid=2063425807 > > We want it in *word format*. It has to look as though it is the final one. > > > 2) *Architects *to review their chapter (if not already done) and to pass > comments to the GE owners if necessary. They should modify both the doc and > the wiki that originated it . Once accepted internally and final, the > architect delivers putting a link to the doc for review in this place: > > - > https://docs.google.com/spreadsheets/d/1AxrcNOfvvglFc0T0rC-Wkz3OtvytnOtUG1eCmaVoZgk > > The links should point at the doc uploaded to the forge, project FIWARE > Private (*NOT FI-WARE Private*, the hyphenated one is the old one), > folder "Deliverable Edition" -> "Architecture_v4". I have granted you > access there (let me know if you cannot get there). > > The doc delivered in *word format* here should have a quality suitable > for delivery. > > 3) The cross review starts. An architect from other chapter reviews the > architecture and provides comments. He deposits the reviewed doc with > comments/suggestions on the same location: > > - > https://docs.google.com/spreadsheets/d/1AxrcNOfvvglFc0T0rC-Wkz3OtvytnOtUG1eCmaVoZgk > > 4) The architect of the chapter coordinates whatever internal reviews that > are needed and the internal iterations as necessary. After this, a final > version for delivery is generated. > > 5) The coordinator takes a final look (formal, codes in the cover,format > and things like that, do not expect a technical review) > > 6) Final delivery to the EC > > 7) Updates of the wiki with the final version. > > 8) Eventually, the Friendly testers or the FIWARE main architect may take > a look. > > Note that delivering late, or with sloppy format, or in the wrong place, > low quality, etc. will result in penalties. Same with step 8 (that could be > serious). The architect can report on bad performance of a GE owner (with > the accompanying result in the karma of the GE owner). Timely deliveries > with quality may mean positive scores as well. > > This is the timeline: > > - 20/05 - Delivery for cross review (note that all this should have > been done ages ago, but just in case someone did not do the review > properly) > - 27/05 - Delivery of the result of the cross review > - 03/06 - Delivery of a final architecture to the coordination > - 05/06 - Delivery to the EC > > According to my info, these are the architects: > > - IBM - Alex Glikson > - TID - Sergio GarcÃa > - TID - Carlos Ralli Ucendo > - DFKI - Philipp Slusallek > - UPM - Javier Soriano > - Thales - Cyril Dangerville > - ZHAW - Thomas M. Bohnert > > At each deadline I will go to the online doc and will check the status. I > will not ask one by one. If it is not there, it means that the objective > was not attained. No excuses. > > Congratulations to all of you who got this far reading! :) > > Best 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 > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-apps/attachments/20150527/c1ce4757/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy