[Fiware-apps] Fwd: [IMPORTANT] Guidelines for the Architecture Document

[Javier Soriano]

Dear colleagues,

With regard to this email from Miguel Carrillo I am forwarding you, please
find here [1] the Word doc I have generated from the content of the public
wiki following the guidelines established by Miguel in step 1).

As you know we already did the review mentioned in 2) when we updated the
wiki to reflect the current situation of the chapter in FICORE (many GEs
left FIWARE, other GEs changed their owners and a new GE joined the
project, so many changes were required in this case), so we are ready for
cross-review (i.e. step 3). Nevertheless, before adding the link to the
word document as required in step 2) I want to give you a last chance to
review the Word doc.

Please maintain activated the change control feature of Word so that I can
find your changes. Remember that I need to maintain synced the Word doc and
the public wiki.

*The deadline for sending back your changes and suggestions/comments is
Tuesday the 19th (tomorrow), at 17:00*. At that time I will proceed to
consolidate the final version of the Word doc (and update the wiki if
needed) and add a link to that final document so that we accomplish with
step 2) on time.

I am cc'ing Miguel because I know that he wants to be informed about the
status/progression of this important task.

[1]
https://www.dropbox.com/s/zj1dlkv7dwwvdd2/FIWARE%20Architecture%20Doc%20WP1.6%20Release%204_v0.1.docx?dl=0

Best regards,
Javier

---------- Forwarded message ----------
From: MIGUEL CARRILLO PACHECO <miguel.carrillopacheco at telefonica.com>
Date: 2015-05-13 17:21 GMT+02:00
Subject: [IMPORTANT] Guidelines for the Architecture Document
To: "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>, Alex Glikson <GLIKSON at il.ibm.com>,
Javier Soriano <jsoriano at fi.upm.es>, SERGIO GARCIA GOMEZ <
sergio.garciagomez at telefonica.com>, CARLOS RALLI UCENDO <
carlos.ralliucendo at telefonica.com>, Philipp Slusallek <slusallek at dfki.de>,
Torsten Spieldenner <Torsten.Spieldenner at dfki.de>, DANGERVILLE Cyril <
cyril.dangerville at thalesgroup.com>, "gilles.privat at orange.com" <
gilles.privat at orange.com>, Thomas Michael Bohnert <thomas.bohnert at zhaw.ch>


 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/20150518/37cdc4c7/attachment.html>