[Fiware-security] FI-WARE - AP from yesterday WPL/WPA audi conf: putting the links on the private wiki

[BISSON Pascal]

Yes First complete draft is due end of April as already announced and in the minutes.

BR
Pascal



-----Message d'origine-----
De : Alexandre Boeglin [mailto:alexandre.boeglin at inria.fr] 
Envoyé : jeudi 11 avril 2013 19:26
À : BISSON Pascal
Cc : fiware-security at lists.fi-ware.eu; DANGERVILLE Cyril; SIEUX Corinne
Objet : Re: [Fiware-security] FI-WARE - AP from yesterday WPL/WPA audi conf: putting the links on the private wiki

Dear Pascal, All,

I have one "small" question, reading the email from Miguel.

He states: "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."

But I think it was previously stated that these were expected for end of
april as "first draft", and were due in final form at the end of june.

Could you please clarify the situation regarding these 3 documents, as
well as the Open Specification one?


Best regards,
Alex

Le mardi 09 avril 2013 à 10:16, BISSON Pascal a écrit:
> Dear all,
> 
> As per demand of project management I'd like to urge each of the GE owners for V2 to make the wiki links of 3 deliverables point at the place where you are editing (or will edit) them.
> 
> So here are the instructions you must follow:
> 
> go to
> 
>  *   https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2
> and make here point your links to :
>     * the place where you are editing the 3 documents (in principle, the private wiki)
>     * or alternatively ... if you have not started, point at the place where you will edit the 3 documents
> 
> If the page is blank because you have not started, put a note there with an "ongoing work" or something to justify why.
> 
> If there are particular circumstances why the doc is not going to be edited on the wiki (very exceptional case), the page must not remain blank. In that case put duly justify (put an explanatory note).
> 
> Counting on you to address promptly the demand above as it will greatly help assess the status but also the reviewing process at both Chapter level and project level.
> 
> Would appreciate if you could have this demand addressed asap (by today EOB preferably).
> 
> Many thanks in advance for your cooperation and support.
> 
> Best regards,
> 
> Pascal
> 
> PS: Enclosed are the general guidelines as a reminder already distributed.
> 
> 

> From: Miguel Carrillo <mcp at tid.es>
> Subject: [Fiware] Guidelines for Release 2
> To: "fiware at lists.fi-ware.eu" <fiware at lists.fi-ware.eu>
> Reply-to: "mcp at tid.es" <mcp at tid.es>
> Date: Thu, 28 Mar 2013 02:24:26 +0100
> user-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307
>  Thunderbird/17.0.4
> 
> 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
> 

> _______________________________________________
> Fiware mailing list
> Fiware at lists.fi-ware.eu
> https://lists.fi-ware.eu/listinfo/fiware


> _______________________________________________
> Fiware-security mailing list
> Fiware-security at lists.fi-ware.eu
> https://lists.fi-ware.eu/listinfo/fiware-security


-- 
Alexandre Boeglin
Madynes project-team – http://madynes.loria.fr/
Inria – http://www.inria.fr/