[Fiware-iot] FW: [Fiware-wpa] Instructions to give the deliverables

[Bisztray, Denes (NSN - HU/Budapest)]

FYI,

Here is the mail that gives link to the Private Wiki and contains the instructions on the deliverables as well.

 

Best,

Dénes

 

From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of ext Miguel Carrillo
Sent: Tuesday, July 03, 2012 1:05 PM
To: fiware at lists.fi-ware.eu
Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Subject: [Fiware-wpa] Instructions to give the deliverables

 

Dear all,

I apologise for the long email but I prefer to put all the info in one single message and provide detailed instructions.

After discussing things in the weekly confcall with the WPLs and the WPAs we saw the need to reorganize the delivery of our commitments with the EC. We apologize again for all the trouble. It is the first release,  the next one will be smoother as we all will know how to do things.

Please note that the common reference is still valid:

*	[REF 1] - https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverables 

We have 5 basic blocks that will be explained separately. 

To make clear that we share the same interpretation of the terms I will first clarify this:

*	Public = open to the whole world 
*	Private = open to the PPP (Use Case Projects, EC ...) but not to the outside world 


BLOCK 1 - Source code
======================================================
Publicly available - upload it to the SVN (it appears as "SCM" in the forge) of the project "FI-WARE"

Privately available - do not bother to deliver, it is not mandatory in this case. If some one for whatever reason wants to deliver it anyway keeping it private, he can use the SVN of his chapter (FI-WARE Data, FI-WARE IoT ,etc.) , it will be fully private.

Please follow this naming convention and structure on SVN:

*	A directory called FI-WARE will be the first level 
*	The second level will be named after the chapter. Take the same names as used in the Features names under "Materializing...". To be more precise use these: "Apps", "Cloud", "IoT", "Data","I2ND" and "Security".

	     

*	The third level will be named after the GE, using the same name as in "Materializing...". For instance, in the following example  the GE must be called "PublishSubscribe" 

		
		

*	In the 4th level  you upload the different releases of your software.

In summary, something like this:





BLOCK 2 - Binaries, packages, configuration 
======================================================
After discussing this with a few people, we will do it on SVN now (it appears as "SCM" in the forge) - the "Files" part of the forge  will no longer be used. Here is a big change, actually.

Two cases:

*	Publicly available - upload it to the SVN (it appears as "SCM" in the forge) of the project "FI-WARE" 
*	Privately available - upload it to the SVN (it appears as "SCM" in the forge) of the project "FI-WARE PPP Restricted" 

In this case there is one more naming rule. The files (binaries, packages, properties), whatever their original name is, must be appended with a string that identifies the release. For instance, the file:

*	 openstack-tcloud 

would turn into 

*	openstack-tcloud-1.1.19-SNAPSHOT    (major release 1, minor release1, version 19) - the version is internal to each company, what you put here is your business!. The "SNAPSHOT"  string is compulsory.

All the files here will be tagged with "Release_1_1"


BLOCK 3 - Installation and administration guide
======================================================

*	If the GE is Public  - to be edited on [REF1] and then moved to the public wiki, following the instructions in [REF 1] 
*	If the GE is Private (accessible to PPP members only) - to be edited on [REF1] and then moved to the wiki of the project "FI-WARE PPP Restricted"


BLOCK 4 - User and programmer's guide
======================================================
This is fully public and will be edited on the private wiki on the link on [REF 1]. Then, once matured,  it will be ported to the public wiki

BLOCK 5 - Unit Testing Plan and Report
======================================================
Two parts:

*	Unit Testing Plan is public and it will be created as explained in [REF 1] 
*	The report will be will be a private document only accessible to the PPP members and the CE. It  will be created by filling in a template that I will provide to the WPLs/WPAs. I have added a template, an example and instructions in the private wiki.



Those with no access to the project FI-WARE or the project FI-WARE PPP Restricted can apply following the procedure explained in this tutorial:

*	https://wiki.fi-ware.eu/How_to_join_a_FI-WARE_project_in_FusionForge 

Ask your WPLs/WPAs to approve your request. They have the permissions to do it.

Best regards,

Miguel



-- 
----------------------------------------------------------------------
     _/          _/_/                     Miguel Carrillo Pacheco
    _/   _/     _/  _/   Telefónica       Distrito Telefónica 
   _/ _/_/_/   _/   _/   Investigación y  Edifico Oeste 1, Planta 9 
  _/   _/     _/  _/     Desarrollo       Ronda de la Comunicación S/N 
 _/          _/_/                         28050 Madrid (Spain)  
                                          Tel:  (+34) 91 483 26 77    
 
                                          e-mail: 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20120711/d6968935/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: abeebffj.png
Type: image/png
Size: 14179 bytes
Desc: abeebffj.png
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20120711/d6968935/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ATT1779287.png
Type: image/png
Size: 6226 bytes
Desc: ATT1779287.png
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20120711/d6968935/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ffhgfhjj.png
Type: image/png
Size: 6198 bytes
Desc: ffhgfhjj.png
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20120711/d6968935/attachment-0002.png>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT1779288.txt
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20120711/d6968935/attachment.txt>