Dear GE Coords,
As you know the process for generating the new Architecture deliverable (D2.3.2b) is on going.
While in the mail below you can find the details, and deadlines, for the entire process to complete, I summarise here what is required as first steps concerning our chapter contributions:
- The update of the architecture page can be done, as it has been so far, in the original public wiki page at Interface to Networks and Devices (I2ND)<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Interface_to_Networks_and_Devices_%28I2ND%29_Architecture> and the corresponding GE pages:
o FIWARE.ArchitectureDescription.I2ND.CDI<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.I2ND.CDI>
o FIWARE.ArchitectureDescription.I2ND.CE<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.I2ND.CE>
o FIWARE.ArchitectureDescription.I2ND.NetIC<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.I2ND.NetIC>
o FIWARE.ArchitectureDescription.I2ND.S3C<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.I2ND.S3C>
- Please each GE coord to check that all the expected updates are done in those pages. Deadline for completing updates is Friday 8th march at 12:00 CET, which allows me to have a draft .doc ready by the same day EOB, as already announced in previous mails (and PhCs)
- The guidelines to update properly the architecture description are at link https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions
- I'll take care of all the other steps involving the 'deliverable cockpit' to have the document ready according to the further instructions below. It is at the moment sufficient for you to know that the automatic generation of a draft deliverable (.doc file) can be made available approx. twice a day, assuming that I make the modifications in the cockpit: to do this I kindly ask you to report to me when you have completed the update of one of your pages, so that I can trigger the re-generation of the .doc.
- Once this first version of the deliverable is ready, the peer review will be performed. The modification steps which originate from the review will be done on the .doc file directly.
Please complete those actions according to the schedule, in case you have any doubt about the process let me know.
Thanks and BR
Pier
Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Miguel Carrillo
Inviato: martedì 5 marzo 2013 11:23
A: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu
Oggetto: [Fiware-wpl] Guidelines for the creation of the Architecture
Dear all,
Let us condensate the procedure for the Architecture review in one message.
The calendar is the one agreed yesterday in the WPL/WPA call:
1. First draft of contributions by chapter ready for peer review: end of February
2. .docx first version of chapter ready by March 8
3. Comments on first draft (.docx with traced changes) due by March 13th
4. .docx second version of chapters ready for peer review: March 22nd
5. Comments on second draft due by April 2nd
6. Final version: April 10th
As you surely recall, the guidelines for the Architecture doc are under: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions
The process will be like reflected on the FI-WARE Architecture peer-review cockpit<https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0>:
* We can use any wiki in each chapter but we need to have all the pages of each chapter on the same wiki for the docx generation. It sounds painful but believe me, it is not thanks to the tools provided by Thorsten and his team. Do not change this until you receive a separate message that I will send with more details later today.
* Each WPL will generate a docx document per chapter (SAP will provide support to the doc generation if needed).
o Upload the generated doc to "FI-WARE private" project -> Docs -> folder ""Peer reviews" -> subfolder "Architecture Review"
o Add the link to the doc to the cockpit<https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0>
o Further instructions here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Deliverables.GeneratingDeliverables
* The document from a given chapter will be taken by the reviewers in charge of reviewing it using the link in the cockpit<https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0>
* The WPL of the chapter that reviews it will make sure that it is reviewed before the deadline. Up to him how to organize it internally.
* All the reviewers of a WP receive the same document but each one suggests changes for the GE (or GEs) they review. There is a line per GE, up to each WP to merge them or use them separately. Once finished, they will upload their reviews to the right folder:
o "FI-WARE private" project -> Docs -> folder ""Peer reviews" -> subfolder "Architecture Review"
o The link (or links if more than one) to the doc (or docs) will be added to the cockpit
* Each WPL will analyse with his team the comments provided and will generate a new version of the chapter docx to be further reviewed. The new version should be available on the deliverable cockpit. Note that from this point on, chapter should drive further updates on the Word document, instead of any temporary wiki
* The reviewers will have a second round of comments.
* The final version will be generated for delivery. At this point, we will merge the contributions from all chapters (it is a single monolithic deliverable) and send it to the EC.
* Chapter leaders will then coordinate updates of the public wiki to align with the Word document that was submitted to the EC
This is the assignment:
Chapter to be reviewed
Reviewing chapter
Data
IoT
Cloud
Apps
Apps
Security
IoT
I2ND
I2ND
Cloud
Security
Data
Best regards,
Miguel
--
----------------------------------------------------------------------
_/ _/_/ Miguel Carrillo Pacheco
_/ _/ _/ _/ Telefónica Distrito Telefónica
_/ _/_/_/ _/ _/ Investigación y Edifico Oeste 1, Planta 4
_/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N
_/ _/_/ 28050 Madrid (Spain)
Tel: (+34) 91 483 26 77
e-mail: mcp at tid.es<mailto:mcp at tid.es>
Follow FI-WARE on the net
Website: http://www.fi-ware.eu
Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
Twitter: http://twitter.com/Fiware
LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932
----------------------------------------------------------------------
________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.
This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
[cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non è necessario.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20130306/4a3d0d8c/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20130306/4a3d0d8c/attachment.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo Ambiente_foglia2.jpg
Type: image/jpeg
Size: 677 bytes
Desc: logo Ambiente_foglia2.jpg
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20130306/4a3d0d8c/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy