[Fiware-wpl] Contents of chapters available and planning until official deliverable

[Juanjo Hierro]

Dear colleagues,

  You will find the .doc files of each of your chapters in the usual placeholders.  Now, the name associated to each of them adopts the following convention:

    "FI-WARE High-level Description - <name-of-chapter> Chapter v<x>.<y>"

  The integrated draft is available at:

https://forge.fi-ware.eu/docman/view.php/7/235/FI-WARE+High-Level+Description+integrated+draft+0.1+11-07-06.doc

  But we should keep working with separated files per chapter.

  I first action I would kindly ask all of you to perform is to check that all your stuff is there and I didn't miss anything during the integration :-)   If you find something missing, please let me know.

  Now, we should NOT relax and keep going to get the official release of the deliverable on time.  This was announced for mid July ... what mid July means is up to us, but I would suggest making it available on July 19th.

  What I would suggest now is that we carry out a peer review of each chapter, involving members of a given WP in reviewing the contents of those chapter with whom more inter dependencies may exist.

  In parallel, each group should try to finish what couldn't make for this first draft.   I know that the analysis of Security aspects, just to mention an example, is not closed for all the chapters.  I will try to send a summary of what I see pending per chapter later today.

  In respect to peer reviews, here you have my suggestions for a first round.  We would try to make another round before the deadline:


Chapter Chief editors   Contacts        Suggested peer reviewer (team)
Cloud Hosting   IBM     GLIKSON at il.ibm.com<mailto:GLIKSON at il.ibm.com>   Interfaces to Networks & Devices
Data/Context Management TID     jhierro at tid.es<mailto:jhierro at tid.es>   IoT Services Enablement
Apps/Services Ecosystem & Delivery      SAP     andreas.friesen at sap.com<mailto:andreas.friesen at sap.com>, torsten.leidig at sap.com<mailto:torsten.leidig at sap.com>  Security
IoT Services Enablement Orange & NSN    Thierry.nagellen at orange-ftgroup.com<mailto:Thierry.nagellen at orange-ftgroup.com>, lorant.farkas at nsn.com<mailto:lorant.farkas at nsn.com>    Data/Context Management
Interfaces to Networks & Devices        TI &DT  pierangelo.garino at telecomitalia.it<mailto:pierangelo.garino at telecomitalia.it>, Hans.Einsiedler at telekom.de<mailto:Hans.Einsiedler at telekom.de>    Cloud Hosting
Security        Thales  pascal.bisson at thalesgroup.com<mailto:pascal.bisson at thalesgroup.com>, daniel.gidoin at thalesgroup.com<mailto:daniel.gidoin at thalesgroup.com>        Apps/Services Ecosystem & Delivery


  I would suggest that we define the following milestones linked to this first round unless I hear any objection:

 *   July 11 EOB, reviewers to send their comments (I suggest word files with changes under control)
 *   July 13 EOB, revision of comments by editors of each chapter and upload of new version by chief editors on FusionForge

  If you believe that there would be a better assignment for you, please also let me know and we'll try together to see if there is an alternative arrangement.

  Chief editors in the table above matches the WPLs and WPAs as you may already know.   WPLs are entitled to contact the chief editor of the chapter his team has been assigned to review so that you can agree on how to proceed.

  We can keep the procedure of managing the editor token by playing with the states linked to documents in the docman system so that whenever one file is in "pending" state means somebody is editing it.  Whenever one changes the state of a given document to "pending" it should announce it to the people involved.   Anyway, you should always download the last version from FusionForge (or check that the version you have is downloadable) whenever you decide to start editing a document and change it to "pending".

  A good strategy in some cases is that you split the chapter in several files, so that you keep control of those pieces that you believe are unstable and leave the rest for review.

  If you have still pending points, this procedure won't be perfect so each editor should probably edit his version in parallel someone is reviewing it, then manage how to integrate the comments.   But there is no much better ways to proceed unless you have a better idea.

  There are other things that we should start hard because we are behind the schedule.   An important part has to do with starting to bring content to the website and blogs.   It won't be that difficult now that we have quite a bit of content and nice stories to talk about :-)    I'll send an email with a plan proposal on the matter either today or tomorrow.

  ONE FINAL WORD AND RATHER IMPORTANT: PLEASE respect the styles and procedures for editing describing at the front matter of the documents.   Some of you have tried to respect them, and integration was rather easy.   BUT I HAVE TO SAY THAT OTHERS HAVE NOT.   And this creates a lot of burden.   I can tell you that I have lost almost one hour with one of the chapters just fixing the formats while I have spent just 15 mins with the chapters from those who followed the rules.   FOR THE NEXT ROUND, take it seriously, I will reject any file that contains prohibited styles or broken styles.   I know that it's pretty easy just to copy&paste from another document you may have written before or apart of this project or a web page, but that action breaks everything and has unpredictable consequences in MS Word.   It is also easier to create bullet lists or numbered lists using the buttons for doing so that MS Word offers to you at the upper tool bar, but that also has unpredictable consequences and means breaking an homogeneous style across the whole document (I will indeed try to find out how to prevent these buttons to appear :-)

  And that's all for this very long mail, I want to again thank you for all your efforts, good attitude and, overall, patience with my requests.

  Best regards,

-- Juanjo

________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20110706/799ab7c1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jhierro.vcf
Type: text/x-vcard
Size: 429 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20110706/799ab7c1/attachment.vcf>