From mcp at tid.es Mon Jul 2 09:36:41 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 02 Jul 2012 09:36:41 +0200 Subject: [Fiware-wpa] [Fiware-wpl] R: [Fiware] Users' and Programmers' guides In-Reply-To: References: <4FED77C0.3080905@tid.es> <4FED9DBE.4090508@tid.es> Message-ID: <4FF14F89.7010607@tid.es> Dear Pier, dear Alex, My understanding is that the "Unit testing Plan & Report" (do not forget the "report" part, that has not been discussed yet) has two parts. From my conversations with Juanjo I gather that the first one would be PU (plan) and the second PP (report) In the last weeks we have focused on the review and we are organizing the sw delivery in a bit of a rush. Fortunately, the weekly call is in a few minutes so we have the opportunity to resolve all doubts, detect all the gaps and inconsistencies and (hopefully) and come to agreements where needed. I would suggest to concentrate on organizing the sw delivery this time (including associated docs) and leaving aside all other issues unless there's something particularly urgent. Best regards, Miguel El 29/06/2012 20:54, Alex Glikson escribi?: Perhaps we can have the links in the public wiki, put in some cases they will point to pages with restricted access (e.g., in the private wiki). Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | https://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: Garino Pierangelo To: Miguel Carrillo , Cc: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Date: 29/06/2012 05:58 PM Subject: [Fiware-wpl] R: [Fiware] [Fiware-wpa] Users' and Programmers' guides Sent by: fiware-wpl-bounces at lists.fi-ware.eu ________________________________ Hi Miguel, I still believe that the insertion of all the information concerning the deliverables in the ?Materialising? wiki pages is contrasting with the ?Dissemination Level? of some of these deliverables: in the DoW at least Dx.5n ?Unit testing Plan? is PP (not PUblic), while the only Public deliverable is the Dx.4n ?User Guide?. Both Dx.2n ?SW release? and Dx.3n ?Installation and Admin? might be either PP or PU, depending on what decisions were taken (for the time being in I2ND we decided to have them PP). Collecting the deliverable pages in the fi-ware-private wiki is of help to solve this issue, adding later the pages in the ?Materialising? wiki is not (particularly for the Unit Testing plan). BR Pier Da: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] Per conto di Miguel Carrillo Inviato: venerd? 29 giugno 2012 14:21 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware at lists.fi-ware.eu Oggetto: Re: [Fiware] [Fiware-wpa] Users' and Programmers' guides Dear all, Just for the sake of clarity, I have added all this info in the private wiki on the page dedicated to the edition of deliverables. * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverables I guess that all the project members have access here (if not, ask your WPL) Best regards, Miguel El 29/06/2012 11:39, Juanjo Hierro escribi?: Hi all, I just want to remind that no guidelines have been defined regarding the Users' and Programmers' Guides. This was a fact that and has been explained multiple times since long ago. It is difficult (if not impossible) to define common guidelines regarding the structure of such guides for such a diverse set of technologies like the ones in FI-WARE. On the other hand, this makes it easier to reuse Users' and Programmers' guides that the owners of the baseline asset linked to a given FI-WARE GE may have already (of course, they should be updated to make reference to new features, etc). Regarding the Admin and Installation Guide, we long ago defined a list of sections that every guide should include. The only guideline that we are going to provide has to do with where to place documentation/wiki-page links in the public Wiki. We will publish it in the Project Handbook but I can anticipate that it will just mention that the guides will be published as items in a bullet list that will be there within a section titled "Product guides" right after the "Unit Testing Plan" section linked to a given FI-WARE GE in the "Materializing the FI-WARE Vision" part of the public wiki. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa . -- ---------------------------------------------------------------------- _/ _/_/ 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 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. ispetta l'ambiente. Non stampare questa mail se non ? necessario. _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl -- ---------------------------------------------------------------------- _/ _/_/ 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: From mcp at tid.es Mon Jul 2 10:30:15 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 02 Jul 2012 10:30:15 +0200 Subject: [Fiware-wpa] [Fiware] [Fiware-wpl] Software delivery (how to provideDeliverable D.x.2.a) In-Reply-To: <93D28BDF64839C468B848D14227151A203A9ABE4@FIESEXC014.nsn-intra.net> References: <4FEB2121.9010809@tid.es> <4FEB2E2E.5020302@tid.es> <93D28BDF64839C468B848D14227151A203A9ABE4@FIESEXC014.nsn-intra.net> Message-ID: <4FF15C17.8090904@tid.es> Hi Lorant, Bring this forward in the confcall in a few minutes' time. BR miguel El 29/06/2012 14:32, Farkas, Lorant (NSN - HU/Budapest) escribi?: Hi Miguel, How will be visible to which release the package, binary, properties belong when there is more than one? One approach could be to have a :, e.g. Backend_ThingsManagement_GE:1.1.3 Another approach could be to have one ?package? (in forge terms) for the GE and the filenames of the package to have the release ID in the name, e.g. clotho-management-application-occi-0.3.34_noarch_fiware_rel1.3.rpm Maybe this was discussed, then sorry for my ignorance. Thanks & Br, Lorant From: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] On Behalf Of ext Miguel Carrillo Sent: Wednesday, June 27, 2012 6:01 PM To: fiware at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware] [Fiware-wpl] Software delivery (how to provideDeliverable D.x.2.a) Dear all, I have been warned (thanks, Alex) that in some special cases a given GE could be released privately. This is exceptional but it is stated in the DoW: [cid:part2.08050607.02010708 at tid.es] [cid:part3.06050600.03060204 at tid.es] In these very concrete cases, the SCM will not be used and the "Files" part of the project can be made private for that particular GE. Best regards, Miguel El 27/06/2012 17:05, Miguel Carrillo escribi?: Dear all, As editing the wiki will take a bit longer I will write a (rather long) email and will explain how to proceed with some aspects of the software delivery that were not clearly explained yet. Given the urgency of this I send it to the general list but please proceed to discuss any concerns internally in your respective WP lists. This message refers to software delivery. This means: * 1) Delivery for installation on the testbed(packages, properties and binaries) * 2) Source code delivery - this does not apply to those GE who have agreed not to provide it I will add all tall his to the private wiki later, putting alongside all the guidelines that are there already. First of all, the software delivery will take place on the forge. As regards the project within the forge, we will use the project of the WP (Iot, Data, Apps, Tools...) PART 1 - Delivery for installation on the testbed ======================================== The packages, properties and binaries go to the "Files" part of the project. [cid:part4.05010901.00050107 at tid.es] We have already delivered a GE in cloud and you can use it as an example: * https://forge.fi-ware.eu/frs/?group_id=14 First you create a Package (this goes with the GE name) Then you create 3 blocks per GE (using the "Create New Release" feature) * Packages (rpm, debian... ) - this does not apply to the particular example we provide but it should apply in many cases in your GEs * Binaries * Properties - miscelaneous files Please follow the same naming convention for the 3 blocks (Packages, Binaries, Properties). Add all three even if one of them is empty in your particular case. I see that this deliverable is Public according to the DoW so this should be publicly available, not private (the WPL must administrate this). If there are any particular concerns, let me know (privately - please do not reply to this email, it gets to more than 100 people!). For the WPL/WPA - hint: if you still cannot see this publicly, go to the admin part of the "Users" of the "Admin" section of the project and tweak the "Observer" user. [cid:part6.02010902.04010601 at tid.es] (this is not visible to most users, just those with admin right on the project) PART 2 - Delivery of source code ======================================== Depending on the GE, you may have decided to provide this or not. We would expect this for most of the GEs. This goes to the "SCM" tool in the project. [cid:part7.07010706.01060006 at tid.es] There you have a link to subversion where you can upload all the software. The admin of each WP (WPL and WPA, please proceed to do so) has the right to make their SCM public on the internet on the admin page of the SCM: [cid:part8.03010403.03000707 at tid.es] It is "all or nothing". Once this is made public, you cannot hide branches. Let us settle this: the SVN will be made public for each technical WP so the code that is uploaded here will be public. If something is private, you will not upload it here. When the testbed environment is fully set up we will send further instructions to provide extended info for the deployment (we will ask for maven - *.pom files - or test scripts, for instance). But this is not strictly necessary to meet the deadline that is upon us so we will do it later (but very soon!) 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 4916 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 5904 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 6424 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 8244 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 3857 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 2746 bytes Desc: not available URL: From jhierro at tid.es Mon Jul 2 10:59:31 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 02 Jul 2012 10:59:31 +0200 Subject: [Fiware-wpa] Shared minutes for our joint WPLs/WPAs follow-up confcall Message-ID: <4FF162F3.5090703@tid.es> Hi, Is here: https://docs.google.com/document/d/1JCLvt8rTu918iDa6aNQ8NMSVhB9Jv4PdxAv-aIt4rhQ/edit# Currently, it contains what was there last week because essentially we need to go and check the status of the different APs, with focus on deliverables due on Jun 30. I have already revised, based on progress by SAP, the text about the deliverable on "third innovation enablement in FI-WARE". Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 From pascal.bisson at thalesgroup.com Mon Jul 2 12:03:54 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 2 Jul 2012 12:03:54 +0200 Subject: [Fiware-wpa] TR: [Fiware-wpl] Software delivery (how to provide Deliverable D.x.2.a) Message-ID: <19821_1341223436_4FF1720C_19821_17332_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D3148C01@THSONEA01CMS04P.one.grp> As we discussed and as a reminder. Hearing from instructions also on this. BR Pascal De : BISSON Pascal Envoy? : vendredi 29 juin 2012 15:49 ? : Miguel Carrillo; JUAN JOSE HIERRO SUREDA Cc : BISSON Pascal; GIDOIN Daniel Objet : RE: [Fiware-wpl] Software delivery (how to provide Deliverable D.x.2.a) Importance : Haute Dear Miguel, Dear Juanjo, As you know for some our GEs there would be no software delivery being said those GEs would be running on local infrastructure and accessed only remotely. This is especially the case for IDM GE (NSN & DT). So question what should be reported for those type of GEs in the context of D8.2 ???? Thanks for instructions/guidance you and Juanjo could provide me on this and that I could pass to my team members facing such situation (indeed the case for NSN & DT). Hearing from you. BR Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : mercredi 27 juin 2012 17:05 ? : fiware at lists.fi-ware.eu Cc : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Software delivery (how to provide Deliverable D.x.2.a) Dear all, As editing the wiki will take a bit longer I will write a (rather long) email and will explain how to proceed with some aspects of the software delivery that were not clearly explained yet. Given the urgency of this I send it to the general list but please proceed to discuss any concerns internally in your respective WP lists. This message refers to software delivery. This means: * 1) Delivery for installation on the testbed(packages, properties and binaries) * 2) Source code delivery - this does not apply to those GE who have agreed not to provide it I will add all tall his to the private wiki later, putting alongside all the guidelines that are there already. First of all, the software delivery will take place on the forge. As regards the project within the forge, we will use the project of the WP (Iot, Data, Apps, Tools...) PART 1 - Delivery for installation on the testbed ======================================== The packages, properties and binaries go to the "Files" part of the project. [cid:image001.png at 01CD560E.7554B930] We have already delivered a GE in cloud and you can use it as an example: * https://forge.fi-ware.eu/frs/?group_id=14 First you create a Package (this goes with the GE name) Then you create 3 blocks per GE (using the "Create New Release" feature) * Packages (rpm, debian... ) - this does not apply to the particular example we provide but it should apply in many cases in your GEs * Binaries * Properties - miscelaneous files Please follow the same naming convention for the 3 blocks (Packages, Binaries, Properties). Add all three even if one of them is empty in your particular case. I see that this deliverable is Public according to the DoW so this should be publicly available, not private (the WPL must administrate this). If there are any particular concerns, let me know (privately - please do not reply to this email, it gets to more than 100 people!). For the WPL/WPA - hint: if you still cannot see this publicly, go to the admin part of the "Users" of the "Admin" section of the project and tweak the "Observer" user. [cid:image002.png at 01CD560E.7554B930] (this is not visible to most users, just those with admin right on the project) PART 2 - Delivery of source code ======================================== Depending on the GE, you may have decided to provide this or not. We would expect this for most of the GEs. This goes to the "SCM" tool in the project. [cid:image003.png at 01CD560E.7554B930] There you have a link to subversion where you can upload all the software. The admin of each WP (WPL and WPA, please proceed to do so) has the right to make their SCM public on the internet on the admin page of the SCM: [cid:image004.png at 01CD560E.7554B930] It is "all or nothing". Once this is made public, you cannot hide branches. Let us settle this: the SVN will be made public for each technical WP so the code that is uploaded here will be public. If something is private, you will not upload it here. When the testbed environment is fully set up we will send further instructions to provide extended info for the deployment (we will ask for maven - *.pom files - or test scripts, for instance). But this is not strictly necessary to meet the deadline that is upon us so we will do it later (but very soon!) 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 6424 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 8244 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 3857 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 2746 bytes Desc: image004.png URL: From mcp at tid.es Mon Jul 2 12:45:49 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 02 Jul 2012 12:45:49 +0200 Subject: [Fiware-wpa] Software delivery (how to provide Deliverable D.x.2.a) - REORGANIZED In-Reply-To: <4FEB2121.9010809@tid.es> References: <4FEB2121.9010809@tid.es> Message-ID: <4FF17BDD.7000805@tid.es> Dear all We have found that deliverables tagged as PP (private within the PPP programme ) need a different treatment and therefore we will have to reorganise the whole delivery process. We apologise for all the inconveniences caused to the ones that have already done the delivery. Wait until you receive further instructions. Best regards, Miguel El 27/06/2012 17:05, Miguel Carrillo escribi?: Dear all, As editing the wiki will take a bit longer I will write a (rather long) email and will explain how to proceed with some aspects of the software delivery that were not clearly explained yet. Given the urgency of this I send it to the general list but please proceed to discuss any concerns internally in your respective WP lists. This message refers to software delivery. This means: * 1) Delivery for installation on the testbed(packages, properties and binaries) * 2) Source code delivery - this does not apply to those GE who have agreed not to provide it I will add all tall his to the private wiki later, putting alongside all the guidelines that are there already. First of all, the software delivery will take place on the forge. As regards the project within the forge, we will use the project of the WP (Iot, Data, Apps, Tools...) PART 1 - Delivery for installation on the testbed ======================================== The packages, properties and binaries go to the "Files" part of the project. [cid:part1.08060007.04020604 at tid.es] We have already delivered a GE in cloud and you can use it as an example: * https://forge.fi-ware.eu/frs/?group_id=14 First you create a Package (this goes with the GE name) Then you create 3 blocks per GE (using the "Create New Release" feature) * Packages (rpm, debian... ) - this does not apply to the particular example we provide but it should apply in many cases in your GEs * Binaries * Properties - miscelaneous files Please follow the same naming convention for the 3 blocks (Packages, Binaries, Properties). Add all three even if one of them is empty in your particular case. I see that this deliverable is Public according to the DoW so this should be publicly available, not private (the WPL must administrate this). If there are any particular concerns, let me know (privately - please do not reply to this email, it gets to more than 100 people!). For the WPL/WPA - hint: if you still cannot see this publicly, go to the admin part of the "Users" of the "Admin" section of the project and tweak the "Observer" user. [cid:part3.07080901.06020708 at tid.es] (this is not visible to most users, just those with admin right on the project) PART 2 - Delivery of source code ======================================== Depending on the GE, you may have decided to provide this or not. We would expect this for most of the GEs. This goes to the "SCM" tool in the project. [cid:part4.02000203.00020706 at tid.es] There you have a link to subversion where you can upload all the software. The admin of each WP (WPL and WPA, please proceed to do so) has the right to make their SCM public on the internet on the admin page of the SCM: [cid:part5.05030704.07060508 at tid.es] It is "all or nothing". Once this is made public, you cannot hide branches. Let us settle this: the SVN will be made public for each technical WP so the code that is uploaded here will be public. If something is private, you will not upload it here. When the testbed environment is fully set up we will send further instructions to provide extended info for the deployment (we will ask for maven - *.pom files - or test scripts, for instance). But this is not strictly necessary to meet the deadline that is upon us so we will do it later (but very soon!) 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 ---------------------------------------------------------------------- -- ---------------------------------------------------------------------- _/ _/_/ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 6424 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 8244 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 3857 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 2746 bytes Desc: not available URL: From mcp at tid.es Mon Jul 2 18:33:48 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 02 Jul 2012 18:33:48 +0200 Subject: [Fiware-wpa] Generation of document deliverables Message-ID: <4FF1CD6C.7080800@tid.es> Dear WPLs/WPAs, This is a long message. If I send something long, people complain that it is too long. If I send it concise, they say that I do not provide details. So I choose "long" and then you have all the info you may need together! This is a message just for the WPLs/WPAs and it does not need forwarding to your teams (you can resend it but I do not think they need it for anything). As you are aware, apart from the software (D.x.2.a) we have to deliver 3 documents per chapter in pdf format extracted form the wiki: * D.x.3.a Installation and Administration Guide * D.x.4.a User and Programmers Guide * D.x.5.a Unit Testing Plan and Report As we stated in our weekly call, each WPL/WPA is responsible for the generation of the pdf version of the deliverables of his chapter. There is a tutorial here: * http://wiki.fi-ware.eu/How_to_create_pdf_deliverables_from_wiki_pages (Put particular attention to the utility to handle pdf files that we mention here, it is very useful) I remind you that once the 4 deliverables of a given chapter are ready, we will deliver them altogether. That is to say, we will deliver once for Cloud, another time for IOT, etc, etc. Each chapter has their own timing (and may need to explain on an individual basis significant deviations in time with respect to other chapters should it they happen) Covers =========== * Please add entries with your cover pages here: http://wiki.fi-ware.eu/Front_pages_for_deliverables_(wiki_books) * We have created 3 templates (please do not modify them, copy and paste them on your cover pages, replacing all the "X" with the right values - use the "search" facility on the browser, there are more "x"' than it seems) * FI-WARE Installation and Administration Guide(common template for 1st release) * FI-WARE User and Programmers Guide(common template for 1st release) * FI-WARE Unit Testing Plan and Report(common template for 1st release) * I see that WP7 have already done it so you can proceed taking them as an example of doing this. Merging private and public docs ============================ The plugin that we use to generate pdf files does not work with pages from two wikis at the same time. So if you need to merge pages from two wikis because part of the pages are on the public wiki and some others are on a private one, you need to generate two pdf books separately and merge them with the previously mentioned tool to obtain a single doc. In this case my advice is: * Add the cover just to one of them, you are going to use it just once! * Remove the index from both docs, or else you will mix two numberings and it will make no sense It seems difficult but it is terrible simple. I offer my help if something is unclear but please read this and the online tutorial carefully, there are 6 chapters and only one person on the other side, who also has other commitments !! 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: From mcp at tid.es Mon Jul 2 21:11:44 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 02 Jul 2012 21:11:44 +0200 Subject: [Fiware-wpa] How (and where) to deliver Release 1 (drop of june) Message-ID: <4FF1F270.4000109@tid.es> Dear WPLs/WPAs, It looks like today is a day of long emails. Before I send this to the whole consortium I prefer to see if you have any feedback. Please refrain from making minor comments as a delay has an impact on all the FI-WARE team and the delivery, we really need comments just if something key is overlooked(for instance, the other day Alex and Pier made a few fundamental remarks that made us reconsider things: privateness of chapter projects, dissemination level of deliverables, ...) Once this is settled, I will add all this info to the private wiki in the guidelines sections for future reference. I will send the following message to the general list at 12:00 on Tuesday (tomorrow) unless there is one or more strong objections. Thanks Miguel P.S.: Pascal, I would apply the rules for "private" to the GEs that are installed locally. ======== Dear all, 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. 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". [cid:part1.03090907.09030404 at tid.es] * 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" [cid:part2.03070508.04030404 at tid.es] * In the 4th level you upload the different releases of your software. In summary, something like this: [cid:part3.06030409.02050508 at tid.es] 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. 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 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: ibfbicfb.png Type: image/png Size: 14179 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ddgbbadc.png Type: image/png Size: 6226 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: gffficgc.png Type: image/png Size: 6198 bytes Desc: not available URL: From mcp at tid.es Mon Jul 2 21:16:30 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 02 Jul 2012 21:16:30 +0200 Subject: [Fiware-wpa] [Fiware-wpl] How (and where) to deliver Release 1 (drop of june) In-Reply-To: <4FF1F270.4000109@tid.es> References: <4FF1F270.4000109@tid.es> Message-ID: <4FF1F38E.9000003@tid.es> One thing I forgot in Block 2 - the files here will be tagged with "Release_1_1" El 02/07/2012 21:11, Miguel Carrillo escribi?: Dear WPLs/WPAs, It looks like today is a day of long emails. Before I send this to the whole consortium I prefer to see if you have any feedback. Please refrain from making minor comments as a delay has an impact on all the FI-WARE team and the delivery, we really need comments just if something key is overlooked(for instance, the other day Alex and Pier made a few fundamental remarks that made us reconsider things: privateness of chapter projects, dissemination level of deliverables, ...) Once this is settled, I will add all this info to the private wiki in the guidelines sections for future reference. I will send the following message to the general list at 12:00 on Tuesday (tomorrow) unless there is one or more strong objections. Thanks Miguel P.S.: Pascal, I would apply the rules for "private" to the GEs that are installed locally. ======== Dear all, 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. 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". [cid:part2.08090208.08050604 at tid.es] * 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" [cid:part3.07040306.01090605 at tid.es] * In the 4th level you upload the different releases of your software. In summary, something like this: [cid:part4.07070204.08090708 at tid.es] 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. 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 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 -- ---------------------------------------------------------------------- _/ _/_/ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 14179 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 6226 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 6198 bytes Desc: not available URL: From mcp at tid.es Tue Jul 3 13:04:38 2012 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 03 Jul 2012 13:04:38 +0200 Subject: [Fiware-wpa] Instructions to give the deliverables Message-ID: <4FF2D1C6.5090205@tid.es> 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". [cid:part2.08030600.09080201 at tid.es] * 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" [cid:part3.09020906.06070908 at tid.es] * In the 4th level you upload the different releases of your software. In summary, something like this: [cid:part4.09020907.01030705 at tid.es] 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: abeebffj.png Type: image/png Size: 14179 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 6226 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ffhgfhjj.png Type: image/png Size: 6198 bytes Desc: not available URL: From mcp at tid.es Tue Jul 3 13:08:19 2012 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 03 Jul 2012 13:08:19 +0200 Subject: [Fiware-wpa] Unit Test Report Message-ID: <4FF2D2A3.1050309@tid.es> Dear all, This is just to draw to your attention that there is a template and an example of the unit test report. Detailed instructions are in the private wiki. You must append this to the deliverable in pdf and it will be complete. BR 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 From mcp at tid.es Tue Jul 3 14:06:42 2012 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 03 Jul 2012 14:06:42 +0200 Subject: [Fiware-wpa] Auditing status of deliverables Message-ID: <4FF2E052.8020406@tid.es> Dear all, In coming days we will undertake a quick auditing of the status of the deliverables. I will start now with the parts that are already reasonable to inspect at this stage (first bullet point and maybe the second, basically) and then will continue going through the others in the course of the week. I will deal with this sending private messages to the WPLs. Best regards, Miguel ================== * Adding Features in the backlog per GE (public part of the backlog available on the Wiki) * Goals: * Try to get a complete set of features characterizing a given GE * Critical for resubmission of "Technical Roadmap" deliverable. Also a prerequisite for building a complete Unit Testing Plan * Way to audit: * Check, per GE, inclusion of new Features in the description of backlog entries available on the "Materializing the FI-WARE Vision" part of the wiki (means: checking of History on the wiki) - in this context "new" is added after 1/May or so * (note: this will be the first check, a more careful check will be performed afterwards, during July to confirm that the published Features give a complete vision of all the features supported by a given GE) * Unit Testing Plan (deliverable D.x.5.a "Unit Testing Plan and Report") * Goal: check that corresponding deliverable is ready for submission to the EC * Way to audit: * Previous point (Adding Features) is a prerequisite, therefore deliverable cannot be submitted without that part * Availability of specific section, per GE, on "Materializing the FI-WARE Vision" part of the public wiki following established guidelines * Availability of a Test Report following strictly the instructions provided on the private wiki * Users' and Programmers' Guides (public deliverable D.x.4.a) * Goal: check that corresponding deliverable is ready for submission to the EC * Way to audit: * Availability of item in section titled "Product guides", per GE, on "Materializing the FI-WARE Vision" part of the public wiki, following established guidelines * Installation and Admin Guides (deliverable D.x.3.a) * Goal: check that corresponding deliverable is ready for submission to the EC * Way to audit (software with PP dissemination level) * Availability of item in section titled "Product guides", per GE, on "Materializing the FI-WARE Vision (contents with restricted access)" part of the wiki of the "FI-WARE PPP Restricted" project, following established guidelines. (note per chapter: structure the contents of your chapter in this wiki following the case example of the Cloud chapter) * Way to audit (software with PU dissemination level) * Availability of item in section titled "Product guides", per GE, on "Materializing the FI-WARE Vision" part of the public wiki, following established guidelines * SW Release (public part of deliverable D.x.2.a "SW Release") * Goal: check that corresponding deliverable is ready for submission to the EC * Way to audit (software with PP dissemination level) * The binaries, properties and packages are on SVN following the naming convention and the structure defined. Also they are tagged with the release. * Way to audit (software with PU dissemination level) * The binaries, properties and packages are on SVN following the naming convention and the structure defined. Also they are tagged with the release. * The source code is deposited on the SCM -- ---------------------------------------------------------------------- _/ _/_/ 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: From stefano.depanfilis at eng.it Tue Jul 3 14:13:38 2012 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Tue, 3 Jul 2012 14:13:38 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Auditing status of deliverables In-Reply-To: <4FF2E052.8020406@tid.es> References: <4FF2E052.8020406@tid.es> Message-ID: dear miguel, i see that the "sanicity check" needed by the testbed, and proposed by you, to verify the ges installation is disappeared from your notes and requests? i wonder if this is part of the installation guide? can you please clarify? ciao, stefano 2012/7/3 Miguel Carrillo > Dear all, > > In coming days we will undertake a quick auditing of the status of the > deliverables. I will start now with the parts that are already reasonable > to inspect at this stage (first bullet point and maybe the second, > basically) and then will continue going through the others in the course of > the week. > > I will deal with this sending private messages to the WPLs. > > Best regards, > > Miguel > ================== > > - Adding Features in the backlog per GE (public part of the backlog > available on the Wiki) > - Goals: > - Try to get a complete set of features characterizing a given GE > - Critical for resubmission of "Technical Roadmap" > deliverable. Also a prerequisite for building a complete Unit Testing Plan > - Way to audit: > - Check, per GE, inclusion of *new* Features in the description > of backlog entries available on the "Materializing the FI-WARE Vision" part > of the wiki (means: checking of History on the wiki) - in this context > "new" is added after 1/May or so > - (note: this will be the first check, a more careful check will > be performed afterwards, during July to confirm that the published Features > give a complete vision of all the features supported by a given GE) > - Unit Testing Plan (deliverable D.x.5.a "Unit Testing Plan and > Report") > - Goal: check that corresponding deliverable is ready for > submission to the EC > - Way to audit: > - Previous point (Adding Features) is a prerequisite, therefore > deliverable cannot be submitted without that part > - Availability of specific section, per GE, on "Materializing > the FI-WARE Vision" part of the public wiki following established > guidelines > - Availability of a Test Report following strictly the > instructions provided on the private wiki > - Users' and Programmers' Guides (public deliverable D.x.4.a) > - Goal: check that corresponding deliverable is ready for > submission to the EC > - Way to audit: > - Availability of item in section titled "Product guides", per > GE, on "Materializing the FI-WARE Vision" part of the public wiki, > following established guidelines > - Installation and Admin Guides (deliverable D.x.3.a) > - Goal: check that corresponding deliverable is ready for > submission to the EC > - Way to audit (software with PP dissemination level) > - Availability of item in section titled "Product guides", per > GE, on "Materializing the FI-WARE Vision (contents with restricted access)" > part of the wiki of the "FI-WARE PPP Restricted" project, following > established guidelines. (note per chapter: structure the contents of your > chapter in this wiki following the case example of the Cloud chapter) > - Way to audit (software with PU dissemination level) > - Availability of item in section titled "Product guides", per > GE, on "Materializing the FI-WARE Vision" part of the public wiki, > following established guidelines > > > - SW Release (public part of deliverable D.x.2.a "SW Release") > - Goal: check that corresponding deliverable is ready for > submission to the EC > - Way to audit (software with PP dissemination level) > - The binaries, properties and packages are on SVN following the > naming convention and the structure defined. Also they are tagged with the > release. > - Way to audit (software with PU dissemination level) > - The binaries, properties and packages are on SVN following the > naming convention and the structure defined. Also they are tagged with the > release. > - The source code is deposited on the SCM > > -- > ---------------------------------------------------------------------- > _/ _/_/ 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 > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpl > > -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Tue Jul 3 14:33:22 2012 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 03 Jul 2012 14:33:22 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Auditing status of deliverables In-Reply-To: References: <4FF2E052.8020406@tid.es> Message-ID: <4FF2E692.7030005@tid.es> Dear Stefano, Thanks for noticing. If you go to the section for the deliverables on the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverables You will see in the specific instructions for the Installation & Admin guides that this is there. In my looong email to all the people in FI-WARE I wrote at the beginning this "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 " So I guess it should be clear. Of course I will check this. When I check a deliverable I will do it with all its particular rules in front of me. Best regards, Miguel . El 03/07/2012 14:13, stefano de panfilis escribi?: dear miguel, i see that the "sanicity check" needed by the testbed, and proposed by you, to verify the ges installation is disappeared from your notes and requests? i wonder if this is part of the installation guide? can you please clarify? ciao, stefano 2012/7/3 Miguel Carrillo > Dear all, In coming days we will undertake a quick auditing of the status of the deliverables. I will start now with the parts that are already reasonable to inspect at this stage (first bullet point and maybe the second, basically) and then will continue going through the others in the course of the week. I will deal with this sending private messages to the WPLs. Best regards, Miguel ================== * Adding Features in the backlog per GE (public part of the backlog available on the Wiki) * Goals: * Try to get a complete set of features characterizing a given GE * Critical for resubmission of "Technical Roadmap" deliverable. Also a prerequisite for building a complete Unit Testing Plan * Way to audit: * Check, per GE, inclusion of new Features in the description of backlog entries available on the "Materializing the FI-WARE Vision" part of the wiki (means: checking of History on the wiki) - in this context "new" is added after 1/May or so * (note: this will be the first check, a more careful check will be performed afterwards, during July to confirm that the published Features give a complete vision of all the features supported by a given GE) * Unit Testing Plan (deliverable D.x.5.a "Unit Testing Plan and Report") * Goal: check that corresponding deliverable is ready for submission to the EC * Way to audit: * Previous point (Adding Features) is a prerequisite, therefore deliverable cannot be submitted without that part * Availability of specific section, per GE, on "Materializing the FI-WARE Vision" part of the public wiki following established guidelines * Availability of a Test Report following strictly the instructions provided on the private wiki * Users' and Programmers' Guides (public deliverable D.x.4.a) * Goal: check that corresponding deliverable is ready for submission to the EC * Way to audit: * Availability of item in section titled "Product guides", per GE, on "Materializing the FI-WARE Vision" part of the public wiki, following established guidelines * Installation and Admin Guides (deliverable D.x.3.a) * Goal: check that corresponding deliverable is ready for submission to the EC * Way to audit (software with PP dissemination level) * Availability of item in section titled "Product guides", per GE, on "Materializing the FI-WARE Vision (contents with restricted access)" part of the wiki of the "FI-WARE PPP Restricted" project, following established guidelines. (note per chapter: structure the contents of your chapter in this wiki following the case example of the Cloud chapter) * Way to audit (software with PU dissemination level) * Availability of item in section titled "Product guides", per GE, on "Materializing the FI-WARE Vision" part of the public wiki, following established guidelines * SW Release (public part of deliverable D.x.2.a "SW Release") * Goal: check that corresponding deliverable is ready for submission to the EC * Way to audit (software with PP dissemination level) * The binaries, properties and packages are on SVN following the naming convention and the structure defined. Also they are tagged with the release. * Way to audit (software with PU dissemination level) * The binaries, properties and packages are on SVN following the naming convention and the structure defined. Also they are tagged with the release. * The source code is deposited on the SCM -- ---------------------------------------------------------------------- _/ _/_/ 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 _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -- ---------------------------------------------------------------------- _/ _/_/ 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: From juan.bareno at atosresearch.eu Thu Jul 5 15:49:24 2012 From: juan.bareno at atosresearch.eu (=?iso-8859-1?Q?Juan_Bare=F1o_Guerenabarrena?=) Date: Thu, 5 Jul 2012 15:49:24 +0200 Subject: [Fiware-wpa] FW: NEC Commitments for MONTH-15 FI-WARE D11.4 Deliverable and requests confirmation //email 1 of 2// In-Reply-To: <58967817BA9AEA4E92A38F89CE2EA93224D1C428@PALLENE.office.hd> References: <58967817BA9AEA4E92A38F89CE2EA93224D1C428@PALLENE.office.hd> Message-ID: Dear WPLs Please find below the detailed plan for complete the standardization deliverable for M15, end of this month Please react to what NEC, task leader, ask from you: - Identify a responsible partner per WP - Provide the inputs required in the wiki - Review content and format requirements For any doubt please contact Lindsay/Ernoe, in cc Thanks for your contribution Juan From: Lindsay Frost [mailto:Lindsay.Frost at neclab.eu] Sent: jueves, 05 de julio de 2012 15:12 To: Juan Bare?o Guerenabarrena; Miguel Carrillo; Nuria De-Lama Sanchez; Carmen Perea Escribano; lorant.farkas at nsn.com; thierry.nagellen at orange.com Cc: Ernoe Kovacs Subject: NEC Commitments for MONTH-15 FI-WARE D11.4 Deliverable and requests confirmation //email 1 of 2// Importance: High Dear FI-WARE management team, Please distribute this email on PCC; fiware-wpl at lists.fi-ware.eu; and fiware-wpa at lists.fi-ware.eu We refer to information provided to NEC in a teleconference on 02.07 by FI-WARE management regarding providing in the next 3 weeks a new Standardization Plan. NEC protests at the way the management decision was reached and communicated. The decision took no account of NEC proposals which were sent 23.05.2012 and for which responses were twice requested. The decision now requires NEC to make a burst of effort in the next 3 weeks to immediately create a new Standardization Plan, without considering NEC staff availability. Furthermore, the needed strategic inputs are not in the hands of NEC to create. Nevertheless, NEC has created a new fast-track plan with some chance of success, assuming continuous and strong input from partners. Endorsement, help and support from FI-Ware management and PCC is strongly requested. Depending on the inputs from FI-WARE partners and the later review of the EC, NEC will reconsider its' future participation in this part of WP11. Outline of Plan (detailed plan below): ? FI-WARE WPLs identify which Generic Enabler interfaces are important and therefore crucial for standardization. It is essential that a FI-WARE software architect complete such a list/diagram immediately to focus the work. ? FI-WARE WPLs nominate responsible partners and _persons_ who will input the plan and status for standardization at _specific_ SDOs, for _each_ of those important interfaces (a subset of all interfaces) ? The nominated responsible persons input their plan into the private Wiki as described below, and update the Wiki FI-WARE Standardization v2 (private wiki) with (their) past contributions as well as planned future ones. FI-WARE management team has promised weekly oversight of this activity. ? NEC summarizes results in last week of July, creating D11.4b pdf from the Wiki NEC requests confirmation of this plan, which is detailed below. Yours sincerely, Dr. Lindsay Frost, Dr. Ernoe Kovacs ATTACHMENTs (1) Old, still valid Action Plan to react to EC comments (file 2012-05-23-ActionPlan.txt) (2) Detailed Plan for D11.4.b by End July (see below) Attachment 2: The following is the step-by-step plan: (D) NEC Conclusions for Standardization Plan content and format 6. General content required (to be generated by FI-WARE partners) a. identify what standardization makes sense for FI-WARE (targets), taking account of specific gaps which the EC requested fixed b. identify where to do it (selected SDOs) /note: should reference "Section 2 CONTRIBUTE" actions in D11.4a/ c. explain (if it is planned) where IP generated in FI-WARE is inserted into SDOs specifications d. for each selected SDO and FI-WARE target, show the timeline of how to achieve the target, with "concrete steps" and partners, starting work "even before usable results" as requested by EC e. show how ongoing actual contributions to SDOs fulfill the "concrete steps" (i.e. ongoing status) 7. Step by step Format a. WPLs create a webpage mapping important FI-WARE interfaces/protocols to the Target SDO which could be responsible. It should also indicate any IPR which FI-WARE may bring in. This webpage would satisfy (D)6.a and (D)6.b and (D)6.c above. In the opinion of NEC, standardization is most valuable for the exposed interfaces, and in a secondary way to efficiently design the internal interfaces. Therefore all exposed interfaces are important, and some internal ones. As an example of some important interfaces, the (old) picture https://forge.fi-ware.eu/plugins/mediawiki/wiki/iot/index.php/Snapshot_2012.06.01_of_Deliverable_Page_for_D2.3_Architecture_Specifications could be used. b. WPLs create a webpage showing which partner is responsible for each important interface and their responsible person to make it standardized. The format can be a table ("Target SDO / Responsible Persons") with entries . c. Responsible persons add to FI-WARE Standardization v2 (private wiki) page, for each Target SDO, a timeline based on the SDO meeting schedules and methods, which is designed to get the exposed interface standardized. A partial example is given for ETSI M2M. This satisfies (D)6.d. This can only be created by the responsible persons who also ensure that that Target SDO work happens. It should indicate the phases as e.g. (1) feasibility-study (2) architecture (3) datamodels and protocols. The format can be a table ("Target SDO / Contributions Table ") ordered by date, so later it is easier for the information to be integrated into a complete project plan, e.g. d. The responsible person updates the Target SDO / Contributions Table every week, with new planned inputs and new results. Care should be taken to note any IPR. This satisfies (D)6.e. e. NEC creates an integrated timetable showing the aggregated copies of all tables from step (c) above, which is the overview for the EC. NEC will combine it with (a) and (b) - assuming all partners have strongly contributed - so as to resolve all EC requests. f. Optionally partners can extend the information in (c) above, to include highly relevant non-FI-WARE results which are monitored (M). Also partners can include relevant work they do which however is not part of the agreed important interface work. Monitoring standards is also part of the standardization plan and this work should be reported to the EC, as long as it is shown as supporting a significant amount of active contributions work. NEC rejects proposals to use Googledocs because NEC was required to change from doc to Wiki during the previous phase of the project and the good reasons for doing that still hold. ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: 2012-05-23-ActionPlan.txt URL: From jhierro at tid.es Thu Jul 5 17:15:42 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 05 Jul 2012 17:15:42 +0200 Subject: [Fiware-wpa] Fwd: FI-WARE: change of unit and financial officers In-Reply-To: <69AD1A9684E7184DADBE43806285BA9D0576D8@S-DC-ESTF03-B.net1.cec.eu.int> References: <69AD1A9684E7184DADBE43806285BA9D0576D8@S-DC-ESTF03-B.net1.cec.eu.int> Message-ID: <4FF5AF9E.3080409@tid.es> Nothing rather relevant, but just to keep you informed -------- Original Message -------- Subject: FI-WARE: change of unit and financial officers Date: Thu, 5 Jul 2012 14:52:14 +0000 From: To: , , , CC: , , , , Dear all, Please be informed that FI-WARE has been transferred to unit CNECT-E3 "Net Innovation", with Head of Unit Jesus Villasante, as of July 1. I am still the responsible Project Officer. For financial/contact matters, please contact Stephane Andries and Gaelle Lanckmans (back-up) from now on. Best regards, Arian. ________________________________ 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: From ralli at tid.es Fri Jul 6 15:32:21 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Fri, 06 Jul 2012 13:32:21 +0000 Subject: [Fiware-wpa] Analysis (& Work to be done by WPls/WPas) - Support tracker for UC projects requirements Message-ID: Dear Colleagues, This morning I have analyzed the tickets opened by UCs in this tracker since we announced to give more weight to this communication channel in the context of the recent "Fi-PPP SW Architects Weeks" (I tool as starting point the first day of the first edition in Zurich = May 21st 2012). As a result I have generated a table in the excel book attached to this e-mail in order to start the monitoring/control process of these tickets as committed in the past review also during my presentation of the WP12 chapter. Juanjo is including a specific slot for our next call on Monday and we will be making a short roundtable to ask each WPl/WPa about these tickets and your plans in order to solve and close them. I would like to hear also which inputs/UCs you are missing according to the feedback received during the last call so Juanjo can highlight and request the submission of those concrete points in the context of the Architecture Board meetings. In the call I will be providing information and plans for the tickets related to Data chapter and all tickets marked as "unknown" and thus not specifically assigned to any chapter. As you can see there are tickets addressed to Security, I2ND and IoT too. Thanks for your cooperation. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @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 -------------- A non-text attachment was scrubbed... Name: 20120706_Supp-Tracker-Analysis.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 21084 bytes Desc: 20120706_Supp-Tracker-Analysis.xlsx URL: From jhierro at tid.es Fri Jul 6 16:06:47 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 06 Jul 2012 16:06:47 +0200 Subject: [Fiware-wpa] IMPORTANT: Shared minutes of next follow-up confcall on Monday 11:00am Message-ID: <4FF6F0F7.4030406@tid.es> Hi all, Please find enclosed the shared draft minutes that we will follow during our next joint WPLs/WPAs follow-up confcall on Monday, starting 11:00am and planned to last 2h: https://docs.google.com/document/d/1hCtDnOvH6-hRaNVX9G_l-2zwL5G1YvkoJjaehmtBj9k/edit There are a number of specific slots, marked in yellow, where we ask you to provide a brief report on the status of your chapter. Please try to cover it by the starting time of the confcall. During his analysis, Miguel Carrillo has identified very little progress of some chapters so we need to justify why and what are the expected recovery plan. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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: From jhierro at tid.es Mon Jul 9 10:15:36 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 09 Jul 2012 10:15:36 +0200 Subject: [Fiware-wpa] REMINDER Fwd: IMPORTANT: Shared minutes of next follow-up confcall on Monday 11:00am In-Reply-To: <4FF6F0F7.4030406@tid.es> References: <4FF6F0F7.4030406@tid.es> Message-ID: <4FFA9328.6080902@tid.es> Hi all, This is a reminder of the joint WPLs/WPAs follow-up confcall starting at 11:00am. Bear in mind that you were requested to fill a number of slots in the shared minutes where you were asked to provide a brief report on the status of your chapter Cheers, -- Juanjo -------- Original Message -------- Subject: IMPORTANT: Shared minutes of next follow-up confcall on Monday 11:00am Date: Fri, 06 Jul 2012 16:06:47 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, Please find enclosed the shared draft minutes that we will follow during our next joint WPLs/WPAs follow-up confcall on Monday, starting 11:00am and planned to last 2h: https://docs.google.com/document/d/1hCtDnOvH6-hRaNVX9G_l-2zwL5G1YvkoJjaehmtBj9k/edit There are a number of specific slots, marked in yellow, where we ask you to provide a brief report on the status of your chapter. Please try to cover it by the starting time of the confcall. During his analysis, Miguel Carrillo has identified very little progress of some chapters so we need to justify why and what are the expected recovery plan. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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: From mcp at tid.es Mon Jul 9 16:26:47 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 09 Jul 2012 16:26:47 +0200 Subject: [Fiware-wpa] Discount at FUSECO Message-ID: <4FFAEA27.9010309@tid.es> Dear all, Those interested in attending the FUSECO in november must be aware that the early bird registration is open and that if they contact me privately I can provide extended info (that possibly is on their website, anyway!) and a code to get a 15% discount. The site is this one: http://www.fokus.fraunhofer.de/en/fokus_events/ngni/fuseco_forum_2012/program/detailed_program/index.html Juanjo will be present in one of the pannels. Just ot clarify. I believe this is not eligible for funding unless you present something of FI-WARE (that the case with Juanjo) ... I am just telling you in case you are interested in the discount. 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 From stefano.depanfilis at eng.it Mon Jul 9 16:29:18 2012 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Mon, 9 Jul 2012 16:29:18 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Analysis (& Work to be done by WPls/WPas) - Support tracker for UC projects requirements In-Reply-To: References: Message-ID: dear carlos, as per current tickets system there is no possibility of rthe uc projects to issue a ticket with respect to the testbed as this entry is not in the drop-box. it migth be useful to add this item in the list, unless we do not want ticket on this critical aspect ... ;-) ciao, stefano 2012/7/6 CARLOS RALLI UCENDO > Dear Colleagues, > > This morning I have analyzed the tickets opened by UCs in this tracker > since we announced to give more weight to this communication channel in the > context of the recent "Fi-PPP SW Architects Weeks" (I tool as starting > point the first day of the first edition in Zurich = May 21st 2012). > > As a result I have generated a table in the excel book attached to this > e-mail in order to start the monitoring/control process of these tickets as > committed in the past review also during my presentation of the WP12 > chapter. > > Juanjo is including a specific slot for our next call on Monday and we > will be making a short roundtable to ask each WPl/WPa about these tickets > and your plans in order to solve and close them. I would like to hear also > which inputs/UCs you are missing according to the feedback received during > the last call so Juanjo can highlight and request the submission of those > concrete points in the context of the Architecture Board meetings. > > In the call I will be providing information and plans for the tickets > related to Data chapter and all tickets marked as "unknown" and thus not > specifically assigned to any chapter. > > As you can see there are tickets addressed to Security, I2ND and IoT too. > > Thanks for your cooperation. > Best regards, > -- > > ------------------------------------------------------------------------------------------------------------------------ > Carlos Ralli Ucendo (ralli at tid.es) > Cell: +34696923588 > Twitter: @carlosralli > Product Development & Innovation (Telef?nica Digital) > Telef?nica I+D SAU > Madrid, Spain > > ------------------------------------------------------------------------------------------------------------------------ > Follow FI-WARE project (Future Internet Services Core Platform): > Website: http://www.fi-ware.eu > Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > Twitter: @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 > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpl > > -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue Jul 10 06:58:29 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 10 Jul 2012 06:58:29 +0200 Subject: [Fiware-wpa] YOUR HOMEWORK on Deliverable on 3rd Party Innovation Enablement Message-ID: <4FFBB675.7050101@tid.es> Hi all, As you all know, we have to submit a deliverable on "3rd Party Innovation Enablement in FI-WARE" by end of July. This deliverable was due on Month 12 (i.e., end of April) but our PO agreed to re-plan it for the end of July. You have a summary of the progress and APs on the shared minutes of our last joint WPLs/WPAs follow up confcalls: https://docs.google.com/document/d/1hCtDnOvH6-hRaNVX9G_l-2zwL5G1YvkoJjaehmtBj9k/edit?pli=1# The relevant point is that each Chapter should make a contribution to the deliverable, covering a section where you should elaborate on how the design choices in you chapter contributes to 3rd Party Innovation. You contribution should be 2-3 pages long and should be ready by July 20th. We are going to work on a shared google docs version of the document located at: https://docs.google.com/document/d/1HnmGAJ7LuHJs9oBIhVwbR9LuKMK-Xhb_c7SF-EVQi_Q/edit#heading=h.o4fda49w1fqp There are a number of hints marked in yellow within the document that, hopefully, will allow you to complete your work. Nevertheless, don't hesitate to ask for any doubt you may have. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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: From jhierro at tid.es Tue Jul 10 11:59:53 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 10 Jul 2012 11:59:53 +0200 Subject: [Fiware-wpa] ACTION POINT on SAP regarding safety of place where to submit deliverables marked as PP Message-ID: <4FFBFD19.6090801@tid.es> Hi Axel, This is a reminder to you regarding SAP's position objecting to submit deliverables marked as PP. As we explained to you during the last joint WPLs/WPAs follow-up confcall, SAP has argued that the restricted access collaborative space we had setup to upload deliverables marked as PP didn't provide enough "trust". This collaborative space with restricted access is essentially a separate project in the family of FI-WARE related projects under FusionForge, named as "FI-WARE PPP Restricted". Visibility of content uploaded in this project is as follows: * Wiki is only accessible to members of the project (the "FI-WARE PPP Restricted" project in FusionForge). Here it is where partners are expected to provide guidelines accompanying software, unless in document formant in which case should be available in the SVN system * SVN (where software and accompanying documentation has been asked to be uploaded) is only accessible to members of the project * docman: this is as the docman in rest of projects, i.e., documents can be marked as private in which case they are accessible only to members of the project * rest of tools are not active In order to manage membership to the "FI-WARE PPP Restricted" project, we have tried to find out a trade-off between avoiding to become a bottleneck while keeping the process "in the hands of people we can trust". Therefore, we only add WPLs and WPAs initially to the project and we only assign Admin privileges to them, you, Miguel Carrillo and myself (we two, merely as backups). Admin users are the only ones that would then have the right to accept membership requests and assign a profile to new members (they should assign them a profile of "Senior Developer") we have asked them to avoid accepting anyone they don't trust and do not belong to their team. Once we have managed membership requests as to be able to upload all deliverables marked as PP, we should establish a process to handle requests coming from other parties in the FI-PPP program. My understanding is that this should be handled by the "cooperation team" we established, i.e., you and Carlos, asking WPLs and WPAs to stay apart from that process. This looks all reasonable to us and apparently to other WPLs/WPAs but I'm still not sure whether it looks reasonable to SAP (maybe all this mess was due to a misunderstanding because someone may have interpreted that anyone with an account in FusionForge has access to all projects, which is false). If SAP still has objections on the formula above, it should come with some suggestions on what to do. And should come soon. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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: From jhierro at tid.es Wed Jul 11 07:57:19 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 11 Jul 2012 07:57:19 +0200 Subject: [Fiware-wpa] IMPORTANT: Topics for the 2nd Open Call to be proposed by FI-WARE Message-ID: <4FFD15BF.4030105@tid.es> Hi all, Just to make sure where the Epics linked to topics you wish to incorporate in the 2nd Open Call are available in the Materializing the FI-WARE Vision part of the wiki ... I can find the ones linked to the Cloud Proxy: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE#Cloud_Proxy_Software_Development_Kit Regarding Security, I understand that we are referring to the two following Epics: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Security.Security_Monitoring.Digital_forensics_for_evidence * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Security.Security_Monitoring.Business_Continuity_under_Attack I was expecting the description of the Security Epics a bit more concrete ... Note that they should provide enough detailed information as to make sure that submitters really make proposals along the lines of what we are expecting ... Do you think that such need would be covered with the provided descriptions ? Initially, unless changed during approval of the agenda (first thing this morning), the 2nd Open Call will be addressed tomorrow, from 09:30am until 11:15am ... this gives you a last change to incorporate further refinements. I would also like to check whether you would be available for joining the FI-PPP AB and elaborate on the topics if needed (we would have to find out how, depending on the facilities provided by the host of this meeting) Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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: From axel.fasse at sap.com Wed Jul 11 08:49:42 2012 From: axel.fasse at sap.com (Fasse, Axel) Date: Wed, 11 Jul 2012 08:49:42 +0200 Subject: [Fiware-wpa] ACTION POINT on SAP regarding safety of place where to submit deliverables marked as PP In-Reply-To: <4FFBFD19.6090801@tid.es> References: <4FFBFD19.6090801@tid.es> Message-ID: <2C6296E1876B5C49962495FDACDC7A63616674064F@DEWDFECCR01.wdf.sap.corp> Dear Juanjo, thank you for the presentation of the planned procedure model. In principle, we can agree to the suggested procedure. But actually I cannot imagine, on which basis the WPL's/WPA's will be able to decide, whether a person is a member within PPP or not. Because of this, I would suggest that you - as FI-WARE Coordinator - ask CONCORD to provide a complete list with all PPP partner-companies and the concrete project-members that are assigned to the PPP program by these companies. With this list, it would become very easy for the WPL's/WPA's to decide if it is allowed to grant access or not. If CONCORD is able to provide this list, we are completely fine with the procedure if the WPL's/WPA's use this list to decide if they are allowed to grant access or not. If you have any questions or further suggestions, please let me know. Best regards, Axel From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Dienstag, 10. Juli 2012 12:00 To: Fasse, Axel Cc: Miguel Carrillo; jhierro >> "Juan J. Hierro"; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: ACTION POINT on SAP regarding safety of place where to submit deliverables marked as PP Hi Axel, This is a reminder to you regarding SAP's position objecting to submit deliverables marked as PP. As we explained to you during the last joint WPLs/WPAs follow-up confcall, SAP has argued that the restricted access collaborative space we had setup to upload deliverables marked as PP didn't provide enough "trust". This collaborative space with restricted access is essentially a separate project in the family of FI-WARE related projects under FusionForge, named as "FI-WARE PPP Restricted". Visibility of content uploaded in this project is as follows: * Wiki is only accessible to members of the project (the "FI-WARE PPP Restricted" project in FusionForge). Here it is where partners are expected to provide guidelines accompanying software, unless in document formant in which case should be available in the SVN system * SVN (where software and accompanying documentation has been asked to be uploaded) is only accessible to members of the project * docman: this is as the docman in rest of projects, i.e., documents can be marked as private in which case they are accessible only to members of the project * rest of tools are not active In order to manage membership to the "FI-WARE PPP Restricted" project, we have tried to find out a trade-off between avoiding to become a bottleneck while keeping the process "in the hands of people we can trust". Therefore, we only add WPLs and WPAs initially to the project and we only assign Admin privileges to them, you, Miguel Carrillo and myself (we two, merely as backups). Admin users are the only ones that would then have the right to accept membership requests and assign a profile to new members (they should assign them a profile of "Senior Developer") we have asked them to avoid accepting anyone they don't trust and do not belong to their team. Once we have managed membership requests as to be able to upload all deliverables marked as PP, we should establish a process to handle requests coming from other parties in the FI-PPP program. My understanding is that this should be handled by the "cooperation team" we established, i.e., you and Carlos, asking WPLs and WPAs to stay apart from that process. This looks all reasonable to us and apparently to other WPLs/WPAs but I'm still not sure whether it looks reasonable to SAP (maybe all this mess was due to a misunderstanding because someone may have interpreted that anyone with an account in FusionForge has access to all projects, which is false). If SAP still has objections on the formula above, it should come with some suggestions on what to do. And should come soon. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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: From pascal.bisson at thalesgroup.com Wed Jul 11 09:34:11 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 11 Jul 2012 09:34:11 +0200 Subject: [Fiware-wpa] [Fiware-wpl] IMPORTANT: Topics for the 2nd Open Call to be proposed by FI-WARE In-Reply-To: <4FFD15BF.4030105@tid.es> References: <4FFD15BF.4030105@tid.es> Message-ID: <13334_1341992055_4FFD2C77_13334_6790_1_f315d5c4-7383-4719-9861-6c48e0dee3a9@THSONEA01HUB06P.one.grp> Dear Juanjo, At the level of the Security Chapter we have so far confirmed as candidate topics for the 2nd Open Call 4 EPICS: The two EPICS you are referring too and which are coming from T8.1: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Security.Security_Monitoring.Digital_forensics_for_evidence * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Security.Security_Monitoring.Business_Continuity_under_Attack [Regarding you remark: "I was expecting the description of the Security Epics a bit more concrete ... Note that they should provide enough detailed information as to make sure that submitters really make proposals along the lines of what we are expecting ... Do you think that such need would be covered with the provided descriptions ?" I must say Daniel is working on it with support of T8.1 team and would have far more elaborated text for the Open Call to make things crystal clear ... For the time being and evne if we can still enhance we thing it is enough to figure what we are looking for and where the innovation will be - @Daniel if you want to add please do so !) But also two EPICS coming from task T8.3 (that were communicated to you in a previous but that I see here in your email missing - so please add!) ? Epic 885 FIWARE.Epic.Security.Context-based security and compliance.Monitoring ? Epic 886 FIWARE.Epic.Security.Context-based security and compliance.Rules Last but not least please and apart from those topics please consider the topics the security chapter submitted for the 1st Open Call and which were postponed for the 2nd Open Call also valid topics. Hope I have clarified. Counting on you to have these Security EPICS be reported at your interaction with UC Projects. Best Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mercredi 11 juillet 2012 07:57 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] IMPORTANT: Topics for the 2nd Open Call to be proposed by FI-WARE Hi all, Just to make sure where the Epics linked to topics you wish to incorporate in the 2nd Open Call are available in the Materializing the FI-WARE Vision part of the wiki ... I can find the ones linked to the Cloud Proxy: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE#Cloud_Proxy_Software_Development_Kit Regarding Security, I understand that we are referring to the two following Epics: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Security.Security_Monitoring.Digital_forensics_for_evidence * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Security.Security_Monitoring.Business_Continuity_under_Attack I was expecting the description of the Security Epics a bit more concrete ... Note that they should provide enough detailed information as to make sure that submitters really make proposals along the lines of what we are expecting ... Do you think that such need would be covered with the provided descriptions ? Initially, unless changed during approval of the agenda (first thing this morning), the 2nd Open Call will be addressed tomorrow, from 09:30am until 11:15am ... this gives you a last change to incorporate further refinements. I would also like to check whether you would be available for joining the FI-PPP AB and elaborate on the topics if needed (we would have to find out how, depending on the facilities provided by the host of this meeting) Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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: From mcp at tid.es Thu Jul 12 10:01:09 2012 From: mcp at tid.es (Miguel Carrillo) Date: Thu, 12 Jul 2012 10:01:09 +0200 Subject: [Fiware-wpa] [Suspected Spam] Deliverables Message-ID: <4FFE8445.60602@tid.es> Dear all, As you are aware, I am checking out the status of the deliverables and pestering you in private with details. Take it as it is: a (boring) personal work to make sure that you get early feedback and avoid problems near the deadline. It could be also seen a help to stimulate the partners who are not contributing enough as you can forward my comments to them. One offer: those who have the deliverables 100% ready on the wiki before the 23rd (right before creating the pdf: cover ready + contents 100% ready) they can contact me if they want (completely optional) for a quick check and I would take a look to avoid rejections - re-generating the pdf file is always a bit annoying. Take it as a plus for the "early bird" :) 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: From jhierro at tid.es Mon Jul 16 08:44:09 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 16 Jul 2012 08:44:09 +0200 Subject: [Fiware-wpa] Reminder: Joint WPLs/WPAs follow-up confcall Message-ID: <5003B839.7070907@tid.es> Hi all, This is a reminder of our joint WPLs/WPAs follow-up confcall at 11:00am Previous to that, and using the same bridge facilities, we are celebrating the FI-WARE PCC. Therefore, to avoid any collision in the event that the PCC is longer than expected, we will let you know and will update the starting time. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 From jhierro at tid.es Mon Jul 16 10:16:58 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 16 Jul 2012 10:16:58 +0200 Subject: [Fiware-wpa] Joint WPLs/WPAs follow-up confcall Message-ID: <5003CDFA.7060704@tid.es> Hi all, The FI-WARE PCC meeting is taking more than expected, therefore for sure the joint WPLs/WPAs follow-up confcall will not start at 11:00am. Please keep tuned. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 From jhierro at tid.es Mon Jul 16 11:35:43 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 16 Jul 2012 11:35:43 +0200 Subject: [Fiware-wpa] Joint WPLs/WPAs follow-up confcall Message-ID: <5003E06F.7060808@tid.es> Hi all, We have just finished the PCC confcall. Let's have the joint WPLs/WPAs confcall at 12:00pm. Bridge details as always. We should try to keep it so that it ends by 13:00pm Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 From jhierro at tid.es Mon Jul 16 11:51:19 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 16 Jul 2012 11:51:19 +0200 Subject: [Fiware-wpa] Shared minutes for joint WPLs/WPAs follow-up confcall Message-ID: <5003E417.4060808@tid.es> Hi, Please find the shared draft minutes at: https://docs.google.com/document/d/1iTjesAxpfattBQjIAHFhV6RFkzI_fIxwuQ5-JX7sSYM/edit# Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 From jhierro at tid.es Tue Jul 17 06:44:54 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 17 Jul 2012 06:44:54 +0200 Subject: [Fiware-wpa] Communication of penalization measures to all partners in FI-WARE Message-ID: <5004EDC6.2020105@tid.es> Hi all, This is a reminder that one very important AP from our confcall yesterday was that you will communicate to the partners the measures that have been approved to manage delays from partners on deliverables linked to WP3-WP8 that we committed to deliver by end of June and September. However, it seems like some WPLs have not yet communicated this. We will send an email to the whole general FI-WARE consortia by EOB today confirming this "As your respective WPL should have already announced you". Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 From mcp at tid.es Tue Jul 17 12:25:21 2012 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 17 Jul 2012 12:25:21 +0200 Subject: [Fiware-wpa] Naming convention for enablers with more than one implementation In-Reply-To: <66E3B1FDDB04BE4D92DC3A2BA8D98D9AF1ED24@INTMAIL03.es.int.atosorigin.com> References: <50000061.3080803@tid.es> <66E3B1FDDB04BE4D92DC3A2BA8D98D9AB40F03@INTMAIL03.es.int.atosorigin.com> <500016B4.7040207@tid.es> <66E3B1FDDB04BE4D92DC3A2BA8D98D9AF1ED24@INTMAIL03.es.int.atosorigin.com> Message-ID: <50053D91.1060703@tid.es> Dear Torsten, dear Pascal, As regards those deliverables not following the naming convention now let us follow these rules: * Enablers with a single implementation. There is no reason to use an alternative name. The User & Prog. Manual, The Install. and Admin guide etc. must follow the convention expressed in the guidelines. * Enablers with more than one implementation: I understand that this is undefined as it is now. Let us proceed this way: * Under the section "Materializing ... " in the wiki we will have entries with the usual names: * - Unit Testing Plan * - Installation and Administration Guide * - User and Programmers Guide * Example: [cid:part1.00010008.00080500 at tid.es] * Then each one of these takes to a page with a list of all the manuals, one line per manual, and you can have something like this per line/manual. * - * Example: clicking on "Composition Editor - Unit Testing Plan" will take us to a page where the first line is: * Composition Editor - Light Semantic Composition Unit Testing Plan * there will be others in the future, one per implementation of the GE * each one of these lines will link to a dedicated page with the manual for that concrete implementation Hope this is clear and helps you to organize thing. Note that this is not added work, you do not need to do it in the private wiki if you do not want to, it can be done in 5 minutes as you take the contents to the public wiki. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: ecjdcije.png Type: image/png Size: 4332 bytes Desc: not available URL: From torsten.leidig at sap.com Tue Jul 17 12:58:06 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Tue, 17 Jul 2012 12:58:06 +0200 Subject: [Fiware-wpa] Naming convention for enablers with more than one implementation In-Reply-To: <50053D91.1060703@tid.es> References: <50000061.3080803@tid.es> <66E3B1FDDB04BE4D92DC3A2BA8D98D9AB40F03@INTMAIL03.es.int.atosorigin.com> <500016B4.7040207@tid.es> <66E3B1FDDB04BE4D92DC3A2BA8D98D9AF1ED24@INTMAIL03.es.int.atosorigin.com> <50053D91.1060703@tid.es> Message-ID: Fine with me. Thanks for clarification. Regards, Torsten From: Miguel Carrillo [mailto:mcp at tid.es] Sent: Dienstag, 17. Juli 2012 12:25 To: Leidig, Torsten; BISSON Pascal Cc: JUAN JOSE HIERRO SUREDA; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Naming convention for enablers with more than one implementation Dear Torsten, dear Pascal, As regards those deliverables not following the naming convention now let us follow these rules: * Enablers with a single implementation. There is no reason to use an alternative name. The User & Prog. Manual, The Install. and Admin guide etc. must follow the convention expressed in the guidelines. * Enablers with more than one implementation: I understand that this is undefined as it is now. Let us proceed this way: * Under the section "Materializing ... " in the wiki we will have entries with the usual names: * - Unit Testing Plan * - Installation and Administration Guide * - User and Programmers Guide * Example: [cid:image001.png at 01CD641B.CED48060] * Then each one of these takes to a page with a list of all the manuals, one line per manual, and you can have something like this per line/manual. * - * Example: clicking on "Composition Editor - Unit Testing Plan" will take us to a page where the first line is: * Composition Editor - Light Semantic Composition Unit Testing Plan * there will be others in the future, one per implementation of the GE * each one of these lines will link to a dedicated page with the manual for that concrete implementation Hope this is clear and helps you to organize thing. Note that this is not added work, you do not need to do it in the private wiki if you do not want to, it can be done in 5 minutes as you take the contents to the public wiki. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 4332 bytes Desc: image001.png URL: From jhierro at tid.es Wed Jul 18 07:54:34 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 18 Jul 2012 07:54:34 +0200 Subject: [Fiware-wpa] Clarification on task dealing with documentation of Features describing FI-WARE GEs Message-ID: <50064F9A.7070308@tid.es> Dear all, Let me clarify, at the risk of repeating myself a bit, some aspects about the task dealing with documentation of Features describing FI-WARE GEs. I believe that what I'm going to explain in this email has already been explained several times, at leas communicated to WPLs and WPAs, but I hope that repeating it again is not harmful and may be helpful. The target goal of the task is to end up with a set of "Features" for each FI-WARE GE that provides a complete description of the functionalities supported by that GE. When we created the first version of the backlogs linked to all FI-WARE GEs back in month 7, it was agreed that it was only necessary to include entries (Themes, Epics, Features, User Stories) linked to new functionalities that we were going to develop on top of selected baseline assets during the course of the FI-WARE project. This agreement was captured on the wiki page where we describe how we were planning to use Agile: In defining how we were going to use Agile in FI-WARE, we have had to deal with a fundamental characteristic of the project: it is not about developing from the scratch but from a set of selected products (assets) resulted from previous projects, many of which hadn't been developed using Agile. If we had started development of every FI-WARE Generic Enabler (that's the way we name components in FI-WARE) from the scratch, the FI-WARE GE backlogs would contain Themes/Epics/Features/User-stories that, all together, would summarize the whole functionality of FI-WARE. But this is not the case. When creating the backlog for a given FI-WARE GE, we have considered that it should contain the Themes/Epics/Features/User-stories that, at the start of the FI-WARE project, map to "functionality to be developed" in the reference implementation of the GE we are building based on a number of baseline products. We won't capture all the functionality that was already implemented in the baseline products. That would mean trying to carry out a kind of "reverse engineering" of baseline products, deriving User-Stories from what those baseline products already support. This, apart from meaning a huge effort would not be be that useful to development teams and would simply delay start of our development. This didn't prevent the development team behind a given FI-WARE GE to define the whole set of Features characterizing all the functionalities of a given FI-WARE GE, including functionality already supported by the selected baseline assets. We simply didn't force them to do so (it was not mandatory). However, apparently some of the teams did this at month 7. That's fine and this only means they don't need to add entries for Features now. Remember: the target goal now is to end up with a set of "Features" per FI-WARE GE that provides a complete description of the functionalities supported by the GE. Why are we doing this exercise if we had agreed that documenting Features already supported in baseline assets was not mandatory ? Essentially because we have had to deal with a comment made by reviewers on the Technical Roadmap deliverable that was the major cause why they rejected that deliverable: we were not giving enough details of what was going to be provided by each GE in each major release (including functionalities supported already by baseline assets in the case of the first major release). The decision was to handle this comment by means of completing the backlogs of FI-WARE GEs to add "Features" that describe the complete set of functionalities of the GE. Those teams that already identified the complete set of Features describing a FI-WARE GE back in month 7 would not need to do anything. On the other hand, this shouldn't be that difficult for the rest of the teams that didn't include features describing functionalities supported by baseline assets at that time. And we will solve the comment for sure (do you want to know what a given FI-WARE GE will give in the first major release ? just take a look a the following Features description). It's true that it would be something that overrides what we explained on the wiki about following Agile (the text copied above) but we will certainly fix that text on the wiki after the task is finished. Do we need to create entries in the trackers corresponding to added Features ? I would say it is not mandatory but certainly highly desirable and a goal to achieve not later than September (it would be a matter of one hour - two hours maximum once the Features are registered on the Wiki). When doing so, we agreed that teams should assign a value "FI-WARE.Release.0" to the "FI-WARE Release Id" field. Note that you don't need to derive any short of User Story from Features linked to functionality supported by baseline assets. User stories should map to Features that have been planned for development during the course of the FI-WARE project. How are we going to elaborate on what Features of a given GE are going to go for the first major release and what Features are going to go for later major releases within the revised version of the Technical Roadmap deliverable ? This is something that we have not closed yet but will be closed in the joint WPLs/WPAs follow-up confcall that will take place on July 23rd. For the time being, we prefer that you concentrate on all what is needed to meet the July 23rd deadline (maximum extension of the original deadline by end of June that we communicated to our POs regarding late delivery of deliverables linked to FI-WARE GEs). Are we going to distinguish between Features planned to be developed in the first Release and Features already supported by baseline assets within the Technical Roadmap deliverable ? I believe it is not needed. All of them together comprise the Features that describe what is going to be supported in the first major release and that is what really matters to a potential user of a given FI-WARE GE in the first major release: what is the set of features that the GE will support that they can use. Hope this helps, although I guess most of what is being explained was already understood by you. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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: From jhierro at tid.es Wed Jul 18 08:28:18 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 18 Jul 2012 08:28:18 +0200 Subject: [Fiware-wpa] Revision of Technical Roadmap deliverable Message-ID: <50065782.60809@tid.es> Hi all, We need to close how are going to re-structure the Technical Roadmap deliverable in order to re-submit it by end of July. This means we need to decide how links to Features on the Wiki will be established. We will provide concrete editorial guidelines but, prior to that, we would like to discuss with you on what approach to follow. Essentially we have two options: a) Create a table per section linked to each major release within the Technical Roadmap wiki page of each chapter, where we will list the Features supported for each GE in that major release (listing of the Features would be links to the corresponding Wiki pages). That table may look like the following one for the Data chapter (the example is only illustrative): FI-WARE GE Supported Features Publish/Subscribe Broker FIWARE.EPIC.Data.PublishSubscribe.UpdateOperation, FIWARE.EPIC.Data.PublishSubscribe.QueryLanguage, FIWARE.EPIC.Data.PublishSubscribe.Subsciprion&Notification, .... BigData Analysis FIWARE.Feature.Data.BigData-Analysis.MapReduceExtensions, FIWARE.Feature.Data.BigData-Analysis.Cluster, .... .... ... b) Create a table per section linked to each major release within the Technical Roadmap wiki page of each chapter, where we will provide a pointer to the "Features" section in the "Materializing the FI-WARE Vision" part of the wiki for each GE. Then structure that "Features" section of a given GE in the "Materializing the FI-WARE Vision" part of the wiki so that Features are classified into subsections corresponding to major releases. That table may look like the following one for the Data chapter (note that we would still need to create the subsections within the Features section linked here, each subsection matching a different major releases): FI-WARE GE Supported Features Publish/Subscribe Broker Publish/Subscribe Broker GE Features BigData Analysis BigData Analysis GE Features .... ... I would go for option a) but I would like to hear your opinions. Please cast your preference in the following doodle before this friday: http://www.doodle.com/vy97txn7n4qybucw Based on results on the poll we will generate guidelines that we will share with you during next joint WPLs/WPAs follow-up confcall. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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: From stefano.depanfilis at eng.it Tue Jul 17 22:58:21 2012 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Tue, 17 Jul 2012 22:58:21 +0200 Subject: [Fiware-wpa] Monitoring FI-WARE Tesbed V1 deployment Message-ID: dear all, the following days and weeks will be very hot for us and not only for the summer, but because we have to deploy the fi-ware testbed v1. as you know we foreseen two major deplyments: v1.1 on 31 july and v1.2 on 30 september. we, in particular henar (gracias!!!), already prepared some vm for some of the ge to be installed and the ge instance repsonsibles, also recepients in this email, have been emailed on how to go ahead. in the next coming days and weeks more vms, where necessary, will be ready in order to have all the ge instance for v1.1 to be installed. in this context what we need is: 1. ge instance responsibles and testbed team to fill the doodle with their holidays period so that we can better synchronise the activity http://www.doodle.com/8isz9atgcgdukiek 2. for ge instance responsibles, to fill the doodle telling when they will install their ge instance http://www.doodle.com/bymgm9h9gnbfms8k 3. for ge instance responsibles and wpl leaders/architects to declare if their ge instance is multi-tenant or not (you can do that by accessing the form of your ge instance from the implemantation cockpit page at https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Implementation_Cockpit#Testbed_V1_Cockpitand than following the link of the ge instance box). this info is of critical importance!!! in fact, if your ge instance is not multi tenant, or you suspect it not to be so for the version to be deployed in testbed v1, we have to prepare different vms one for each of the uc project interested .... as you can recognise all of the above is of great importance as we have to syncronise not only the work of the testbed deplyoment, but also the access of it from the uc projects which, in fact, are already asking access.....!!! for your convenience, please find attached the current testbed status. if you spot any error please let me know immediately please react promptly on all of the above! ciao, stefano -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Testbed_status_20120716.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 19874 bytes Desc: not available URL: From matteo.melideo at eng.it Wed Jul 18 10:07:39 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 18 Jul 2012 10:07:39 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Revision of Technical Roadmap deliverable In-Reply-To: <50065782.60809@tid.es> References: <50065782.60809@tid.es> Message-ID: <50066ECB.2040005@eng.it> Dear Juanjo, I also second option a), in fact in Tools Chapter we also decided to go with this approach. On the other hand, we decided to not describe the Features but stay with the User Stories that according to our personal feeling are sufficient for Wp9 scope. I hope this is good for you. Best regards Matteo Il 18/07/2012 08:28, Juanjo Hierro ha scritto: > Hi all, > > We need to close how are going to re-structure the Technical Roadmap > deliverable in order to re-submit it by end of July. > > This means we need to decide how links to Features on the Wiki will > be established. > > We will provide concrete editorial guidelines but, prior to that, we > would like to discuss with you on what approach to follow. > Essentially we have two options: > > a) Create a table per section linked to each major release within > the Technical Roadmap wiki page of each chapter, where we will list > the Features supported for each GE in that major release (listing of > the Features would be links to the corresponding Wiki pages). That > table may look like the following one for the Data chapter (the > example is only illustrative): > > > FI-WARE GE > Supported Features > Publish/Subscribe Broker > FIWARE.EPIC.Data.PublishSubscribe.UpdateOperation > , > FIWARE.EPIC.Data.PublishSubscribe.QueryLanguage > , > FIWARE.EPIC.Data.PublishSubscribe.Subsciprion&Notification > , > .... > BigData Analysis > FIWARE.Feature.Data.BigData-Analysis.MapReduceExtensions > , > FIWARE.Feature.Data.BigData-Analysis.Cluster > , > .... > .... > ... > > > b) Create a table per section linked to each major release within the > Technical Roadmap wiki page of each chapter, where we will provide a > pointer to the "Features" section in the "Materializing the FI-WARE > Vision" part of the wiki for each GE. Then structure that "Features" > section of a given GE in the "Materializing the FI-WARE Vision" part > of the wiki so that Features are classified into subsections > corresponding to major releases. That table may look like the > following one for the Data chapter (note that we would still need to > create the subsections within the Features section linked here, each > subsection matching a different major releases): > > FI-WARE GE > Supported Features > Publish/Subscribe Broker > Publish/Subscribe Broker GE Features > > BigData Analysis > BigData Analysis GE Features > > .... > ... > > > I would go for option a) but I would like to hear your opinions. > Please cast your preference in the following doodle before this friday: > > http://www.doodle.com/vy97txn7n4qybucw > > > Based on results on the poll we will generate guidelines that we > will share with you during next joint WPLs/WPAs follow-up confcall. > > Cheers, > > -- Juanjo > > > > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website:www.tid.es > email:jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Chief Architect > > You can follow FI-WARE at: > 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 > > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From stefano.depanfilis at eng.it Wed Jul 18 18:11:09 2012 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Wed, 18 Jul 2012 18:11:09 +0200 Subject: [Fiware-wpa] Monitoring FI-WARE Tesbed V1 deployment In-Reply-To: References: Message-ID: dear all, for the avoidance of misunderstaing please fill the doodle poll as follows:1. > ge instance responsibles and testbed team to fill the doodle with their > holidays period so that we can better synchronise the activity > http://www.doodle.com/8isz9atgcgdukiek > put "yes" when you are avilable and "no" when you are in holidays. "may be" can be used if you do not know yet, or if you are partially available that week. > > 2. > for ge instance responsibles, to fill the doodle telling when they will > install their ge instance > http://www.doodle.com/bymgm9h9gnbfms8k > put "yes" when you plan to install your ge. please can you check you filled according the above? ciao, stefano -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed Jul 18 19:55:25 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 18 Jul 2012 19:55:25 +0200 Subject: [Fiware-wpa] Fwd: RE: Open Call: next steps and possible objections to prospective winners - Individual Evaluation Reports In-Reply-To: <69AD1A9684E7184DADBE43806285BA9D078231@S-DC-ESTF03-B.net1.cec.eu.int> References: <69AD1A9684E7184DADBE43806285BA9D078231@S-DC-ESTF03-B.net1.cec.eu.int> Message-ID: <5006F88D.8090103@tid.es> Hi all, Our PO, Arian Zwegers, has finally approved the results of the 1st Open Call ... We will send the Evalution Summary Reports tomorrow to all submitters and will contact the selected consortia for each of the topics (BM&BE and middleware) Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 -------- Original Message -------- Subject: RE: Open Call: next steps and possible objections to prospective winners - Individual Evaluation Reports Date: Wed, 18 Jul 2012 16:49:00 +0000 From: To: , CC: , , Dear Juanjo, Thanks for the responses, which fully answered the open points. I hereby approve the report on the first FI-WARE Open Call. One more thing: I need to have signed versions of the Individual Evaluation Report. Please send me the signed versions (no hurry). Best regards, Arian From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Wednesday, July 18, 2012 11:03 AM To: MARIA ISABEL ALONSO MEDIAVILLA Cc: ZWEGERS Arian (CNECT); MIGUEL CARRILLO PACHECO; subsidies at tid.es; jhierro >> "Juan J. Hierro" Subject: Re: Open Call: next steps and possible objections to prospective winners - Individual Evaluation Reports Dear Arian, Please let us know if our responses to your questions are satisfactory. If so, please confirm this to us so that we can start sending the Summary Evaluation Reports to all submitters and we can start negotiations with the selected partners. Looking forward your confirmation. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 On 18/07/12 10:43, MARIA ISABEL ALONSO MEDIAVILLA wrote: Dear Arian, As requested, I am sending you on behalf of Juanjo, the Individual Evaluation Reports for the eligible proposals for each topic. If you need further information, please let us know. Best wishes Isabel [Descripci?n: firma correo_iam] ________________________________ 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 ________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 8796 bytes Desc: not available URL: From lorant.farkas at nsn.com Fri Jul 20 14:43:48 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Fri, 20 Jul 2012 15:43:48 +0300 Subject: [Fiware-wpa] FW: deliverables for GE-s running as a service Message-ID: <93D28BDF64839C468B848D14227151A203BB62CB@FIESEXC014.nsn-intra.net> _____________________________________________ From: Farkas, Lorant (NSN - HU/Budapest) Sent: Friday, July 20, 2012 2:08 PM To: fiware-wpl at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Cc: Seidl, Robert (NSN - DE/Munich) Subject: deliverables for GE-s running as a service Dear All, Recently there have been discussions around the need for providing binaries constituting background in case of FI-WARE. Several partners raised concerns about that. The issue is burning, because in the current situation unless the partner contributes the binary of the background by the 23rd of July, 40% of the PM-s are lost. Let me share NSN's view on this. 1. According to the FI-WARE contract special clause 41 (article 7.3) "other beneficiaries" (meaning FI-PPP partners excluding FI-WARE ones) rights and obligations are limited to foreground and do not extend to background. Translated: they should not have access to background. To comply to this clause with the tool called "fi-ware restricted" 1.1 either there would be no reason for exposing it to all FI-PPP consortium, but just FI-WARE and the commission 1.2 or there would be no reason for asking partners to upload binaries related to background 2. According to Annex 2 of the FI-WARE contract beneficiaries may define the background needed for the purposes of the project in a written agreement and, where appropriate, may agree to exclude specific background. All requests for access rights shall be made in writing. The granting of access rights may be made conditional on the acceptance of specific conditions aimed at ensuring that these rights will be used only for the intended purpose and that appropriate confidentiality obligations are in place. So when you expose background through "forge fi-ware restricted", even restricted to the FI-WARE partners, you take the possibility away from partners to impose such conditions. This would breach the contract. 3. According to Annex 2 of the FI-WARE contract access rights to background shall be granted to the other beneficiaries, if it is needed to enable those beneficiaries to carry out their own work under the project provided that the beneficiary concerned is entitled to grant them. Example: from our side for the NSN IDM solution there is no such need, because it is available as a service. 4. On the other hand beneficiaries shall provide all detailed data requested by the Commission for the purposes of the proper administration of this project. Our interpretation is that there might be a request from the Commission to take a look at binaries of background. The technical means for that would be to establish sharing space only for the Commission's representatives, not the entire FI-WARE/FI-PPP consortium. As a result, NSN rightfully believes there is no reason for any partner offering a GE as a service to provide binaries in "fi-ware restricted". Therefore also the content of the contributions to D8.x would be different for partners providing their assets as a service or as SW (e.g. unit testing plan, installation guide, etc.). Thanks & Br, L?r?nt Farkas Senior Research Engineer H-1092 Budapest, Hungary K?ztelek u.6. Tel: +36 20 977 7797 Mob: +36 20 936 9002 lorant.farkas at nsn.com http://www.nokiasiemensnetworks.com/global/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Fri Jul 20 15:20:57 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 20 Jul 2012 15:20:57 +0200 Subject: [Fiware-wpa] [Fiware-wpl] deliverables for GE-s running as a service In-Reply-To: <50095615.2050901@tid.es> References: <93D28BDF64839C468B848D14227151A203BB62A4@FIESEXC014.nsn-intra.net> <50095615.2050901@tid.es> Message-ID: <19867_1342790459_50095B3B_19867_12227_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D36000CB@THSONEA01CMS04P.one.grp> Dear Juanjo, Ok but here you forgot one important point which is that the way GEs are released as a service versus as software package also impacts the content of the User guide, Install guide, Unit test plan & reporting. That's also why I was asking in one of my previous emails for different instructions/guidelines to be provided for each of the two cases. Hope you can share and agree. BR Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : vendredi 20 juillet 2012 14:59 ? : fiware-wpl at lists.fi-ware.eu Objet : Re: [Fiware-wpl] deliverables for GE-s running as a service Hi all, Regarding software that will be provided on the FI-WARE Testbed as a Service, we will extend the deadline for delivery of binaries until we get the response from our PO regarding how he believes that delivery of the software can be confirmed. That extension doesn't apply neither to software that needs to be installed on the FI-WARE Testbed nor to software that will be provided for installation at UC projects' premises/facilities/equipments (e.g., Cloud Proxy). With respect to distinction between background and foreground, I will respond in a separate mail. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 On 20/07/12 14:07, Farkas, Lorant (NSN - HU/Budapest) wrote: Dear All, Recently there have been discussions around the need for providing binaries constituting background in case of FI-WARE. Several partners raised concerns about that. The issue is burning, because in the current situation unless the partner contributes the binary of the background by the 23rd of July, 40% of the PM-s are lost. Let me share NSN's view on this. 1. According to the FI-WARE contract special clause 41 (article 7.3) "other beneficiaries" (meaning FI-PPP partners excluding FI-WARE ones) rights and obligations are limited to foreground and do not extend to background. Translated: they should not have access to background. To comply to this clause with the tool called "fi-ware restricted" 1.1 either there would be no reason for exposing it to all FI-PPP consortium, but just FI-WARE and the commission 1.2 or there would be no reason for asking partners to upload binaries related to background 2. According to Annex 2 of the FI-WARE contract beneficiaries may define the background needed for the purposes of the project in a written agreement and, where appropriate, may agree to exclude specific background. All requests for access rights shall be made in writing. The granting of access rights may be made conditional on the acceptance of specific conditions aimed at ensuring that these rights will be used only for the intended purpose and that appropriate confidentiality obligations are in place. So when you expose background through "forge fi-ware restricted", even restricted to the FI-WARE partners, you take the possibility away from partners to impose such conditions. This would breach the contract. 3. According to Annex 2 of the FI-WARE contract access rights to background shall be granted to the other beneficiaries, if it is needed to enable those beneficiaries to carry out their own work under the project provided that the beneficiary concerned is entitled to grant them. Example: from our side for the NSN IDM solution there is no such need, because it is available as a service. 4. On the other hand beneficiaries shall provide all detailed data requested by the Commission for the purposes of the proper administration of this project. Our interpretation is that there might be a request from the Commission to take a look at binaries of background. The technical means for that would be to establish sharing space only for the Commission's representatives, not the entire FI-WARE/FI-PPP consortium. As a result, NSN rightfully believes there is no reason for any partner offering a GE as a service to provide binaries in "fi-ware restricted". Therefore also the content of the contributions to D8.x would be different for partners providing their assets as a service or as SW (e.g. unit testing plan, installation guide, etc.). Thanks & Br, L?r?nt Farkas Senior Research Engineer H-1092 Budapest, Hungary K?ztelek u.6. Tel: +36 20 977 7797 Mob: +36 20 936 9002 lorant.farkas at nsn.com http://www.nokiasiemensnetworks.com/global/ _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl ________________________________ 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: From jhierro at tid.es Fri Jul 20 15:44:12 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 20 Jul 2012 15:44:12 +0200 Subject: [Fiware-wpa] [Fiware-wpl] deliverables for GE-s running as a service In-Reply-To: <19867_1342790459_50095B3B_19867_12227_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D36000CB@THSONEA01CMS04P.one.grp> References: <93D28BDF64839C468B848D14227151A203BB62A4@FIESEXC014.nsn-intra.net> <50095615.2050901@tid.es> <19867_1342790459_50095B3B_19867_12227_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D36000CB@THSONEA01CMS04P.one.grp> Message-ID: <500960AC.8090909@tid.es> Dear Pascal, SAME instructions/guidelines do apply to both Users' & Programmers' Guides and the Unit Test Plans and Report: * Users' & Programmers' Guides should guide developers in how to configure or program applications using the services provided by the GE. As I have explained multiple times, they should not be just a repetition of the GE's API specifications but some sort of "Hello World" example. And the way these Users' and Programmers' Guides would not vary because a GE instance is hosted in the FI-WARE Testbed dedicated datacenter facility or any other remote location. * The Unit Testing Plan should document "how-to-test" the different features of an GE instance, no matter where it is hosted. The report, of course, is relevant to a particular instance of the GE: the one against which you passed the tests of the Unit Testing Plan. In this respect, we are asking you to report on the execution of the Testing Plan against the instance of the GE you have used for Unit Testing purposes. In the case of GEs provided as a service, we would highly recommend that you run the Unit Testing Plan against the instance of the GE that will be provided as a service. In the case of GEs that will be hosted in the FI-WARE dedicated datacenter or in facilities owned by UC projects, we assume that you have run the Unit Testing Plan against an instance of the GE in your own lab. Of course, one thing you should be prepared for, is that someone from WP10 decides to run the Unit Testing Plan against the instance of a GE that has been deployed in the FI-WARE Testbed dedicated datacenter facility or remotely. That would lead to a report different from the one we are asking you now to provide. Such a second report, may be used as a sanity check and, eventually, to reject the deliverable in the case that the software doesn't pass a significant number of Tests in the Unit Testing Plan, provided that the Unit Testing Plan has been run properly. Amendment to my previous mail: the deadline extension regaring binaries of GEs that were agreed that would be provided as a service hosted remotely also applies to the Installation & Admin Guides of those GEs. Hope it helps, -- Juanjo On 20/07/12 15:20, BISSON Pascal wrote: Dear Juanjo, Ok but here you forgot one important point which is that the way GEs are released as a service versus as software package also impacts the content of the User guide, Install guide, Unit test plan & reporting. That's also why I was asking in one of my previous emails for different instructions/guidelines to be provided for each of the two cases. Hope you can share and agree. BR Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : vendredi 20 juillet 2012 14:59 ? : fiware-wpl at lists.fi-ware.eu Objet : Re: [Fiware-wpl] deliverables for GE-s running as a service Hi all, Regarding software that will be provided on the FI-WARE Testbed as a Service, we will extend the deadline for delivery of binaries until we get the response from our PO regarding how he believes that delivery of the software can be confirmed. That extension doesn't apply neither to software that needs to be installed on the FI-WARE Testbed nor to software that will be provided for installation at UC projects' premises/facilities/equipments (e.g., Cloud Proxy). With respect to distinction between background and foreground, I will respond in a separate mail. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 On 20/07/12 14:07, Farkas, Lorant (NSN - HU/Budapest) wrote: Dear All, Recently there have been discussions around the need for providing binaries constituting background in case of FI-WARE. Several partners raised concerns about that. The issue is burning, because in the current situation unless the partner contributes the binary of the background by the 23rd of July, 40% of the PM-s are lost. Let me share NSN's view on this. 1. According to the FI-WARE contract special clause 41 (article 7.3) "other beneficiaries" (meaning FI-PPP partners excluding FI-WARE ones) rights and obligations are limited to foreground and do not extend to background. Translated: they should not have access to background. To comply to this clause with the tool called "fi-ware restricted" 1.1 either there would be no reason for exposing it to all FI-PPP consortium, but just FI-WARE and the commission 1.2 or there would be no reason for asking partners to upload binaries related to background 2. According to Annex 2 of the FI-WARE contract beneficiaries may define the background needed for the purposes of the project in a written agreement and, where appropriate, may agree to exclude specific background. All requests for access rights shall be made in writing. The granting of access rights may be made conditional on the acceptance of specific conditions aimed at ensuring that these rights will be used only for the intended purpose and that appropriate confidentiality obligations are in place. So when you expose background through "forge fi-ware restricted", even restricted to the FI-WARE partners, you take the possibility away from partners to impose such conditions. This would breach the contract. 3. According to Annex 2 of the FI-WARE contract access rights to background shall be granted to the other beneficiaries, if it is needed to enable those beneficiaries to carry out their own work under the project provided that the beneficiary concerned is entitled to grant them. Example: from our side for the NSN IDM solution there is no such need, because it is available as a service. 4. On the other hand beneficiaries shall provide all detailed data requested by the Commission for the purposes of the proper administration of this project. Our interpretation is that there might be a request from the Commission to take a look at binaries of background. The technical means for that would be to establish sharing space only for the Commission's representatives, not the entire FI-WARE/FI-PPP consortium. As a result, NSN rightfully believes there is no reason for any partner offering a GE as a service to provide binaries in "fi-ware restricted". Therefore also the content of the contributions to D8.x would be different for partners providing their assets as a service or as SW (e.g. unit testing plan, installation guide, etc.). Thanks & Br, L?r?nt Farkas Senior Research Engineer H-1092 Budapest, Hungary K?ztelek u.6. Tel: +36 20 977 7797 Mob: +36 20 936 9002 lorant.farkas at nsn.com http://www.nokiasiemensnetworks.com/global/ _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl ________________________________ 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 ________________________________ 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: From jhierro at tid.es Fri Jul 20 15:59:33 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 20 Jul 2012 15:59:33 +0200 Subject: [Fiware-wpa] FI-WARE GEs as a Service Message-ID: <50096445.6040601@tid.es> Hi all, Please note that which GEs where going to be provided "as a Service" was a matter of discussion long time ago and nothing that a given partner may change or decide when they want. We only accepted the provision of a very limited set of GEs as a Service and only for the first release, still pending of discussion for later releases. This cannot be changed without prior discussion and agreement. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 From juan.bareno at atosresearch.eu Mon Jul 23 09:48:18 2012 From: juan.bareno at atosresearch.eu (=?iso-8859-1?Q?Juan_Bare=F1o_Guerenabarrena?=) Date: Mon, 23 Jul 2012 09:48:18 +0200 Subject: [Fiware-wpa] FW: NEC Commitments for MONTH-15 FI-WARE D11.4 Deliverable and requests confirmation //email 1 of 2// In-Reply-To: <8152E2132B13FB488CFD1947E2DEF19C32E39458@PALLENE.office.hd> References: <58967817BA9AEA4E92A38F89CE2EA93224D1C428@PALLENE.office.hd> <8152E2132B13FB488CFD1947E2DEF19C32E39458@PALLENE.office.hd> Message-ID: Dear WPLs Please check the status of standardization deliverable by WP, July is closing, and fullfill the missing information ASAP and according to the concrete guideliness provided in the mail below Thanks for your contribution Juan From: Ernoe Kovacs [mailto:Ernoe.Kovacs at neclab.eu] Sent: lunes, 23 de julio de 2012 9:31 To: Juan Bare?o Guerenabarrena; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: jhierro at tid.es; mcp at tid.es; Nuria De-Lama Sanchez; Carmen Perea Escribano; Lindsay Frost Subject: RE: NEC Commitments for MONTH-15 FI-WARE D11.4 Deliverable and requests confirmation //email 1 of 2// Dear Juan, Juanjo, all, July is rapidly closing and we need to get done with the D11.4b "Standardization Plan v2". I did a rough check on the status of the table we needed to fill in. Just whether content is there and a quick sanity check. No detailed analysis yet. Thanks to all who already inserted material. Please find below the summary status and concrete missing aspects. Summary: (a) All please fill in all tables 7a, 7b, 7c. Too many are still missing. Please do not merge them as they will be used for different purposes in the final deliverable. (b) Please also look at the second action plan for answering to the review comments. Some partners need to do stuff here. Note: There are concrete actions to be done with respect to unclarity in the original standard plan. Please work on them. If already clarified in the new tables, drop us a note. (c) Overall, there is some progress on the issues, but the main critic point "A coherent strategy" is not yet really materializing Please discuss progress and actions in the WPL phone calls... - Ern? & Lindsay Progress Standardization Plan Date: 2012/07/23 [Action 7a] Mapping of FI-Ware interfaces/protocols to Target SDO Where documented: https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Standardization_Plan_v2 Short Analysis of Status (a) Cloud Hosting Table 7a (IF to SDO) is existing and seems to reasonable content. Thank you. Table 7b (partner responsibility) & 7c (Timeline) are commented out. Please add again. There are clear indications that FI-Ware partners are in the position and can influence respective bodies. We might get criticism that it is not clear how we can use that potential. Please try to - identify more concrete steps - already established transfers As said, it would be good to be a step more concrete (b) Data Context Management Not there yet (c) Internet of Things Table 7a: Interface to SDO table existing and looking good. Same comment as for Cloud: If possible somehow strengthen the aspect that we actually do action. IMHO, for ETSI M2M we can do that. 7b & 7C only started (d) Applications Services Ecosystem 7a existing, might need some more details. Contributions from other partners need to be entered. (e) Security Table for 7a, 7b, 7c filled in. Thank you. Some entries missing, but it is coming into shape. (f) I2ND Table 7a existing, looking good, some concrete actions. Thank you. 7b and 7c not filled in yet. From: Juan Bare?o Guerenabarrena [mailto:juan.bareno at atosresearch.eu] Sent: Donnerstag, 5. Juli 2012 15:49 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: jhierro at tid.es; mcp at tid.es; nuria.delama at atosresearch.eu; carmen.perea at atosresearch.eu; Ernoe Kovacs; Lindsay Frost Subject: FW: NEC Commitments for MONTH-15 FI-WARE D11.4 Deliverable and requests confirmation //email 1 of 2// Importance: High Dear WPLs Please find below the detailed plan for complete the standardization deliverable for M15, end of this month Please react to what NEC, task leader, ask from you: - Identify a responsible partner per WP - Provide the inputs required in the wiki - Review content and format requirements For any doubt please contact Lindsay/Ernoe, in cc Thanks for your contribution Juan From: Lindsay Frost [mailto:Lindsay.Frost at neclab.eu] Sent: jueves, 05 de julio de 2012 15:12 To: Juan Bare?o Guerenabarrena; Miguel Carrillo; Nuria De-Lama Sanchez; Carmen Perea Escribano; lorant.farkas at nsn.com; thierry.nagellen at orange.com Cc: Ernoe Kovacs Subject: NEC Commitments for MONTH-15 FI-WARE D11.4 Deliverable and requests confirmation //email 1 of 2// Importance: High Dear FI-WARE management team, Please distribute this email on PCC; fiware-wpl at lists.fi-ware.eu; and fiware-wpa at lists.fi-ware.eu We refer to information provided to NEC in a teleconference on 02.07 by FI-WARE management regarding providing in the next 3 weeks a new Standardization Plan. NEC protests at the way the management decision was reached and communicated. The decision took no account of NEC proposals which were sent 23.05.2012 and for which responses were twice requested. The decision now requires NEC to make a burst of effort in the next 3 weeks to immediately create a new Standardization Plan, without considering NEC staff availability. Furthermore, the needed strategic inputs are not in the hands of NEC to create. Nevertheless, NEC has created a new fast-track plan with some chance of success, assuming continuous and strong input from partners. Endorsement, help and support from FI-Ware management and PCC is strongly requested. Depending on the inputs from FI-WARE partners and the later review of the EC, NEC will reconsider its' future participation in this part of WP11. Outline of Plan (detailed plan below): ? FI-WARE WPLs identify which Generic Enabler interfaces are important and therefore crucial for standardization. It is essential that a FI-WARE software architect complete such a list/diagram immediately to focus the work. ? FI-WARE WPLs nominate responsible partners and _persons_ who will input the plan and status for standardization at _specific_ SDOs, for _each_ of those important interfaces (a subset of all interfaces) ? The nominated responsible persons input their plan into the private Wiki as described below, and update the Wiki FI-WARE Standardization v2 (private wiki) with (their) past contributions as well as planned future ones. FI-WARE management team has promised weekly oversight of this activity. ? NEC summarizes results in last week of July, creating D11.4b pdf from the Wiki NEC requests confirmation of this plan, which is detailed below. Yours sincerely, Dr. Lindsay Frost, Dr. Ernoe Kovacs ATTACHMENTs (1) Old, still valid Action Plan to react to EC comments (file 2012-05-23-ActionPlan.txt) (2) Detailed Plan for D11.4.b by End July (see below) Attachment 2: The following is the step-by-step plan: (D) NEC Conclusions for Standardization Plan content and format 6. General content required (to be generated by FI-WARE partners) a. identify what standardization makes sense for FI-WARE (targets), taking account of specific gaps which the EC requested fixed b. identify where to do it (selected SDOs) /note: should reference "Section 2 CONTRIBUTE" actions in D11.4a/ c. explain (if it is planned) where IP generated in FI-WARE is inserted into SDOs specifications d. for each selected SDO and FI-WARE target, show the timeline of how to achieve the target, with "concrete steps" and partners, starting work "even before usable results" as requested by EC e. show how ongoing actual contributions to SDOs fulfill the "concrete steps" (i.e. ongoing status) 7. Step by step Format a. WPLs create a webpage mapping important FI-WARE interfaces/protocols to the Target SDO which could be responsible. It should also indicate any IPR which FI-WARE may bring in. This webpage would satisfy (D)6.a and (D)6.b and (D)6.c above. In the opinion of NEC, standardization is most valuable for the exposed interfaces, and in a secondary way to efficiently design the internal interfaces. Therefore all exposed interfaces are important, and some internal ones. As an example of some important interfaces, the (old) picture https://forge.fi-ware.eu/plugins/mediawiki/wiki/iot/index.php/Snapshot_2012.06.01_of_Deliverable_Page_for_D2.3_Architecture_Specifications could be used. b. WPLs create a webpage showing which partner is responsible for each important interface and their responsible person to make it standardized. The format can be a table ("Target SDO / Responsible Persons") with entries . c. Responsible persons add to FI-WARE Standardization v2 (private wiki) page, for each Target SDO, a timeline based on the SDO meeting schedules and methods, which is designed to get the exposed interface standardized. A partial example is given for ETSI M2M. This satisfies (D)6.d. This can only be created by the responsible persons who also ensure that that Target SDO work happens. It should indicate the phases as e.g. (1) feasibility-study (2) architecture (3) datamodels and protocols. The format can be a table ("Target SDO / Contributions Table ") ordered by date, so later it is easier for the information to be integrated into a complete project plan, e.g. d. The responsible person updates the Target SDO / Contributions Table every week, with new planned inputs and new results. Care should be taken to note any IPR. This satisfies (D)6.e. e. NEC creates an integrated timetable showing the aggregated copies of all tables from step (c) above, which is the overview for the EC. NEC will combine it with (a) and (b) - assuming all partners have strongly contributed - so as to resolve all EC requests. f. Optionally partners can extend the information in (c) above, to include highly relevant non-FI-WARE results which are monitored (M). Also partners can include relevant work they do which however is not part of the agreed important interface work. Monitoring standards is also part of the standardization plan and this work should be reported to the EC, as long as it is shown as supporting a significant amount of active contributions work. NEC rejects proposals to use Googledocs because NEC was required to change from doc to Wiki during the previous phase of the project and the good reasons for doing that still hold. ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: 2012-07-23-FI-Ware-StandardisationPlan Check.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: 2012-05-23-ActionPlan.txt URL: From mcp at tid.es Mon Jul 23 09:51:15 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 23 Jul 2012 09:51:15 +0200 Subject: [Fiware-wpa] Draft minutes of meeting for the WPL/WPA follow up confcall Message-ID: <500D0273.7050707@tid.es> Dear all, These are the draft minutes. May I suggest a brief reading prior to the call at 11. * https://docs.google.com/document/d/1e1wzsOolpqhVGc6e6DmhU9ek9Ru9gJIMAF4YuLo7AMs/edit?pli=1# 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: From jhierro at tid.es Mon Jul 23 10:37:14 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 23 Jul 2012 10:37:14 +0200 Subject: [Fiware-wpa] Status regarding issues about how to make software binaries and Installation/Administration Guides marked as PP available Message-ID: <500D0D3A.5070008@tid.es> Here, Just a brief update regarding status of the analysis of some of the issues raised regarding access to software (binaries) and Installation/Administration Guides marked as PP. My current view on the matter is as follows: * Relying on certain clauses of the Collaboration Agreement, access to binaries and Installation/Administration Guides should be granted royalty-free to FI-PPP members when ALL the following requirements are met: * they request it in writing * they require it for execution of their respective projects within the FI-PPP * they can explain that using it "as a Service" through a well defined API (from the FI-WARE Testbed or any other hosting facility) is not enough * Notwithstanding the previous point, we shall provide access to binaries and Installation/Administration Guides to the EC (and reviewers) for auditing/reviewing purposes. Here, it is not clear whether it is enough to provide access to the facilities where GEs offered "as a Service" are hosted. It will depend very much on EC's willingness. This is just my view. As already mentioned, the issues have been shared with our PO and we are waiting for his response. Note that if my view is correct, the binaries and Installation Guides of most of the software linked to FI-WARE GEs would not need to become accessible to UC projects in the first phase (except maybe the one linked to the Cloud Proxy or any FI-WARE GE that runs on local infrastructures linked to the Proof of Concepts). However, a different story may apply to UC trials or SME experiments in phase 2 and 3, where I can foreseen that the above mentioned requirements could be met. Based on this, and until the EC provides an answer: * We will keep access to the "FI-WARE PPP Restricted" project only limited to FI-WARE partners * Owners of GEs that we had agreed could be offered "as a Service" hosted in facilities different than the FI-WARE Testbed will not be requested to upload their binaries and Installation/Administration Guides until the EC provides an official answer about where binaries and Installation/Administration Guides can be delivered in their particular case. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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: From Ernoe.Kovacs at neclab.eu Mon Jul 23 09:30:40 2012 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Mon, 23 Jul 2012 07:30:40 +0000 Subject: [Fiware-wpa] NEC Commitments for MONTH-15 FI-WARE D11.4 Deliverable and requests confirmation //email 1 of 2// In-Reply-To: References: <58967817BA9AEA4E92A38F89CE2EA93224D1C428@PALLENE.office.hd> Message-ID: <8152E2132B13FB488CFD1947E2DEF19C32E39458@PALLENE.office.hd> Dear Juan, Juanjo, all, July is rapidly closing and we need to get done with the D11.4b "Standardization Plan v2". I did a rough check on the status of the table we needed to fill in. Just whether content is there and a quick sanity check. No detailed analysis yet. Thanks to all who already inserted material. Please find below the summary status and concrete missing aspects. Summary: (a) All please fill in all tables 7a, 7b, 7c. Too many are still missing. Please do not merge them as they will be used for different purposes in the final deliverable. (b) Please also look at the second action plan for answering to the review comments. Some partners need to do stuff here. Note: There are concrete actions to be done with respect to unclarity in the original standard plan. Please work on them. If already clarified in the new tables, drop us a note. (c) Overall, there is some progress on the issues, but the main critic point "A coherent strategy" is not yet really materializing Please discuss progress and actions in the WPL phone calls... - Ern? & Lindsay Progress Standardization Plan Date: 2012/07/23 [Action 7a] Mapping of FI-Ware interfaces/protocols to Target SDO Where documented: https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Standardization_Plan_v2 Short Analysis of Status (a) Cloud Hosting Table 7a (IF to SDO) is existing and seems to reasonable content. Thank you. Table 7b (partner responsibility) & 7c (Timeline) are commented out. Please add again. There are clear indications that FI-Ware partners are in the position and can influence respective bodies. We might get criticism that it is not clear how we can use that potential. Please try to - identify more concrete steps - already established transfers As said, it would be good to be a step more concrete (b) Data Context Management Not there yet (c) Internet of Things Table 7a: Interface to SDO table existing and looking good. Same comment as for Cloud: If possible somehow strengthen the aspect that we actually do action. IMHO, for ETSI M2M we can do that. 7b & 7C only started (d) Applications Services Ecosystem 7a existing, might need some more details. Contributions from other partners need to be entered. (e) Security Table for 7a, 7b, 7c filled in. Thank you. Some entries missing, but it is coming into shape. (f) I2ND Table 7a existing, looking good, some concrete actions. Thank you. 7b and 7c not filled in yet. From: Juan Bare?o Guerenabarrena [mailto:juan.bareno at atosresearch.eu] Sent: Donnerstag, 5. Juli 2012 15:49 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: jhierro at tid.es; mcp at tid.es; nuria.delama at atosresearch.eu; carmen.perea at atosresearch.eu; Ernoe Kovacs; Lindsay Frost Subject: FW: NEC Commitments for MONTH-15 FI-WARE D11.4 Deliverable and requests confirmation //email 1 of 2// Importance: High Dear WPLs Please find below the detailed plan for complete the standardization deliverable for M15, end of this month Please react to what NEC, task leader, ask from you: - Identify a responsible partner per WP - Provide the inputs required in the wiki - Review content and format requirements For any doubt please contact Lindsay/Ernoe, in cc Thanks for your contribution Juan From: Lindsay Frost [mailto:Lindsay.Frost at neclab.eu] Sent: jueves, 05 de julio de 2012 15:12 To: Juan Bare?o Guerenabarrena; Miguel Carrillo; Nuria De-Lama Sanchez; Carmen Perea Escribano; lorant.farkas at nsn.com; thierry.nagellen at orange.com Cc: Ernoe Kovacs Subject: NEC Commitments for MONTH-15 FI-WARE D11.4 Deliverable and requests confirmation //email 1 of 2// Importance: High Dear FI-WARE management team, Please distribute this email on PCC; fiware-wpl at lists.fi-ware.eu; and fiware-wpa at lists.fi-ware.eu We refer to information provided to NEC in a teleconference on 02.07 by FI-WARE management regarding providing in the next 3 weeks a new Standardization Plan. NEC protests at the way the management decision was reached and communicated. The decision took no account of NEC proposals which were sent 23.05.2012 and for which responses were twice requested. The decision now requires NEC to make a burst of effort in the next 3 weeks to immediately create a new Standardization Plan, without considering NEC staff availability. Furthermore, the needed strategic inputs are not in the hands of NEC to create. Nevertheless, NEC has created a new fast-track plan with some chance of success, assuming continuous and strong input from partners. Endorsement, help and support from FI-Ware management and PCC is strongly requested. Depending on the inputs from FI-WARE partners and the later review of the EC, NEC will reconsider its' future participation in this part of WP11. Outline of Plan (detailed plan below): ? FI-WARE WPLs identify which Generic Enabler interfaces are important and therefore crucial for standardization. It is essential that a FI-WARE software architect complete such a list/diagram immediately to focus the work. ? FI-WARE WPLs nominate responsible partners and _persons_ who will input the plan and status for standardization at _specific_ SDOs, for _each_ of those important interfaces (a subset of all interfaces) ? The nominated responsible persons input their plan into the private Wiki as described below, and update the Wiki FI-WARE Standardization v2 (private wiki) with (their) past contributions as well as planned future ones. FI-WARE management team has promised weekly oversight of this activity. ? NEC summarizes results in last week of July, creating D11.4b pdf from the Wiki NEC requests confirmation of this plan, which is detailed below. Yours sincerely, Dr. Lindsay Frost, Dr. Ernoe Kovacs ATTACHMENTs (1) Old, still valid Action Plan to react to EC comments (file 2012-05-23-ActionPlan.txt) (2) Detailed Plan for D11.4.b by End July (see below) Attachment 2: The following is the step-by-step plan: (D) NEC Conclusions for Standardization Plan content and format 6. General content required (to be generated by FI-WARE partners) a. identify what standardization makes sense for FI-WARE (targets), taking account of specific gaps which the EC requested fixed b. identify where to do it (selected SDOs) /note: should reference "Section 2 CONTRIBUTE" actions in D11.4a/ c. explain (if it is planned) where IP generated in FI-WARE is inserted into SDOs specifications d. for each selected SDO and FI-WARE target, show the timeline of how to achieve the target, with "concrete steps" and partners, starting work "even before usable results" as requested by EC e. show how ongoing actual contributions to SDOs fulfill the "concrete steps" (i.e. ongoing status) 7. Step by step Format a. WPLs create a webpage mapping important FI-WARE interfaces/protocols to the Target SDO which could be responsible. It should also indicate any IPR which FI-WARE may bring in. This webpage would satisfy (D)6.a and (D)6.b and (D)6.c above. In the opinion of NEC, standardization is most valuable for the exposed interfaces, and in a secondary way to efficiently design the internal interfaces. Therefore all exposed interfaces are important, and some internal ones. As an example of some important interfaces, the (old) picture https://forge.fi-ware.eu/plugins/mediawiki/wiki/iot/index.php/Snapshot_2012.06.01_of_Deliverable_Page_for_D2.3_Architecture_Specifications could be used. b. WPLs create a webpage showing which partner is responsible for each important interface and their responsible person to make it standardized. The format can be a table ("Target SDO / Responsible Persons") with entries . c. Responsible persons add to FI-WARE Standardization v2 (private wiki) page, for each Target SDO, a timeline based on the SDO meeting schedules and methods, which is designed to get the exposed interface standardized. A partial example is given for ETSI M2M. This satisfies (D)6.d. This can only be created by the responsible persons who also ensure that that Target SDO work happens. It should indicate the phases as e.g. (1) feasibility-study (2) architecture (3) datamodels and protocols. The format can be a table ("Target SDO / Contributions Table ") ordered by date, so later it is easier for the information to be integrated into a complete project plan, e.g. d. The responsible person updates the Target SDO / Contributions Table every week, with new planned inputs and new results. Care should be taken to note any IPR. This satisfies (D)6.e. e. NEC creates an integrated timetable showing the aggregated copies of all tables from step (c) above, which is the overview for the EC. NEC will combine it with (a) and (b) - assuming all partners have strongly contributed - so as to resolve all EC requests. f. Optionally partners can extend the information in (c) above, to include highly relevant non-FI-WARE results which are monitored (M). Also partners can include relevant work they do which however is not part of the agreed important interface work. Monitoring standards is also part of the standardization plan and this work should be reported to the EC, as long as it is shown as supporting a significant amount of active contributions work. NEC rejects proposals to use Googledocs because NEC was required to change from doc to Wiki during the previous phase of the project and the good reasons for doing that still hold. ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: 2012-07-23-FI-Ware-StandardisationPlan Check.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: 2012-05-23-ActionPlan.txt URL: From matteo.melideo at eng.it Mon Jul 23 13:24:50 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Mon, 23 Jul 2012 13:24:50 +0200 Subject: [Fiware-wpa] Minutes updated Message-ID: <500D3482.5080704@eng.it> Dear All, as requested by Juanjo during the conference call, I updated the minutes on the part regarding the catalogue. Please, do not hesitate to contact me for any clarification. Best regards Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From jhierro at tid.es Tue Jul 24 00:27:03 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 24 Jul 2012 00:27:03 +0200 Subject: [Fiware-wpa] On formula for delivering software and Installation/Administration Guidelines marked as PP and linked to GEs In-Reply-To: <500D8E9A.4050506@tid.es> References: <500D8E9A.4050506@tid.es> Message-ID: <500DCFB7.4020404@tid.es> Dear colleagues, I have had a long conversation with our PO this afternoon and we managed to agree on the formula for delivering the software and Installation/Administration Guidelines linked to the GEs that are marked as PP. The agreement is that both deliverables can be made available to the EC for auditing/reviewing purposes on the servers (indeed, VMs) where the software will actually be hosted, this meaning either servers located in the datacenter linked to the FI-WARE Testbed or remote servers (this only applying to those cases where it was agreed that the GE would not be deployed on the FI-WARE Testbed datacenter). We just need to generate a document that identifies the server where the software (binaries) and Installation/Administration Guides will be available and also explains how the EC can get access to the binaries and Installation/Administration Guides. Note that software must be binaries and not VM images. I have push for adoption of this solution as a mean to cover all the concerns expressed by some of the partners. Based on the Collaboration Agreement signed by all parties, FI-WARE GE software binaries and Installation/Administration Guides will not be made available to FI-PPP partners unless they: * request them in writing * require them because they need them for execution of their respective projects within the FI-PPP * can explain that using them "as a Service" through a well defined API (from the FI-WARE Testbed or any other alternative hosting facility) is not enough * an agreement is signed between the GE owner and the FI-PPP partner requesting the software Note that while it's unlikely that a UC project may require access to binaries and Installation/Administration Guides in this first phase of the program ... I expect that these three conditions may fulfilled by several trials in phase 2 and 3 of the FI-PPP. Nevertheless, there will be some few cases where the above conditions would apply even in the current, first phase of the program. It is clear regarding the Cloud Proxy GE in my opinion, but maybe also true with respect to some IoT gateway -related GEs or other GEs that UC projects may need to deploy in local infrastructures. We will keep the "FI-WARE PPP Restricted" project only accessible to FI-WARE partners and the EC (plus reviewers). We will also probably rename it as "FI-WARE Review". GE owners are free to officially deliver their software (binaries) and Installation/Administration Guides on the SVN and docman tools of that project. They may also deliver only foreground software there. This would be an alternative to creation of a dedicated space, at the servers where the software is hosted, where the software should easily be identifiable against any other software. Actually, we will deliver a document to the EC where we will declare that the software is available in the SVN and docman system of this project in FusionForge. Please let us know what of the two options you will choose before end of this week. That way, we will be able to organize the final package of deliverables. In the case that any UC project requires access to binaries and Installation/Administration Guides of a given FI-WARE GE, the above conditions should be met and then we will discuss how the software should be delivered. Hope it helps. Don't hesitate to ask any doubt or question you may have. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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: From jhierro at tid.es Tue Jul 24 01:14:00 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 24 Jul 2012 01:14:00 +0200 Subject: [Fiware-wpa] Report on conversation with our PO on status of the FI-WARE project Message-ID: <500DDAB8.3060303@tid.es> Hi all, I have had a confcall with our PO where we have addressed a number of important issues and have discussed about general status of the project and the program. This email is trying to share with you information about what has been discussed. Don't hesitate to share this information with members of your respective chapter/WP teams. As I have already reported in a previous mail, the first thing we discussed had to do with how to manage deliverables linked to software and Installation/Administration Guides marked as PP. I hope this solves major concerns raised by some of the partners. Second point that was addressed had to do with measurements defined to avoid further delays in meeting defined deadlines. PO is backing us on the decision taken and welcome them. Even in the case that TID were not legally able to reject submission of financial/cost statements (something he doubts because he believes it can), he believes that TID not only can but must identify financial/costs reports TID believes are not in line with what is the actual work carried out and the EC would take decisions accordingly. Nevertheless, I shared with the PO that we believe that all partners will do their best to comply with the defined milestones not just to avoid implementation of the defined measurements but for the sake of the project. I believe that the PO feels confident about the status but let's try not to let him down. I reported about the status of the Testbed and the contingency plan that we put in place. He seemed to be fine with that. I asked him about the 1st year FI-WARE Review Report and he told me that we shouldn't expect this earlier than mid August. I explained Arian our plans regarding resubmission of the Technical Roadmap (in line with what we proposed during the 1st year FI-WARE Review meeting) and he seemed to be fine with them. He confirmed the relevance of the white paper describing the encompassing usage of GEs. I already announced him that it would be rather difficult to get it finished by the end of July because we are all so busy. It seemed that his major concern was to to make sure it be ready before an Information Day regarding the phase 2 of the FI-PPP that the EC has planned by August 30 in Brussels. I reported also that we were working hard on the deliverable regarding 3rd party innovation enablement and trying to get it ready by end of July or, if not, just a few days later. He seemed to be happy with that. Regarding results of the 1st Open Call, Arian expects that the next step will be that we elaborate an amendment of the DoW which incorporates the new partners and their description of work. However, we agreed that such DoW amendment should try to go after the one where we will try to incorporate all pending changes which were summarized and agreed during the last PCC meetings. He was ok with the planning of the second Open Call but would like to see the third Open Call later than what we proposed (January next year instead of end of October) in order to allow incorporation of topics that may be demanded by UC trials selected in phase 2 (hearings are planned to end beginning of December this year). I proposed him the possibility to formulate the 2nd Open Call so that it may consider topics with different closing dates for final publication of Epics and different submission deadlines. This would allow to incorporate topics like Security in this 2nd Open Call. Arian believes this may be feasible. Definitively, I will propose discussing this during the confcall of the FI-PPP AB that will take place this week. I think this was all. I'm happy to respond any question that you may have. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 From ste.depanfilis at gmail.com Tue Jul 24 07:08:10 2012 From: ste.depanfilis at gmail.com (ste.depanfilis at gmail.com) Date: Tue, 24 Jul 2012 05:08:10 +0000 Subject: [Fiware-wpa] R: [Fiware-wpl] Report on conversation with our PO on status of the FI-WARE project In-Reply-To: <500DDAB8.3060303@tid.es> References: <500DDAB8.3060303@tid.es> Message-ID: <1890526146-1343106182-cardhu_decombobulator_blackberry.rim.net-43342595-@b26.c14.bise7.blackberry> Dear Juanjo, Thank you very much for you report. Just a small issue: about the first point you said you talked about sw delivery, but you did not specified what you told him. I guess what agreed during yesterday phc. Can you further detail? Thank you in advance! Ciao Stefano Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! -----Original Message----- From: Juanjo Hierro Sender: fiware-wpl-bounces at lists.fi-ware.eu Date: Tue, 24 Jul 2012 01:14:00 To: fiware-pcc at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpl] Report on conversation with our PO on status of the FI-WARE project Hi all, I have had a confcall with our PO where we have addressed a number of important issues and have discussed about general status of the project and the program. This email is trying to share with you information about what has been discussed. Don't hesitate to share this information with members of your respective chapter/WP teams. As I have already reported in a previous mail, the first thing we discussed had to do with how to manage deliverables linked to software and Installation/Administration Guides marked as PP. I hope this solves major concerns raised by some of the partners. Second point that was addressed had to do with measurements defined to avoid further delays in meeting defined deadlines. PO is backing us on the decision taken and welcome them. Even in the case that TID were not legally able to reject submission of financial/cost statements (something he doubts because he believes it can), he believes that TID not only can but must identify financial/costs reports TID believes are not in line with what is the actual work carried out and the EC would take decisions accordingly. Nevertheless, I shared with the PO that we believe that all partners will do their best to comply with the defined milestones not just to avoid implementation of the defined measurements but for the sake of the project. I believe that the PO feels confident about the status but let's try not to let him down. I reported about the status of the Testbed and the contingency plan that we put in place. He seemed to be fine with that. I asked him about the 1st year FI-WARE Review Report and he told me that we shouldn't expect this earlier than mid August. I explained Arian our plans regarding resubmission of the Technical Roadmap (in line with what we proposed during the 1st year FI-WARE Review meeting) and he seemed to be fine with them. He confirmed the relevance of the white paper describing the encompassing usage of GEs. I already announced him that it would be rather difficult to get it finished by the end of July because we are all so busy. It seemed that his major concern was to to make sure it be ready before an Information Day regarding the phase 2 of the FI-PPP that the EC has planned by August 30 in Brussels. I reported also that we were working hard on the deliverable regarding 3rd party innovation enablement and trying to get it ready by end of July or, if not, just a few days later. He seemed to be happy with that. Regarding results of the 1st Open Call, Arian expects that the next step will be that we elaborate an amendment of the DoW which incorporates the new partners and their description of work. However, we agreed that such DoW amendment should try to go after the one where we will try to incorporate all pending changes which were summarized and agreed during the last PCC meetings. He was ok with the planning of the second Open Call but would like to see the third Open Call later than what we proposed (January next year instead of end of October) in order to allow incorporation of topics that may be demanded by UC trials selected in phase 2 (hearings are planned to end beginning of December this year). I proposed him the possibility to formulate the 2nd Open Call so that it may consider topics with different closing dates for final publication of Epics and different submission deadlines. This would allow to incorporate topics like Security in this 2nd Open Call. Arian believes this may be feasible. Definitively, I will propose discussing this during the confcall of the FI-PPP AB that will take place this week. I think this was all. I'm happy to respond any question that you may have. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl From jhierro at tid.es Tue Jul 24 08:48:36 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 24 Jul 2012 08:48:36 +0200 Subject: [Fiware-wpa] R: [Fiware-wpl] Report on conversation with our PO on status of the FI-WARE project In-Reply-To: <1890526146-1343106182-cardhu_decombobulator_blackberry.rim.net-43342595-@b26.c14.bise7.blackberry> References: <500DDAB8.3060303@tid.es> <1890526146-1343106182-cardhu_decombobulator_blackberry.rim.net-43342595-@b26.c14.bise7.blackberry> Message-ID: <500E4544.1010303@tid.es> On 24/07/12 07:08, ste.depanfilis at gmail.com wrote: > Dear Juanjo, > > Thank you very much for you report. > Just a small issue: about the first point you said you talked about sw delivery, but you did not specified what you told him. I guess what agreed during yesterday phc. Can you further detail? I sent a dedicated mail on the matter previous to that mail. Look for mail with subject "On formula for delivering software and Installation/Administration Guidelines marked as PP and linked to GEs" Cheers, -- Juanjo > > Thank you in advance! > > Ciao > Stefano > > Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! > > -----Original Message----- > From: Juanjo Hierro > Sender: fiware-wpl-bounces at lists.fi-ware.eu > Date: Tue, 24 Jul 2012 01:14:00 > To: fiware-pcc at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu > Subject: [Fiware-wpl] Report on conversation with our PO on status of the > FI-WARE project > > Hi all, > > I have had a confcall with our PO where we have addressed a number > of important issues and have discussed about general status of the > project and the program. This email is trying to share with you > information about what has been discussed. > > Don't hesitate to share this information with members of your > respective chapter/WP teams. > > As I have already reported in a previous mail, the first thing we > discussed had to do with how to manage deliverables linked to software > and Installation/Administration Guides marked as PP. I hope this > solves major concerns raised by some of the partners. > > Second point that was addressed had to do with measurements defined > to avoid further delays in meeting defined deadlines. PO is backing us > on the decision taken and welcome them. Even in the case that TID were > not legally able to reject submission of financial/cost statements > (something he doubts because he believes it can), he believes that TID > not only can but must identify financial/costs reports TID believes are > not in line with what is the actual work carried out and the EC would > take decisions accordingly. Nevertheless, I shared with the PO that > we believe that all partners will do their best to comply with the > defined milestones not just to avoid implementation of the defined > measurements but for the sake of the project. I believe that the PO > feels confident about the status but let's try not to let him down. > > I reported about the status of the Testbed and the contingency plan > that we put in place. He seemed to be fine with that. > > I asked him about the 1st year FI-WARE Review Report and he told me > that we shouldn't expect this earlier than mid August. I explained > Arian our plans regarding resubmission of the Technical Roadmap (in line > with what we proposed during the 1st year FI-WARE Review meeting) and he > seemed to be fine with them. He confirmed the relevance of the white > paper describing the encompassing usage of GEs. I already announced > him that it would be rather difficult to get it finished by the end of > July because we are all so busy. It seemed that his major concern was to > to make sure it be ready before an Information Day regarding the phase 2 > of the FI-PPP that the EC has planned by August 30 in Brussels. > > I reported also that we were working hard on the deliverable > regarding 3rd party innovation enablement and trying to get it ready by > end of July or, if not, just a few days later. He seemed to be happy > with that. > > Regarding results of the 1st Open Call, Arian expects that the next > step will be that we elaborate an amendment of the DoW which > incorporates the new partners and their description of work. However, we > agreed that such DoW amendment should try to go after the one where we > will try to incorporate all pending changes which were summarized and > agreed during the last PCC meetings. > > He was ok with the planning of the second Open Call but would like to > see the third Open Call later than what we proposed (January next year > instead of end of October) in order to allow incorporation of topics > that may be demanded by UC trials selected in phase 2 (hearings are > planned to end beginning of December this year). I proposed him the > possibility to formulate the 2nd Open Call so that it may consider > topics with different closing dates for final publication of Epics and > different submission deadlines. This would allow to incorporate topics > like Security in this 2nd Open Call. Arian believes this may be > feasible. Definitively, I will propose discussing this during the > confcall of the FI-PPP AB that will take place this week. > > I think this was all. I'm happy to respond any question that you > may have. > > Best regards, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website: www.tid.es > email: jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Chief Architect > > You can follow FI-WARE at: > 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 > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpl > ________________________________ 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 From thierry.nagellen at orange.com Tue Jul 24 10:43:06 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 24 Jul 2012 08:43:06 +0000 Subject: [Fiware-wpa] Comments on 3rd party innovation document Message-ID: <19131_1343119408_500E6030_19131_342_6_976A65C5A08ADF49B9A8523F7F81925C0218E7@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear partners, I'm trying to fulfill my part for IoT in the related document and based on what you have previously written I have the following comments: Some comments on the roles just to try to simplify the picture because too many roles would introduce confusion for the reader and this is typically what we have to avoid: 1. Application developer: one of the main trends is that everybody could be application developer based on Apps stores (Apple and Android). This dimension is missing in the role description and we should introduce it to clearly target SMEs and people as potential player for this role. If you agree I can improve this part. This would also emphasize a bit the application end users (end consumers) role for each chapter description 2. Service aggregator seems not relevant because if this role has to deliver something for specific requirements of niche End Users this is a dedicated Service provider Some comments on the content per chapter: 1. Some of you are using the role descriptions as entry points to explain how 3rd parties will take benefit from what we will deliver, some other are using GE description. As I understand the guidelines role descriptions is the right entry point and we should avoid too technical descriptions regarding GE but explain how they are relevant to deliver an innovation, in other words try to imagine some FI-Ware scenarios to use several GEs for a new service/apps. The existing wiki is the place where we provide GEs description. 2. Developer roles are just mentioned in the Tools chapter... this I not really consistent with what we explained during the last review so from my perspective we should find these two roles in each chapter General comment: where can we emphasize that developers could use GEs from several chapters and not only from one chapter: the global scenario for an Application developer for example? Your comments are welcome because this document should be a first draft for marketing document to explain the relevance of FI-Ware project for the ICT ecosystem. BR Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 New email address: thierry.nagellen at orange.com _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue Jul 24 10:57:45 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 24 Jul 2012 10:57:45 +0200 Subject: [Fiware-wpa] [Suspected Spam] IMPORTANT: General comments regarding addition/revision of Features linked to FI-WARE GEs Message-ID: <500E6389.90701@tid.es> Dear Chapter Leaders, We will send each of you an email with specific comments on your chapter, but we have decided to compile a number of generic comments you have to take into account. You have to find out to what extend they are applicable to your chapter. Note that rejection of work made regarding addition/revision of Features linked to FI-WARE GEs will impact the justification of resources that were supposed to work contributing to development of WP2 deliverables (the Technical Roadmap deliverable in this case) and the development of Unit Testing Plans (since they should be formulated upon defined Features). Not up to 100% of those resources but significantly. Cheers, -- Juanjo Hierro 1. General Comments regarding addition/revision of Features linked to FI-WARE GEs 1.1 Completeness of the set of Features linked to GEs We have commented many times that any third party should be able to understand what a GE is about and what functional and non-functional features it will support by means of reading the complete set of Features defined in the Backlog (that's why they are called Features). Adding Epics to this reading (though excluding Epics that are mere ascendants of identified Features), a third party may also gain a general idea of what topics are planned in the future for that GE. If someone ask you tomorrow to develop the technical brochure of any GE in your chapter, it should be an easy exercise you should be able to complete based on text of the goals linked to Features of that GE. Are these general rules applicable to FI-WARE GEs in your chapter ? We sincerely believe that not in all cases. Please check it yourself. It hadn't been a bad idea if you have carried out some sort of peer-review process within your chapter having this goal in mind. 1.2 Single-Featured GEs There are several GEs that are characterized by just a couple of Features. We believe that this is a rather poor description and most probably we will ask to improve it. There are even some GEs that are just characterized by a single Feature. If it were the case that the Feature contains a long description with a rather elaborated description of all the functionality covered by the GE we would recommend to split the Feature into several. However, in many (if not all) the cases where this happens, the Feature comprises a rather brief and too high-level description. We believe this is unjustifiable. We will reject this. One general formula that some GE owners have followed is that of identifying at least one Feature per operation exported by the GE. Sometimes a given operation is too complex and admit several variants that will not all be supported in the first release of FI-WARE (e.g., it receives arguments of different nature and there are special type of arguments that will not be supported until certain Release of FI-WARE). This circumstance should lead to several Features, one per variant. You may also identify some additional Features linked to description of how the GE can be configured by users. Last but not least, you may also identify some non-functional features linked to certain requirements that, at minimum, any product that would be considered a valid implementation of the GE should comply with. 1.3 Features map to functional or non-functional characteristics, not to Work Items. We have seen some Features linked to some GEs that are indeed Work Items and not Features. Setting up a working testing environment to ease development of the GE cannot be considered a Feature but a Work Item that we understand could have been needed during development of the project. But it doesn't have anything to do with characteristics of the GE. Note that Work Items should only be visible on the trackers and not in the backlog of the Wiki. 1.4 Shouldn't some User Stories be labeled as Features ? There are some cases in which we have found that some of the User Stories had fit nicely as Features. They had helped to compile a final set of Features that allow to meet the goal described in section 1.1. above. However, the Features that may be considered as "Ascendants" of those User Stories include descriptions that are too high-level or vague, thus making it difficult to meet the goal described in section 1.1. if considered alone. We suggest that you address this issue in any of the two following ways: * Were these User Stories actually resolved in the course of a Sprint (i.e., one month) ? * If the answer is 'Yes', then we propose to follow any of the two following options: * clone the User Stories as Features. There is no Agile principle that would go against it. We would justify that each Feature had led to a single User Story because we have realized it could be addressed in the course of a Sprint. * refine the description of the 'father' Feature (there should be some and, if not, just create it) so that it contains a bullet list of related functions, each item in the list mapping to one of the User Stories * If the answer is 'No', transform the User Story into a Feature. This will imply that you didn't refine the Feature into User Stories that you could address in the course of each of the Sprints that belonged to a Release. We can't relax and forget meeting this rule for this first major release of FI-WARE. We'll try to do it better during development of the second major release of FI-WARE 1.5 Description of some Features is missing or is very poor The Description of some Features is simple missing or is very poor (almost a copy and paste of the goal). While goals should try to capture the functional or non-functional feature supported by the GE in one or maximum 2 lines, the Description should be more elaborated. 1.6 Formula for Goals Following Agile principles, the definition of Goals should follow patterns such as " will be able to " or "By means of invoking the exported by the GE, will be able to " or even following a more typical Agile approach "As a , I will be able to do " ... However, certain Goals do not follow any similar approach. Please review it. ________________________________ 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: From jhierro at tid.es Tue Jul 24 13:04:33 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 24 Jul 2012 13:04:33 +0200 Subject: [Fiware-wpa] On formula for delivering software and Installation/Administration Guidelines marked as PP and linked to GEs In-Reply-To: <500DCFB7.4020404@tid.es> References: <500D8E9A.4050506@tid.es> <500DCFB7.4020404@tid.es> Message-ID: <500E8141.2080108@tid.es> Please share this within your teams. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 On 24/07/12 00:27, Juanjo Hierro wrote: Dear colleagues, I have had a long conversation with our PO this afternoon and we managed to agree on the formula for delivering the software and Installation/Administration Guidelines linked to the GEs that are marked as PP. The agreement is that both deliverables can be made available to the EC for auditing/reviewing purposes on the servers (indeed, VMs) where the software will actually be hosted, this meaning either servers located in the datacenter linked to the FI-WARE Testbed or remote servers (this only applying to those cases where it was agreed that the GE would not be deployed on the FI-WARE Testbed datacenter). We just need to generate a document that identifies the server where the software (binaries) and Installation/Administration Guides will be available and also explains how the EC can get access to the binaries and Installation/Administration Guides. Note that software must be binaries and not VM images. I have push for adoption of this solution as a mean to cover all the concerns expressed by some of the partners. Based on the Collaboration Agreement signed by all parties, FI-WARE GE software binaries and Installation/Administration Guides will not be made available to FI-PPP partners unless they: * request them in writing * require them because they need them for execution of their respective projects within the FI-PPP * can explain that using them "as a Service" through a well defined API (from the FI-WARE Testbed or any other alternative hosting facility) is not enough * an agreement is signed between the GE owner and the FI-PPP partner requesting the software Note that while it's unlikely that a UC project may require access to binaries and Installation/Administration Guides in this first phase of the program ... I expect that these three conditions may fulfilled by several trials in phase 2 and 3 of the FI-PPP. Nevertheless, there will be some few cases where the above conditions would apply even in the current, first phase of the program. It is clear regarding the Cloud Proxy GE in my opinion, but maybe also true with respect to some IoT gateway -related GEs or other GEs that UC projects may need to deploy in local infrastructures. We will keep the "FI-WARE PPP Restricted" project only accessible to FI-WARE partners and the EC (plus reviewers). We will also probably rename it as "FI-WARE Review". GE owners are free to officially deliver their software (binaries) and Installation/Administration Guides on the SVN and docman tools of that project. They may also deliver only foreground software there. This would be an alternative to creation of a dedicated space, at the servers where the software is hosted, where the software should easily be identifiable against any other software. Actually, we will deliver a document to the EC where we will declare that the software is available in the SVN and docman system of this project in FusionForge. Please let us know what of the two options you will choose before end of this week. That way, we will be able to organize the final package of deliverables. In the case that any UC project requires access to binaries and Installation/Administration Guides of a given FI-WARE GE, the above conditions should be met and then we will discuss how the software should be delivered. Hope it helps. Don't hesitate to ask any doubt or question you may have. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa ________________________________ 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: From lorant.farkas at nsn.com Tue Jul 24 13:49:31 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 24 Jul 2012 14:49:31 +0300 Subject: [Fiware-wpa] On formula for delivering software and Installation/Administration Guidelines marked as PP and linked to GEs In-Reply-To: <500DCFB7.4020404@tid.es> References: <500D8E9A.4050506@tid.es> <500DCFB7.4020404@tid.es> Message-ID: <93D28BDF64839C468B848D14227151A203C10934@FIESEXC014.nsn-intra.net> Hi Juanjo, We are not able to tell from which IP addess range the commission will access the docs&binaries. Miguel told us yesterday to disclose the IP address from which we will access the VM, because all other IP addresses will be rejected. I sense a conflict here. Thanks & Br, Lorant From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of ext Juanjo Hierro Sent: Tuesday, July 24, 2012 12:27 AM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: fiware-pcc at lists.fi-ware.eu Subject: [Fiware-wpa] On formula for delivering software and Installation/Administration Guidelines marked as PP and linked to GEs Dear colleagues, I have had a long conversation with our PO this afternoon and we managed to agree on the formula for delivering the software and Installation/Administration Guidelines linked to the GEs that are marked as PP. The agreement is that both deliverables can be made available to the EC for auditing/reviewing purposes on the servers (indeed, VMs) where the software will actually be hosted, this meaning either servers located in the datacenter linked to the FI-WARE Testbed or remote servers (this only applying to those cases where it was agreed that the GE would not be deployed on the FI-WARE Testbed datacenter). We just need to generate a document that identifies the server where the software (binaries) and Installation/Administration Guides will be available and also explains how the EC can get access to the binaries and Installation/Administration Guides. Note that software must be binaries and not VM images. I have push for adoption of this solution as a mean to cover all the concerns expressed by some of the partners. Based on the Collaboration Agreement signed by all parties, FI-WARE GE software binaries and Installation/Administration Guides will not be made available to FI-PPP partners unless they: * request them in writing * require them because they need them for execution of their respective projects within the FI-PPP * can explain that using them "as a Service" through a well defined API (from the FI-WARE Testbed or any other alternative hosting facility) is not enough * an agreement is signed between the GE owner and the FI-PPP partner requesting the software Note that while it's unlikely that a UC project may require access to binaries and Installation/Administration Guides in this first phase of the program ... I expect that these three conditions may fulfilled by several trials in phase 2 and 3 of the FI-PPP. Nevertheless, there will be some few cases where the above conditions would apply even in the current, first phase of the program. It is clear regarding the Cloud Proxy GE in my opinion, but maybe also true with respect to some IoT gateway -related GEs or other GEs that UC projects may need to deploy in local infrastructures. We will keep the "FI-WARE PPP Restricted" project only accessible to FI-WARE partners and the EC (plus reviewers). We will also probably rename it as "FI-WARE Review". GE owners are free to officially deliver their software (binaries) and Installation/Administration Guides on the SVN and docman tools of that project. They may also deliver only foreground software there. This would be an alternative to creation of a dedicated space, at the servers where the software is hosted, where the software should easily be identifiable against any other software. Actually, we will deliver a document to the EC where we will declare that the software is available in the SVN and docman system of this project in FusionForge. Please let us know what of the two options you will choose before end of this week. That way, we will be able to organize the final package of deliverables. In the case that any UC project requires access to binaries and Installation/Administration Guides of a given FI-WARE GE, the above conditions should be met and then we will discuss how the software should be delivered. Hope it helps. Don't hesitate to ask any doubt or question you may have. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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: From axel.fasse at sap.com Tue Jul 24 19:20:39 2012 From: axel.fasse at sap.com (Fasse, Axel) Date: Tue, 24 Jul 2012 19:20:39 +0200 Subject: [Fiware-wpa] Report on conversation with our PO on status of the FI-WARE project In-Reply-To: <500DDAB8.3060303@tid.es> References: <500DDAB8.3060303@tid.es> Message-ID: <2C6296E1876B5C49962495FDACDC7A6361671BB324@DEWDFECCR01.wdf.sap.corp> Dera Juanjo, thank you very much for your clarification. I think it would be a good idea to make some comments, that are already mentioned before in the different mails with respect to the PCC Call and which were mentioned again within the PDF File with my comments to the PCC minutes. So far as I understand your mail, it seems to me, as if you have not taken into account my remarks during the call with our PO. Because of that, I would like to make my comments again. I have added my comments directly into your mail. Best regards, Axel -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Dienstag, 24. Juli 2012 01:14 To: fiware-pcc at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpa] Report on conversation with our PO on status of the FI-WARE project Hi all, I have had a confcall with our PO where we have addressed a number of important issues and have discussed about general status of the project and the program. This email is trying to share with you information about what has been discussed. Don't hesitate to share this information with members of your respective chapter/WP teams. As I have already reported in a previous mail, the first thing we discussed had to do with how to manage deliverables linked to software and Installation/Administration Guides marked as PP. I hope this solves major concerns raised by some of the partners. Yes, that's the right way, that's fine for us. Second point that was addressed had to do with measurements defined to avoid further delays in meeting defined deadlines. PO is backing us on the decision taken and welcome them. Even in the case that TID were not legally able to reject submission of financial/cost statements (something he doubts because he believes it can), he believes that TID not only can but must identify financial/costs reports TID believes are not in line with what is the actual work carried out and the EC would take decisions accordingly. Nevertheless, I shared with the PO that we believe that all partners will do their best to comply with the defined milestones not just to avoid implementation of the defined measurements but for the sake of the project. I believe that the PO feels confident about the status but let's try not to let him down. >From the PO's point of view, I can understand that he likes your proposal. But this is actually not compatible with the existing legal contracts. I would suggest to propose another way that is compliant to all of the legal contracts and that is formally agreed by all partners. If you - as the coordinator - have finished the proposal we should explain the existing problem to the PO and try to convince him about our new way to take care about the timeline and the quality of the deliverables I reported about the status of the Testbed and the contingency plan that we put in place. He seemed to be fine with that. >From my point of view some of the details are missing. I would suggest to avoid any over-selling. I asked him about the 1st year FI-WARE Review Report and he told me that we shouldn't expect this earlier than mid August. I explained Arian our plans regarding resubmission of the Technical Roadmap (in line with what we proposed during the 1st year FI-WARE Review meeting) and he seemed to be fine with them. He confirmed the relevance of the white paper describing the encompassing usage of GEs. I already announced him that it would be rather difficult to get it finished by the end of July because we are all so busy. It seemed that his major concern was to to make sure it be ready before an Information Day regarding the phase 2 of the FI-PPP that the EC has planned by August 30 in Brussels. I reported also that we were working hard on the deliverable regarding 3rd party innovation enablement and trying to get it ready by end of July or, if not, just a few days later. He seemed to be happy with that. Regarding results of the 1st Open Call, Arian expects that the next step will be that we elaborate an amendment of the DoW which incorporates the new partners and their description of work. However, we agreed that such DoW amendment should try to go after the one where we will try to incorporate all pending changes which were summarized and agreed during the last PCC meetings. That's a very good approach. He was ok with the planning of the second Open Call but would like to see the third Open Call later than what we proposed (January next year instead of end of October) in order to allow incorporation of topics that may be demanded by UC trials selected in phase 2 (hearings are planned to end beginning of December this year). I proposed him the possibility to formulate the 2nd Open Call so that it may consider topics with different closing dates for final publication of Epics and different submission deadlines. This would allow to incorporate topics like Security in this 2nd Open Call. Arian believes this may be feasible. Definitively, I will propose discussing this during the confcall of the FI-PPP AB that will take place this week. I think this was all. I'm happy to respond any question that you may have. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed Jul 25 13:20:38 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 25 Jul 2012 13:20:38 +0200 Subject: [Fiware-wpa] Comments on Features Linked to the GEs Message-ID: <500FD686.8000502@tid.es> Hi all, I have already sent the comments to the Cloud, IoT and Apps Chapter (only comments on Composition GE are remaining there). These besides the general comments already provided to all of you. However, I won't be able to provide comments for the rest until tomorrow early morning. Given this fact, the deadline for fixing issues raised in the comments for the remaining chapters (as well as the Composition GE in the Apps Chapter) will be extended until Monday July 30th EOB. Those chapters still waiting for the comments: please review general comments and start to apply corrective actions regarding those that you believe would apply to your chapter. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 From jhierro at tid.es Thu Jul 26 18:03:48 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 26 Jul 2012 18:03:48 +0200 Subject: [Fiware-wpa] Format of deliverable linked to software and Installation/Administration Guides of GEs marked as PP Message-ID: <50116A64.9010907@tid.es> Dear colleagues, As already announced, the software and Installation/Administration Guides of GEs marked as PP will be covered by the insertion of a page per GE that will be part of the corresponding WP deliverable. Following is the draft text of the page we plan to insert for your consideration in case you have any comments (please send them not just to me but with cc to Miguel): === - Software Release and Installation and Administration guide The GE will be offered as a service by the GE owner. Besides, the software release of the GE and the accompanying Installation and Administration guide are of PP dissemination level[1]. In accordance with the privacy restrictions requested by GE owner, both the software (binaries) and the Installation and Administration Guides were not reviewed by the FI-WARE coordinator or the Work Package leader and the responsibility for the quality and appropriateness of this part of the deliverables remain solely with the partner who is the GE owner. The software (binaries) and the Installation and Administration Guides are accessible to the EC for reviewing purposes on a remote server located at via ssh with user: EC and password to be disclaimed upon explicit request to the project coordinator. The partner who is the GE owner will govern this access. ________________________________ [1] Restricted to FI-PPP programme participants (including the Commission Services) upon request in writing, where access to the API is not sufficient for execution of a FI-PPP project. ==== The final version of this text, incorporating any comment you may have, will be provided to you in Word format by tomorrow. Best, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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: From lorant.farkas at nsn.com Fri Jul 27 07:35:27 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Fri, 27 Jul 2012 08:35:27 +0300 Subject: [Fiware-wpa] Format of deliverable linked to software and Installation/Administration Guides of GEs marked as PP In-Reply-To: <50116A64.9010907@tid.es> References: <50116A64.9010907@tid.es> Message-ID: <93D28BDF64839C468B848D14227151A203C112F3@FIESEXC014.nsn-intra.net> Hi Juanjo, 1. Do you mean PP GE-s, SaaS GE-s (not installed in the testbed) or PP + SaaS GE-s? I guess you mean SaaS GE-s (e.g. NSN IDM). 2. Just FYI, in that case you caused at least for us (NSN) extra work which turns up not to be needed: colleagues are struggling to create install/admin guides for NSN IDM complying with Miguel's guidelines, which finally will not be required. Other partners might be in the same situation. Thanks & Br, Lorant From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of ext Juanjo Hierro Sent: Thursday, July 26, 2012 6:04 PM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Format of deliverable linked to software and Installation/Administration Guides of GEs marked as PP Dear colleagues, As already announced, the software and Installation/Administration Guides of GEs marked as PP will be covered by the insertion of a page per GE that will be part of the corresponding WP deliverable. Following is the draft text of the page we plan to insert for your consideration in case you have any comments (please send them not just to me but with cc to Miguel): === - Software Release and Installation and Administration guide The GE will be offered as a service by the GE owner. Besides, the software release of the GE and the accompanying Installation and Administration guide are of PP dissemination level[1]. In accordance with the privacy restrictions requested by GE owner, both the software (binaries) and the Installation and Administration Guides were not reviewed by the FI-WARE coordinator or the Work Package leader and the responsibility for the quality and appropriateness of this part of the deliverables remain solely with the partner who is the GE owner. The software (binaries) and the Installation and Administration Guides are accessible to the EC for reviewing purposes on a remote server located at via ssh with user: EC and password to be disclaimed upon explicit request to the project coordinator. The partner who is the GE owner will govern this access. ________________________________ [1] Restricted to FI-PPP programme participants (including the Commission Services) upon request in writing, where access to the API is not sufficient for execution of a FI-PPP project. ==== The final version of this text, incorporating any comment you may have, will be provided to you in Word format by tomorrow. Best, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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: From jhierro at tid.es Fri Jul 27 13:12:16 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 27 Jul 2012 13:12:16 +0200 Subject: [Fiware-wpa] Format of deliverable linked to software and Installation/Administration Guides of GEs marked as PP In-Reply-To: <93D28BDF64839C468B848D14227151A203C112F3@FIESEXC014.nsn-intra.net> References: <50116A64.9010907@tid.es> <93D28BDF64839C468B848D14227151A203C112F3@FIESEXC014.nsn-intra.net> Message-ID: <50127790.3080200@tid.es> On 27/07/12 07:35, Farkas, Lorant (NSN - HU/Budapest) wrote: Hi Juanjo, 1. Do you mean PP GE-s, SaaS GE-s (not installed in the testbed) or PP + SaaS GE-s? I guess you mean SaaS GE-s (e.g. NSN IDM). Thanks for raising this. Actually the template apply both to: * PP GEs that are offered as a Service, hosted in remote facilities provided by the GE owner * PP GEs that are hosted on the Testbed (as one of the possible options, see below) I remind you that for GEs hosted on the Testbed we have given two alternatives regarding delivery of software and Installation/Admin Guides (for the GE owner to decide): * Deliver the binaries and Installation/Admin guide on the VMs allocated to the GE on the Testbed * Deliver the binaries and Installation/Admin guide on FusionForge (restricted access area) If the first option is chosen, what will be submitted to the EC is a document based on the template that I attached to my email. Note that the template will be the same for this case and the case of PP GEs hosted in remote facilities provided by the GE owner. Obviously, what will change is the IP address (in one case, it will be one linked to the Tesbed, in the other case, it will be one to be provided by the GE owner) Hope it is clear. 2. Just FYI, in that case you caused at least for us (NSN) extra work which turns up not to be needed: colleagues are struggling to create install/admin guides for NSN IDM complying with Miguel's guidelines, which finally will not be required. Other partners might be in the same situation. The GEs offered as a service in remote facilities have to be ready by end of July. The Installation/Admin guides have to be delivered in those servers according to the contract so that the EC can review them or double-check they exist when they want. This means, in the case of the NSN IDM GE, that they have to make it accessible in the hosting facility where they have deployed the GE. I don't know when the EC will try to check that they are actually there, or even if they will do it ... but if you play with the timing and want to run the risk of not providing it now and bet that you will have it ready a the time the EC actually request for the access to check it has been delivered, it would be at your own risk. They should be there by end of July. TID won't check it to comply with your privacy requirements. If you want us to check it, you should provide us access, the same way as with the EC. Best regards, -- Juanjo Thanks & Br, Lorant From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of ext Juanjo Hierro Sent: Thursday, July 26, 2012 6:04 PM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Format of deliverable linked to software and Installation/Administration Guides of GEs marked as PP Dear colleagues, As already announced, the software and Installation/Administration Guides of GEs marked as PP will be covered by the insertion of a page per GE that will be part of the corresponding WP deliverable. Following is the draft text of the page we plan to insert for your consideration in case you have any comments (please send them not just to me but with cc to Miguel): === - Software Release and Installation and Administration guide The GE will be offered as a service by the GE owner. Besides, the software release of the GE and the accompanying Installation and Administration guide are of PP dissemination level[1]. In accordance with the privacy restrictions requested by GE owner, both the software (binaries) and the Installation and Administration Guides were not reviewed by the FI-WARE coordinator or the Work Package leader and the responsibility for the quality and appropriateness of this part of the deliverables remain solely with the partner who is the GE owner. The software (binaries) and the Installation and Administration Guides are accessible to the EC for reviewing purposes on a remote server located at via ssh with user: EC and password to be disclaimed upon explicit request to the project coordinator. The partner who is the GE owner will govern this access. ________________________________ [1] Restricted to FI-PPP programme participants (including the Commission Services) upon request in writing, where access to the API is not sufficient for execution of a FI-PPP project. ==== The final version of this text, incorporating any comment you may have, will be provided to you in Word format by tomorrow. Best, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 ________________________________ 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: From mcp at tid.es Fri Jul 27 15:18:36 2012 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 27 Jul 2012 15:18:36 +0200 Subject: [Fiware-wpa] Format of deliverable linked to software and Installation/Administration Guides of GEs marked as PP In-Reply-To: <50116A64.9010907@tid.es> References: <50116A64.9010907@tid.es> Message-ID: <5012952C.4080503@tid.es> Dear all, Further to this message from Juanjo and after a reasonable wait for comments, I send the definite template that tries to be reasonable uniform with the wiki-generated pdf files. Fill in the part in yellow (note that there is also one in the header) and then place them in the installation guide in he place where you would have the part of the PP enabler if it was PU. This implies printing this out to pdf and using the pdf handling tool I mention in the manual to generate pdf deliverables (of course, if you can use another tool if you like). Best regards, Miguel El 26/07/2012 18:03, Juanjo Hierro escribi?: Dear colleagues, As already announced, the software and Installation/Administration Guides of GEs marked as PP will be covered by the insertion of a page per GE that will be part of the corresponding WP deliverable. Following is the draft text of the page we plan to insert for your consideration in case you have any comments (please send them not just to me but with cc to Miguel): === - Software Release and Installation and Administration guide The GE will be offered as a service by the GE owner. Besides, the software release of the GE and the accompanying Installation and Administration guide are of PP dissemination level[1]. In accordance with the privacy restrictions requested by GE owner, both the software (binaries) and the Installation and Administration Guides were not reviewed by the FI-WARE coordinator or the Work Package leader and the responsibility for the quality and appropriateness of this part of the deliverables remain solely with the partner who is the GE owner. The software (binaries) and the Installation and Administration Guides are accessible to the EC for reviewing purposes on a remote server located at via ssh with user: EC and password to be disclaimed upon explicit request to the project coordinator. The partner who is the GE owner will govern this access. ________________________________ [1] Restricted to FI-PPP programme participants (including the Commission Services) upon request in writing, where access to the API is not sufficient for execution of a FI-PPP project. ==== The final version of this text, incorporating any comment you may have, will be provided to you in Word format by tomorrow. Best, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 -- ---------------------------------------------------------------------- _/ _/_/ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: PP binaries and admin guide deliverables.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 18605 bytes Desc: not available URL: From mcp at tid.es Fri Jul 27 17:42:41 2012 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 27 Jul 2012 17:42:41 +0200 Subject: [Fiware-wpa] Format of deliverable linked to software and Installation/Administration Guides of GEs marked as PP In-Reply-To: <5012952C.4080503@tid.es> References: <50116A64.9010907@tid.es> <5012952C.4080503@tid.es> Message-ID: <5012B6F1.4090105@tid.es> Dear all, We have received comments to the wording. Anyway, I uploaded the final version to the tutorial to make sure that we do not lean on emails and centralise it a bit. . https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverables#Instructions_for_the_delivery_of_the_Installation_and_Administration_Guide BR Miguel El 27/07/2012 15:18, Miguel Carrillo escribi?: Dear all, Further to this message from Juanjo and after a reasonable wait for comments, I send the definite template that tries to be reasonable uniform with the wiki-generated pdf files. Fill in the part in yellow (note that there is also one in the header) and then place them in the installation guide in he place where you would have the part of the PP enabler if it was PU. This implies printing this out to pdf and using the pdf handling tool I mention in the manual to generate pdf deliverables (of course, if you can use another tool if you like). Best regards, Miguel El 26/07/2012 18:03, Juanjo Hierro escribi?: Dear colleagues, As already announced, the software and Installation/Administration Guides of GEs marked as PP will be covered by the insertion of a page per GE that will be part of the corresponding WP deliverable. Following is the draft text of the page we plan to insert for your consideration in case you have any comments (please send them not just to me but with cc to Miguel): === - Software Release and Installation and Administration guide The GE will be offered as a service by the GE owner. Besides, the software release of the GE and the accompanying Installation and Administration guide are of PP dissemination level[1]. In accordance with the privacy restrictions requested by GE owner, both the software (binaries) and the Installation and Administration Guides were not reviewed by the FI-WARE coordinator or the Work Package leader and the responsibility for the quality and appropriateness of this part of the deliverables remain solely with the partner who is the GE owner. The software (binaries) and the Installation and Administration Guides are accessible to the EC for reviewing purposes on a remote server located at via ssh with user: EC and password to be disclaimed upon explicit request to the project coordinator. The partner who is the GE owner will govern this access. ________________________________ [1] Restricted to FI-PPP programme participants (including the Commission Services) upon request in writing, where access to the API is not sufficient for execution of a FI-PPP project. ==== The final version of this text, incorporating any comment you may have, will be provided to you in Word format by tomorrow. Best, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: PP binaries and admin guide deliverables.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 18555 bytes Desc: not available URL: From lorant.farkas at nsn.com Sun Jul 29 07:55:32 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Sun, 29 Jul 2012 08:55:32 +0300 Subject: [Fiware-wpa] Format of deliverable linked to software and Installation/Administration Guides of GEs marked as PP References: <50116A64.9010907@tid.es> <5012952C.4080503@tid.es> <5012B6F1.4090105@tid.es> Message-ID: <93D28BDF64839C468B848D14227151A2C531E5@FIESEXC014.nsn-intra.net> Hi Miguel, The guidelines are a bit misleading, from 2 perspectives: 1. for PP assets that are non SaaS the understanding so far was that the partner will upload the binaries and install/admin guide in the testbed on the VM you provide for the GE. 2. my understanding was that this would be a possibility also for SaaS GE-s: they could have a VM just to host the binaries and the install/admin guide, while the GE runs as a service at the premises of the partner. Is my understanding wrong? Thanks & Br, Lorant -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu on behalf of ext Miguel Carrillo Sent: Fri 7/27/2012 5:42 PM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] Format of deliverable linked to software and Installation/Administration Guides of GEs marked as PP Dear all, We have received comments to the wording. Anyway, I uploaded the final version to the tutorial to make sure that we do not lean on emails and centralise it a bit. . https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverables#Instructions_for_the_delivery_of_the_Installation_and_Administration_Guide BR Miguel El 27/07/2012 15:18, Miguel Carrillo escribi?: Dear all, Further to this message from Juanjo and after a reasonable wait for comments, I send the definite template that tries to be reasonable uniform with the wiki-generated pdf files. Fill in the part in yellow (note that there is also one in the header) and then place them in the installation guide in he place where you would have the part of the PP enabler if it was PU. This implies printing this out to pdf and using the pdf handling tool I mention in the manual to generate pdf deliverables (of course, if you can use another tool if you like). Best regards, Miguel El 26/07/2012 18:03, Juanjo Hierro escribi?: Dear colleagues, As already announced, the software and Installation/Administration Guides of GEs marked as PP will be covered by the insertion of a page per GE that will be part of the corresponding WP deliverable. Following is the draft text of the page we plan to insert for your consideration in case you have any comments (please send them not just to me but with cc to Miguel): === - Software Release and Installation and Administration guide The GE will be offered as a service by the GE owner. Besides, the software release of the GE and the accompanying Installation and Administration guide are of PP dissemination level[1]. In accordance with the privacy restrictions requested by GE owner, both the software (binaries) and the Installation and Administration Guides were not reviewed by the FI-WARE coordinator or the Work Package leader and the responsibility for the quality and appropriateness of this part of the deliverables remain solely with the partner who is the GE owner. The software (binaries) and the Installation and Administration Guides are accessible to the EC for reviewing purposes on a remote server located at via ssh with user: EC and password to be disclaimed upon explicit request to the project coordinator. The partner who is the GE owner will govern this access. ________________________________ [1] Restricted to FI-PPP programme participants (including the Commission Services) upon request in writing, where access to the API is not sufficient for execution of a FI-PPP project. ==== The final version of this text, incorporating any comment you may have, will be provided to you in Word format by tomorrow. Best, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 From mcp at tid.es Mon Jul 30 10:55:38 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 30 Jul 2012 10:55:38 +0200 Subject: [Fiware-wpa] Link to shared minutes of the WPL/WPA call today Message-ID: <50164C0A.2090002@tid.es> Dear all, This is the link for the shared minutes today. https://docs.google.com/document/d/1Z4edEjU8j1FF2GvVCVqlVRhgFpfO3yN1JjFK64bzJwA/edit?pli=1# 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 From jhierro at tid.es Mon Jul 30 10:58:31 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 30 Jul 2012 10:58:31 +0200 Subject: [Fiware-wpa] Fwd: FI-WARE: extract executive summary draft review report In-Reply-To: <69AD1A9684E7184DADBE43806285BA9D07CB70@S-DC-ESTF03-B.net1.cec.eu.int> References: <69AD1A9684E7184DADBE43806285BA9D07CB70@S-DC-ESTF03-B.net1.cec.eu.int> Message-ID: <50164CB7.1060804@tid.es> Dear colleagues, We have just received the following extract of the executive summary draft review report. We haven't had time to review it. But certainly the review report is not as positive as we thought after the first year review meeting. Overall, it is worth to highlight that the project's assestment is: * Unsatisfactory progress (The project has failed to achieve key objectives and/or is not at all on schedule)" This, among other things, confirms us that the recent measurements put in place were required. Now, it's critical to demonstrate that we are going to deliver what was due and that the testbed will not get delayed. We'll come with additional comments later. Best regards, -- Juanjo -------- Original Message -------- Subject: FI-WARE: extract executive summary draft review report Date: Mon, 30 Jul 2012 08:42:05 +0000 From: To: , CC: , , Dear all, Below is an extract from the draft executive summary of the draft M12 review report. The extract may deviate from the executive summary in the final version of the review report. It is sent since it contains some information, e.g. about deliverable acceptance, that you may want to know asap. Best regards, Arian. ====================== The objectives of the project during this period remain unchanged, but are brought into sharp focus due to the delay of two months plus now apparent, and the critical need to release the complete and comprehensive Generic Enabler (GE) Open Specifications and accompanying reference code as soon as possible in order to not risk destabilizing the entire FI PPP. Many primary technical deliverables expected at M12 are not yet available, which is extremely poor progress given that they are some of the main achievements planned for Month 12 and create the first useable foundation for Use Cases projects to build upon. Compounding this failure is the poor quality and incompleteness of various technical deliverables; a quite astounding result given the resources available to the project. According to the Description of Work (DoW), the main achievements for this period should be the first version of the GE open specifications, software prototypes and related guidance material and test plan. Only the specifications were delivered so far. However, they are inadequate for communication and unified understanding with the Use Case projects, are not of the required quality to serve the needs of those projects, and do not provide sufficient basis for practical implementation by software developers - all of which are fundamental to the rationale for and objectives of FI-WARE. It is unclear in many of the GE specifications which are the reusable and commonly shared functions, and which usage areas across various sectors would utilize these GEs. There are also no details on the protocols that support interoperability with other GEs or third party products or how this interoperability would be achieved. Moreover, a consolidated and consistent presentation of the specifications is still missing. There is a lot of confusion about what the GEs really are, or meant to be, within the FI-WARE consortium, and most probably the UC projects, not to mention the world at large. They are a mixed bag, including functional descriptions, specifications of (not necessarily well-defined) technical functions, specification of access and other operational protocols, specification of access to other existing "modules"/"components"/"devices" and so on, specifications to enable interfaces between existing protocols, specifications to enable deployment of other collection of protocols as "engines", etc. As mentioned in the DoW, "GE Open Specifications will contain all the information required in order to build compliant products which can work as alternative implementations of GEs developed in FI-WARE and therefore may replace a GE implementation developed in FI-WARE within a particular FI-WARE Instance." However, given the current state of the GE deliverables, there are severe doubts about how a FI-WARE instance ("platform") could be built from the GEs without a massive amount of "imagination" and tweaking to make them work together. There are also severe doubts about how a "Future Internet Application" could be portable across different FI-WARE Instances that implement the (same set of?) GEs that the Future Internet Application relies on. The GEs as currently defined are not, by themselves, implementable in the sense of delivering a practical software solution ("platform"). This is compounded by the difficulty of understanding what is really meant by a "coherent" set of GEs. Some GEs seem to have closer inter-relationships than others. Notwithstanding the (useful) clarifications and information orally provided at the review meeting, the inadequate and indeed scarce information within these specifications and the discrepancies between the Technical Roadmap and the available GE contents lead the reviewers to cast doubts on the project achievement so far, and its prospect. FI-WARE failed to meet its milestones for Month 12. Given the above, technical progress of the project for the first year is unacceptable. Moreover, any further delay is likely to significantly risk integrity of the entire FI-PPP and the smooth transition to Phase 2. The consortium made a generally positive and concerted effort so far as the review meeting is concerned. It presented itself as a credible team. The verbal presentations made at the meeting were typically more informative and explanatory than the written deliverables would lead readers to expect (some material within the presentation, such as the matrix of use cases using GEs, is highly appreciated by the reviewers). With evident technical capability, but lack of timely and quality delivery, managerial action is an absolute and urgent must for an accelerated FI-WARE recovery, and to ensure that the FI-PPP programme will deliver meaningful innovations. Collaboration with Use Case projects appears to be improving markedly thanks to key face-to-face training weeks, and enhancements to the way the Fusion Forge system is managed. However, there are still significant issues concerning the processing and documentation of the requirements/backlogs. A main conclusion from the review is that the Use Cases requirements are still not considered as high priority by FI-WARE. Feedback from Use Case projects, including implications for the technology perspective and choices made by FI-WARE, should be (more visibly) taken into account and demonstrated as such. Traceability is crucial for the credibility of the FI-WARE technical deliverables and uptake beyond the consortium; and accountability is required to justify financing from the public purse. The recently conducted architecture training weeks should be used as a stepping stone towards building an FI-PPP "culture" between all Programme participants. More such sessions should be planned, particularly around the test-bed integration deployment and use of the DevComE toolset. For its own part, DevComE is presently a positive highlight of the project. Integration planning for the test-bed is sound and detailed. The testing and the integration activities are among the project highlights. Both are carefully planned and well specified. As the development of the GEs is delayed, the integration activities still lack concreteness in terms of specific scenarios in which several of the GEs will be involved, which is a pity. Work undertaken regarding communication and dissemination is showing significant advancement, albeit with still substantial opportunity for improvement. Given the overall delay in the work plan, the postponement of many key deliverables, and the insufficient quality (and quantity) of the technical specifications, the reviewers consider that the resources were not utilized effectively within the first project year. The consortium has put reasonable effort into analysing and positioning FI-WARE in the current market context. The exploitation within the scope of "Smart Cities" is promising and welcome, but the Use Cases projects should be targeted as prime users. The business strategy is however absent, in so far that no credible and preliminary quantified business case has been presented yet. The consortium's position that the business case will arrive in the second year of the project is a matter of serious concerns; for example, the reviewers have the strong impression that nobody in the consortium has any notion of the overall amount of investment required to take FI-WARE results to the market, and the work presented is clearly (still) lacking substantive input from the business departments of the industrial partners. Despite the extensive comments in the Month 6 Review Report and notwithstanding the voluminous deliverable D11.2.1, there is still no unified or compelling marketing message, including no compelling unique selling proposition, of the FI-WARE results. The individual exploitation plans of the partners are timid. There is inadequate consideration of third party development and SME exploitation at the business level. The globalisation dimension of the exploitation plan is unconvincing. The consortium is reminded that the success of FI-WARE depends on the delivery of a genuine global solution, exploitable by partners inside and outside the consortium and beyond Europe. In summary, there is a glaring and alarming discrepancy between the high ambitions of FI-WARE given in the DoW and the very limited perspective of exploitation offered so far. The reviewers are disappointed that many of the recommendations made - dating back to the Month 6 review or even earlier - have not been sufficiently considered. Additionally, the reviewers are frustrated by the pattern of (extremely) late submission of the majority of the deliverables, and hastily communicated rescheduling of other deliverables with debatable arguments. Such behaviour is not acceptable in the business world; it is equally unacceptable in the context of European collaborative activity, especially in view of the public funding involved. b. Recommendations concerning the period under review The following deliverables require re-submission: * D2.3.1 by Month 15 (from Month 9 review) * D2.4.1 by Month 15 (from Month 9 review) * D2.1.2 by Month 18 * D3.1.1 by Month 18 * D4.1.1 by Month 18 * D5.1.1 by Month 18 * D6.1.1 by Month 18 * D7.1.1 by Month 18 * D8.1.1 by Month 18 * D11.1.1 by Month 18 * D11.2.1 by Month 18 * D11.3.1 by Month 18 The following recommendations are reiterated from the Month 6 review report (with the timeframe for R[1][2]1 adjusted in light of the Month 9 review) and were expected to be addressed in a satisfactory manner by the Month 12 review (original recommendations re-produced in italics): R [1-3]1. Given FI-WARE's intent to remain domain neutral, a comprehensive technology map must be created that clearly and unambiguously illustrates the relationships between all Generic Enablers to be produced by FI-WARE. This was expected to be documented in deliverable D2.3.1 originally due Month 9, for which re-submission is now due Month 15. Still to be addressed in the forthcoming resubmission of D2.3.1 due Month 15. As regards the "transparent encompassing architecture" for FI-WARE as a whole also asked for already in the first recommendation of the review report at M3, we advise the consortium to keep in mind and log this recommendation, and re-visit it in 2013, after the projects selected under Phase 2 have joined the FI PPP. R [1-3]3. Ensure meaningful interaction with standards bodies including Internet-related standards groups such as the IETF, the W3C, the IEEE, the ITU-T, the OMA, and the 3GPP/2. This is expected to be reported in deliverable D12.3.2 due Month 12 and/or deliverable D11.4.1 due Month 9. Still to be addressed in the forthcoming D11.4.2 due Month 15. R [1-3]6. Ensure there is a focus on attracting a development community for FI-WARE, and not only within the FI-PPP, but where possible within the partner organisations and the open community of potential users. This is expected to be considered in relation to deliverable D2.5.1 and reported in deliverable D12.2.2. Still to be addressed in the forthcoming D2.5.1. R [1-3]7. As there is substantial reliance on external technology sources, e.g., other FP7 projects and open source projects, contingencies should be prepared which address what actions to take should those projects fail to deliver, or are delayed with planned delivery upon which FI-WARE depends. This is expected to be documented in deliverable D1.1.2 due Month 12. The sourcing of technology is still not sufficiently clear. Contingency planning is still not adequately provided for or documented in D1.1.2. Please provide an adequate plan in the online version of the Project Management Handbook asap. R [1-3]8. There is a reasonable likelihood that FI-WARE chapters will be unable to achieve all that they would like to. A risk mitigation strategy should be put in place for this, with thought given in advance on how the project plans to prioritise resources if insufficient resources are available to cope with all planned work. This is expected to be documented in deliverable D1.1.2. The consortium is reminded that effort and funding allocations in the DoW are indicative and not sacrosanct. A robust risk management strategy is still missing from D1.1.2. Please provide such a strategy in the online version of the Project Management Handbook asap. R [1-3]9. Make sustained effort to enrol the support of stakeholders from the business and marketing departments of all major commercial partners in the project. External to the consortium, dissemination should go considerably beyond the "traditional groups" that are usually targeted for dissemination in FP7 projects. This concerns both the RTD communities and the business communities at large, within as well as outside Europe. Consumer organisations should also be considered and inputs be sought, to make sure that the FI-PPP results will be successfully adopted by the mass market. This is expected to be reported in deliverable D12.2.2. Progress has been made in relation to dissemination. The active involvement and support of the business and marketing personnel from the industrial project partners is still largely absent. R [1-3]10. Ensure that planning of the Open Calls starts early and the Open Calls are inclusive enough to attract any prospective submitters including specialist SMEs (without making a priori assumptions about who might be interested in the calls). The Open Calls should be used as a strategic opportunity for disseminating FI-WARE to FI stakeholders and engaging their interest in FI-WARE outputs. The Open Call processes and experience, including lessons learnt, should be documented and assimilated by the consortium for subsequent calls, and included in the relevant editions of deliverable D1.2.x for reporting and auditing purposes. Please take into full account our remarks on the management and administration of the Open Calls in Section 1a of the previous (M6) Review Report, and clarify the rationale for the selection of the topic(s) for the forthcoming first Open Call and to what extent the use case projects have a voice in the topic selection in the first and subsequent calls. The reviewers are still awaiting the reporting of the first Open Call. Progress to be re-assessed in relation to the planning/reporting of the next Open Call in the forthcoming D1.3.2. R [1-3]11. The reviewers cannot over-emphasise the importance of exploitation planning, including detailed documentation of IPR management. In our view, this is also intimately linked to enablement of third party exploitation. Please refer to our remarks in Sections 1a and 1b of the previous (M6) Review Report. It is obvious that high expectations are placed by the reviewers on deliverables D11.2.1 and D2.5.1 due Month 12. Please do not treat this as a paper exercise for satisfying the reviewers. Instead, they should be treated as initial blueprints for realistic business models backed by genuine commitment from especially the industrial partners. Unsatisfactory addressed. Exploitation planning lacks credibility and market traction. To be addressed in the resubmission of D11.2.1 due M18. R [1-3]12. All future deliverables should continue to be made available to the reviewers in pdf format. They should also be submitted on time. The consortium should investigate whether posting such files on its website or wiki might provide value for potential users, in addition to the wiki pages (at least those files relating to key deliverables). Please report the findings of the investigation at the next review. Unsatisfactory addressed. Large numbers of deliverables not submitted on time, yet again. Others have been rescheduled in a hasty manner. The reviewers strongly recommend corrective actions. Additionally, the reviewers request that project deliverables be made available as a consolidated file for future reviews. The consortium has no inclination to make deliverables available in a file format, other than to the EC and reviewers for pure compliance purposes, after evident resistance. The need to investigate the usefulness of such files to would-be users was dismissed. R [1-3]13. Improve the usefulness and attractiveness of the project website: make the information (even) more easy to find, bearing in mind that users might not be familiar with the FI-PPP; enhance the website as a marketing tool to would-be third parties and 'customers' of FI-WARE results (make the website answer the question to companies not involved in EU funded activities: why should I be interested in what FI-WARE is doing, and what is in it for me?). Consider the use of creditable Search Engine Optimization techniques. Unsatisfactorily addressed - no evidence of website improvement as a marketing tool. Significant improvement required for Month 17. The consortium is also encouraged to bring forward the implementation of the FI-WARE GE portal (not in DoW, but highly welcome) currently planned for Year 3. R [1-3]14. Put in place contingencies for loss of key people from the project. This is expected to be documented in deliverable D1.1.2. Recommendation addressed to some degree, for example by involving WP leaders in the management of backlog. Please provide a clear update in the online version of the Project Management Handbook asap. Recommendations still outstanding from the initial review of D2.2.1: * R2: the relationship between GEs and the Specific Enablers needs to be clarified and documented, bearing in mind that the former are potential candidates for standardisation in due course, and the latter are critical from the view point of making business out of FI-WARE results. Documentation is now expected at Month 9 with deliverable D2.3.1. Still to be addressed in the resubmitted version of the D2.3.1 due Month 15. * R9: The requested delivery schedule for the GEs, or at a minimum indication of prioritisation, has not been presented. This is now expected for deliverable D2.4.1 at Month 9. The information should be made visibly available in the public domain. Still not addressed, with mismatches between the Backlog, the Technical Roadmap and the Open Specifications delivered; To be addressed in the resubmitted version of the D2.4.1 due Month 15. c. Recommendations concerning future work R[3]15. Ensure that the quality of the GE specifications is high and consistent. Use GE specification for WP8 as a template for all other WPs. R[3]16. Clean up the backlog, and keep it up to date at all times. Specific resources must be dedicated to this. R[3]17. Focus on delivery of critical-path, high-priority (for the Use Cases) GEs. R[3]18. GE code releases must be synchronized with GE priorities indicated by Use Case projects. R[3]19. Ensure that architectural documentation clearly and unambiguously indicates the trace of source requirements and justification. R[3]20. Transparency and visibility in what was delivered and what is going to be delivered by the consortium in all future FI-WARE Releases. R[3]21. Meeting the "check points" set by the reviewers. For the next period leading up to the M18 review, the reviewers will be monitoring and assessing project progress against the following key "check points", in addition to DoW compliance and assessment of the project deliverables due: 1. Technical Paper including common usage scenarios for the GEs for wide dissemination (incl. to Use Case projects and third parties), month 15 2. Public availability matrix of use cases using the GEs; continuous update of the matrix, month 15 & thereafter 3. FI-WARE software release, month 15 4. Public availability of the SAP GEs in WP3, month 15 (done) 5. Testbed in operation, feedback from UC projects on using the testbed, month 17 6. Enhancement/re-design of the current website for impact creation, month 17 7. Hold additional architectural weeks, develop training plan for use of the DevComE framework, consider inviting 3rd party developers, month 18 8. Develop and publish a plan for fostering developer communities, month 18 9. Live demonstration of the FI-WARE test-bed with deployed GE software, Next review meeting 10. Presentation by senior business personnel from the main commercial partners of the consortium (at a minimum: TID, SAP, TI, Orange/FT) on corporate plans to bring the FI-WARE key results to the market, Next review meeting R[3]22. For the next period overall project resource allocation should be reviewed to identify the specific weaknesses leading to the failings identified in this review project; resources should be re-planned and re-allocated to rectify the failings where necessary. d. Assessment Unsatisfactory progress (The project has failed to achieve key objectives and/or is not at all on schedule) ============================== Some other considerations: After one year in the project, one may want to evaluate what has been achieved, esp taking into account that 12 MEuro has been spent. A specific feature of the first reporting period, and a direct result of the delays, is that efforts have been spent on tasks that did not result in submitted deliverables. The economy, effectiveness and efficiency of these efforts can therefore not be evaluated. More importantly, after one year in the project, one may want to evaluate what can be realistically achieved at the end of the project: - The status and maturity of single GEs differ a lot. More consistency and maturity in the specification of GEs needs to be achieved. The litmus test is that these specifications need to be sufficiently mature and complete so that independent software developers can use them to develop implementations that are interchangeable. Prospect: good. - It is not clear to what extent the GE Open Specifications satisfy the requirements from use cases, FI-WARE organisations, or otherwise. There is a risk that at the end of the project the GE Open Specifications do not satisfy the requirements of the use cases. - The baseline assets of each individual GE are not clear. Partly because of this, the roadmap is not clear. At the end of the project, there will be reference implementations, no doubt, but it is not clear to what extent the GE Open Specifications follow the existing baseline assets or v.v. There is a risk that the reference implementations do not satisfy the requirements of the use cases. - The IPR protection of the reference implementations is unclear. At the end of the project, the use cases need clarity on this. It is essential that this information becomes available as soon as possible. - Likewise, the exploitation plans of the owners of the reference implementations are unclear. At the end of the project, the use cases need clarity on this. It is essential that this information becomes available as soon as possible. - The division of budgets in FI-WARE is (largely) based on the existence of baseline assets. The more baseline assets a partner brought into the project, the larger its budget in FI-WARE. The advantage is that the work does not start from scratch. It is likely that these baseline assets are typically proprietary solutions. It can be expected that partners will give priority to their baseline assets, further developing these assets, and give less priority to fulfilling use case requirements. Although access to these assets by use case projects after the end of the FI-WARE project is addressed by clause 41, the exact conditions for access, the availability of the assets, and their maturity are unknown. This leaves use cases, possible FI-WARE Instance providers, and third party application developers in an uncertain situation, and clarity is necessary. - There is a high risk that current developments on GE reference implementations do not fulfil the requirements of the use cases. This could be accepted to some extent if these reference implementations would be based on clear requirements from the business departments of the technology providers, and if there were clear exploitation plans for these reference implementations. In such situation, usefulness to use cases would be offset by wide availability and accessibility. However, at the moment there is a high risk that at the end of the FI-WARE project the reference implementations will not fulfil the requirements from the use cases AND will not be accessible. The month 18 review and the Call 2 evaluation will provide an opportunity to analyse the situation with respect to a) the FI-WARE GEs and their reference implementations, b) the priorities of the phase 2 use cases, and c) the commitments of the FI-WARE beneficiaries. Regarding the FI-WARE GEs and their reference implementations, information is needed a.o. concerning: - The final list of GEs for which Open Specifications will be written - The extent to which these GEs fulfil requirements (from all sources), providing justification and accountability - For each GE: the reference implementation(s) of the GE - For each GE reference implementation: the baseline asset(s) upon which the reference implementation will be based, the current status, the owner, the relation to other GE (reference implementations) Regarding the phase 2 use cases: - The list of GEs the phase 2 use cases plan to use, and their priority - The list of GE reference implementations the phase 2 use cases plan to use, and their priority Regarding the commitment of the FI-WARE beneficiaries: - For each GE reference implementation: the conditions under which it will be available for FI-PPP programme participants and third parties beyond the lifetime of FI-WARE With respect to the last point, stated intentions in confidential exploitation plans are not sufficient. True commitment and therefore true assurance of the use cases and third parties of the sustainability of their efforts building on FI-WARE can be shown via e.g. a public statement by the GE reference implementation IPR holders. Such a public statement could follow lines as sketched below: - "Our developments in FI-WARE/FI-PPP will be made available as open-source, and/or - Our developments in FI-WARE will be proprietary, conforming to the GE Open Specifications, and we guarantee that they will be available on the market as of [date] under FRAND conditions and will be available for at least [y] years. The exact conditions will be specified within [x] months. In case our companies determine the product will no longer be commercially offered, the source code will be made available as open source and donated to [xyz], and/or - Company X is developing an implementation of a certain GE. Within FI-WARE, an open source reference implementation of the same GE is being developed. Company X builds a proprietary implementation, outside the FI-WARE project, using own funds, and/or - Our companies encourage the development of multiple implementations of a certain GE, will develop a reference implementation for each of the specified GEs within the context of the FI-WARE project, using public money, and will develop additional proprietary implementations [for GEs g,h,k] using own funds - We commit to safeguard the evolution and nature of the GEs for at least [x] years after the FI-PPP programme. - Etc" ________________________________ 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: From jhierro at tid.es Mon Jul 30 11:00:09 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 30 Jul 2012 11:00:09 +0200 Subject: [Fiware-wpa] Fwd: FI-WARE: extract executive summary draft review report In-Reply-To: <50164CB7.1060804@tid.es> References: <69AD1A9684E7184DADBE43806285BA9D07CB70@S-DC-ESTF03-B.net1.cec.eu.int> <50164CB7.1060804@tid.es> Message-ID: <50164D19.1080207@tid.es> Hi, Just wanted to add the fiware-pcc, in order to make the dissemination more complete. Don't hesitate to use this as a tool to demonstrate members of your team the need that they take things seriously and deliver. Best regards, -- Juanjo On 30/07/12 10:58, Juanjo Hierro wrote: Dear colleagues, We have just received the following extract of the executive summary draft review report. We haven't had time to review it. But certainly the review report is not as positive as we thought after the first year review meeting. Overall, it is worth to highlight that the project's assestment is: * Unsatisfactory progress (The project has failed to achieve key objectives and/or is not at all on schedule)" This, among other things, confirms us that the recent measurements put in place were required. Now, it's critical to demonstrate that we are going to deliver what was due and that the testbed will not get delayed. We'll come with additional comments later. Best regards, -- Juanjo -------- Original Message -------- Subject: FI-WARE: extract executive summary draft review report Date: Mon, 30 Jul 2012 08:42:05 +0000 From: To: , CC: , , Dear all, Below is an extract from the draft executive summary of the draft M12 review report. The extract may deviate from the executive summary in the final version of the review report. It is sent since it contains some information, e.g. about deliverable acceptance, that you may want to know asap. Best regards, Arian. ====================== The objectives of the project during this period remain unchanged, but are brought into sharp focus due to the delay of two months plus now apparent, and the critical need to release the complete and comprehensive Generic Enabler (GE) Open Specifications and accompanying reference code as soon as possible in order to not risk destabilizing the entire FI PPP. Many primary technical deliverables expected at M12 are not yet available, which is extremely poor progress given that they are some of the main achievements planned for Month 12 and create the first useable foundation for Use Cases projects to build upon. Compounding this failure is the poor quality and incompleteness of various technical deliverables; a quite astounding result given the resources available to the project. According to the Description of Work (DoW), the main achievements for this period should be the first version of the GE open specifications, software prototypes and related guidance material and test plan. Only the specifications were delivered so far. However, they are inadequate for communication and unified understanding with the Use Case projects, are not of the required quality to serve the needs of those projects, and do not provide sufficient basis for practical implementation by software developers - all of which are fundamental to the rationale for and objectives of FI-WARE. It is unclear in many of the GE specifications which are the reusable and commonly shared functions, and which usage areas across various sectors would utilize these GEs. There are also no details on the protocols that support interoperability with other GEs or third party products or how this interoperability would be achieved. Moreover, a consolidated and consistent presentation of the specifications is still missing. There is a lot of confusion about what the GEs really are, or meant to be, within the FI-WARE consortium, and most probably the UC projects, not to mention the world at large. They are a mixed bag, including functional descriptions, specifications of (not necessarily well-defined) technical functions, specification of access and other operational protocols, specification of access to other existing "modules"/"components"/"devices" and so on, specifications to enable interfaces between existing protocols, specifications to enable deployment of other collection of protocols as "engines", etc. As mentioned in the DoW, "GE Open Specifications will contain all the information required in order to build compliant products which can work as alternative implementations of GEs developed in FI-WARE and therefore may replace a GE implementation developed in FI-WARE within a particular FI-WARE Instance." However, given the current state of the GE deliverables, there are severe doubts about how a FI-WARE instance ("platform") could be built from the GEs without a massive amount of "imagination" and tweaking to make them work together. There are also severe doubts about how a "Future Internet Application" could be portable across different FI-WARE Instances that implement the (same set of?) GEs that the Future Internet Application relies on. The GEs as currently defined are not, by themselves, implementable in the sense of delivering a practical software solution ("platform"). This is compounded by the difficulty of understanding what is really meant by a "coherent" set of GEs. Some GEs seem to have closer inter-relationships than others. Notwithstanding the (useful) clarifications and information orally provided at the review meeting, the inadequate and indeed scarce information within these specifications and the discrepancies between the Technical Roadmap and the available GE contents lead the reviewers to cast doubts on the project achievement so far, and its prospect. FI-WARE failed to meet its milestones for Month 12. Given the above, technical progress of the project for the first year is unacceptable. Moreover, any further delay is likely to significantly risk integrity of the entire FI-PPP and the smooth transition to Phase 2. The consortium made a generally positive and concerted effort so far as the review meeting is concerned. It presented itself as a credible team. The verbal presentations made at the meeting were typically more informative and explanatory than the written deliverables would lead readers to expect (some material within the presentation, such as the matrix of use cases using GEs, is highly appreciated by the reviewers). With evident technical capability, but lack of timely and quality delivery, managerial action is an absolute and urgent must for an accelerated FI-WARE recovery, and to ensure that the FI-PPP programme will deliver meaningful innovations. Collaboration with Use Case projects appears to be improving markedly thanks to key face-to-face training weeks, and enhancements to the way the Fusion Forge system is managed. However, there are still significant issues concerning the processing and documentation of the requirements/backlogs. A main conclusion from the review is that the Use Cases requirements are still not considered as high priority by FI-WARE. Feedback from Use Case projects, including implications for the technology perspective and choices made by FI-WARE, should be (more visibly) taken into account and demonstrated as such. Traceability is crucial for the credibility of the FI-WARE technical deliverables and uptake beyond the consortium; and accountability is required to justify financing from the public purse. The recently conducted architecture training weeks should be used as a stepping stone towards building an FI-PPP "culture" between all Programme participants. More such sessions should be planned, particularly around the test-bed integration deployment and use of the DevComE toolset. For its own part, DevComE is presently a positive highlight of the project. Integration planning for the test-bed is sound and detailed. The testing and the integration activities are among the project highlights. Both are carefully planned and well specified. As the development of the GEs is delayed, the integration activities still lack concreteness in terms of specific scenarios in which several of the GEs will be involved, which is a pity. Work undertaken regarding communication and dissemination is showing significant advancement, albeit with still substantial opportunity for improvement. Given the overall delay in the work plan, the postponement of many key deliverables, and the insufficient quality (and quantity) of the technical specifications, the reviewers consider that the resources were not utilized effectively within the first project year. The consortium has put reasonable effort into analysing and positioning FI-WARE in the current market context. The exploitation within the scope of "Smart Cities" is promising and welcome, but the Use Cases projects should be targeted as prime users. The business strategy is however absent, in so far that no credible and preliminary quantified business case has been presented yet. The consortium's position that the business case will arrive in the second year of the project is a matter of serious concerns; for example, the reviewers have the strong impression that nobody in the consortium has any notion of the overall amount of investment required to take FI-WARE results to the market, and the work presented is clearly (still) lacking substantive input from the business departments of the industrial partners. Despite the extensive comments in the Month 6 Review Report and notwithstanding the voluminous deliverable D11.2.1, there is still no unified or compelling marketing message, including no compelling unique selling proposition, of the FI-WARE results. The individual exploitation plans of the partners are timid. There is inadequate consideration of third party development and SME exploitation at the business level. The globalisation dimension of the exploitation plan is unconvincing. The consortium is reminded that the success of FI-WARE depends on the delivery of a genuine global solution, exploitable by partners inside and outside the consortium and beyond Europe. In summary, there is a glaring and alarming discrepancy between the high ambitions of FI-WARE given in the DoW and the very limited perspective of exploitation offered so far. The reviewers are disappointed that many of the recommendations made - dating back to the Month 6 review or even earlier - have not been sufficiently considered. Additionally, the reviewers are frustrated by the pattern of (extremely) late submission of the majority of the deliverables, and hastily communicated rescheduling of other deliverables with debatable arguments. Such behaviour is not acceptable in the business world; it is equally unacceptable in the context of European collaborative activity, especially in view of the public funding involved. b. Recommendations concerning the period under review The following deliverables require re-submission: * D2.3.1 by Month 15 (from Month 9 review) * D2.4.1 by Month 15 (from Month 9 review) * D2.1.2 by Month 18 * D3.1.1 by Month 18 * D4.1.1 by Month 18 * D5.1.1 by Month 18 * D6.1.1 by Month 18 * D7.1.1 by Month 18 * D8.1.1 by Month 18 * D11.1.1 by Month 18 * D11.2.1 by Month 18 * D11.3.1 by Month 18 The following recommendations are reiterated from the Month 6 review report (with the timeframe for R[1][2]1 adjusted in light of the Month 9 review) and were expected to be addressed in a satisfactory manner by the Month 12 review (original recommendations re-produced in italics): R [1-3]1. Given FI-WARE's intent to remain domain neutral, a comprehensive technology map must be created that clearly and unambiguously illustrates the relationships between all Generic Enablers to be produced by FI-WARE. This was expected to be documented in deliverable D2.3.1 originally due Month 9, for which re-submission is now due Month 15. Still to be addressed in the forthcoming resubmission of D2.3.1 due Month 15. As regards the "transparent encompassing architecture" for FI-WARE as a whole also asked for already in the first recommendation of the review report at M3, we advise the consortium to keep in mind and log this recommendation, and re-visit it in 2013, after the projects selected under Phase 2 have joined the FI PPP. R [1-3]3. Ensure meaningful interaction with standards bodies including Internet-related standards groups such as the IETF, the W3C, the IEEE, the ITU-T, the OMA, and the 3GPP/2. This is expected to be reported in deliverable D12.3.2 due Month 12 and/or deliverable D11.4.1 due Month 9. Still to be addressed in the forthcoming D11.4.2 due Month 15. R [1-3]6. Ensure there is a focus on attracting a development community for FI-WARE, and not only within the FI-PPP, but where possible within the partner organisations and the open community of potential users. This is expected to be considered in relation to deliverable D2.5.1 and reported in deliverable D12.2.2. Still to be addressed in the forthcoming D2.5.1. R [1-3]7. As there is substantial reliance on external technology sources, e.g., other FP7 projects and open source projects, contingencies should be prepared which address what actions to take should those projects fail to deliver, or are delayed with planned delivery upon which FI-WARE depends. This is expected to be documented in deliverable D1.1.2 due Month 12. The sourcing of technology is still not sufficiently clear. Contingency planning is still not adequately provided for or documented in D1.1.2. Please provide an adequate plan in the online version of the Project Management Handbook asap. R [1-3]8. There is a reasonable likelihood that FI-WARE chapters will be unable to achieve all that they would like to. A risk mitigation strategy should be put in place for this, with thought given in advance on how the project plans to prioritise resources if insufficient resources are available to cope with all planned work. This is expected to be documented in deliverable D1.1.2. The consortium is reminded that effort and funding allocations in the DoW are indicative and not sacrosanct. A robust risk management strategy is still missing from D1.1.2. Please provide such a strategy in the online version of the Project Management Handbook asap. R [1-3]9. Make sustained effort to enrol the support of stakeholders from the business and marketing departments of all major commercial partners in the project. External to the consortium, dissemination should go considerably beyond the "traditional groups" that are usually targeted for dissemination in FP7 projects. This concerns both the RTD communities and the business communities at large, within as well as outside Europe. Consumer organisations should also be considered and inputs be sought, to make sure that the FI-PPP results will be successfully adopted by the mass market. This is expected to be reported in deliverable D12.2.2. Progress has been made in relation to dissemination. The active involvement and support of the business and marketing personnel from the industrial project partners is still largely absent. R [1-3]10. Ensure that planning of the Open Calls starts early and the Open Calls are inclusive enough to attract any prospective submitters including specialist SMEs (without making a priori assumptions about who might be interested in the calls). The Open Calls should be used as a strategic opportunity for disseminating FI-WARE to FI stakeholders and engaging their interest in FI-WARE outputs. The Open Call processes and experience, including lessons learnt, should be documented and assimilated by the consortium for subsequent calls, and included in the relevant editions of deliverable D1.2.x for reporting and auditing purposes. Please take into full account our remarks on the management and administration of the Open Calls in Section 1a of the previous (M6) Review Report, and clarify the rationale for the selection of the topic(s) for the forthcoming first Open Call and to what extent the use case projects have a voice in the topic selection in the first and subsequent calls. The reviewers are still awaiting the reporting of the first Open Call. Progress to be re-assessed in relation to the planning/reporting of the next Open Call in the forthcoming D1.3.2. R [1-3]11. The reviewers cannot over-emphasise the importance of exploitation planning, including detailed documentation of IPR management. In our view, this is also intimately linked to enablement of third party exploitation. Please refer to our remarks in Sections 1a and 1b of the previous (M6) Review Report. It is obvious that high expectations are placed by the reviewers on deliverables D11.2.1 and D2.5.1 due Month 12. Please do not treat this as a paper exercise for satisfying the reviewers. Instead, they should be treated as initial blueprints for realistic business models backed by genuine commitment from especially the industrial partners. Unsatisfactory addressed. Exploitation planning lacks credibility and market traction. To be addressed in the resubmission of D11.2.1 due M18. R [1-3]12. All future deliverables should continue to be made available to the reviewers in pdf format. They should also be submitted on time. The consortium should investigate whether posting such files on its website or wiki might provide value for potential users, in addition to the wiki pages (at least those files relating to key deliverables). Please report the findings of the investigation at the next review. Unsatisfactory addressed. Large numbers of deliverables not submitted on time, yet again. Others have been rescheduled in a hasty manner. The reviewers strongly recommend corrective actions. Additionally, the reviewers request that project deliverables be made available as a consolidated file for future reviews. The consortium has no inclination to make deliverables available in a file format, other than to the EC and reviewers for pure compliance purposes, after evident resistance. The need to investigate the usefulness of such files to would-be users was dismissed. R [1-3]13. Improve the usefulness and attractiveness of the project website: make the information (even) more easy to find, bearing in mind that users might not be familiar with the FI-PPP; enhance the website as a marketing tool to would-be third parties and 'customers' of FI-WARE results (make the website answer the question to companies not involved in EU funded activities: why should I be interested in what FI-WARE is doing, and what is in it for me?). Consider the use of creditable Search Engine Optimization techniques. Unsatisfactorily addressed - no evidence of website improvement as a marketing tool. Significant improvement required for Month 17. The consortium is also encouraged to bring forward the implementation of the FI-WARE GE portal (not in DoW, but highly welcome) currently planned for Year 3. R [1-3]14. Put in place contingencies for loss of key people from the project. This is expected to be documented in deliverable D1.1.2. Recommendation addressed to some degree, for example by involving WP leaders in the management of backlog. Please provide a clear update in the online version of the Project Management Handbook asap. Recommendations still outstanding from the initial review of D2.2.1: * R2: the relationship between GEs and the Specific Enablers needs to be clarified and documented, bearing in mind that the former are potential candidates for standardisation in due course, and the latter are critical from the view point of making business out of FI-WARE results. Documentation is now expected at Month 9 with deliverable D2.3.1. Still to be addressed in the resubmitted version of the D2.3.1 due Month 15. * R9: The requested delivery schedule for the GEs, or at a minimum indication of prioritisation, has not been presented. This is now expected for deliverable D2.4.1 at Month 9. The information should be made visibly available in the public domain. Still not addressed, with mismatches between the Backlog, the Technical Roadmap and the Open Specifications delivered; To be addressed in the resubmitted version of the D2.4.1 due Month 15. c. Recommendations concerning future work R[3]15. Ensure that the quality of the GE specifications is high and consistent. Use GE specification for WP8 as a template for all other WPs. R[3]16. Clean up the backlog, and keep it up to date at all times. Specific resources must be dedicated to this. R[3]17. Focus on delivery of critical-path, high-priority (for the Use Cases) GEs. R[3]18. GE code releases must be synchronized with GE priorities indicated by Use Case projects. R[3]19. Ensure that architectural documentation clearly and unambiguously indicates the trace of source requirements and justification. R[3]20. Transparency and visibility in what was delivered and what is going to be delivered by the consortium in all future FI-WARE Releases. R[3]21. Meeting the "check points" set by the reviewers. For the next period leading up to the M18 review, the reviewers will be monitoring and assessing project progress against the following key "check points", in addition to DoW compliance and assessment of the project deliverables due: 1. Technical Paper including common usage scenarios for the GEs for wide dissemination (incl. to Use Case projects and third parties), month 15 2. Public availability matrix of use cases using the GEs; continuous update of the matrix, month 15 & thereafter 3. FI-WARE software release, month 15 4. Public availability of the SAP GEs in WP3, month 15 (done) 5. Testbed in operation, feedback from UC projects on using the testbed, month 17 6. Enhancement/re-design of the current website for impact creation, month 17 7. Hold additional architectural weeks, develop training plan for use of the DevComE framework, consider inviting 3rd party developers, month 18 8. Develop and publish a plan for fostering developer communities, month 18 9. Live demonstration of the FI-WARE test-bed with deployed GE software, Next review meeting 10. Presentation by senior business personnel from the main commercial partners of the consortium (at a minimum: TID, SAP, TI, Orange/FT) on corporate plans to bring the FI-WARE key results to the market, Next review meeting R[3]22. For the next period overall project resource allocation should be reviewed to identify the specific weaknesses leading to the failings identified in this review project; resources should be re-planned and re-allocated to rectify the failings where necessary. d. Assessment Unsatisfactory progress (The project has failed to achieve key objectives and/or is not at all on schedule) ============================== Some other considerations: After one year in the project, one may want to evaluate what has been achieved, esp taking into account that 12 MEuro has been spent. A specific feature of the first reporting period, and a direct result of the delays, is that efforts have been spent on tasks that did not result in submitted deliverables. The economy, effectiveness and efficiency of these efforts can therefore not be evaluated. More importantly, after one year in the project, one may want to evaluate what can be realistically achieved at the end of the project: - The status and maturity of single GEs differ a lot. More consistency and maturity in the specification of GEs needs to be achieved. The litmus test is that these specifications need to be sufficiently mature and complete so that independent software developers can use them to develop implementations that are interchangeable. Prospect: good. - It is not clear to what extent the GE Open Specifications satisfy the requirements from use cases, FI-WARE organisations, or otherwise. There is a risk that at the end of the project the GE Open Specifications do not satisfy the requirements of the use cases. - The baseline assets of each individual GE are not clear. Partly because of this, the roadmap is not clear. At the end of the project, there will be reference implementations, no doubt, but it is not clear to what extent the GE Open Specifications follow the existing baseline assets or v.v. There is a risk that the reference implementations do not satisfy the requirements of the use cases. - The IPR protection of the reference implementations is unclear. At the end of the project, the use cases need clarity on this. It is essential that this information becomes available as soon as possible. - Likewise, the exploitation plans of the owners of the reference implementations are unclear. At the end of the project, the use cases need clarity on this. It is essential that this information becomes available as soon as possible. - The division of budgets in FI-WARE is (largely) based on the existence of baseline assets. The more baseline assets a partner brought into the project, the larger its budget in FI-WARE. The advantage is that the work does not start from scratch. It is likely that these baseline assets are typically proprietary solutions. It can be expected that partners will give priority to their baseline assets, further developing these assets, and give less priority to fulfilling use case requirements. Although access to these assets by use case projects after the end of the FI-WARE project is addressed by clause 41, the exact conditions for access, the availability of the assets, and their maturity are unknown. This leaves use cases, possible FI-WARE Instance providers, and third party application developers in an uncertain situation, and clarity is necessary. - There is a high risk that current developments on GE reference implementations do not fulfil the requirements of the use cases. This could be accepted to some extent if these reference implementations would be based on clear requirements from the business departments of the technology providers, and if there were clear exploitation plans for these reference implementations. In such situation, usefulness to use cases would be offset by wide availability and accessibility. However, at the moment there is a high risk that at the end of the FI-WARE project the reference implementations will not fulfil the requirements from the use cases AND will not be accessible. The month 18 review and the Call 2 evaluation will provide an opportunity to analyse the situation with respect to a) the FI-WARE GEs and their reference implementations, b) the priorities of the phase 2 use cases, and c) the commitments of the FI-WARE beneficiaries. Regarding the FI-WARE GEs and their reference implementations, information is needed a.o. concerning: - The final list of GEs for which Open Specifications will be written - The extent to which these GEs fulfil requirements (from all sources), providing justification and accountability - For each GE: the reference implementation(s) of the GE - For each GE reference implementation: the baseline asset(s) upon which the reference implementation will be based, the current status, the owner, the relation to other GE (reference implementations) Regarding the phase 2 use cases: - The list of GEs the phase 2 use cases plan to use, and their priority - The list of GE reference implementations the phase 2 use cases plan to use, and their priority Regarding the commitment of the FI-WARE beneficiaries: - For each GE reference implementation: the conditions under which it will be available for FI-PPP programme participants and third parties beyond the lifetime of FI-WARE With respect to the last point, stated intentions in confidential exploitation plans are not sufficient. True commitment and therefore true assurance of the use cases and third parties of the sustainability of their efforts building on FI-WARE can be shown via e.g. a public statement by the GE reference implementation IPR holders. Such a public statement could follow lines as sketched below: - "Our developments in FI-WARE/FI-PPP will be made available as open-source, and/or - Our developments in FI-WARE will be proprietary, conforming to the GE Open Specifications, and we guarantee that they will be available on the market as of [date] under FRAND conditions and will be available for at least [y] years. The exact conditions will be specified within [x] months. In case our companies determine the product will no longer be commercially offered, the source code will be made available as open source and donated to [xyz], and/or - Company X is developing an implementation of a certain GE. Within FI-WARE, an open source reference implementation of the same GE is being developed. Company X builds a proprietary implementation, outside the FI-WARE project, using own funds, and/or - Our companies encourage the development of multiple implementations of a certain GE, will develop a reference implementation for each of the specified GEs within the context of the FI-WARE project, using public money, and will develop additional proprietary implementations [for GEs g,h,k] using own funds - We commit to safeguard the evolution and nature of the GEs for at least [x] years after the FI-PPP programme. - Etc" ________________________________ 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: From jhierro at tid.es Mon Jul 30 11:34:49 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 30 Jul 2012 11:34:49 +0200 Subject: [Fiware-wpa] Doodle poll for URGENT confcall dealing with analysis and reaction to executive summary of FI-WARE review report Message-ID: <50165539.6030909@tid.es> Hi all, Here it is the doodle to find out the time for the confcall tomorrow: http://www.doodle.com/qkgryy9wxx7safzr We will close the poll at 15:00 CET. Best regards -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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: From jhierro at tid.es Mon Jul 30 16:30:39 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 30 Jul 2012 16:30:39 +0200 Subject: [Fiware-wpa] Confcall - analysis of Review Report month 12 Message-ID: <50169A8F.3000909@tid.es> Hi all, Based on results of the doodle poll, let's plan it for tomorrow, starting 12:00pm CET. Confcall bridge will be as usual. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 From jhierro at tid.es Mon Jul 30 16:32:23 2012 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Mon, 30 Jul 2012 14:32:23 +0000 Subject: [Fiware-wpa] Analysis of RI-WARE 1st Year Review Report (executive summary) Message-ID: <936DECD07EB54B4BAA44E7B823EC89411C5DB7A5@EX10-MB2-MAD.hi.inet> When: Tuesday, July 31, 2012 12:00 PM-2:00 PM. (UTC+01:00) Brussels, Copenhagen, Madrid, Paris *~*~*~*~*~*~*~*~*~* We'll use powwownow. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf ________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2202 bytes Desc: not available URL: From axel.fasse at sap.com Tue Jul 31 10:34:50 2012 From: axel.fasse at sap.com (Fasse, Axel) Date: Tue, 31 Jul 2012 10:34:50 +0200 Subject: [Fiware-wpa] FW: Please note: Work on D.2.5.a Third Party Innovation In-Reply-To: <50178B9C.6050006@tid.es> References: <1491C91A94302A448D73CD9C6B7A782046C04552D1@DEWDFECCR02.wdf.sap.corp> <2C6296E1876B5C49962495FDACDC7A6361673F49CB@DEWDFECCR01.wdf.sap.corp> <50178B9C.6050006@tid.es> Message-ID: <2C6296E1876B5C49962495FDACDC7A6361674DB041@DEWDFECCR01.wdf.sap.corp> Dear Juanjo, der partners, thank you very much for your contribution. It would be very helpful for us, if all of the involved WPL's and WPA's send a mail to Juanjo, Uwe and me that indicates that their contribution is the final contribution. Because of the missed deadline yesterday, please try to finalize your contribution until today (EOB) and take into account the comments from Juanjo. Otherwise we are not able to finalize the deliverable and might get in additional trouble with the EU. If you have any questions, please let us (Juanjo, Use and me) know. Best regards, Axel From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Dienstag, 31. Juli 2012 09:39 To: Fasse, Axel Cc: fiware-wpl at lists.fi-ware.eu Subject: Re: FW: Please note: Work on D.2.5.a Third Party Innovation Hi all, I have fulfilled all my assignments but the final section on Conclusions but I believe it is better to wait for that one until the rest of the document is finished. My contributions on section 1 and 2 are there for SAP to review. I have also provided comments in the rest of sections. I agree with Uwe in that not all the contributions are in a good shape as to carry out a final review. In some cases will not only be a matter of bringing valuable content but present it in coherent way, i.e., more aligned with the reference example provided by SAP. I expect SAP will continue pushing for consolidation of this section 3 of the document giving more detailed instructions, if necessary, about how to achieve this alignment. Best regards, -- Juanjo On 30/07/12 15:25, Fasse, Axel wrote: Dear Juanjo, With the clarification from Uwe, the responsibility are completely clear assigned. If you need further clarifications, please let me know. Best regards, Axel From: Riss, Uwe Sent: Montag, 30. Juli 2012 13:54 To: Stefano de Panfilis; Matteo Melideo; Pascal Bisson; Pierangelo Garino; Juanjo Hierro; Thierry Nagellen; Alex Glikson Cc: Fasse, Axel Subject: Please note: Work on D.2.5.a Third Party Innovation Dear Juanjo and Colleagues, Last Friday I sent you some feedback regarding the last review of your contributions to Deliverable D.2.5 about Third Party Innovation. Due to a technical problem since I was not in my office, I was not able to send my comments directly to you on Friday. In order to ensure that Telefonica (as coordinator) can deliver this deliverables accordingly the new timeline "in time", I want to mention, that there are some open issues that should be handled within until today (EOB). Chapter 1 --> Task for Telefonica: Completion and finalization of the SAP contribution Chapter 2 --> Task for Telefonica: First Draft of the chapter content, review by SAP Chapter 3 -->Task for all WPL/WPA's and their contributing partners: Follow the instructions of Telefonica (Juanjo) to ensure that your contribution is a final. Actually some of the contributions are not in satisfactory state to start the review process. The first (final) version of the requested WP-subchapters should be provided by you! Chapter 4 --> Task for Telefonica: Please provide a first draft of the conclusion that could be adjusted - if it is required - within the final reviews Please take into account the very close timeline: Timeline: 9. July - introduction provided to partners/chapters 9. July - 20. July contributions by partners/chapters 30. July - final version ready for review Review: 2. August - Peer reviewer 1 5. August - Review by Deliverable Lead 10. August - Release to commission I would suggest that Telefonica assigns the reviewers within the document to avoid any lack of clarity reagrding the responsibilities. Currently I am on vacations but I hope that my support has helped our colleagues from Telefonica to reach the planned timeline. If you have any questions about the timeline or the technical issues with the document, please ask Axel Fasse for support. If you have any questions about the focus of your contributions or the "over-all" strategy behind the deliverable, please ask these questions directly to Juanjo as the coordinator. Best regards, Uwe From: Riss, Uwe Sent: Donnerstag, 26. Juli 2012 10:35 To: Stefano de Panfilis; Matteo Melideo; Pascal Bisson; Pierangelo Garino; Juanjo Hierro; Thierry Nagellen; Alex Glikson Cc: Fasse, Axel Subject: Work on D.2.5.a Third Party Innovation Dear Colleagues, Since some of you are not able to provide the required revision in the proposed timeframe I'd suggest a new timeline for the revision of the document as proposed in the WPL/WPA call, which reads as follows: * 30. July - final version ready for review For the review: * 2. August - Peer reviewer 1 * 5. August - Review by Deliverable Lead * 10. August - Release to commission I have kept the timeline exigent since many contributions are already in a good shape. Please feel free to contact me if you have any questions. Next week I will not be in the office and Axel Fasse will take over the coordination for that period of time. Best regards, Uwe PS The document: https://docs.google.com/document/d/1HnmGAJ7LuHJs9oBIhVwbR9LuKMK-Xhb_c7SF-EVQi_Q/edit Dr. Uwe Riss Senior Researcher, Internet Applications & Services | SAP Research Karlsruhe SAP AG | Vincenz-Priessnitz-Str. 1 | 76131 Karlsruhe | Germany T +49 6227 7-70212 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Geschaeftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdruecklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. ________________________________ 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: From pierangelo.garino at telecomitalia.it Tue Jul 31 11:25:09 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 31 Jul 2012 11:25:09 +0200 Subject: [Fiware-wpa] R: [Fiware-wpl] FW: Please note: Work on D.2.5.a Third Party Innovation In-Reply-To: <2C6296E1876B5C49962495FDACDC7A6361674DB041@DEWDFECCR01.wdf.sap.corp> References: <1491C91A94302A448D73CD9C6B7A782046C04552D1@DEWDFECCR02.wdf.sap.corp> <2C6296E1876B5C49962495FDACDC7A6361673F49CB@DEWDFECCR01.wdf.sap.corp> <50178B9C.6050006@tid.es> <2C6296E1876B5C49962495FDACDC7A6361674DB041@DEWDFECCR01.wdf.sap.corp> Message-ID: Dear Axel, I have asked the I2ND members in charge of this document to perform a final check and update, based on the comments by Juanjo, with a deadline for today EOB. BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Fasse, Axel Inviato: marted? 31 luglio 2012 10:35 A: Juanjo Hierro; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: Re: [Fiware-wpl] FW: Please note: Work on D.2.5.a Third Party Innovation Dear Juanjo, der partners, thank you very much for your contribution. It would be very helpful for us, if all of the involved WPL's and WPA's send a mail to Juanjo, Uwe and me that indicates that their contribution is the final contribution. Because of the missed deadline yesterday, please try to finalize your contribution until today (EOB) and take into account the comments from Juanjo. Otherwise we are not able to finalize the deliverable and might get in additional trouble with the EU. If you have any questions, please let us (Juanjo, Use and me) know. Best regards, Axel From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Dienstag, 31. Juli 2012 09:39 To: Fasse, Axel Cc: fiware-wpl at lists.fi-ware.eu Subject: Re: FW: Please note: Work on D.2.5.a Third Party Innovation Hi all, I have fulfilled all my assignments but the final section on Conclusions but I believe it is better to wait for that one until the rest of the document is finished. My contributions on section 1 and 2 are there for SAP to review. I have also provided comments in the rest of sections. I agree with Uwe in that not all the contributions are in a good shape as to carry out a final review. In some cases will not only be a matter of bringing valuable content but present it in coherent way, i.e., more aligned with the reference example provided by SAP. I expect SAP will continue pushing for consolidation of this section 3 of the document giving more detailed instructions, if necessary, about how to achieve this alignment. Best regards, -- Juanjo On 30/07/12 15:25, Fasse, Axel wrote: Dear Juanjo, With the clarification from Uwe, the responsibility are completely clear assigned. If you need further clarifications, please let me know. Best regards, Axel From: Riss, Uwe Sent: Montag, 30. Juli 2012 13:54 To: Stefano de Panfilis; Matteo Melideo; Pascal Bisson; Pierangelo Garino; Juanjo Hierro; Thierry Nagellen; Alex Glikson Cc: Fasse, Axel Subject: Please note: Work on D.2.5.a Third Party Innovation Dear Juanjo and Colleagues, Last Friday I sent you some feedback regarding the last review of your contributions to Deliverable D.2.5 about Third Party Innovation. Due to a technical problem since I was not in my office, I was not able to send my comments directly to you on Friday. In order to ensure that Telefonica (as coordinator) can deliver this deliverables accordingly the new timeline "in time", I want to mention, that there are some open issues that should be handled within until today (EOB). Chapter 1 --> Task for Telefonica: Completion and finalization of the SAP contribution Chapter 2 --> Task for Telefonica: First Draft of the chapter content, review by SAP Chapter 3 -->Task for all WPL/WPA's and their contributing partners: Follow the instructions of Telefonica (Juanjo) to ensure that your contribution is a final. Actually some of the contributions are not in satisfactory state to start the review process. The first (final) version of the requested WP-subchapters should be provided by you! Chapter 4 --> Task for Telefonica: Please provide a first draft of the conclusion that could be adjusted - if it is required - within the final reviews Please take into account the very close timeline: Timeline: 9. July - introduction provided to partners/chapters 9. July - 20. July contributions by partners/chapters 30. July - final version ready for review Review: 2. August - Peer reviewer 1 5. August - Review by Deliverable Lead 10. August - Release to commission I would suggest that Telefonica assigns the reviewers within the document to avoid any lack of clarity reagrding the responsibilities. Currently I am on vacations but I hope that my support has helped our colleagues from Telefonica to reach the planned timeline. If you have any questions about the timeline or the technical issues with the document, please ask Axel Fasse for support. If you have any questions about the focus of your contributions or the "over-all" strategy behind the deliverable, please ask these questions directly to Juanjo as the coordinator. Best regards, Uwe From: Riss, Uwe Sent: Donnerstag, 26. Juli 2012 10:35 To: Stefano de Panfilis; Matteo Melideo; Pascal Bisson; Pierangelo Garino; Juanjo Hierro; Thierry Nagellen; Alex Glikson Cc: Fasse, Axel Subject: Work on D.2.5.a Third Party Innovation Dear Colleagues, Since some of you are not able to provide the required revision in the proposed timeframe I'd suggest a new timeline for the revision of the document as proposed in the WPL/WPA call, which reads as follows: * 30. July - final version ready for review For the review: * 2. August - Peer reviewer 1 * 5. August - Review by Deliverable Lead * 10. August - Release to commission I have kept the timeline exigent since many contributions are already in a good shape. Please feel free to contact me if you have any questions. Next week I will not be in the office and Axel Fasse will take over the coordination for that period of time. Best regards, Uwe PS The document: https://docs.google.com/document/d/1HnmGAJ7LuHJs9oBIhVwbR9LuKMK-Xhb_c7SF-EVQi_Q/edit Dr. Uwe Riss Senior Researcher, Internet Applications & Services | SAP Research Karlsruhe SAP AG | Vincenz-Priessnitz-Str. 1 | 76131 Karlsruhe | Germany T +49 6227 7-70212 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Geschaeftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdruecklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. ________________________________ 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: -------------- 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: From jhierro at tid.es Tue Jul 31 11:48:54 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 31 Jul 2012 11:48:54 +0200 Subject: [Fiware-wpa] Shared minutes for the confcall on analysis of the 1st year review report Message-ID: <5017AA06.6050405@tid.es> Hi all, Please find the link of the shared minutes we will use during the confcall in few minutes: https://docs.google.com/document/d/1ApAhu-8qD8FV6dGqAyMSvm-wLA_S2sQ0u49kOUGwtM8/edit Note that we will start a little bit later: 12:15. Sorry but I cannot make it earlier. You can take that time though to take a look at the thoughts I have added in the minutes about goals to fulfill in the short-term. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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: From jhierro at tid.es Tue Jul 31 11:48:55 2012 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Tue, 31 Jul 2012 09:48:55 +0000 Subject: [Fiware-wpa] Analysis of RI-WARE 1st Year Review Report (executive summary) Message-ID: <936DECD07EB54B4BAA44E7B823EC89411FA8BFCA@EX10-MB2-MAD.hi.inet> When: Tuesday, July 31, 2012 12:15 PM-2:15 PM. (UTC+01:00) Brussels, Copenhagen, Madrid, Paris *~*~*~*~*~*~*~*~*~* We'll use powwownow. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf ________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3057 bytes Desc: not available URL: From davide.dallecarbonare at eng.it Tue Jul 31 12:04:14 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Tue, 31 Jul 2012 12:04:14 +0200 Subject: [Fiware-wpa] Catalogue: missing GE implementations Message-ID: <5017AD9E.3090806@eng.it> Dear partners, here is the report, as required yesterday during the WPL/WPA conf call, of the GE implementations that are still missing on the Catalogue. It's not always easy to map the names used on the Catalogue with the ones reported on the Testbed dashboard to monitor the deployment status. It's useless to say that this mismatch doesn't contribute to keep the situation clear, nor for us neither for UC projects. APPS: - all 4 Composition Editor (DT, EAB, UPM, ATOS) - all 3 Composition Execution (DT, EAB, UPM) CLOUD: IOT: - (Backend) Things Management/Configuration Management - is this the unpublished "Things Management GE"? - (Backend) Things Management/IoT broker - is this the unpublished "Things Management GE"? - (Gateway) Data Handling/SOL/CEP - (Gateway) Device Management - (Backend) Device Management GE - publish it asap DATA: - Publish/Subscribe Broker GE - Semantic Annotator GE - Location Server GE - Semantic Application Support GE - Meta-data Annotation GE I2ND: SEC: - Identity Management GE GCP - Data Handling GE - Security Storage Service - Attack-Paths Engine I've reported this list also on the minutes of yesterday conf call. BR Davide. -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefano.depanfilis at eng.it Tue Jul 31 14:39:55 2012 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Tue, 31 Jul 2012 14:39:55 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Confcall - analysis of Review Report month 12 In-Reply-To: <50169A8F.3000909@tid.es> References: <50169A8F.3000909@tid.es> Message-ID: dear juanjo and all, as discussed during the call, here it is a form and writing deliverable guidlines for peer review. i think this short doc should be put in the project quality plan deliverbale. ciao, stefano 2012/7/30 Juanjo Hierro > Hi all, > > Based on results of the doodle poll, let's plan it for tomorrow, > starting 12:00pm CET. > > Confcall bridge will be as usual. > > Cheers, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website: www.tid.es > email: jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Chief Architect > > You can follow FI-WARE at: > 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 > ______________________________**_________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > http://lists.fi-ware.eu/**listinfo/fiware-wpl > > -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Quality Plan - Review Form.doc Type: application/msword Size: 86016 bytes Desc: not available URL: From mcp at tid.es Tue Jul 31 16:08:11 2012 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 31 Jul 2012 16:08:11 +0200 Subject: [Fiware-wpa] Catalogue: missing GE implementations In-Reply-To: <5017AD9E.3090806@eng.it> References: <5017AD9E.3090806@eng.it> Message-ID: <5017E6CB.6000801@tid.es> Hi Thank you, Davide. I encountered the same problem in my initial reviews in the wiki. People tend to neglect the "official" name of the GE and use particular names that confuses someone not familiar with them. Entries in the catalogue with wrong names should be rejected. WPLs: Please tell your parters to react (and to stick to the official GE names!) Torsten, Thierry/Lorant, Carlos and Pascal, please distribute this and make sure that this is settled, I do not think it is such a complicated thing. Best regards, Miguel El 31/07/2012 12:04, Davide Dalle Carbonare escribi?: Dear partners, here is the report, as required yesterday during the WPL/WPA conf call, of the GE implementations that are still missing on the Catalogue. It's not always easy to map the names used on the Catalogue with the ones reported on the Testbed dashboard to monitor the deployment status. It's useless to say that this mismatch doesn't contribute to keep the situation clear, nor for us neither for UC projects. APPS: - all 4 Composition Editor (DT, EAB, UPM, ATOS) - all 3 Composition Execution (DT, EAB, UPM) CLOUD: IOT: - (Backend) Things Management/Configuration Management - is this the unpublished "Things Management GE"? - (Backend) Things Management/IoT broker - is this the unpublished "Things Management GE"? - (Gateway) Data Handling/SOL/CEP - (Gateway) Device Management - (Backend) Device Management GE - publish it asap DATA: - Publish/Subscribe Broker GE - Semantic Annotator GE - Location Server GE - Semantic Application Support GE - Meta-data Annotation GE I2ND: SEC: - Identity Management GE GCP - Data Handling GE - Security Storage Service - Attack-Paths Engine I've reported this list also on the minutes of yesterday conf call. BR Davide. -- ---------------------------------------------------------------------- _/ _/_/ 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: