[Fiware-chapter-architects] [IMPORTANT] Guidelines for the Architecture Document

MIGUEL CARRILLO PACHECO miguel.carrillopacheco at telefonica.com
Thu May 21 16:06:46 CEST 2015

Previous message: [Fiware-chapter-architects] [IMPORTANT] Guidelines for the Architecture Document
Next message: [Fiware-chapter-architects] [IMPORTANT] Guidelines for the Architecture Document
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Dear all,

At 12:00 I did a quick check. All but one in reasonable good order (I2ND could be much better, we requested a version suitable for delivery). IoT unfortunately did not deliver.

Karma was applied accordingly, most of them positively.

Next Wednesday (27/May) there will be another checkpoint with "Relevant Achievement/Failure" (+5/-10). This is for the delivery of the cross reviews. Again, I will look at the links and if these do not have reasonable work or are empty, I will record it as negative. I will not accept a "I forgot to copy the link to the google doc" as a valid exculpatory circumstance.

We will see how to deal with Chapter 14 and the review of Thales, who can't obviously start now.

Best regards,

Miguel

El 14/05/2015 a las 16:56, MIGUEL CARRILLO PACHECO escribió:
Dear all,

In response to queries received, I confirm that the check on 20/05 with have an associated karma for the Architects of "Relevant Achievement/Failure" (+5/-10)

I intend to remove the bottlenecks of micromanagement from the old project. New project, new rules. I will only look at the google doc and act upon what I see there (not contacting anyone in private). If the doc is delivered by e-mail, or other means that does not count, the google doc will be the only means of delivering. Those who delivered in the past must put the link to the doc there.

Regards,

Miguel

El 13/05/2015 a las 17:21, MIGUEL CARRILLO PACHECO escribió:
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<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
----------------------------------------------------------------------

Please update your address book with my new e-mail address: miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>

e-mail: miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>

Follow FIWARE on the net

Please update your address book with my new e-mail address: miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>

e-mail: miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>

Follow FIWARE on the net

________________________________

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-chapter-architects/attachments/20150521/3e19826c/attachment.html>

Previous message: [Fiware-chapter-architects] [IMPORTANT] Guidelines for the Architecture Document
Next message: [Fiware-chapter-architects] [IMPORTANT] Guidelines for the Architecture Document
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Fiware-chapter-architects mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy