[Fiware-security] TR: [Fiware] Guidelines for Release 2

BISSON Pascal pascal.bisson at thalesgroup.com
Thu Mar 28 10:19:11 CET 2013


FYI = Guidelines for Release 2 (counting on you all to follow those guidelines & deliver according to the set deadline for review aka April 22 !)

De : fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo
Envoyé : jeudi 28 mars 2013 02:24
À : fiware at lists.fi-ware.eu
Objet : [Fiware] Guidelines for Release 2

Dear all,

Given the importance of the general guidelines for the delivery of the deliverables associated to the software and the absence of key components of the team due to the Easter holidays, this message is directly sent to all the consortium. Be ready for a long but extremely important message.

This is strictly about :

 *   Delivery of the Software itself
 *   Installation and Administration manual
 *   User and Programmer manual
 *   Unit Testing Plan and report
The date for delivery to the EC is the end of April so we will need to have all complete and ready for review by April, 22 , as agreed in the past WPL/WPA call.

The guidelines are available on the private wiki (if you do not have access, ask your WPL or WPA to fix it) . The link to the detailed guidelines  is here(you need to this them before editing the deliverables):

 *   https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2
Please note that:

 *   The guidelines  for the docs are basically the same ones as for Release 1
 *   The guidelines for the software delivery are completely different and were sent by Fermín to this list ages ago
Please use the placeholders to edit each document (linked from the guidelines page). Most of the chapters have not started this work, they must use the private wiki following the links under the placeholder section in the guidelines. Exceptionally, if someone has started editing the changes somewhere else (I am only aware of some GEs in WP3), carry on working there but this place must be linked from the placeholders, so make them point at the right location where you actually work . If you start working now you must use the links provided and the private wiki.  I will ask to revert any unauthorised changes in the public wiki, I insist that you must use the private wiki (the public wiki should only have definite manuals, not intermediate stuff).

Be aware that this time moving pages across different wikis (figures included) is done in a matter of seconds thanks to a tool developed by SAP. Your WPL must have access to it (or can ask for access to it if he has not done so yet)

 *   This will ease the work of copying the definite versions of the manuals to their final destinations.
 *   Also, if you need to use a previous version on the manual as the basis for the coming issue of the docs, this   tool can be used to take a copy of the current wiki pages to the private wiki prior to the start of your work.
Check with your WPL/WPA if you have any doubts, I will only answer queries routed via the WPL/WPAs to ensure a good synchronisation of the whole process.

Best regards,

Miguel



________________________________

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/old-fiware-security/attachments/20130328/b9db77b4/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20130328/b9db77b4/attachment.txt>


More information about the Old-Fiware-security mailing list

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