From lorant.farkas at nsn.com Wed Aug 1 07:46:07 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 1 Aug 2012 08:46:07 +0300 Subject: [Fiware-iot] FW: Wrong naming convention in SVN Message-ID: <93D28BDF64839C468B848D14227151A203C6068B@FIESEXC014.nsn-intra.net> Dear All, Please comply with Miguel's request on the naming of the binaries. GE names should be respected. Thanks & Br, Lorant From: ext Miguel Carrillo [mailto:mcp at tid.es] Sent: Wednesday, August 01, 2012 12:58 AM To: Farkas, Lorant (NSN - HU/Budapest); thierry.nagellen at orange.com Cc: JUAN JOSE HIERRO SUREDA Subject: Wrong naming convention in SVN Thierry, Lorant, One of the things I am trying to avoid is that people try to escape the official names and use their internal ones. This is completely misleading for anyone outside FI-WARE's WP5. Example: if you look at the private one and not being part of IoT, I do not know what GE "Ericsson gateway" is. The name of each level is well defined in the guidelines. I also do not see the need to state the partner who is the owner, not here,. The "NEC", "Ericsson", etc must go away. Can you please ensure that the GE names are respected ? Same in the public SVN: When I know the answer to my previous question (what to do with the GE from NSN) and when this change on the SVN is ready,I will deliver your WP. 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: jdjjfhha.png Type: image/png Size: 5892 bytes Desc: jdjjfhha.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: hgcdjjbb.png Type: image/png Size: 3723 bytes Desc: hgcdjjbb.png URL: From lorant.farkas at nsn.com Wed Aug 1 08:02:20 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 1 Aug 2012 09:02:20 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A203C60698@FIESEXC014.nsn-intra.net> When: 2012. augusztus 1. 10:00-11:30 (UTC+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (phone number: in the pdf, conference code: 3865541959#) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, I guess today we need to speak today about the following (unless Thierry will send an updated agenda): 1. FI-WARE review outcome (interim report) and measures 2. last todos for the M12 deliverables: missing items, testbed installation status, catalogue would be covered at the minimum 3. status of action items 4. other admin issues (here I have one particular topic to announce) 5. AoB Thanks & Br, Lorant Update on all instances because NSN has a new voice conferencing service. To join the voice conference: Dial the your country-specific local access number, indicated in the following pdf: <> Enter the conference code: 3865541959# ------------------------------------------------------- To join the online meeting Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&ORT=MTgjMjM%3D <> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 3851 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Local_access_numbers.pdf Type: application/pdf Size: 88754 bytes Desc: Local_access_numbers.pdf URL: From lorant.farkas at nsn.com Wed Aug 1 12:03:04 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 1 Aug 2012 13:03:04 +0300 Subject: [Fiware-iot] IoT weekly minutes Message-ID: <93D28BDF64839C468B848D14227151A203C6081B@FIESEXC014.nsn-intra.net> Dear All, Please find attached the minutes of the IoT weekly. <> This was most probably the last IoT weekly meeting we attended, let me thank you all for your work and cooperation and hope to meet you in the future. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IoT-Minutes-Telco-01082012.docx Type: application/octet-stream Size: 198156 bytes Desc: IoT-Minutes-Telco-01082012.docx URL: From lorant.farkas at nsn.com Mon Aug 6 16:13:05 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 6 Aug 2012 17:13:05 +0300 Subject: [Fiware-iot] Canceled: IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A203CC72AC@FIESEXC014.nsn-intra.net> When: Occurs every szerda effective 2011.09.28. until 2014.03.26. from 10:00 to 11:30 GMT +0100 (Standard) / GMT +0200 (Daylight). Where: telco/webex (phone number: in the pdf, conference code: 3865541959#) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* WPL will send new meeting series. Update on all instances because NSN has a new voice conferencing service. To join the voice conference: Dial the your country-specific local access number, indicated in the following pdf: <> Enter the conference code: 3865541959# ------------------------------------------------------- To join the online meeting Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&ORT=MTgjMjM%3D <> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 84398 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Local_access_numbers.pdf Type: application/pdf Size: 88754 bytes Desc: Local_access_numbers.pdf URL: From p.barnaghi at surrey.ac.uk Wed Aug 8 15:11:44 2012 From: p.barnaghi at surrey.ac.uk (p.barnaghi at surrey.ac.uk) Date: Wed, 8 Aug 2012 14:11:44 +0100 Subject: [Fiware-iot] [Fiware-testbed] University of Surrey's Cloud Platfrom In-Reply-To: References: Message-ID: Hi Stefano, Miguel, all, At the University of Surrey we have recently deployed a new Cloud Platform with high computing and bandwidth resources. The cloud platform also provides user friendly interfaces (Web and remote desktop) that can be used by external users. We are already working to host and deploy our GE components in FI-Ware IoT on this cloud. My colleagues are happy to extend this to other FI-WARE partners and to share our computing and software facilities over the cloud; the cloud environment runs VMwareESX that allows creating computing, storage and network resources and supports different OS Platforms; If this is something that other FI-WARE testbed partners are interested, please let us know. I have included my colleague Adetola Oredope in CC. Please contact Adetola if you are interested. Best, Payam ------------------------------------------------ Dr. Payam Barnaghi Lecturer, Centre for Communication Systems Research University of Surrey Guildford, Surrey, UK Phone: +44 1483 68 3460 Fax: +44 1483 68 6011 Email: p.barnaghi at surrey.ac.uk http://personal.ee.surrey.ac.uk/Personal/P.Barnaghi/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri Aug 10 07:57:11 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 10 Aug 2012 07:57:11 +0200 Subject: [Fiware-iot] [Fiware-testbed] University of Surrey's Cloud Platfrom In-Reply-To: References: Message-ID: <5024A2B7.1060302@tid.es> Dear Payam, Thanks for your offering, but a couple of remarks here: * It has already been discussed many times and it has been decided that FI-WARE GEs are going to be hosted in the datacenter facilities linked to the FI-WARE Testbed. Using a set of dedicated VMs for the First Release of FI-WARE, deployed on the FI-WARE Cloud that will be available as part of the FI-WARE Testbed for the Second Release of FI-WARE. This is not just because it is always nice to eat our own dog food, but because we are also asked to go beyond that and demonstrate that a particular player, who wants to play the role of FI-WARE Instance Provider, is able to create an integrated FI-WARE Instance by means of picking and bundle together a number of products implementing FI-WARE GEs. The FI-WARE Testbed, besides providing an environment for UC projects to test their Proof of Concepts and provide feedback to FI-WARE Developments and Specifications, is there to prove the feasibility of integrating FI-WARE GEs to build a FI-WARE Instance that can be deployed on a number of concrete facilities operated by a given operator, as a single platform. Delivering a given FI-WARE GE only as a Service raises a lot of questions about the feasibility to build and operate FI-WARE Instances and, therefore, the ability to exploit results of the project. Bottom line: * All FI-WARE GEs have to be made available on the FI-WARE Testbed and offered "as a Service" from there to the UC projects. * The FI-WARE GEs hosted on the FI-WARE Testbed will be the only ones offered to UC projects for experimentation unless explicitly agreed. * We will not accept justification of any PMs devoted to deploy and host a FI-WARE GE on any infrastructure different than the one linked to the FI-WARE Testbed unless explicitly agreed. * Of course, all the rest of partners are advised NOT to use your facilities as a mean to host their GE implementations and offer them to the UC projects. Indeed, I have to confess that I find it a bit inappropriate that a partner encourages the rest of partners to use a Cloud Hosting service different than the one we are going to build and offer in FI-WARE. 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 08/08/12 15:11, p.barnaghi at surrey.ac.uk wrote: Hi Stefano, Miguel, all, At the University of Surrey we have recently deployed a new Cloud Platform with high computing and bandwidth resources. The cloud platform also provides user friendly interfaces (Web and remote desktop) that can be used by external users. We are already working to host and deploy our GE components in FI-Ware IoT on this cloud. My colleagues are happy to extend this to other FI-WARE partners and to share our computing and software facilities over the cloud; the cloud environment runs VMwareESX that allows creating computing, storage and network resources and supports different OS Platforms; If this is something that other FI-WARE testbed partners are interested, please let us know. I have included my colleague Adetola Oredope in CC. Please contact Adetola if you are interested. Best, Payam ------------------------------------------------ Dr. Payam Barnaghi Lecturer, Centre for Communication Systems Research University of Surrey Guildford, Surrey, UK Phone: +44 1483 68 3460 Fax: +44 1483 68 6011 Email: p.barnaghi at surrey.ac.uk http://personal.ee.surrey.ac.uk/Personal/P.Barnaghi/ ________________________________ 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 p.barnaghi at surrey.ac.uk Fri Aug 10 14:55:29 2012 From: p.barnaghi at surrey.ac.uk (p.barnaghi at surrey.ac.uk) Date: Fri, 10 Aug 2012 13:55:29 +0100 Subject: [Fiware-iot] [Fiware-testbed] University of Surrey's Cloud Platfrom In-Reply-To: <5024A2B7.1060302@tid.es> References: , <5024A2B7.1060302@tid.es> Message-ID: Dear Juanjo, Thank you for the clarification. I didn't mean it as an alternative Cloud Hosting service different than the one that is going to be built and offered in FI-WARE; we meant it more as a complimentary and connected solution to FI-WARe cloud; and in fact, our cloud can't offer the capabilities that FI-WARE is going to build after all. Thanks again and sorry if my suggestion wasn't appropriate; I did it with good intention and tried to help... Thanks, Payam ________________________________ From: Juanjo Hierro [jhierro at tid.es] Sent: 10 August 2012 06:57 To: Barnaghi P Dr (Electronic Eng) Cc: stefano.depanfilis at eng.it; mcp at tid.es; Oredope A Dr (Electronic Eng); fiware-testbed at lists.fi-ware.eu; fiware-iot at lists.fi-ware.eu; Tafazolli R Prof (CCSR); Evans BG Prof (CCSR); jhierro >> "Juan J. Hierro" Subject: Re: [Fiware-testbed] University of Surrey's Cloud Platfrom Dear Payam, Thanks for your offering, but a couple of remarks here: * It has already been discussed many times and it has been decided that FI-WARE GEs are going to be hosted in the datacenter facilities linked to the FI-WARE Testbed. Using a set of dedicated VMs for the First Release of FI-WARE, deployed on the FI-WARE Cloud that will be available as part of the FI-WARE Testbed for the Second Release of FI-WARE. This is not just because it is always nice to eat our own dog food, but because we are also asked to go beyond that and demonstrate that a particular player, who wants to play the role of FI-WARE Instance Provider, is able to create an integrated FI-WARE Instance by means of picking and bundle together a number of products implementing FI-WARE GEs. The FI-WARE Testbed, besides providing an environment for UC projects to test their Proof of Concepts and provide feedback to FI-WARE Developments and Specifications, is there to prove the feasibility of integrating FI-WARE GEs to build a FI-WARE Instance that can be deployed on a number of concrete facilities operated by a given operator, as a single platform. Delivering a given FI-WARE GE only as a Service raises a lot of questions about the feasibility to build and operate FI-WARE Instances and, therefore, the ability to exploit results of the project. Bottom line: * All FI-WARE GEs have to be made available on the FI-WARE Testbed and offered "as a Service" from there to the UC projects. * The FI-WARE GEs hosted on the FI-WARE Testbed will be the only ones offered to UC projects for experimentation unless explicitly agreed. * We will not accept justification of any PMs devoted to deploy and host a FI-WARE GE on any infrastructure different than the one linked to the FI-WARE Testbed unless explicitly agreed. * Of course, all the rest of partners are advised NOT to use your facilities as a mean to host their GE implementations and offer them to the UC projects. Indeed, I have to confess that I find it a bit inappropriate that a partner encourages the rest of partners to use a Cloud Hosting service different than the one we are going to build and offer in FI-WARE. 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 08/08/12 15:11, p.barnaghi at surrey.ac.uk wrote: Hi Stefano, Miguel, all, At the University of Surrey we have recently deployed a new Cloud Platform with high computing and bandwidth resources. The cloud platform also provides user friendly interfaces (Web and remote desktop) that can be used by external users. We are already working to host and deploy our GE components in FI-Ware IoT on this cloud. My colleagues are happy to extend this to other FI-WARE partners and to share our computing and software facilities over the cloud; the cloud environment runs VMwareESX that allows creating computing, storage and network resources and supports different OS Platforms; If this is something that other FI-WARE testbed partners are interested, please let us know. I have included my colleague Adetola Oredope in CC. Please contact Adetola if you are interested. Best, Payam ------------------------------------------------ Dr. Payam Barnaghi Lecturer, Centre for Communication Systems Research University of Surrey Guildford, Surrey, UK Phone: +44 1483 68 3460 Fax: +44 1483 68 6011 Email: p.barnaghi at surrey.ac.uk http://personal.ee.surrey.ac.uk/Personal/P.Barnaghi/ ________________________________ 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 Aug 13 16:07:56 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 13 Aug 2012 16:07:56 +0200 Subject: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap In-Reply-To: <5028A975.4010405@tid.es> References: <5028A975.4010405@tid.es> Message-ID: <50290A3C.70403@tid.es> Dear all, Sorry for contacting you directly but there is something of the utmost importance and we need to make sure that it is properly attended. If you see the enclosed message, the Project Coordinator is preparing the final delivery that will be sent out very soon. We are in the process of closing the Technical Roadmap deliverable and IoT seems the only chapter that has not delivered their contributions (I2ND had created them in time but they forgot to link them to the placeholder). This is largely the responsibility of the WP Leader but I do not know who is replacing Thierry in his holidays. Who has been appointed by him as contact point in his absence? (I see from his vacation email that he is on leave until the end of the month but he does not mention any replacement or deputy) Best regards, Miguel -------- Mensaje original -------- Asunto: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Fecha: Mon, 13 Aug 2012 09:15:01 +0200 De: Juanjo Hierro A: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear all, I have checked the contributions by the different chapters to the resubmission of the Technical Roadmap and all are Ok IMHO but the one from the IoT and the I2ND chapters that are still missing. I would suggest that the rest of chapters upload their contributions to the FI-WARE public wiki so that contents of their respective chapter get updated the same way that the Apps Chapter has done. It would be nice that they implement one enhancement that the Apps Chapter has introduced that I rather like: create a wiki link between the names of the GEs when they appear in the Technical Roadmap page (i.e., the tables listing Features/Epics) and the corresponding section on the "Materializing the FI-WARE Vision" part of the wiki. Deadline for the IoT chapter to complete their task is August 15th EOB. Please get it done so that we can officially resubmit by August 16th. Rest of chapters are free to update their contributions until August 15th EOB if they desire to do so. In order to complete the picture, don't miss that one remaining task would be that of updating the Stakeholder field in each backlog entry linked to an Epic or Feature published on the wiki. I would suggest using "FI-WARE" in the case this is a need identified by us, instead of naming a specific partner of FI-WARE. This will avoid questions like "Is only xxx the partner in FI-WARE asking for this feature ?". You can keep information about the specific company that proposed the feature by using the field "Owner". You should also try to add the name of those UC projects that you know are also asking for that Epic or Feature (thanks to interaction during/after the educational weeks). We will nevertheless ask the UC projects to list themselves in the Stakeholder field on another track (but this once we have published the new contents of the Technical Roadmap with the tables of Epics and Features) Besides this, I would kindly ask you to carry out a revision of the tracker of your chapter to make sure it gets aligned with what is currently on the Wiki, thus we can start from a new page in September: * Some of the Epics/Features may have changed, so please translate whatever change on the tracker * Make sure that Release Ids (numbering) is ok. I remind you the conventions at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Don't forget that reviewers have also asked us to resubmit the tracker contents, so this is an exercise that we definitively have to do. Last but not least, regarding updates of Technical Roadmap wiki pages, a couple of minor comments though: * Regarding contribution of the Cloud chapter: * Please update listing of features linked to the Cloud Proxy GE so that it aligns with the rest of the table * You didn't need a table for "Future Releases". You can mention that you will work in a "stabilized version taking into account new Use Cases requirements" in a dedicated statement within the last paragraph * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) * Regarding contribution of the Security chapter: * Please use references to wiki pages on the public wiki (built using the notation '[[]]') instead of hyperlinks * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps 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 ________________________________ 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 -------------- _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa From Tobias.Jacobs at neclab.eu Tue Aug 14 10:15:00 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Tue, 14 Aug 2012 08:15:00 +0000 Subject: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap In-Reply-To: <50290A3C.70403@tid.es> References: <5028A975.4010405@tid.es> <50290A3C.70403@tid.es> Message-ID: <8755F290097BD941865DC4245B335D2D168B91D6@PALLENE.office.hd> Dear Miguel, The situation in IoT is somewhat unclear at the moment, as the WPA (which was NSN) has left the work package two week ago. I have to admit that I do not really have an overview about the overall status of the deliverables, but what I can offer is to check the minutes of the weekly meetings and try to find out what the status is. Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Montag, 13. August 2012 16:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear all, Sorry for contacting you directly but there is something of the utmost importance and we need to make sure that it is properly attended. If you see the enclosed message, the Project Coordinator is preparing the final delivery that will be sent out very soon. We are in the process of closing the Technical Roadmap deliverable and IoT seems the only chapter that has not delivered their contributions (I2ND had created them in time but they forgot to link them to the placeholder). This is largely the responsibility of the WP Leader but I do not know who is replacing Thierry in his holidays. Who has been appointed by him as contact point in his absence? (I see from his vacation email that he is on leave until the end of the month but he does not mention any replacement or deputy) Best regards, Miguel -------- Mensaje original -------- Asunto: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Fecha: Mon, 13 Aug 2012 09:15:01 +0200 De: Juanjo Hierro A: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear all, I have checked the contributions by the different chapters to the resubmission of the Technical Roadmap and all are Ok IMHO but the one from the IoT and the I2ND chapters that are still missing. I would suggest that the rest of chapters upload their contributions to the FI-WARE public wiki so that contents of their respective chapter get updated the same way that the Apps Chapter has done. It would be nice that they implement one enhancement that the Apps Chapter has introduced that I rather like: create a wiki link between the names of the GEs when they appear in the Technical Roadmap page (i.e., the tables listing Features/Epics) and the corresponding section on the "Materializing the FI-WARE Vision" part of the wiki. Deadline for the IoT chapter to complete their task is August 15th EOB. Please get it done so that we can officially resubmit by August 16th. Rest of chapters are free to update their contributions until August 15th EOB if they desire to do so. In order to complete the picture, don't miss that one remaining task would be that of updating the Stakeholder field in each backlog entry linked to an Epic or Feature published on the wiki. I would suggest using "FI-WARE" in the case this is a need identified by us, instead of naming a specific partner of FI-WARE. This will avoid questions like "Is only xxx the partner in FI-WARE asking for this feature ?". You can keep information about the specific company that proposed the feature by using the field "Owner". You should also try to add the name of those UC projects that you know are also asking for that Epic or Feature (thanks to interaction during/after the educational weeks). We will nevertheless ask the UC projects to list themselves in the Stakeholder field on another track (but this once we have published the new contents of the Technical Roadmap with the tables of Epics and Features) Besides this, I would kindly ask you to carry out a revision of the tracker of your chapter to make sure it gets aligned with what is currently on the Wiki, thus we can start from a new page in September: * Some of the Epics/Features may have changed, so please translate whatever change on the tracker * Make sure that Release Ids (numbering) is ok. I remind you the conventions at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Don't forget that reviewers have also asked us to resubmit the tracker contents, so this is an exercise that we definitively have to do. Last but not least, regarding updates of Technical Roadmap wiki pages, a couple of minor comments though: * Regarding contribution of the Cloud chapter: * Please update listing of features linked to the Cloud Proxy GE so that it aligns with the rest of the table * You didn't need a table for "Future Releases". You can mention that you will work in a "stabilized version taking into account new Use Cases requirements" in a dedicated statement within the last paragraph * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) * Regarding contribution of the Security chapter: * Please use references to wiki pages on the public wiki (built using the notation '[[]]') instead of hyperlinks * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps 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 ________________________________ 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 Tobias.Jacobs at neclab.eu Tue Aug 14 16:34:54 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Tue, 14 Aug 2012 14:34:54 +0000 Subject: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Message-ID: <8755F290097BD941865DC4245B335D2D168B926C@PALLENE.office.hd> Hi all, Up to now there is a draft of the 'technical roadmap' in the common private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT - At the moment there are some comments by NEC requesting changes. I will ask Telefonica about that in an extra email and hopefully remove the comments very soon. - Lorant or Denes, could you make a short statement about what was the status of this deliverable? (Sorry, I hope that we do not need to bother you with WP5 requests too often in the future) Anyone else wants to comment, or are you all on holiday? ;-) Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: Dienstag, 14. August 2012 10:15 To: Miguel Carrillo; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear Miguel, The situation in IoT is somewhat unclear at the moment, as the WPA (which was NSN) has left the work package two week ago. I have to admit that I do not really have an overview about the overall status of the deliverables, but what I can offer is to check the minutes of the weekly meetings and try to find out what the status is. Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Montag, 13. August 2012 16:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear all, Sorry for contacting you directly but there is something of the utmost importance and we need to make sure that it is properly attended. If you see the enclosed message, the Project Coordinator is preparing the final delivery that will be sent out very soon. We are in the process of closing the Technical Roadmap deliverable and IoT seems the only chapter that has not delivered their contributions (I2ND had created them in time but they forgot to link them to the placeholder). This is largely the responsibility of the WP Leader but I do not know who is replacing Thierry in his holidays. Who has been appointed by him as contact point in his absence? (I see from his vacation email that he is on leave until the end of the month but he does not mention any replacement or deputy) Best regards, Miguel -------- Mensaje original -------- Asunto: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Fecha: Mon, 13 Aug 2012 09:15:01 +0200 De: Juanjo Hierro A: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear all, I have checked the contributions by the different chapters to the resubmission of the Technical Roadmap and all are Ok IMHO but the one from the IoT and the I2ND chapters that are still missing. I would suggest that the rest of chapters upload their contributions to the FI-WARE public wiki so that contents of their respective chapter get updated the same way that the Apps Chapter has done. It would be nice that they implement one enhancement that the Apps Chapter has introduced that I rather like: create a wiki link between the names of the GEs when they appear in the Technical Roadmap page (i.e., the tables listing Features/Epics) and the corresponding section on the "Materializing the FI-WARE Vision" part of the wiki. Deadline for the IoT chapter to complete their task is August 15th EOB. Please get it done so that we can officially resubmit by August 16th. Rest of chapters are free to update their contributions until August 15th EOB if they desire to do so. In order to complete the picture, don't miss that one remaining task would be that of updating the Stakeholder field in each backlog entry linked to an Epic or Feature published on the wiki. I would suggest using "FI-WARE" in the case this is a need identified by us, instead of naming a specific partner of FI-WARE. This will avoid questions like "Is only xxx the partner in FI-WARE asking for this feature ?". You can keep information about the specific company that proposed the feature by using the field "Owner". You should also try to add the name of those UC projects that you know are also asking for that Epic or Feature (thanks to interaction during/after the educational weeks). We will nevertheless ask the UC projects to list themselves in the Stakeholder field on another track (but this once we have published the new contents of the Technical Roadmap with the tables of Epics and Features) Besides this, I would kindly ask you to carry out a revision of the tracker of your chapter to make sure it gets aligned with what is currently on the Wiki, thus we can start from a new page in September: * Some of the Epics/Features may have changed, so please translate whatever change on the tracker * Make sure that Release Ids (numbering) is ok. I remind you the conventions at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Don't forget that reviewers have also asked us to resubmit the tracker contents, so this is an exercise that we definitively have to do. Last but not least, regarding updates of Technical Roadmap wiki pages, a couple of minor comments though: * Regarding contribution of the Cloud chapter: * Please update listing of features linked to the Cloud Proxy GE so that it aligns with the rest of the table * You didn't need a table for "Future Releases". You can mention that you will work in a "stabilized version taking into account new Use Cases requirements" in a dedicated statement within the last paragraph * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) * Regarding contribution of the Security chapter: * Please use references to wiki pages on the public wiki (built using the notation '[[]]') instead of hyperlinks * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps 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 ________________________________ 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 Aug 14 16:46:17 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 14 Aug 2012 17:46:17 +0300 Subject: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap In-Reply-To: <8755F290097BD941865DC4245B335D2D168B926C@PALLENE.office.hd> References: <8755F290097BD941865DC4245B335D2D168B926C@PALLENE.office.hd> Message-ID: <93D28BDF64839C468B848D14227151A203D15964@FIESEXC014.nsn-intra.net> Dear All, The status of this deliverable as I know it was that there were no guidelines for the generation. We left on the 1st of August. Juanjo sent guidelines to the WPA/WPL lists on the 3rd of August. We received it as fortunately/unfortunately noone took the action to remove us from the list J, so I attach it hereby. Someone should take care of it. Hasn't Thierry asked NEC whether you want to become WPA? At least that was our recommendation at the time. If you want to become WPA, I guess this would be the right opportunity J Thanks & Br, Lorant From: ext Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: Tuesday, August 14, 2012 4:35 PM To: Tobias Jacobs; Miguel Carrillo; fiware-iot at lists.fi-ware.eu Cc: Farkas, Lorant (NSN - HU/Budapest); Bisztray, Denes (NSN - HU/Budapest) Subject: RE: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Hi all, Up to now there is a draft of the 'technical roadmap' in the common private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT - At the moment there are some comments by NEC requesting changes. I will ask Telefonica about that in an extra email and hopefully remove the comments very soon. - Lorant or Denes, could you make a short statement about what was the status of this deliverable? (Sorry, I hope that we do not need to bother you with WP5 requests too often in the future) Anyone else wants to comment, or are you all on holiday? ;-) Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: Dienstag, 14. August 2012 10:15 To: Miguel Carrillo; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear Miguel, The situation in IoT is somewhat unclear at the moment, as the WPA (which was NSN) has left the work package two week ago. I have to admit that I do not really have an overview about the overall status of the deliverables, but what I can offer is to check the minutes of the weekly meetings and try to find out what the status is. Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Montag, 13. August 2012 16:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear all, Sorry for contacting you directly but there is something of the utmost importance and we need to make sure that it is properly attended. If you see the enclosed message, the Project Coordinator is preparing the final delivery that will be sent out very soon. We are in the process of closing the Technical Roadmap deliverable and IoT seems the only chapter that has not delivered their contributions (I2ND had created them in time but they forgot to link them to the placeholder). This is largely the responsibility of the WP Leader but I do not know who is replacing Thierry in his holidays. Who has been appointed by him as contact point in his absence? (I see from his vacation email that he is on leave until the end of the month but he does not mention any replacement or deputy) Best regards, Miguel -------- Mensaje original -------- Asunto: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Fecha: Mon, 13 Aug 2012 09:15:01 +0200 De: Juanjo Hierro A: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear all, I have checked the contributions by the different chapters to the resubmission of the Technical Roadmap and all are Ok IMHO but the one from the IoT and the I2ND chapters that are still missing. I would suggest that the rest of chapters upload their contributions to the FI-WARE public wiki so that contents of their respective chapter get updated the same way that the Apps Chapter has done. It would be nice that they implement one enhancement that the Apps Chapter has introduced that I rather like: create a wiki link between the names of the GEs when they appear in the Technical Roadmap page (i.e., the tables listing Features/Epics) and the corresponding section on the "Materializing the FI-WARE Vision" part of the wiki. Deadline for the IoT chapter to complete their task is August 15th EOB. Please get it done so that we can officially resubmit by August 16th. Rest of chapters are free to update their contributions until August 15th EOB if they desire to do so. In order to complete the picture, don't miss that one remaining task would be that of updating the Stakeholder field in each backlog entry linked to an Epic or Feature published on the wiki. I would suggest using "FI-WARE" in the case this is a need identified by us, instead of naming a specific partner of FI-WARE. This will avoid questions like "Is only xxx the partner in FI-WARE asking for this feature ?". You can keep information about the specific company that proposed the feature by using the field "Owner". You should also try to add the name of those UC projects that you know are also asking for that Epic or Feature (thanks to interaction during/after the educational weeks). We will nevertheless ask the UC projects to list themselves in the Stakeholder field on another track (but this once we have published the new contents of the Technical Roadmap with the tables of Epics and Features) Besides this, I would kindly ask you to carry out a revision of the tracker of your chapter to make sure it gets aligned with what is currently on the Wiki, thus we can start from a new page in September: * Some of the Epics/Features may have changed, so please translate whatever change on the tracker * Make sure that Release Ids (numbering) is ok. I remind you the conventions at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Don't forget that reviewers have also asked us to resubmit the tracker contents, so this is an exercise that we definitively have to do. Last but not least, regarding updates of Technical Roadmap wiki pages, a couple of minor comments though: * Regarding contribution of the Cloud chapter: * Please update listing of features linked to the Cloud Proxy GE so that it aligns with the rest of the table * You didn't need a table for "Future Releases". You can mention that you will work in a "stabilized version taking into account new Use Cases requirements" in a dedicated statement within the last paragraph * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) * Regarding contribution of the Security chapter: * Please use references to wiki pages on the public wiki (built using the notation '[[]]') instead of hyperlinks * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps 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 ________________________________ 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 -------------- An embedded message was scrubbed... From: "ext Juanjo Hierro" Subject: [Fiware-wpa] Instructions for resubmission of FI-WARE Technical Roadmap Date: Fri, 3 Aug 2012 11:02:26 +0300 Size: 19955 URL: From Tobias.Jacobs at neclab.eu Tue Aug 14 16:54:26 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Tue, 14 Aug 2012 14:54:26 +0000 Subject: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap In-Reply-To: <93D28BDF64839C468B848D14227151A203D15964@FIESEXC014.nsn-intra.net> References: <8755F290097BD941865DC4245B335D2D168B926C@PALLENE.office.hd> <93D28BDF64839C468B848D14227151A203D15964@FIESEXC014.nsn-intra.net> Message-ID: <8755F290097BD941865DC4245B335D2D168B92B2@PALLENE.office.hd> Hi Lorant, Thanks for the good and accurate info, I really miss you guys! I cannot decide if we want to become WPA or not at this point of time where all my colleagues are on holiday, but anyway thanks a lot for recommending us. Best regards Tobias From: Farkas, Lorant (NSN - HU/Budapest) [mailto:lorant.farkas at nsn.com] Sent: Dienstag, 14. August 2012 16:46 To: Tobias Jacobs; Miguel Carrillo; fiware-iot at lists.fi-ware.eu Cc: Bisztray, Denes (NSN - HU/Budapest) Subject: RE: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear All, The status of this deliverable as I know it was that there were no guidelines for the generation. We left on the 1st of August. Juanjo sent guidelines to the WPA/WPL lists on the 3rd of August. We received it as fortunately/unfortunately noone took the action to remove us from the list :), so I attach it hereby. Someone should take care of it. Hasn't Thierry asked NEC whether you want to become WPA? At least that was our recommendation at the time. If you want to become WPA, I guess this would be the right opportunity :) Thanks & Br, Lorant From: ext Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: Tuesday, August 14, 2012 4:35 PM To: Tobias Jacobs; Miguel Carrillo; fiware-iot at lists.fi-ware.eu Cc: Farkas, Lorant (NSN - HU/Budapest); Bisztray, Denes (NSN - HU/Budapest) Subject: RE: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Hi all, Up to now there is a draft of the 'technical roadmap' in the common private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT - At the moment there are some comments by NEC requesting changes. I will ask Telefonica about that in an extra email and hopefully remove the comments very soon. - Lorant or Denes, could you make a short statement about what was the status of this deliverable? (Sorry, I hope that we do not need to bother you with WP5 requests too often in the future) Anyone else wants to comment, or are you all on holiday? ;-) Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: Dienstag, 14. August 2012 10:15 To: Miguel Carrillo; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear Miguel, The situation in IoT is somewhat unclear at the moment, as the WPA (which was NSN) has left the work package two week ago. I have to admit that I do not really have an overview about the overall status of the deliverables, but what I can offer is to check the minutes of the weekly meetings and try to find out what the status is. Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Montag, 13. August 2012 16:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear all, Sorry for contacting you directly but there is something of the utmost importance and we need to make sure that it is properly attended. If you see the enclosed message, the Project Coordinator is preparing the final delivery that will be sent out very soon. We are in the process of closing the Technical Roadmap deliverable and IoT seems the only chapter that has not delivered their contributions (I2ND had created them in time but they forgot to link them to the placeholder). This is largely the responsibility of the WP Leader but I do not know who is replacing Thierry in his holidays. Who has been appointed by him as contact point in his absence? (I see from his vacation email that he is on leave until the end of the month but he does not mention any replacement or deputy) Best regards, Miguel -------- Mensaje original -------- Asunto: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Fecha: Mon, 13 Aug 2012 09:15:01 +0200 De: Juanjo Hierro A: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear all, I have checked the contributions by the different chapters to the resubmission of the Technical Roadmap and all are Ok IMHO but the one from the IoT and the I2ND chapters that are still missing. I would suggest that the rest of chapters upload their contributions to the FI-WARE public wiki so that contents of their respective chapter get updated the same way that the Apps Chapter has done. It would be nice that they implement one enhancement that the Apps Chapter has introduced that I rather like: create a wiki link between the names of the GEs when they appear in the Technical Roadmap page (i.e., the tables listing Features/Epics) and the corresponding section on the "Materializing the FI-WARE Vision" part of the wiki. Deadline for the IoT chapter to complete their task is August 15th EOB. Please get it done so that we can officially resubmit by August 16th. Rest of chapters are free to update their contributions until August 15th EOB if they desire to do so. In order to complete the picture, don't miss that one remaining task would be that of updating the Stakeholder field in each backlog entry linked to an Epic or Feature published on the wiki. I would suggest using "FI-WARE" in the case this is a need identified by us, instead of naming a specific partner of FI-WARE. This will avoid questions like "Is only xxx the partner in FI-WARE asking for this feature ?". You can keep information about the specific company that proposed the feature by using the field "Owner". You should also try to add the name of those UC projects that you know are also asking for that Epic or Feature (thanks to interaction during/after the educational weeks). We will nevertheless ask the UC projects to list themselves in the Stakeholder field on another track (but this once we have published the new contents of the Technical Roadmap with the tables of Epics and Features) Besides this, I would kindly ask you to carry out a revision of the tracker of your chapter to make sure it gets aligned with what is currently on the Wiki, thus we can start from a new page in September: * Some of the Epics/Features may have changed, so please translate whatever change on the tracker * Make sure that Release Ids (numbering) is ok. I remind you the conventions at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Don't forget that reviewers have also asked us to resubmit the tracker contents, so this is an exercise that we definitively have to do. Last but not least, regarding updates of Technical Roadmap wiki pages, a couple of minor comments though: * Regarding contribution of the Cloud chapter: * Please update listing of features linked to the Cloud Proxy GE so that it aligns with the rest of the table * You didn't need a table for "Future Releases". You can mention that you will work in a "stabilized version taking into account new Use Cases requirements" in a dedicated statement within the last paragraph * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) * Regarding contribution of the Security chapter: * Please use references to wiki pages on the public wiki (built using the notation '[[]]') instead of hyperlinks * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps 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 ________________________________ 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 Aug 15 11:04:06 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 15 Aug 2012 11:04:06 +0200 Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap In-Reply-To: <501B8592.9040109@tid.es> References: <501B8592.9040109@tid.es> Message-ID: <502B6606.5050705@tid.es> Hi all, There were clear and precise instructions on how to deal with this deliverable since August 3rd. Please find them enclosed. Despite also an example was provided at that time, you may already check the contributions from the other chapters for reference. It's basically a matter of adding a number of tables, which make reference to the Epics/Features in the FI-WARE Backlog. In the case of the Things Management GEs, they can easily be created, and I could even do it myself, but I have no clear idea about the rest of GEs in the IoT chapter. Since we are in a rush and it will be rather difficult to organize parallel editing of the wiki at this point, I would kindly ask you to provide your input to such tables in some sort of spreadsheet and I can take care of the final editing of the page later tonight. Could NEC provide the template for that spreadsheet and distribute it to the rest of the IoT team so that they can return them filled by EOB today ? Cheers, -- Juanjo -------- Original Message -------- Subject: Instructions for resubmission of FI-WARE Technical Roadmap Date: Fri, 03 Aug 2012 10:02:26 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear colleagues, Please find here the instructions to be followed to generate a new version of the Technical Roadmap deliverable to be published on the public Wiki and be resubmitted to the EC. The instructions are pretty simple and the best way to explain them is by referring to the example I have created on the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Example_(Resubmission)_-_Reference_Example That example is based on the current contents of the Technical Roadmap linked to the Apps Chapter. Based on that, the steps to follow are: * Update the Introduction: * We should make a reference to contents of the FI-WARE Architecture and Open Specifications part of the wiki, rather than the FI-WARE Product Vision (at the time at which the first version of the Technical Roadmap, the Architecture and Open Specifications didn't exist, but this is no longer the case) * You should also refer to the page dealing with Release and Sprint numbering, with reference to calendar dates. * All of this may be done by simple copy&paste from the reference example. * Description of first Major Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that will be supported. The table shall be preceded by the paragraph: * For a more detailed description of features provided, you can refer to the following table which help to identify what Backlog Features will be supported for each FI-WARE GE: * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. Essentially, you just need to include the references to the Backlog Features that have been addressed in the first Release for each FI-WARE GE (note this list should also include Features supported by the baseline assets) * When you distinguished between the delivery by end of July and by end of September, the above three points indeed apply per each (section for the release by end of July and section for the release by end of September) * Description of second Mayor Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that have already been planned or the Epics that will be analyzed and further refine which it is foreseen will lead to specification of Features to be planned as part of the second release. The table shall be preceded by the paragraph: * For a more detailed description of features to be provided, you can refer to the following table which help to identify what Backlog Features have already been specified and planned for the second Major Release of FI-WARE (and indication of the minor release is provided). The table also contain Epics currently under analysis which most probably will lead to the identification of Backlog Features to be planned also in the second Major Release * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. However, since there were no Backlog Features still planned, I have just created some fictitious features to make the reference example complete. If a FI-WARE GE does have Epics, but not Features, then write down "(not yet specified)" in the column about Features. * Regarding links to Features/Epics. They should be wiki references, as they appear in the reference example. No problem if they do not resolve in the FI-WARE Private Wiki, they should work once translated into the public Wiki * Description of Future Releases: * I believe we can keep this part as it is now I have prepared a section with placeholders for your contributions at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4 Please get them ready by Tuesday 12:00pm CET. It shouldn't be that difficult if you made a good exercise updating Epic/Features in the Backlog. During the rest of August, you should update the stakeholder field of each Epic/Feature in the backlog. Please do it with the best of your knowledge. Put "FI-WARE partners" if an Epic/Feature doesn't come from an UC project but was there within our original plans. Add the name of a UC project if you already know they are looking for it (based, for example, on feedback from the educational sessions). We will ask UC projects in parallel to review the Epics/Features on the wiki and add the name of their project in the plan to use the GE and wish to use the functionality linked to that Epic/Feature. 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 Tobias.Jacobs at neclab.eu Wed Aug 15 11:31:48 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Wed, 15 Aug 2012 09:31:48 +0000 Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Message-ID: <8755F290097BD941865DC4245B335D2D294B2678@DAPHNIS.office.hd> Hi all, I just created a first version of the Revised Technical Roadmap. It might look nice at first glance, however the assignment of Features to Release number is nearly completely RANDOM, based on my GUESSING. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT_%28Resubmission%29 So please please, we need every partner to revise the page above, and I guess this is by today. It is a task that every GE owner can fulfill within fifteen minutes, so I would say we will not run into editing conflicts. Please send an email to this list when you are done editing, so that we have an overview. As many people are on holiday, the big question is what to do with the GEs owners who cannot do this task in time. Rather remove the features, or rather keep the random assignment to releases? Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 15. August 2012 11:04 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi all, There were clear and precise instructions on how to deal with this deliverable since August 3rd. Please find them enclosed. Despite also an example was provided at that time, you may already check the contributions from the other chapters for reference. It's basically a matter of adding a number of tables, which make reference to the Epics/Features in the FI-WARE Backlog. In the case of the Things Management GEs, they can easily be created, and I could even do it myself, but I have no clear idea about the rest of GEs in the IoT chapter. Since we are in a rush and it will be rather difficult to organize parallel editing of the wiki at this point, I would kindly ask you to provide your input to such tables in some sort of spreadsheet and I can take care of the final editing of the page later tonight. Could NEC provide the template for that spreadsheet and distribute it to the rest of the IoT team so that they can return them filled by EOB today ? Cheers, -- Juanjo -------- Original Message -------- Subject: Instructions for resubmission of FI-WARE Technical Roadmap Date: Fri, 03 Aug 2012 10:02:26 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear colleagues, Please find here the instructions to be followed to generate a new version of the Technical Roadmap deliverable to be published on the public Wiki and be resubmitted to the EC. The instructions are pretty simple and the best way to explain them is by referring to the example I have created on the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Example_(Resubmission)_-_Reference_Example That example is based on the current contents of the Technical Roadmap linked to the Apps Chapter. Based on that, the steps to follow are: * Update the Introduction: * We should make a reference to contents of the FI-WARE Architecture and Open Specifications part of the wiki, rather than the FI-WARE Product Vision (at the time at which the first version of the Technical Roadmap, the Architecture and Open Specifications didn't exist, but this is no longer the case) * You should also refer to the page dealing with Release and Sprint numbering, with reference to calendar dates. * All of this may be done by simple copy&paste from the reference example. * Description of first Major Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that will be supported. The table shall be preceded by the paragraph: * For a more detailed description of features provided, you can refer to the following table which help to identify what Backlog Features will be supported for each FI-WARE GE: * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. Essentially, you just need to include the references to the Backlog Features that have been addressed in the first Release for each FI-WARE GE (note this list should also include Features supported by the baseline assets) * When you distinguished between the delivery by end of July and by end of September, the above three points indeed apply per each (section for the release by end of July and section for the release by end of September) * Description of second Mayor Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that have already been planned or the Epics that will be analyzed and further refine which it is foreseen will lead to specification of Features to be planned as part of the second release. The table shall be preceded by the paragraph: * For a more detailed description of features to be provided, you can refer to the following table which help to identify what Backlog Features have already been specified and planned for the second Major Release of FI-WARE (and indication of the minor release is provided). The table also contain Epics currently under analysis which most probably will lead to the identification of Backlog Features to be planned also in the second Major Release * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. However, since there were no Backlog Features still planned, I have just created some fictitious features to make the reference example complete. If a FI-WARE GE does have Epics, but not Features, then write down "(not yet specified)" in the column about Features. * Regarding links to Features/Epics. They should be wiki references, as they appear in the reference example. No problem if they do not resolve in the FI-WARE Private Wiki, they should work once translated into the public Wiki * Description of Future Releases: * I believe we can keep this part as it is now I have prepared a section with placeholders for your contributions at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4 Please get them ready by Tuesday 12:00pm CET. It shouldn't be that difficult if you made a good exercise updating Epic/Features in the Backlog. During the rest of August, you should update the stakeholder field of each Epic/Feature in the backlog. Please do it with the best of your knowledge. Put "FI-WARE partners" if an Epic/Feature doesn't come from an UC project but was there within our original plans. Add the name of a UC project if you already know they are looking for it (based, for example, on feedback from the educational sessions). We will ask UC projects in parallel to review the Epics/Features on the wiki and add the name of their project in the plan to use the GE and wish to use the functionality linked to that Epic/Feature. 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 t.elsaleh at surrey.ac.uk Wed Aug 15 15:00:09 2012 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Wed, 15 Aug 2012 14:00:09 +0100 Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap In-Reply-To: <8755F290097BD941865DC4245B335D2D294B2678@DAPHNIS.office.hd> References: <8755F290097BD941865DC4245B335D2D294B2678@DAPHNIS.office.hd> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA59381FC72@EXMB05CMS.surrey.ac.uk> Hello Tobias, >From USurrey point of view, we have edited the Technical Roadmap deliverable wiki page to accommodate USurrey's Epics and Features headers to the table for the Backend Second Release. One question, can we just link these headers to their corresponding original Epic/Features pages, or do we have to duplicate the content as an internal link? Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: 15 August 2012 10:32 To: Juanjo Hierro; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi all, I just created a first version of the Revised Technical Roadmap. It might look nice at first glance, however the assignment of Features to Release number is nearly completely RANDOM, based on my GUESSING. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT_%28Resubmission%29 So please please, we need every partner to revise the page above, and I guess this is by today. It is a task that every GE owner can fulfill within fifteen minutes, so I would say we will not run into editing conflicts. Please send an email to this list when you are done editing, so that we have an overview. As many people are on holiday, the big question is what to do with the GEs owners who cannot do this task in time. Rather remove the features, or rather keep the random assignment to releases? Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 15. August 2012 11:04 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi all, There were clear and precise instructions on how to deal with this deliverable since August 3rd. Please find them enclosed. Despite also an example was provided at that time, you may already check the contributions from the other chapters for reference. It's basically a matter of adding a number of tables, which make reference to the Epics/Features in the FI-WARE Backlog. In the case of the Things Management GEs, they can easily be created, and I could even do it myself, but I have no clear idea about the rest of GEs in the IoT chapter. Since we are in a rush and it will be rather difficult to organize parallel editing of the wiki at this point, I would kindly ask you to provide your input to such tables in some sort of spreadsheet and I can take care of the final editing of the page later tonight. Could NEC provide the template for that spreadsheet and distribute it to the rest of the IoT team so that they can return them filled by EOB today ? Cheers, -- Juanjo -------- Original Message -------- Subject: Instructions for resubmission of FI-WARE Technical Roadmap Date: Fri, 03 Aug 2012 10:02:26 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear colleagues, Please find here the instructions to be followed to generate a new version of the Technical Roadmap deliverable to be published on the public Wiki and be resubmitted to the EC. The instructions are pretty simple and the best way to explain them is by referring to the example I have created on the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Example_(Resubmission)_-_Reference_Example That example is based on the current contents of the Technical Roadmap linked to the Apps Chapter. Based on that, the steps to follow are: * Update the Introduction: * We should make a reference to contents of the FI-WARE Architecture and Open Specifications part of the wiki, rather than the FI-WARE Product Vision (at the time at which the first version of the Technical Roadmap, the Architecture and Open Specifications didn't exist, but this is no longer the case) * You should also refer to the page dealing with Release and Sprint numbering, with reference to calendar dates. * All of this may be done by simple copy&paste from the reference example. * Description of first Major Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that will be supported. The table shall be preceded by the paragraph: * For a more detailed description of features provided, you can refer to the following table which help to identify what Backlog Features will be supported for each FI-WARE GE: * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. Essentially, you just need to include the references to the Backlog Features that have been addressed in the first Release for each FI-WARE GE (note this list should also include Features supported by the baseline assets) * When you distinguished between the delivery by end of July and by end of September, the above three points indeed apply per each (section for the release by end of July and section for the release by end of September) * Description of second Mayor Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that have already been planned or the Epics that will be analyzed and further refine which it is foreseen will lead to specification of Features to be planned as part of the second release. The table shall be preceded by the paragraph: * For a more detailed description of features to be provided, you can refer to the following table which help to identify what Backlog Features have already been specified and planned for the second Major Release of FI-WARE (and indication of the minor release is provided). The table also contain Epics currently under analysis which most probably will lead to the identification of Backlog Features to be planned also in the second Major Release * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. However, since there were no Backlog Features still planned, I have just created some fictitious features to make the reference example complete. If a FI-WARE GE does have Epics, but not Features, then write down "(not yet specified)" in the column about Features. * Regarding links to Features/Epics. They should be wiki references, as they appear in the reference example. No problem if they do not resolve in the FI-WARE Private Wiki, they should work once translated into the public Wiki * Description of Future Releases: * I believe we can keep this part as it is now I have prepared a section with placeholders for your contributions at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4 Please get them ready by Tuesday 12:00pm CET. It shouldn't be that difficult if you made a good exercise updating Epic/Features in the Backlog. During the rest of August, you should update the stakeholder field of each Epic/Feature in the backlog. Please do it with the best of your knowledge. Put "FI-WARE partners" if an Epic/Feature doesn't come from an UC project but was there within our original plans. Add the name of a UC project if you already know they are looking for it (based, for example, on feedback from the educational sessions). We will ask UC projects in parallel to review the Epics/Features on the wiki and add the name of their project in the plan to use the GE and wish to use the functionality linked to that Epic/Feature. 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 Aug 15 15:36:21 2012 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Wed, 15 Aug 2012 13:36:21 +0000 Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCA59381FC72@EXMB05CMS.surrey.ac.uk> References: <8755F290097BD941865DC4245B335D2D294B2678@DAPHNIS.office.hd> <2AAC0B6FF99A064C853BFB1C9295F3CCA59381FC72@EXMB05CMS.surrey.ac.uk> Message-ID: <41BC1993-758D-4C24-97C1-1A8B327DF93F@tid.es> You don't need to duplicate the contents. It's fine if the wiki links just work once we upload the page into the public wiki Enviado desde mi iPhone El 15/08/2012, a las 14:00, "t.elsaleh at surrey.ac.uk" > escribi?: Hello Tobias, >From USurrey point of view, we have edited the Technical Roadmap deliverable wiki page to accommodate USurrey?s Epics and Features headers to the table for the Backend Second Release. One question, can we just link these headers to their corresponding original Epic/Features pages, or do we have to duplicate the content as an internal link? Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: 15 August 2012 10:32 To: Juanjo Hierro; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi all, I just created a first version of the Revised Technical Roadmap. It might look nice at first glance, however the assignment of Features to Release number is nearly completely RANDOM, based on my GUESSING. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT_%28Resubmission%29 So please please, we need every partner to revise the page above, and I guess this is by today. It is a task that every GE owner can fulfill within fifteen minutes, so I would say we will not run into editing conflicts. Please send an email to this list when you are done editing, so that we have an overview. As many people are on holiday, the big question is what to do with the GEs owners who cannot do this task in time. Rather remove the features, or rather keep the random assignment to releases? Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 15. August 2012 11:04 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi all, There were clear and precise instructions on how to deal with this deliverable since August 3rd. Please find them enclosed. Despite also an example was provided at that time, you may already check the contributions from the other chapters for reference. It's basically a matter of adding a number of tables, which make reference to the Epics/Features in the FI-WARE Backlog. In the case of the Things Management GEs, they can easily be created, and I could even do it myself, but I have no clear idea about the rest of GEs in the IoT chapter. Since we are in a rush and it will be rather difficult to organize parallel editing of the wiki at this point, I would kindly ask you to provide your input to such tables in some sort of spreadsheet and I can take care of the final editing of the page later tonight. Could NEC provide the template for that spreadsheet and distribute it to the rest of the IoT team so that they can return them filled by EOB today ? Cheers, -- Juanjo -------- Original Message -------- Subject: Instructions for resubmission of FI-WARE Technical Roadmap Date: Fri, 03 Aug 2012 10:02:26 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear colleagues, Please find here the instructions to be followed to generate a new version of the Technical Roadmap deliverable to be published on the public Wiki and be resubmitted to the EC. The instructions are pretty simple and the best way to explain them is by referring to the example I have created on the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Example_(Resubmission)_-_Reference_Example That example is based on the current contents of the Technical Roadmap linked to the Apps Chapter. Based on that, the steps to follow are: * Update the Introduction: * We should make a reference to contents of the FI-WARE Architecture and Open Specifications part of the wiki, rather than the FI-WARE Product Vision (at the time at which the first version of the Technical Roadmap, the Architecture and Open Specifications didn't exist, but this is no longer the case) * You should also refer to the page dealing with Release and Sprint numbering, with reference to calendar dates. * All of this may be done by simple copy&paste from the reference example. * Description of first Major Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that will be supported. The table shall be preceded by the paragraph: * For a more detailed description of features provided, you can refer to the following table which help to identify what Backlog Features will be supported for each FI-WARE GE: * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. Essentially, you just need to include the references to the Backlog Features that have been addressed in the first Release for each FI-WARE GE (note this list should also include Features supported by the baseline assets) * When you distinguished between the delivery by end of July and by end of September, the above three points indeed apply per each (section for the release by end of July and section for the release by end of September) * Description of second Mayor Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that have already been planned or the Epics that will be analyzed and further refine which it is foreseen will lead to specification of Features to be planned as part of the second release. The table shall be preceded by the paragraph: * For a more detailed description of features to be provided, you can refer to the following table which help to identify what Backlog Features have already been specified and planned for the second Major Release of FI-WARE (and indication of the minor release is provided). The table also contain Epics currently under analysis which most probably will lead to the identification of Backlog Features to be planned also in the second Major Release * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. However, since there were no Backlog Features still planned, I have just created some fictitious features to make the reference example complete. If a FI-WARE GE does have Epics, but not Features, then write down "(not yet specified)" in the column about Features. * Regarding links to Features/Epics. They should be wiki references, as they appear in the reference example. No problem if they do not resolve in the FI-WARE Private Wiki, they should work once translated into the public Wiki * Description of Future Releases: * I believe we can keep this part as it is now I have prepared a section with placeholders for your contributions at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4 Please get them ready by Tuesday 12:00pm CET. It shouldn't be that difficult if you made a good exercise updating Epic/Features in the Backlog. During the rest of August, you should update the stakeholder field of each Epic/Feature in the backlog. Please do it with the best of your knowledge. Put "FI-WARE partners" if an Epic/Feature doesn't come from an UC project but was there within our original plans. Add the name of a UC project if you already know they are looking for it (based, for example, on feedback from the educational sessions). We will ask UC projects in parallel to review the Epics/Features on the wiki and add the name of their project in the plan to use the GE and wish to use the functionality linked to that Epic/Feature. 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 ________________________________ 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 Tobias.Jacobs at neclab.eu Thu Aug 16 08:48:03 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Thu, 16 Aug 2012 06:48:03 +0000 Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap In-Reply-To: <41BC1993-758D-4C24-97C1-1A8B327DF93F@tid.es> References: <8755F290097BD941865DC4245B335D2D294B2678@DAPHNIS.office.hd> <2AAC0B6FF99A064C853BFB1C9295F3CCA59381FC72@EXMB05CMS.surrey.ac.uk> <41BC1993-758D-4C24-97C1-1A8B327DF93F@tid.es> Message-ID: <8755F290097BD941865DC4245B335D2D294B89EF@PALLENE.office.hd> Hi all, Thank for all contributions we received so far! As for the missing ones, I guess we now have to live with my guessings. I had a look into the tracker, and there most features were either assigned to release 1.3 or earlier or did not have an assigned release number at all. Juanjo, do you still want to edit something? (it looks like you did some editings, although your name does not appear in the edit history). Somebody else still wants to do something within the next few hours, let's say until noon? Otherwise I would send Miguel a message that the WP5 contribution is 'ready'. Oh, and sorry for not having reacted yesterday afternoon, for some reasons I did not receive any emails. Best regards Tobias From: JUAN JOSE HIERRO SUREDA [mailto:jhierro at tid.es] Sent: Mittwoch, 15. August 2012 15:36 To: t.elsaleh at surrey.ac.uk Cc: Tobias Jacobs; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap You don't need to duplicate the contents. It's fine if the wiki links just work once we upload the page into the public wiki Enviado desde mi iPhone El 15/08/2012, a las 14:00, "t.elsaleh at surrey.ac.uk" > escribi?: Hello Tobias, >From USurrey point of view, we have edited the Technical Roadmap deliverable wiki page to accommodate USurrey's Epics and Features headers to the table for the Backend Second Release. One question, can we just link these headers to their corresponding original Epic/Features pages, or do we have to duplicate the content as an internal link? Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: 15 August 2012 10:32 To: Juanjo Hierro; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi all, I just created a first version of the Revised Technical Roadmap. It might look nice at first glance, however the assignment of Features to Release number is nearly completely RANDOM, based on my GUESSING. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT_%28Resubmission%29 So please please, we need every partner to revise the page above, and I guess this is by today. It is a task that every GE owner can fulfill within fifteen minutes, so I would say we will not run into editing conflicts. Please send an email to this list when you are done editing, so that we have an overview. As many people are on holiday, the big question is what to do with the GEs owners who cannot do this task in time. Rather remove the features, or rather keep the random assignment to releases? Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 15. August 2012 11:04 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi all, There were clear and precise instructions on how to deal with this deliverable since August 3rd. Please find them enclosed. Despite also an example was provided at that time, you may already check the contributions from the other chapters for reference. It's basically a matter of adding a number of tables, which make reference to the Epics/Features in the FI-WARE Backlog. In the case of the Things Management GEs, they can easily be created, and I could even do it myself, but I have no clear idea about the rest of GEs in the IoT chapter. Since we are in a rush and it will be rather difficult to organize parallel editing of the wiki at this point, I would kindly ask you to provide your input to such tables in some sort of spreadsheet and I can take care of the final editing of the page later tonight. Could NEC provide the template for that spreadsheet and distribute it to the rest of the IoT team so that they can return them filled by EOB today ? Cheers, -- Juanjo -------- Original Message -------- Subject: Instructions for resubmission of FI-WARE Technical Roadmap Date: Fri, 03 Aug 2012 10:02:26 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear colleagues, Please find here the instructions to be followed to generate a new version of the Technical Roadmap deliverable to be published on the public Wiki and be resubmitted to the EC. The instructions are pretty simple and the best way to explain them is by referring to the example I have created on the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Example_(Resubmission)_-_Reference_Example That example is based on the current contents of the Technical Roadmap linked to the Apps Chapter. Based on that, the steps to follow are: * Update the Introduction: * We should make a reference to contents of the FI-WARE Architecture and Open Specifications part of the wiki, rather than the FI-WARE Product Vision (at the time at which the first version of the Technical Roadmap, the Architecture and Open Specifications didn't exist, but this is no longer the case) * You should also refer to the page dealing with Release and Sprint numbering, with reference to calendar dates. * All of this may be done by simple copy&paste from the reference example. * Description of first Major Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that will be supported. The table shall be preceded by the paragraph: * For a more detailed description of features provided, you can refer to the following table which help to identify what Backlog Features will be supported for each FI-WARE GE: * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. Essentially, you just need to include the references to the Backlog Features that have been addressed in the first Release for each FI-WARE GE (note this list should also include Features supported by the baseline assets) * When you distinguished between the delivery by end of July and by end of September, the above three points indeed apply per each (section for the release by end of July and section for the release by end of September) * Description of second Mayor Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that have already been planned or the Epics that will be analyzed and further refine which it is foreseen will lead to specification of Features to be planned as part of the second release. The table shall be preceded by the paragraph: * For a more detailed description of features to be provided, you can refer to the following table which help to identify what Backlog Features have already been specified and planned for the second Major Release of FI-WARE (and indication of the minor release is provided). The table also contain Epics currently under analysis which most probably will lead to the identification of Backlog Features to be planned also in the second Major Release * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. However, since there were no Backlog Features still planned, I have just created some fictitious features to make the reference example complete. If a FI-WARE GE does have Epics, but not Features, then write down "(not yet specified)" in the column about Features. * Regarding links to Features/Epics. They should be wiki references, as they appear in the reference example. No problem if they do not resolve in the FI-WARE Private Wiki, they should work once translated into the public Wiki * Description of Future Releases: * I believe we can keep this part as it is now I have prepared a section with placeholders for your contributions at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4 Please get them ready by Tuesday 12:00pm CET. It shouldn't be that difficult if you made a good exercise updating Epic/Features in the Backlog. During the rest of August, you should update the stakeholder field of each Epic/Feature in the backlog. Please do it with the best of your knowledge. Put "FI-WARE partners" if an Epic/Feature doesn't come from an UC project but was there within our original plans. Add the name of a UC project if you already know they are looking for it (based, for example, on feedback from the educational sessions). We will ask UC projects in parallel to review the Epics/Features on the wiki and add the name of their project in the plan to use the GE and wish to use the functionality linked to that Epic/Feature. 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 ________________________________ 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 Aug 16 11:24:56 2012 From: mcp at tid.es (Miguel Carrillo) Date: Thu, 16 Aug 2012 11:24:56 +0200 Subject: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap In-Reply-To: <8755F290097BD941865DC4245B335D2D168B91D6@PALLENE.office.hd> References: <5028A975.4010405@tid.es> <50290A3C.70403@tid.es> <8755F290097BD941865DC4245B335D2D168B91D6@PALLENE.office.hd> Message-ID: <502CBC68.2090504@tid.es> Dear Tobias, Sorry for the belated response, I was not at the office yesterday and on Tuesday. Anything that you can do will be much appreciated. I am really surprised that this is left to itself with no one taking care of it officially! I see messages that hint that something is being done so let us hope that we can complete the task! Thanks Miguel El 14/08/2012 10:15, Tobias Jacobs escribi?: Dear Miguel, The situation in IoT is somewhat unclear at the moment, as the WPA (which was NSN) has left the work package two week ago. I have to admit that I do not really have an overview about the overall status of the deliverables, but what I can offer is to check the minutes of the weekly meetings and try to find out what the status is. Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Montag, 13. August 2012 16:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear all, Sorry for contacting you directly but there is something of the utmost importance and we need to make sure that it is properly attended. If you see the enclosed message, the Project Coordinator is preparing the final delivery that will be sent out very soon. We are in the process of closing the Technical Roadmap deliverable and IoT seems the only chapter that has not delivered their contributions (I2ND had created them in time but they forgot to link them to the placeholder). This is largely the responsibility of the WP Leader but I do not know who is replacing Thierry in his holidays. Who has been appointed by him as contact point in his absence? (I see from his vacation email that he is on leave until the end of the month but he does not mention any replacement or deputy) Best regards, Miguel -------- Mensaje original -------- Asunto: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Fecha: Mon, 13 Aug 2012 09:15:01 +0200 De: Juanjo Hierro A: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear all, I have checked the contributions by the different chapters to the resubmission of the Technical Roadmap and all are Ok IMHO but the one from the IoT and the I2ND chapters that are still missing. I would suggest that the rest of chapters upload their contributions to the FI-WARE public wiki so that contents of their respective chapter get updated the same way that the Apps Chapter has done. It would be nice that they implement one enhancement that the Apps Chapter has introduced that I rather like: create a wiki link between the names of the GEs when they appear in the Technical Roadmap page (i.e., the tables listing Features/Epics) and the corresponding section on the "Materializing the FI-WARE Vision" part of the wiki. Deadline for the IoT chapter to complete their task is August 15th EOB. Please get it done so that we can officially resubmit by August 16th. Rest of chapters are free to update their contributions until August 15th EOB if they desire to do so. In order to complete the picture, don't miss that one remaining task would be that of updating the Stakeholder field in each backlog entry linked to an Epic or Feature published on the wiki. I would suggest using "FI-WARE" in the case this is a need identified by us, instead of naming a specific partner of FI-WARE. This will avoid questions like "Is only xxx the partner in FI-WARE asking for this feature ?". You can keep information about the specific company that proposed the feature by using the field "Owner". You should also try to add the name of those UC projects that you know are also asking for that Epic or Feature (thanks to interaction during/after the educational weeks). We will nevertheless ask the UC projects to list themselves in the Stakeholder field on another track (but this once we have published the new contents of the Technical Roadmap with the tables of Epics and Features) Besides this, I would kindly ask you to carry out a revision of the tracker of your chapter to make sure it gets aligned with what is currently on the Wiki, thus we can start from a new page in September: * Some of the Epics/Features may have changed, so please translate whatever change on the tracker * Make sure that Release Ids (numbering) is ok. I remind you the conventions at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Don't forget that reviewers have also asked us to resubmit the tracker contents, so this is an exercise that we definitively have to do. Last but not least, regarding updates of Technical Roadmap wiki pages, a couple of minor comments though: * Regarding contribution of the Cloud chapter: * Please update listing of features linked to the Cloud Proxy GE so that it aligns with the rest of the table * You didn't need a table for "Future Releases". You can mention that you will work in a "stabilized version taking into account new Use Cases requirements" in a dedicated statement within the last paragraph * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) * Regarding contribution of the Security chapter: * Please use references to wiki pages on the public wiki (built using the notation '[[]]') instead of hyperlinks * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps 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 ________________________________ 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: From Tobias.Jacobs at neclab.eu Thu Aug 16 11:40:44 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Thu, 16 Aug 2012 09:40:44 +0000 Subject: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap In-Reply-To: <502CBC68.2090504@tid.es> References: <5028A975.4010405@tid.es> <50290A3C.70403@tid.es> <8755F290097BD941865DC4245B335D2D168B91D6@PALLENE.office.hd> <502CBC68.2090504@tid.es> Message-ID: <8755F290097BD941865DC4245B335D2D294B9A50@PALLENE.office.hd> Dear Miguel, We are at the moment trying to catch up as good as we can. Could you have a look at the current draft at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT_%28Resubmission%29 and make a comment if this goes into the right direction? The main problem is that now many partners are on holidays, so I have difficulties correctly mapping the features to the release dates. Best Tobias From: Miguel Carrillo [mailto:mcp at tid.es] Sent: Donnerstag, 16. August 2012 11:25 To: Tobias Jacobs Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear Tobias, Sorry for the belated response, I was not at the office yesterday and on Tuesday. Anything that you can do will be much appreciated. I am really surprised that this is left to itself with no one taking care of it officially! I see messages that hint that something is being done so let us hope that we can complete the task! Thanks Miguel El 14/08/2012 10:15, Tobias Jacobs escribi?: Dear Miguel, The situation in IoT is somewhat unclear at the moment, as the WPA (which was NSN) has left the work package two week ago. I have to admit that I do not really have an overview about the overall status of the deliverables, but what I can offer is to check the minutes of the weekly meetings and try to find out what the status is. Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Montag, 13. August 2012 16:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear all, Sorry for contacting you directly but there is something of the utmost importance and we need to make sure that it is properly attended. If you see the enclosed message, the Project Coordinator is preparing the final delivery that will be sent out very soon. We are in the process of closing the Technical Roadmap deliverable and IoT seems the only chapter that has not delivered their contributions (I2ND had created them in time but they forgot to link them to the placeholder). This is largely the responsibility of the WP Leader but I do not know who is replacing Thierry in his holidays. Who has been appointed by him as contact point in his absence? (I see from his vacation email that he is on leave until the end of the month but he does not mention any replacement or deputy) Best regards, Miguel -------- Mensaje original -------- Asunto: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Fecha: Mon, 13 Aug 2012 09:15:01 +0200 De: Juanjo Hierro A: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear all, I have checked the contributions by the different chapters to the resubmission of the Technical Roadmap and all are Ok IMHO but the one from the IoT and the I2ND chapters that are still missing. I would suggest that the rest of chapters upload their contributions to the FI-WARE public wiki so that contents of their respective chapter get updated the same way that the Apps Chapter has done. It would be nice that they implement one enhancement that the Apps Chapter has introduced that I rather like: create a wiki link between the names of the GEs when they appear in the Technical Roadmap page (i.e., the tables listing Features/Epics) and the corresponding section on the "Materializing the FI-WARE Vision" part of the wiki. Deadline for the IoT chapter to complete their task is August 15th EOB. Please get it done so that we can officially resubmit by August 16th. Rest of chapters are free to update their contributions until August 15th EOB if they desire to do so. In order to complete the picture, don't miss that one remaining task would be that of updating the Stakeholder field in each backlog entry linked to an Epic or Feature published on the wiki. I would suggest using "FI-WARE" in the case this is a need identified by us, instead of naming a specific partner of FI-WARE. This will avoid questions like "Is only xxx the partner in FI-WARE asking for this feature ?". You can keep information about the specific company that proposed the feature by using the field "Owner". You should also try to add the name of those UC projects that you know are also asking for that Epic or Feature (thanks to interaction during/after the educational weeks). We will nevertheless ask the UC projects to list themselves in the Stakeholder field on another track (but this once we have published the new contents of the Technical Roadmap with the tables of Epics and Features) Besides this, I would kindly ask you to carry out a revision of the tracker of your chapter to make sure it gets aligned with what is currently on the Wiki, thus we can start from a new page in September: * Some of the Epics/Features may have changed, so please translate whatever change on the tracker * Make sure that Release Ids (numbering) is ok. I remind you the conventions at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Don't forget that reviewers have also asked us to resubmit the tracker contents, so this is an exercise that we definitively have to do. Last but not least, regarding updates of Technical Roadmap wiki pages, a couple of minor comments though: * Regarding contribution of the Cloud chapter: * Please update listing of features linked to the Cloud Proxy GE so that it aligns with the rest of the table * You didn't need a table for "Future Releases". You can mention that you will work in a "stabilized version taking into account new Use Cases requirements" in a dedicated statement within the last paragraph * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) * Regarding contribution of the Security chapter: * Please use references to wiki pages on the public wiki (built using the notation '[[]]') instead of hyperlinks * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps 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 ________________________________ 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: From jhierro at tid.es Thu Aug 16 12:00:59 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 16 Aug 2012 12:00:59 +0200 Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap In-Reply-To: <8755F290097BD941865DC4245B335D2D294B89EF@PALLENE.office.hd> References: <8755F290097BD941865DC4245B335D2D294B2678@DAPHNIS.office.hd> <2AAC0B6FF99A064C853BFB1C9295F3CCA59381FC72@EXMB05CMS.surrey.ac.uk> <41BC1993-758D-4C24-97C1-1A8B327DF93F@tid.es> <8755F290097BD941865DC4245B335D2D294B89EF@PALLENE.office.hd> Message-ID: <502CC4DB.8020102@tid.es> Hi, Let's extend the deadline until today EOB. Then I review and make the final editings so that we can officially deliver tomorrow. A couple of questions, that came to my mind while reviewing what was there: * My understanding is that we have to change everything related the Backend Device Management GE given the fact that NSN has dropped out and there will no implementation delivered. My guess would be to change every related feature to the 2nd Release ... * The table proposed in the template for the 2nd Release was slightly different. It deliberately included a column for Epics, so please use that one and place the Epics in the corresponding column * I don't see any feature related to the Backend nor Gateway Security GEs in any Release ... Then I would go for dropping its rows. If there are Epics identified for this GE, then I would go for having it in the second release since that table would include a column for Epics ... so therefore I would add the Epics there. Similar rule applies to any other GE Please try to fix the above points and collect any other additional input that may help to complete the roadmap description. 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 16/08/12 08:48, Tobias Jacobs wrote: Hi all, Thank for all contributions we received so far! As for the missing ones, I guess we now have to live with my guessings. I had a look into the tracker, and there most features were either assigned to release 1.3 or earlier or did not have an assigned release number at all. Juanjo, do you still want to edit something? (it looks like you did some editings, although your name does not appear in the edit history). Somebody else still wants to do something within the next few hours, let's say until noon? Otherwise I would send Miguel a message that the WP5 contribution is 'ready'. Oh, and sorry for not having reacted yesterday afternoon, for some reasons I did not receive any emails. Best regards Tobias From: JUAN JOSE HIERRO SUREDA [mailto:jhierro at tid.es] Sent: Mittwoch, 15. August 2012 15:36 To: t.elsaleh at surrey.ac.uk Cc: Tobias Jacobs; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap You don't need to duplicate the contents. It's fine if the wiki links just work once we upload the page into the public wiki Enviado desde mi iPhone El 15/08/2012, a las 14:00, "t.elsaleh at surrey.ac.uk" > escribi?: Hello Tobias, >From USurrey point of view, we have edited the Technical Roadmap deliverable wiki page to accommodate USurrey's Epics and Features headers to the table for the Backend Second Release. One question, can we just link these headers to their corresponding original Epic/Features pages, or do we have to duplicate the content as an internal link? Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: 15 August 2012 10:32 To: Juanjo Hierro; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi all, I just created a first version of the Revised Technical Roadmap. It might look nice at first glance, however the assignment of Features to Release number is nearly completely RANDOM, based on my GUESSING. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT_%28Resubmission%29 So please please, we need every partner to revise the page above, and I guess this is by today. It is a task that every GE owner can fulfill within fifteen minutes, so I would say we will not run into editing conflicts. Please send an email to this list when you are done editing, so that we have an overview. As many people are on holiday, the big question is what to do with the GEs owners who cannot do this task in time. Rather remove the features, or rather keep the random assignment to releases? Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 15. August 2012 11:04 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi all, There were clear and precise instructions on how to deal with this deliverable since August 3rd. Please find them enclosed. Despite also an example was provided at that time, you may already check the contributions from the other chapters for reference. It's basically a matter of adding a number of tables, which make reference to the Epics/Features in the FI-WARE Backlog. In the case of the Things Management GEs, they can easily be created, and I could even do it myself, but I have no clear idea about the rest of GEs in the IoT chapter. Since we are in a rush and it will be rather difficult to organize parallel editing of the wiki at this point, I would kindly ask you to provide your input to such tables in some sort of spreadsheet and I can take care of the final editing of the page later tonight. Could NEC provide the template for that spreadsheet and distribute it to the rest of the IoT team so that they can return them filled by EOB today ? Cheers, -- Juanjo -------- Original Message -------- Subject: Instructions for resubmission of FI-WARE Technical Roadmap Date: Fri, 03 Aug 2012 10:02:26 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear colleagues, Please find here the instructions to be followed to generate a new version of the Technical Roadmap deliverable to be published on the public Wiki and be resubmitted to the EC. The instructions are pretty simple and the best way to explain them is by referring to the example I have created on the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Example_(Resubmission)_-_Reference_Example That example is based on the current contents of the Technical Roadmap linked to the Apps Chapter. Based on that, the steps to follow are: * Update the Introduction: * We should make a reference to contents of the FI-WARE Architecture and Open Specifications part of the wiki, rather than the FI-WARE Product Vision (at the time at which the first version of the Technical Roadmap, the Architecture and Open Specifications didn't exist, but this is no longer the case) * You should also refer to the page dealing with Release and Sprint numbering, with reference to calendar dates. * All of this may be done by simple copy&paste from the reference example. * Description of first Major Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that will be supported. The table shall be preceded by the paragraph: * For a more detailed description of features provided, you can refer to the following table which help to identify what Backlog Features will be supported for each FI-WARE GE: * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. Essentially, you just need to include the references to the Backlog Features that have been addressed in the first Release for each FI-WARE GE (note this list should also include Features supported by the baseline assets) * When you distinguished between the delivery by end of July and by end of September, the above three points indeed apply per each (section for the release by end of July and section for the release by end of September) * Description of second Mayor Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that have already been planned or the Epics that will be analyzed and further refine which it is foreseen will lead to specification of Features to be planned as part of the second release. The table shall be preceded by the paragraph: * For a more detailed description of features to be provided, you can refer to the following table which help to identify what Backlog Features have already been specified and planned for the second Major Release of FI-WARE (and indication of the minor release is provided). The table also contain Epics currently under analysis which most probably will lead to the identification of Backlog Features to be planned also in the second Major Release * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. However, since there were no Backlog Features still planned, I have just created some fictitious features to make the reference example complete. If a FI-WARE GE does have Epics, but not Features, then write down "(not yet specified)" in the column about Features. * Regarding links to Features/Epics. They should be wiki references, as they appear in the reference example. No problem if they do not resolve in the FI-WARE Private Wiki, they should work once translated into the public Wiki * Description of Future Releases: * I believe we can keep this part as it is now I have prepared a section with placeholders for your contributions at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4 Please get them ready by Tuesday 12:00pm CET. It shouldn't be that difficult if you made a good exercise updating Epic/Features in the Backlog. During the rest of August, you should update the stakeholder field of each Epic/Feature in the backlog. Please do it with the best of your knowledge. Put "FI-WARE partners" if an Epic/Feature doesn't come from an UC project but was there within our original plans. Add the name of a UC project if you already know they are looking for it (based, for example, on feedback from the educational sessions). We will ask UC projects in parallel to review the Epics/Features on the wiki and add the name of their project in the plan to use the GE and wish to use the functionality linked to that Epic/Feature. 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 ________________________________ 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 Thu Aug 16 12:03:05 2012 From: mcp at tid.es (Miguel Carrillo) Date: Thu, 16 Aug 2012 12:03:05 +0200 Subject: [Fiware-iot] [Suspected Spam] Re: Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap In-Reply-To: <8755F290097BD941865DC4245B335D2D294B9A50@PALLENE.office.hd> References: <5028A975.4010405@tid.es> <50290A3C.70403@tid.es> <8755F290097BD941865DC4245B335D2D168B91D6@PALLENE.office.hd> <502CBC68.2090504@tid.es> <8755F290097BD941865DC4245B335D2D294B9A50@PALLENE.office.hd> Message-ID: <502CC559.50901@tid.es> Dear Tobias, Thanks for the update, I understand. I made a few (cosmetic) changes to make it uniform with contributions of the rest of the chapters (basically, removing bullet points). As regards for a "cleverer" review (i.e. the contents), it is Juanjo the one who will approve or provide feedback. Thanks again! Miguel El 16/08/2012 11:40, Tobias Jacobs escribi?: Dear Miguel, We are at the moment trying to catch up as good as we can. Could you have a look at the current draft at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT_%28Resubmission%29 and make a comment if this goes into the right direction? The main problem is that now many partners are on holidays, so I have difficulties correctly mapping the features to the release dates. Best Tobias From: Miguel Carrillo [mailto:mcp at tid.es] Sent: Donnerstag, 16. August 2012 11:25 To: Tobias Jacobs Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear Tobias, Sorry for the belated response, I was not at the office yesterday and on Tuesday. Anything that you can do will be much appreciated. I am really surprised that this is left to itself with no one taking care of it officially! I see messages that hint that something is being done so let us hope that we can complete the task! Thanks Miguel El 14/08/2012 10:15, Tobias Jacobs escribi?: Dear Miguel, The situation in IoT is somewhat unclear at the moment, as the WPA (which was NSN) has left the work package two week ago. I have to admit that I do not really have an overview about the overall status of the deliverables, but what I can offer is to check the minutes of the weekly meetings and try to find out what the status is. Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Montag, 13. August 2012 16:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear all, Sorry for contacting you directly but there is something of the utmost importance and we need to make sure that it is properly attended. If you see the enclosed message, the Project Coordinator is preparing the final delivery that will be sent out very soon. We are in the process of closing the Technical Roadmap deliverable and IoT seems the only chapter that has not delivered their contributions (I2ND had created them in time but they forgot to link them to the placeholder). This is largely the responsibility of the WP Leader but I do not know who is replacing Thierry in his holidays. Who has been appointed by him as contact point in his absence? (I see from his vacation email that he is on leave until the end of the month but he does not mention any replacement or deputy) Best regards, Miguel -------- Mensaje original -------- Asunto: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Fecha: Mon, 13 Aug 2012 09:15:01 +0200 De: Juanjo Hierro A: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear all, I have checked the contributions by the different chapters to the resubmission of the Technical Roadmap and all are Ok IMHO but the one from the IoT and the I2ND chapters that are still missing. I would suggest that the rest of chapters upload their contributions to the FI-WARE public wiki so that contents of their respective chapter get updated the same way that the Apps Chapter has done. It would be nice that they implement one enhancement that the Apps Chapter has introduced that I rather like: create a wiki link between the names of the GEs when they appear in the Technical Roadmap page (i.e., the tables listing Features/Epics) and the corresponding section on the "Materializing the FI-WARE Vision" part of the wiki. Deadline for the IoT chapter to complete their task is August 15th EOB. Please get it done so that we can officially resubmit by August 16th. Rest of chapters are free to update their contributions until August 15th EOB if they desire to do so. In order to complete the picture, don't miss that one remaining task would be that of updating the Stakeholder field in each backlog entry linked to an Epic or Feature published on the wiki. I would suggest using "FI-WARE" in the case this is a need identified by us, instead of naming a specific partner of FI-WARE. This will avoid questions like "Is only xxx the partner in FI-WARE asking for this feature ?". You can keep information about the specific company that proposed the feature by using the field "Owner". You should also try to add the name of those UC projects that you know are also asking for that Epic or Feature (thanks to interaction during/after the educational weeks). We will nevertheless ask the UC projects to list themselves in the Stakeholder field on another track (but this once we have published the new contents of the Technical Roadmap with the tables of Epics and Features) Besides this, I would kindly ask you to carry out a revision of the tracker of your chapter to make sure it gets aligned with what is currently on the Wiki, thus we can start from a new page in September: * Some of the Epics/Features may have changed, so please translate whatever change on the tracker * Make sure that Release Ids (numbering) is ok. I remind you the conventions at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Don't forget that reviewers have also asked us to resubmit the tracker contents, so this is an exercise that we definitively have to do. Last but not least, regarding updates of Technical Roadmap wiki pages, a couple of minor comments though: * Regarding contribution of the Cloud chapter: * Please update listing of features linked to the Cloud Proxy GE so that it aligns with the rest of the table * You didn't need a table for "Future Releases". You can mention that you will work in a "stabilized version taking into account new Use Cases requirements" in a dedicated statement within the last paragraph * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) * Regarding contribution of the Security chapter: * Please use references to wiki pages on the public wiki (built using the notation '[[]]') instead of hyperlinks * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps 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 ________________________________ 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: From t.elsaleh at surrey.ac.uk Thu Aug 16 12:06:30 2012 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Thu, 16 Aug 2012 11:06:30 +0100 Subject: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap In-Reply-To: <8755F290097BD941865DC4245B335D2D294B9A50@PALLENE.office.hd> References: <5028A975.4010405@tid.es> <50290A3C.70403@tid.es> <8755F290097BD941865DC4245B335D2D168B91D6@PALLENE.office.hd> <502CBC68.2090504@tid.es> <8755F290097BD941865DC4245B335D2D294B9A50@PALLENE.office.hd> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA59381FD0B@EXMB05CMS.surrey.ac.uk> Hello, I added 2 Epics and 2 Features yesterday, but 1 Epic and 1 Feature have been taken out by someone. Can someone please explain why? Are Features only required in this deliverable? I understood from Juanjo's email that Epics are also included. Juanjo, from you recent email you mentioned that there is a column for Epics in the tables. I honestly can't see where it is in any of the tables in the Roadmap page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT_%28Resubmission%29 Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: 16 August 2012 10:41 To: Miguel Carrillo Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear Miguel, We are at the moment trying to catch up as good as we can. Could you have a look at the current draft at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT_%28Resubmission%29 and make a comment if this goes into the right direction? The main problem is that now many partners are on holidays, so I have difficulties correctly mapping the features to the release dates. Best Tobias From: Miguel Carrillo [mailto:mcp at tid.es] Sent: Donnerstag, 16. August 2012 11:25 To: Tobias Jacobs Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear Tobias, Sorry for the belated response, I was not at the office yesterday and on Tuesday. Anything that you can do will be much appreciated. I am really surprised that this is left to itself with no one taking care of it officially! I see messages that hint that something is being done so let us hope that we can complete the task! Thanks Miguel El 14/08/2012 10:15, Tobias Jacobs escribi?: Dear Miguel, The situation in IoT is somewhat unclear at the moment, as the WPA (which was NSN) has left the work package two week ago. I have to admit that I do not really have an overview about the overall status of the deliverables, but what I can offer is to check the minutes of the weekly meetings and try to find out what the status is. Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Montag, 13. August 2012 16:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear all, Sorry for contacting you directly but there is something of the utmost importance and we need to make sure that it is properly attended. If you see the enclosed message, the Project Coordinator is preparing the final delivery that will be sent out very soon. We are in the process of closing the Technical Roadmap deliverable and IoT seems the only chapter that has not delivered their contributions (I2ND had created them in time but they forgot to link them to the placeholder). This is largely the responsibility of the WP Leader but I do not know who is replacing Thierry in his holidays. Who has been appointed by him as contact point in his absence? (I see from his vacation email that he is on leave until the end of the month but he does not mention any replacement or deputy) Best regards, Miguel -------- Mensaje original -------- Asunto: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Fecha: Mon, 13 Aug 2012 09:15:01 +0200 De: Juanjo Hierro A: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear all, I have checked the contributions by the different chapters to the resubmission of the Technical Roadmap and all are Ok IMHO but the one from the IoT and the I2ND chapters that are still missing. I would suggest that the rest of chapters upload their contributions to the FI-WARE public wiki so that contents of their respective chapter get updated the same way that the Apps Chapter has done. It would be nice that they implement one enhancement that the Apps Chapter has introduced that I rather like: create a wiki link between the names of the GEs when they appear in the Technical Roadmap page (i.e., the tables listing Features/Epics) and the corresponding section on the "Materializing the FI-WARE Vision" part of the wiki. Deadline for the IoT chapter to complete their task is August 15th EOB. Please get it done so that we can officially resubmit by August 16th. Rest of chapters are free to update their contributions until August 15th EOB if they desire to do so. In order to complete the picture, don't miss that one remaining task would be that of updating the Stakeholder field in each backlog entry linked to an Epic or Feature published on the wiki. I would suggest using "FI-WARE" in the case this is a need identified by us, instead of naming a specific partner of FI-WARE. This will avoid questions like "Is only xxx the partner in FI-WARE asking for this feature ?". You can keep information about the specific company that proposed the feature by using the field "Owner". You should also try to add the name of those UC projects that you know are also asking for that Epic or Feature (thanks to interaction during/after the educational weeks). We will nevertheless ask the UC projects to list themselves in the Stakeholder field on another track (but this once we have published the new contents of the Technical Roadmap with the tables of Epics and Features) Besides this, I would kindly ask you to carry out a revision of the tracker of your chapter to make sure it gets aligned with what is currently on the Wiki, thus we can start from a new page in September: * Some of the Epics/Features may have changed, so please translate whatever change on the tracker * Make sure that Release Ids (numbering) is ok. I remind you the conventions at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Don't forget that reviewers have also asked us to resubmit the tracker contents, so this is an exercise that we definitively have to do. Last but not least, regarding updates of Technical Roadmap wiki pages, a couple of minor comments though: * Regarding contribution of the Cloud chapter: * Please update listing of features linked to the Cloud Proxy GE so that it aligns with the rest of the table * You didn't need a table for "Future Releases". You can mention that you will work in a "stabilized version taking into account new Use Cases requirements" in a dedicated statement within the last paragraph * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) * Regarding contribution of the Security chapter: * Please use references to wiki pages on the public wiki (built using the notation '[[]]') instead of hyperlinks * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps 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 ________________________________ 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: From jhierro at tid.es Thu Aug 16 12:09:39 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 16 Aug 2012 12:09:39 +0200 Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap In-Reply-To: <502CC4DB.8020102@tid.es> References: <8755F290097BD941865DC4245B335D2D294B2678@DAPHNIS.office.hd> <2AAC0B6FF99A064C853BFB1C9295F3CCA59381FC72@EXMB05CMS.surrey.ac.uk> <41BC1993-758D-4C24-97C1-1A8B327DF93F@tid.es> <8755F290097BD941865DC4245B335D2D294B89EF@PALLENE.office.hd> <502CC4DB.8020102@tid.es> Message-ID: <502CC6E3.9030303@tid.es> Note that for GEs planned in the second release, it's fine to only have Epics at this point (despite soon they should turn into planned features). The message would be that we know what sort of functionality we are going to address, but we need to further refine its definition so that the Epics turn into more concrete "features" that can be planned into a minor release. That's why the table for second release was different and didn't include only a column for features but for both Features (already concrete functionality that is planned for some minor release) or Epics to be analyzed. Hope this helps and, we these insights, you may deliver a more complete shot of the tables. 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 16/08/12 12:00, Juanjo Hierro wrote: Hi, Let's extend the deadline until today EOB. Then I review and make the final editings so that we can officially deliver tomorrow. A couple of questions, that came to my mind while reviewing what was there: * My understanding is that we have to change everything related the Backend Device Management GE given the fact that NSN has dropped out and there will no implementation delivered. My guess would be to change every related feature to the 2nd Release ... * The table proposed in the template for the 2nd Release was slightly different. It deliberately included a column for Epics, so please use that one and place the Epics in the corresponding column * I don't see any feature related to the Backend nor Gateway Security GEs in any Release ... Then I would go for dropping its rows. If there are Epics identified for this GE, then I would go for having it in the second release since that table would include a column for Epics ... so therefore I would add the Epics there. Similar rule applies to any other GE Please try to fix the above points and collect any other additional input that may help to complete the roadmap description. 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 16/08/12 08:48, Tobias Jacobs wrote: Hi all, Thank for all contributions we received so far! As for the missing ones, I guess we now have to live with my guessings. I had a look into the tracker, and there most features were either assigned to release 1.3 or earlier or did not have an assigned release number at all. Juanjo, do you still want to edit something? (it looks like you did some editings, although your name does not appear in the edit history). Somebody else still wants to do something within the next few hours, let's say until noon? Otherwise I would send Miguel a message that the WP5 contribution is 'ready'. Oh, and sorry for not having reacted yesterday afternoon, for some reasons I did not receive any emails. Best regards Tobias From: JUAN JOSE HIERRO SUREDA [mailto:jhierro at tid.es] Sent: Mittwoch, 15. August 2012 15:36 To: t.elsaleh at surrey.ac.uk Cc: Tobias Jacobs; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap You don't need to duplicate the contents. It's fine if the wiki links just work once we upload the page into the public wiki Enviado desde mi iPhone El 15/08/2012, a las 14:00, "t.elsaleh at surrey.ac.uk" > escribi?: Hello Tobias, >From USurrey point of view, we have edited the Technical Roadmap deliverable wiki page to accommodate USurrey's Epics and Features headers to the table for the Backend Second Release. One question, can we just link these headers to their corresponding original Epic/Features pages, or do we have to duplicate the content as an internal link? Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: 15 August 2012 10:32 To: Juanjo Hierro; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi all, I just created a first version of the Revised Technical Roadmap. It might look nice at first glance, however the assignment of Features to Release number is nearly completely RANDOM, based on my GUESSING. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT_%28Resubmission%29 So please please, we need every partner to revise the page above, and I guess this is by today. It is a task that every GE owner can fulfill within fifteen minutes, so I would say we will not run into editing conflicts. Please send an email to this list when you are done editing, so that we have an overview. As many people are on holiday, the big question is what to do with the GEs owners who cannot do this task in time. Rather remove the features, or rather keep the random assignment to releases? Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 15. August 2012 11:04 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi all, There were clear and precise instructions on how to deal with this deliverable since August 3rd. Please find them enclosed. Despite also an example was provided at that time, you may already check the contributions from the other chapters for reference. It's basically a matter of adding a number of tables, which make reference to the Epics/Features in the FI-WARE Backlog. In the case of the Things Management GEs, they can easily be created, and I could even do it myself, but I have no clear idea about the rest of GEs in the IoT chapter. Since we are in a rush and it will be rather difficult to organize parallel editing of the wiki at this point, I would kindly ask you to provide your input to such tables in some sort of spreadsheet and I can take care of the final editing of the page later tonight. Could NEC provide the template for that spreadsheet and distribute it to the rest of the IoT team so that they can return them filled by EOB today ? Cheers, -- Juanjo -------- Original Message -------- Subject: Instructions for resubmission of FI-WARE Technical Roadmap Date: Fri, 03 Aug 2012 10:02:26 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear colleagues, Please find here the instructions to be followed to generate a new version of the Technical Roadmap deliverable to be published on the public Wiki and be resubmitted to the EC. The instructions are pretty simple and the best way to explain them is by referring to the example I have created on the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Example_(Resubmission)_-_Reference_Example That example is based on the current contents of the Technical Roadmap linked to the Apps Chapter. Based on that, the steps to follow are: * Update the Introduction: * We should make a reference to contents of the FI-WARE Architecture and Open Specifications part of the wiki, rather than the FI-WARE Product Vision (at the time at which the first version of the Technical Roadmap, the Architecture and Open Specifications didn't exist, but this is no longer the case) * You should also refer to the page dealing with Release and Sprint numbering, with reference to calendar dates. * All of this may be done by simple copy&paste from the reference example. * Description of first Major Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that will be supported. The table shall be preceded by the paragraph: * For a more detailed description of features provided, you can refer to the following table which help to identify what Backlog Features will be supported for each FI-WARE GE: * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. Essentially, you just need to include the references to the Backlog Features that have been addressed in the first Release for each FI-WARE GE (note this list should also include Features supported by the baseline assets) * When you distinguished between the delivery by end of July and by end of September, the above three points indeed apply per each (section for the release by end of July and section for the release by end of September) * Description of second Mayor Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that have already been planned or the Epics that will be analyzed and further refine which it is foreseen will lead to specification of Features to be planned as part of the second release. The table shall be preceded by the paragraph: * For a more detailed description of features to be provided, you can refer to the following table which help to identify what Backlog Features have already been specified and planned for the second Major Release of FI-WARE (and indication of the minor release is provided). The table also contain Epics currently under analysis which most probably will lead to the identification of Backlog Features to be planned also in the second Major Release * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. However, since there were no Backlog Features still planned, I have just created some fictitious features to make the reference example complete. If a FI-WARE GE does have Epics, but not Features, then write down "(not yet specified)" in the column about Features. * Regarding links to Features/Epics. They should be wiki references, as they appear in the reference example. No problem if they do not resolve in the FI-WARE Private Wiki, they should work once translated into the public Wiki * Description of Future Releases: * I believe we can keep this part as it is now I have prepared a section with placeholders for your contributions at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4 Please get them ready by Tuesday 12:00pm CET. It shouldn't be that difficult if you made a good exercise updating Epic/Features in the Backlog. During the rest of August, you should update the stakeholder field of each Epic/Feature in the backlog. Please do it with the best of your knowledge. Put "FI-WARE partners" if an Epic/Feature doesn't come from an UC project but was there within our original plans. Add the name of a UC project if you already know they are looking for it (based, for example, on feedback from the educational sessions). We will ask UC projects in parallel to review the Epics/Features on the wiki and add the name of their project in the plan to use the GE and wish to use the functionality linked to that Epic/Feature. 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 ________________________________ 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 Thu Aug 16 12:31:40 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 16 Aug 2012 12:31:40 +0200 Subject: [Fiware-iot] [Suspected Spam] Re: Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCA59381FD0B@EXMB05CMS.surrey.ac.uk> References: <5028A975.4010405@tid.es> <50290A3C.70403@tid.es> <8755F290097BD941865DC4245B335D2D168B91D6@PALLENE.office.hd> <502CBC68.2090504@tid.es> <8755F290097BD941865DC4245B335D2D294B9A50@PALLENE.office.hd> <2AAC0B6FF99A064C853BFB1C9295F3CCA59381FD0B@EXMB05CMS.surrey.ac.uk> Message-ID: <502CCC0C.50707@tid.es> On 16/08/12 12:06, t.elsaleh at surrey.ac.uk wrote: Hello, I added 2 Epics and 2 Features yesterday, but 1 Epic and 1 Feature have been taken out by someone. Can someone please explain why? Are Features only required in this deliverable? I understood from Juanjo's email that Epics are also included. Juanjo, from you recent email you mentioned that there is a column for Epics in the tables. I honestly can't see where it is in any of the tables in the Roadmap page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT_%28Resubmission%29 It was on the reference example that was provided in the email I sent on August 3rd (yes, that was the date at which detailed instructions were given to FI-WARE WPLs and WPAs): https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Example_(Resubmission)_-_Reference_Example I'll foward all of your that email for your convenience in my next message. Best regards, -- Juanjo Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: 16 August 2012 10:41 To: Miguel Carrillo Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear Miguel, We are at the moment trying to catch up as good as we can. Could you have a look at the current draft at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT_%28Resubmission%29 and make a comment if this goes into the right direction? The main problem is that now many partners are on holidays, so I have difficulties correctly mapping the features to the release dates. Best Tobias From: Miguel Carrillo [mailto:mcp at tid.es] Sent: Donnerstag, 16. August 2012 11:25 To: Tobias Jacobs Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear Tobias, Sorry for the belated response, I was not at the office yesterday and on Tuesday. Anything that you can do will be much appreciated. I am really surprised that this is left to itself with no one taking care of it officially! I see messages that hint that something is being done so let us hope that we can complete the task! Thanks Miguel El 14/08/2012 10:15, Tobias Jacobs escribi?: Dear Miguel, The situation in IoT is somewhat unclear at the moment, as the WPA (which was NSN) has left the work package two week ago. I have to admit that I do not really have an overview about the overall status of the deliverables, but what I can offer is to check the minutes of the weekly meetings and try to find out what the status is. Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Montag, 13. August 2012 16:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear all, Sorry for contacting you directly but there is something of the utmost importance and we need to make sure that it is properly attended. If you see the enclosed message, the Project Coordinator is preparing the final delivery that will be sent out very soon. We are in the process of closing the Technical Roadmap deliverable and IoT seems the only chapter that has not delivered their contributions (I2ND had created them in time but they forgot to link them to the placeholder). This is largely the responsibility of the WP Leader but I do not know who is replacing Thierry in his holidays. Who has been appointed by him as contact point in his absence? (I see from his vacation email that he is on leave until the end of the month but he does not mention any replacement or deputy) Best regards, Miguel -------- Mensaje original -------- Asunto: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Fecha: Mon, 13 Aug 2012 09:15:01 +0200 De: Juanjo Hierro A: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear all, I have checked the contributions by the different chapters to the resubmission of the Technical Roadmap and all are Ok IMHO but the one from the IoT and the I2ND chapters that are still missing. I would suggest that the rest of chapters upload their contributions to the FI-WARE public wiki so that contents of their respective chapter get updated the same way that the Apps Chapter has done. It would be nice that they implement one enhancement that the Apps Chapter has introduced that I rather like: create a wiki link between the names of the GEs when they appear in the Technical Roadmap page (i.e., the tables listing Features/Epics) and the corresponding section on the "Materializing the FI-WARE Vision" part of the wiki. Deadline for the IoT chapter to complete their task is August 15th EOB. Please get it done so that we can officially resubmit by August 16th. Rest of chapters are free to update their contributions until August 15th EOB if they desire to do so. In order to complete the picture, don't miss that one remaining task would be that of updating the Stakeholder field in each backlog entry linked to an Epic or Feature published on the wiki. I would suggest using "FI-WARE" in the case this is a need identified by us, instead of naming a specific partner of FI-WARE. This will avoid questions like "Is only xxx the partner in FI-WARE asking for this feature ?". You can keep information about the specific company that proposed the feature by using the field "Owner". You should also try to add the name of those UC projects that you know are also asking for that Epic or Feature (thanks to interaction during/after the educational weeks). We will nevertheless ask the UC projects to list themselves in the Stakeholder field on another track (but this once we have published the new contents of the Technical Roadmap with the tables of Epics and Features) Besides this, I would kindly ask you to carry out a revision of the tracker of your chapter to make sure it gets aligned with what is currently on the Wiki, thus we can start from a new page in September: * Some of the Epics/Features may have changed, so please translate whatever change on the tracker * Make sure that Release Ids (numbering) is ok. I remind you the conventions at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Don't forget that reviewers have also asked us to resubmit the tracker contents, so this is an exercise that we definitively have to do. Last but not least, regarding updates of Technical Roadmap wiki pages, a couple of minor comments though: * Regarding contribution of the Cloud chapter: * Please update listing of features linked to the Cloud Proxy GE so that it aligns with the rest of the table * You didn't need a table for "Future Releases". You can mention that you will work in a "stabilized version taking into account new Use Cases requirements" in a dedicated statement within the last paragraph * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) * Regarding contribution of the Security chapter: * Please use references to wiki pages on the public wiki (built using the notation '[[]]') instead of hyperlinks * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps 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 ________________________________ 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 ________________________________ 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 Thu Aug 16 12:33:31 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 16 Aug 2012 12:33:31 +0200 Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap In-Reply-To: <501B8592.9040109@tid.es> References: <501B8592.9040109@tid.es> Message-ID: <502CCC7B.3020605@tid.es> Hi, Please find enclosed the email of August 3rd with the original instructions. Besides the reference example that I provided at that time, you can know check the contributions by the rest of the chapters in their corresponding placeholders. They can also be useful as a reference. 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 -------- Original Message -------- Subject: Instructions for resubmission of FI-WARE Technical Roadmap Date: Fri, 03 Aug 2012 10:02:26 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear colleagues, Please find here the instructions to be followed to generate a new version of the Technical Roadmap deliverable to be published on the public Wiki and be resubmitted to the EC. The instructions are pretty simple and the best way to explain them is by referring to the example I have created on the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Example_(Resubmission)_-_Reference_Example That example is based on the current contents of the Technical Roadmap linked to the Apps Chapter. Based on that, the steps to follow are: * Update the Introduction: * We should make a reference to contents of the FI-WARE Architecture and Open Specifications part of the wiki, rather than the FI-WARE Product Vision (at the time at which the first version of the Technical Roadmap, the Architecture and Open Specifications didn't exist, but this is no longer the case) * You should also refer to the page dealing with Release and Sprint numbering, with reference to calendar dates. * All of this may be done by simple copy&paste from the reference example. * Description of first Major Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that will be supported. The table shall be preceded by the paragraph: * For a more detailed description of features provided, you can refer to the following table which help to identify what Backlog Features will be supported for each FI-WARE GE: * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. Essentially, you just need to include the references to the Backlog Features that have been addressed in the first Release for each FI-WARE GE (note this list should also include Features supported by the baseline assets) * When you distinguished between the delivery by end of July and by end of September, the above three points indeed apply per each (section for the release by end of July and section for the release by end of September) * Description of second Mayor Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that have already been planned or the Epics that will be analyzed and further refine which it is foreseen will lead to specification of Features to be planned as part of the second release. The table shall be preceded by the paragraph: * For a more detailed description of features to be provided, you can refer to the following table which help to identify what Backlog Features have already been specified and planned for the second Major Release of FI-WARE (and indication of the minor release is provided). The table also contain Epics currently under analysis which most probably will lead to the identification of Backlog Features to be planned also in the second Major Release * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. However, since there were no Backlog Features still planned, I have just created some fictitious features to make the reference example complete. If a FI-WARE GE does have Epics, but not Features, then write down "(not yet specified)" in the column about Features. * Regarding links to Features/Epics. They should be wiki references, as they appear in the reference example. No problem if they do not resolve in the FI-WARE Private Wiki, they should work once translated into the public Wiki * Description of Future Releases: * I believe we can keep this part as it is now I have prepared a section with placeholders for your contributions at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4 Please get them ready by Tuesday 12:00pm CET. It shouldn't be that difficult if you made a good exercise updating Epic/Features in the Backlog. During the rest of August, you should update the stakeholder field of each Epic/Feature in the backlog. Please do it with the best of your knowledge. Put "FI-WARE partners" if an Epic/Feature doesn't come from an UC project but was there within our original plans. Add the name of a UC project if you already know they are looking for it (based, for example, on feedback from the educational sessions). We will ask UC projects in parallel to review the Epics/Features on the wiki and add the name of their project in the plan to use the GE and wish to use the functionality linked to that Epic/Feature. 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 Thu Aug 16 12:49:57 2012 From: mcp at tid.es (Miguel Carrillo) Date: Thu, 16 Aug 2012 12:49:57 +0200 Subject: [Fiware-iot] documents publicly visible on the IoT docman Message-ID: <502CD055.3030600@tid.es> Dear all, This is how an unlogged user sees our IoT documentation repository. All the files you see here are public, please verify if all this can be accessible to anyone on the internet. [cid:part1.06040404.03050406 at tid.es] Do not forget that there is a tutorial to make documents private. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: icdibdea.png Type: image/png Size: 29059 bytes Desc: not available URL: From t.elsaleh at surrey.ac.uk Thu Aug 16 16:07:05 2012 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Thu, 16 Aug 2012 15:07:05 +0100 Subject: [Fiware-iot] documents publicly visible on the IoT docman In-Reply-To: <502CD055.3030600@tid.es> References: <502CD055.3030600@tid.es> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA59381FD81@EXMB05CMS.surrey.ac.uk> Hello Miguel, Tobias, No problem with the repository from USurrey side. By the way, if USurrey can help in any way then please let us know. Best regards, Tarek ------------------------------------------------------------- Tarek Elsaleh Research Assistant Centre for Commuication Systems Research (CCSR) Department of Electronic Engineering University of Surrey Guildford, GU2 7XH Tel: 01483 689485 ------------------------------------------------------------- From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: 16 August 2012 11:50 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] documents publicly visible on the IoT docman Dear all, This is how an unlogged user sees our IoT documentation repository. All the files you see here are public, please verify if all this can be accessible to anyone on the internet. [cid:image001.png at 01CD7BC0.CBFDAF30] Do not forget that there is a tutorial to make documents private. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 29059 bytes Desc: image001.png URL: From Tobias.Jacobs at neclab.eu Thu Aug 16 16:54:59 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Thu, 16 Aug 2012 14:54:59 +0000 Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap In-Reply-To: <502CC4DB.8020102@tid.es> References: <8755F290097BD941865DC4245B335D2D294B2678@DAPHNIS.office.hd> <2AAC0B6FF99A064C853BFB1C9295F3CCA59381FC72@EXMB05CMS.surrey.ac.uk> <41BC1993-758D-4C24-97C1-1A8B327DF93F@tid.es> <8755F290097BD941865DC4245B335D2D294B89EF@PALLENE.office.hd> <502CC4DB.8020102@tid.es> Message-ID: <8755F290097BD941865DC4245B335D2D294BAAFB@PALLENE.office.hd> Dear all, I made a revision according to Juanjo's suggestions below. - Moved everything about the Backend Device Manager to the 2nd major release - Added ALL epics of ALL GEs to a new column in the tables of the 2nd major release. @all: If you have time, please check if you are ok with it. In addition: - Removed (i.e. commented out) the high-level description of the Gateway Things Management GE. I do not think there will be one, will there? Best regards Tobias From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Donnerstag, 16. August 2012 12:01 To: Tobias Jacobs Cc: t.elsaleh at surrey.ac.uk; fiware-iot at lists.fi-ware.eu; jhierro >> "Juan J. Hierro" Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi, Let's extend the deadline until today EOB. Then I review and make the final editings so that we can officially deliver tomorrow. A couple of questions, that came to my mind while reviewing what was there: * My understanding is that we have to change everything related the Backend Device Management GE given the fact that NSN has dropped out and there will no implementation delivered. My guess would be to change every related feature to the 2nd Release ... * The table proposed in the template for the 2nd Release was slightly different. It deliberately included a column for Epics, so please use that one and place the Epics in the corresponding column * I don't see any feature related to the Backend nor Gateway Security GEs in any Release ... Then I would go for dropping its rows. If there are Epics identified for this GE, then I would go for having it in the second release since that table would include a column for Epics ... so therefore I would add the Epics there. Similar rule applies to any other GE Please try to fix the above points and collect any other additional input that may help to complete the roadmap description. 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 16/08/12 08:48, Tobias Jacobs wrote: Hi all, Thank for all contributions we received so far! As for the missing ones, I guess we now have to live with my guessings. I had a look into the tracker, and there most features were either assigned to release 1.3 or earlier or did not have an assigned release number at all. Juanjo, do you still want to edit something? (it looks like you did some editings, although your name does not appear in the edit history). Somebody else still wants to do something within the next few hours, let's say until noon? Otherwise I would send Miguel a message that the WP5 contribution is 'ready'. Oh, and sorry for not having reacted yesterday afternoon, for some reasons I did not receive any emails. Best regards Tobias From: JUAN JOSE HIERRO SUREDA [mailto:jhierro at tid.es] Sent: Mittwoch, 15. August 2012 15:36 To: t.elsaleh at surrey.ac.uk Cc: Tobias Jacobs; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap You don't need to duplicate the contents. It's fine if the wiki links just work once we upload the page into the public wiki Enviado desde mi iPhone El 15/08/2012, a las 14:00, "t.elsaleh at surrey.ac.uk" > escribi?: Hello Tobias, >From USurrey point of view, we have edited the Technical Roadmap deliverable wiki page to accommodate USurrey's Epics and Features headers to the table for the Backend Second Release. One question, can we just link these headers to their corresponding original Epic/Features pages, or do we have to duplicate the content as an internal link? Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: 15 August 2012 10:32 To: Juanjo Hierro; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi all, I just created a first version of the Revised Technical Roadmap. It might look nice at first glance, however the assignment of Features to Release number is nearly completely RANDOM, based on my GUESSING. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT_%28Resubmission%29 So please please, we need every partner to revise the page above, and I guess this is by today. It is a task that every GE owner can fulfill within fifteen minutes, so I would say we will not run into editing conflicts. Please send an email to this list when you are done editing, so that we have an overview. As many people are on holiday, the big question is what to do with the GEs owners who cannot do this task in time. Rather remove the features, or rather keep the random assignment to releases? Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 15. August 2012 11:04 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi all, There were clear and precise instructions on how to deal with this deliverable since August 3rd. Please find them enclosed. Despite also an example was provided at that time, you may already check the contributions from the other chapters for reference. It's basically a matter of adding a number of tables, which make reference to the Epics/Features in the FI-WARE Backlog. In the case of the Things Management GEs, they can easily be created, and I could even do it myself, but I have no clear idea about the rest of GEs in the IoT chapter. Since we are in a rush and it will be rather difficult to organize parallel editing of the wiki at this point, I would kindly ask you to provide your input to such tables in some sort of spreadsheet and I can take care of the final editing of the page later tonight. Could NEC provide the template for that spreadsheet and distribute it to the rest of the IoT team so that they can return them filled by EOB today ? Cheers, -- Juanjo -------- Original Message -------- Subject: Instructions for resubmission of FI-WARE Technical Roadmap Date: Fri, 03 Aug 2012 10:02:26 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear colleagues, Please find here the instructions to be followed to generate a new version of the Technical Roadmap deliverable to be published on the public Wiki and be resubmitted to the EC. The instructions are pretty simple and the best way to explain them is by referring to the example I have created on the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Example_(Resubmission)_-_Reference_Example That example is based on the current contents of the Technical Roadmap linked to the Apps Chapter. Based on that, the steps to follow are: * Update the Introduction: * We should make a reference to contents of the FI-WARE Architecture and Open Specifications part of the wiki, rather than the FI-WARE Product Vision (at the time at which the first version of the Technical Roadmap, the Architecture and Open Specifications didn't exist, but this is no longer the case) * You should also refer to the page dealing with Release and Sprint numbering, with reference to calendar dates. * All of this may be done by simple copy&paste from the reference example. * Description of first Major Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that will be supported. The table shall be preceded by the paragraph: * For a more detailed description of features provided, you can refer to the following table which help to identify what Backlog Features will be supported for each FI-WARE GE: * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. Essentially, you just need to include the references to the Backlog Features that have been addressed in the first Release for each FI-WARE GE (note this list should also include Features supported by the baseline assets) * When you distinguished between the delivery by end of July and by end of September, the above three points indeed apply per each (section for the release by end of July and section for the release by end of September) * Description of second Mayor Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that have already been planned or the Epics that will be analyzed and further refine which it is foreseen will lead to specification of Features to be planned as part of the second release. The table shall be preceded by the paragraph: * For a more detailed description of features to be provided, you can refer to the following table which help to identify what Backlog Features have already been specified and planned for the second Major Release of FI-WARE (and indication of the minor release is provided). The table also contain Epics currently under analysis which most probably will lead to the identification of Backlog Features to be planned also in the second Major Release * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. However, since there were no Backlog Features still planned, I have just created some fictitious features to make the reference example complete. If a FI-WARE GE does have Epics, but not Features, then write down "(not yet specified)" in the column about Features. * Regarding links to Features/Epics. They should be wiki references, as they appear in the reference example. No problem if they do not resolve in the FI-WARE Private Wiki, they should work once translated into the public Wiki * Description of Future Releases: * I believe we can keep this part as it is now I have prepared a section with placeholders for your contributions at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4 Please get them ready by Tuesday 12:00pm CET. It shouldn't be that difficult if you made a good exercise updating Epic/Features in the Backlog. During the rest of August, you should update the stakeholder field of each Epic/Feature in the backlog. Please do it with the best of your knowledge. Put "FI-WARE partners" if an Epic/Feature doesn't come from an UC project but was there within our original plans. Add the name of a UC project if you already know they are looking for it (based, for example, on feedback from the educational sessions). We will ask UC projects in parallel to review the Epics/Features on the wiki and add the name of their project in the plan to use the GE and wish to use the functionality linked to that Epic/Feature. 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 ________________________________ 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 jakob.saros at ericsson.com Thu Aug 16 17:14:29 2012 From: jakob.saros at ericsson.com (Jakob Saros) Date: Thu, 16 Aug 2012 17:14:29 +0200 Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap In-Reply-To: <8755F290097BD941865DC4245B335D2D294BAAFB@PALLENE.office.hd> References: <8755F290097BD941865DC4245B335D2D294B2678@DAPHNIS.office.hd> <2AAC0B6FF99A064C853BFB1C9295F3CCA59381FC72@EXMB05CMS.surrey.ac.uk> <41BC1993-758D-4C24-97C1-1A8B327DF93F@tid.es> <8755F290097BD941865DC4245B335D2D294B89EF@PALLENE.office.hd> <502CC4DB.8020102@tid.es> <8755F290097BD941865DC4245B335D2D294BAAFB@PALLENE.office.hd> Message-ID: <9870BEE781B2694BA446B8FD65882E854912DD2009@ESESSCMS0363.eemea.ericsson.se> Hi Tobias, As far as I know no partner will provide the Gateway Things Management GE so I think you are right in removing it then. BR/Jakob ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: den 16 augusti 2012 16:55 To: Juanjo Hierro Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Dear all, I made a revision according to Juanjo's suggestions below. - Moved everything about the Backend Device Manager to the 2nd major release - Added ALL epics of ALL GEs to a new column in the tables of the 2nd major release. @all: If you have time, please check if you are ok with it. In addition: - Removed (i.e. commented out) the high-level description of the Gateway Things Management GE. I do not think there will be one, will there? Best regards Tobias From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Donnerstag, 16. August 2012 12:01 To: Tobias Jacobs Cc: t.elsaleh at surrey.ac.uk; fiware-iot at lists.fi-ware.eu; jhierro >> "Juan J. Hierro" Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi, Let's extend the deadline until today EOB. Then I review and make the final editings so that we can officially deliver tomorrow. A couple of questions, that came to my mind while reviewing what was there: * My understanding is that we have to change everything related the Backend Device Management GE given the fact that NSN has dropped out and there will no implementation delivered. My guess would be to change every related feature to the 2nd Release ... * The table proposed in the template for the 2nd Release was slightly different. It deliberately included a column for Epics, so please use that one and place the Epics in the corresponding column * I don't see any feature related to the Backend nor Gateway Security GEs in any Release ... Then I would go for dropping its rows. If there are Epics identified for this GE, then I would go for having it in the second release since that table would include a column for Epics ... so therefore I would add the Epics there. Similar rule applies to any other GE Please try to fix the above points and collect any other additional input that may help to complete the roadmap description. 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 16/08/12 08:48, Tobias Jacobs wrote: Hi all, Thank for all contributions we received so far! As for the missing ones, I guess we now have to live with my guessings. I had a look into the tracker, and there most features were either assigned to release 1.3 or earlier or did not have an assigned release number at all. Juanjo, do you still want to edit something? (it looks like you did some editings, although your name does not appear in the edit history). Somebody else still wants to do something within the next few hours, let's say until noon? Otherwise I would send Miguel a message that the WP5 contribution is 'ready'. Oh, and sorry for not having reacted yesterday afternoon, for some reasons I did not receive any emails. Best regards Tobias From: JUAN JOSE HIERRO SUREDA [mailto:jhierro at tid.es] Sent: Mittwoch, 15. August 2012 15:36 To: t.elsaleh at surrey.ac.uk Cc: Tobias Jacobs; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap You don't need to duplicate the contents. It's fine if the wiki links just work once we upload the page into the public wiki Enviado desde mi iPhone El 15/08/2012, a las 14:00, "t.elsaleh at surrey.ac.uk" > escribi?: Hello Tobias, >From USurrey point of view, we have edited the Technical Roadmap deliverable wiki page to accommodate USurrey's Epics and Features headers to the table for the Backend Second Release. One question, can we just link these headers to their corresponding original Epic/Features pages, or do we have to duplicate the content as an internal link? Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: 15 August 2012 10:32 To: Juanjo Hierro; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi all, I just created a first version of the Revised Technical Roadmap. It might look nice at first glance, however the assignment of Features to Release number is nearly completely RANDOM, based on my GUESSING. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT_%28Resubmission%29 So please please, we need every partner to revise the page above, and I guess this is by today. It is a task that every GE owner can fulfill within fifteen minutes, so I would say we will not run into editing conflicts. Please send an email to this list when you are done editing, so that we have an overview. As many people are on holiday, the big question is what to do with the GEs owners who cannot do this task in time. Rather remove the features, or rather keep the random assignment to releases? Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 15. August 2012 11:04 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi all, There were clear and precise instructions on how to deal with this deliverable since August 3rd. Please find them enclosed. Despite also an example was provided at that time, you may already check the contributions from the other chapters for reference. It's basically a matter of adding a number of tables, which make reference to the Epics/Features in the FI-WARE Backlog. In the case of the Things Management GEs, they can easily be created, and I could even do it myself, but I have no clear idea about the rest of GEs in the IoT chapter. Since we are in a rush and it will be rather difficult to organize parallel editing of the wiki at this point, I would kindly ask you to provide your input to such tables in some sort of spreadsheet and I can take care of the final editing of the page later tonight. Could NEC provide the template for that spreadsheet and distribute it to the rest of the IoT team so that they can return them filled by EOB today ? Cheers, -- Juanjo -------- Original Message -------- Subject: Instructions for resubmission of FI-WARE Technical Roadmap Date: Fri, 03 Aug 2012 10:02:26 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear colleagues, Please find here the instructions to be followed to generate a new version of the Technical Roadmap deliverable to be published on the public Wiki and be resubmitted to the EC. The instructions are pretty simple and the best way to explain them is by referring to the example I have created on the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Example_(Resubmission)_-_Reference_Example That example is based on the current contents of the Technical Roadmap linked to the Apps Chapter. Based on that, the steps to follow are: * Update the Introduction: * We should make a reference to contents of the FI-WARE Architecture and Open Specifications part of the wiki, rather than the FI-WARE Product Vision (at the time at which the first version of the Technical Roadmap, the Architecture and Open Specifications didn't exist, but this is no longer the case) * You should also refer to the page dealing with Release and Sprint numbering, with reference to calendar dates. * All of this may be done by simple copy&paste from the reference example. * Description of first Major Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that will be supported. The table shall be preceded by the paragraph: * For a more detailed description of features provided, you can refer to the following table which help to identify what Backlog Features will be supported for each FI-WARE GE: * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. Essentially, you just need to include the references to the Backlog Features that have been addressed in the first Release for each FI-WARE GE (note this list should also include Features supported by the baseline assets) * When you distinguished between the delivery by end of July and by end of September, the above three points indeed apply per each (section for the release by end of July and section for the release by end of September) * Description of second Mayor Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that have already been planned or the Epics that will be analyzed and further refine which it is foreseen will lead to specification of Features to be planned as part of the second release. The table shall be preceded by the paragraph: * For a more detailed description of features to be provided, you can refer to the following table which help to identify what Backlog Features have already been specified and planned for the second Major Release of FI-WARE (and indication of the minor release is provided). The table also contain Epics currently under analysis which most probably will lead to the identification of Backlog Features to be planned also in the second Major Release * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. However, since there were no Backlog Features still planned, I have just created some fictitious features to make the reference example complete. If a FI-WARE GE does have Epics, but not Features, then write down "(not yet specified)" in the column about Features. * Regarding links to Features/Epics. They should be wiki references, as they appear in the reference example. No problem if they do not resolve in the FI-WARE Private Wiki, they should work once translated into the public Wiki * Description of Future Releases: * I believe we can keep this part as it is now I have prepared a section with placeholders for your contributions at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4 Please get them ready by Tuesday 12:00pm CET. It shouldn't be that difficult if you made a good exercise updating Epic/Features in the Backlog. During the rest of August, you should update the stakeholder field of each Epic/Feature in the backlog. Please do it with the best of your knowledge. Put "FI-WARE partners" if an Epic/Feature doesn't come from an UC project but was there within our original plans. Add the name of a UC project if you already know they are looking for it (based, for example, on feedback from the educational sessions). We will ask UC projects in parallel to review the Epics/Features on the wiki and add the name of their project in the plan to use the GE and wish to use the functionality linked to that Epic/Feature. 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 ________________________________ 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 Aug 17 04:29:31 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 17 Aug 2012 04:29:31 +0200 Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap In-Reply-To: <8755F290097BD941865DC4245B335D2D294BAAFB@PALLENE.office.hd> References: <8755F290097BD941865DC4245B335D2D294B2678@DAPHNIS.office.hd> <2AAC0B6FF99A064C853BFB1C9295F3CCA59381FC72@EXMB05CMS.surrey.ac.uk> <41BC1993-758D-4C24-97C1-1A8B327DF93F@tid.es> <8755F290097BD941865DC4245B335D2D294B89EF@PALLENE.office.hd> <502CC4DB.8020102@tid.es> <8755F290097BD941865DC4245B335D2D294BAAFB@PALLENE.office.hd> Message-ID: <502DAC8B.7010408@tid.es> Hi Tobias, I took a look at what you have delivered and I believe it now complies with what required. Good job ! I have introduced some comestic/editorial changes such as deleting empty rows or adding blank lines after tables. There is some final checks and editorial work I would kindly ask you to perform: * check: Make sure that we don't have Epics in the tables for Release 2 for which Features have already been derived. Epics in those tables should only refer to Epics that have not been further refined into Features. * editorial: depending on the screen resolution and font size of who is browsing the wiki page, ids of features/epics may be displayed in the same line or in subsequent lines. The convention I would suggest to follow: * if you don't mind whether the features/epics become displayed one per line or several in the same line, then I would separate their ids with commas * if you prefer that each feature/epic appears in a single line, then I would suggest that you add '
' after the wiki link, for example: * [[FIWARE.Feature.IoT.Backend.ThingsManagement.Registration.simpleGeoScopes]]
* editorial: it was suggested that the name of each FI-WARE GE (listed in columns of each table and bullet lists in textual description) map to wiki links that points to the corresponding section in the "Materializing the FI-WARE vision" part of the public wiki. Check the contents of the Apps Chapter already available on the public wiki for reference. Once you have performed this final checks and editing tasks, please upload the contents into the publick wiki, replacing the current version of the Technical Roadmap at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Internet_of_Things_(IoT)_Services with the new one, then update the contents of the private wiki page informing that you have actually uploaded the contents. You can take as a reference the contents currently at the placeholder of the Cloud Hosting chapter in the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Cloud_(Resubmission) Last but not least, please drop Miguel and myself and email informing you are done. Thanks again for your great work in such a short timeframe. Best regards, -- Juanjo On 16/08/12 16:54, Tobias Jacobs wrote: Dear all, I made a revision according to Juanjo's suggestions below. - Moved everything about the Backend Device Manager to the 2nd major release - Added ALL epics of ALL GEs to a new column in the tables of the 2nd major release. @all: If you have time, please check if you are ok with it. In addition: - Removed (i.e. commented out) the high-level description of the Gateway Things Management GE. I do not think there will be one, will there? Best regards Tobias From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Donnerstag, 16. August 2012 12:01 To: Tobias Jacobs Cc: t.elsaleh at surrey.ac.uk; fiware-iot at lists.fi-ware.eu; jhierro >> "Juan J. Hierro" Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi, Let's extend the deadline until today EOB. Then I review and make the final editings so that we can officially deliver tomorrow. A couple of questions, that came to my mind while reviewing what was there: * My understanding is that we have to change everything related the Backend Device Management GE given the fact that NSN has dropped out and there will no implementation delivered. My guess would be to change every related feature to the 2nd Release ... * The table proposed in the template for the 2nd Release was slightly different. It deliberately included a column for Epics, so please use that one and place the Epics in the corresponding column * I don't see any feature related to the Backend nor Gateway Security GEs in any Release ... Then I would go for dropping its rows. If there are Epics identified for this GE, then I would go for having it in the second release since that table would include a column for Epics ... so therefore I would add the Epics there. Similar rule applies to any other GE Please try to fix the above points and collect any other additional input that may help to complete the roadmap description. 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 16/08/12 08:48, Tobias Jacobs wrote: Hi all, Thank for all contributions we received so far! As for the missing ones, I guess we now have to live with my guessings. I had a look into the tracker, and there most features were either assigned to release 1.3 or earlier or did not have an assigned release number at all. Juanjo, do you still want to edit something? (it looks like you did some editings, although your name does not appear in the edit history). Somebody else still wants to do something within the next few hours, let's say until noon? Otherwise I would send Miguel a message that the WP5 contribution is 'ready'. Oh, and sorry for not having reacted yesterday afternoon, for some reasons I did not receive any emails. Best regards Tobias From: JUAN JOSE HIERRO SUREDA [mailto:jhierro at tid.es] Sent: Mittwoch, 15. August 2012 15:36 To: t.elsaleh at surrey.ac.uk Cc: Tobias Jacobs; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap You don't need to duplicate the contents. It's fine if the wiki links just work once we upload the page into the public wiki Enviado desde mi iPhone El 15/08/2012, a las 14:00, "t.elsaleh at surrey.ac.uk" > escribi?: Hello Tobias, >From USurrey point of view, we have edited the Technical Roadmap deliverable wiki page to accommodate USurrey's Epics and Features headers to the table for the Backend Second Release. One question, can we just link these headers to their corresponding original Epic/Features pages, or do we have to duplicate the content as an internal link? Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: 15 August 2012 10:32 To: Juanjo Hierro; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi all, I just created a first version of the Revised Technical Roadmap. It might look nice at first glance, however the assignment of Features to Release number is nearly completely RANDOM, based on my GUESSING. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT_%28Resubmission%29 So please please, we need every partner to revise the page above, and I guess this is by today. It is a task that every GE owner can fulfill within fifteen minutes, so I would say we will not run into editing conflicts. Please send an email to this list when you are done editing, so that we have an overview. As many people are on holiday, the big question is what to do with the GEs owners who cannot do this task in time. Rather remove the features, or rather keep the random assignment to releases? Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 15. August 2012 11:04 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi all, There were clear and precise instructions on how to deal with this deliverable since August 3rd. Please find them enclosed. Despite also an example was provided at that time, you may already check the contributions from the other chapters for reference. It's basically a matter of adding a number of tables, which make reference to the Epics/Features in the FI-WARE Backlog. In the case of the Things Management GEs, they can easily be created, and I could even do it myself, but I have no clear idea about the rest of GEs in the IoT chapter. Since we are in a rush and it will be rather difficult to organize parallel editing of the wiki at this point, I would kindly ask you to provide your input to such tables in some sort of spreadsheet and I can take care of the final editing of the page later tonight. Could NEC provide the template for that spreadsheet and distribute it to the rest of the IoT team so that they can return them filled by EOB today ? Cheers, -- Juanjo -------- Original Message -------- Subject: Instructions for resubmission of FI-WARE Technical Roadmap Date: Fri, 03 Aug 2012 10:02:26 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear colleagues, Please find here the instructions to be followed to generate a new version of the Technical Roadmap deliverable to be published on the public Wiki and be resubmitted to the EC. The instructions are pretty simple and the best way to explain them is by referring to the example I have created on the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Example_(Resubmission)_-_Reference_Example That example is based on the current contents of the Technical Roadmap linked to the Apps Chapter. Based on that, the steps to follow are: * Update the Introduction: * We should make a reference to contents of the FI-WARE Architecture and Open Specifications part of the wiki, rather than the FI-WARE Product Vision (at the time at which the first version of the Technical Roadmap, the Architecture and Open Specifications didn't exist, but this is no longer the case) * You should also refer to the page dealing with Release and Sprint numbering, with reference to calendar dates. * All of this may be done by simple copy&paste from the reference example. * Description of first Major Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that will be supported. The table shall be preceded by the paragraph: * For a more detailed description of features provided, you can refer to the following table which help to identify what Backlog Features will be supported for each FI-WARE GE: * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. Essentially, you just need to include the references to the Backlog Features that have been addressed in the first Release for each FI-WARE GE (note this list should also include Features supported by the baseline assets) * When you distinguished between the delivery by end of July and by end of September, the above three points indeed apply per each (section for the release by end of July and section for the release by end of September) * Description of second Mayor Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that have already been planned or the Epics that will be analyzed and further refine which it is foreseen will lead to specification of Features to be planned as part of the second release. The table shall be preceded by the paragraph: * For a more detailed description of features to be provided, you can refer to the following table which help to identify what Backlog Features have already been specified and planned for the second Major Release of FI-WARE (and indication of the minor release is provided). The table also contain Epics currently under analysis which most probably will lead to the identification of Backlog Features to be planned also in the second Major Release * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. However, since there were no Backlog Features still planned, I have just created some fictitious features to make the reference example complete. If a FI-WARE GE does have Epics, but not Features, then write down "(not yet specified)" in the column about Features. * Regarding links to Features/Epics. They should be wiki references, as they appear in the reference example. No problem if they do not resolve in the FI-WARE Private Wiki, they should work once translated into the public Wiki * Description of Future Releases: * I believe we can keep this part as it is now I have prepared a section with placeholders for your contributions at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4 Please get them ready by Tuesday 12:00pm CET. It shouldn't be that difficult if you made a good exercise updating Epic/Features in the Backlog. During the rest of August, you should update the stakeholder field of each Epic/Feature in the backlog. Please do it with the best of your knowledge. Put "FI-WARE partners" if an Epic/Feature doesn't come from an UC project but was there within our original plans. Add the name of a UC project if you already know they are looking for it (based, for example, on feedback from the educational sessions). We will ask UC projects in parallel to review the Epics/Features on the wiki and add the name of their project in the plan to use the GE and wish to use the functionality linked to that Epic/Feature. 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 ________________________________ 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 ________________________________ 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 Tobias.Jacobs at neclab.eu Fri Aug 17 10:48:29 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Fri, 17 Aug 2012 08:48:29 +0000 Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap In-Reply-To: <502DAC8B.7010408@tid.es> References: <8755F290097BD941865DC4245B335D2D294B2678@DAPHNIS.office.hd> <2AAC0B6FF99A064C853BFB1C9295F3CCA59381FC72@EXMB05CMS.surrey.ac.uk> <41BC1993-758D-4C24-97C1-1A8B327DF93F@tid.es> <8755F290097BD941865DC4245B335D2D294B89EF@PALLENE.office.hd> <502CC4DB.8020102@tid.es> <8755F290097BD941865DC4245B335D2D294BAAFB@PALLENE.office.hd> <502DAC8B.7010408@tid.es> Message-ID: <8755F290097BD941865DC4245B335D2D294BBB5D@PALLENE.office.hd> Hi Miguel, Juanjo, all, The contents of the new IoT Technical Roadmap are now uploaded to the public wiki, see http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Internet_of_Things_(IoT)_Services My final edits were the following: - Removed the EPIC [[FIWARE.Epic.IoT.Gateway.DeviceManagement.DeviceStatusMonitoring]], as the corresponding wiki page does not exist - Removed some EPICs that were apparently covered by Features. I did this whenever for some epic there was a feature with the same name. In all other cases there is the possibility that the EPIC is not completely covered by existing features. - The two editorial changes (line breaks, linked GE names) requested below Best regards, and have a nice weekend! Tobias From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Freitag, 17. August 2012 04:30 To: Tobias Jacobs Cc: t.elsaleh at surrey.ac.uk; fiware-iot at lists.fi-ware.eu; Miguel Carrillo; jhierro >> "Juan J. Hierro" Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi Tobias, I took a look at what you have delivered and I believe it now complies with what required. Good job ! I have introduced some comestic/editorial changes such as deleting empty rows or adding blank lines after tables. There is some final checks and editorial work I would kindly ask you to perform: * check: Make sure that we don't have Epics in the tables for Release 2 for which Features have already been derived. Epics in those tables should only refer to Epics that have not been further refined into Features. * editorial: depending on the screen resolution and font size of who is browsing the wiki page, ids of features/epics may be displayed in the same line or in subsequent lines. The convention I would suggest to follow: * if you don't mind whether the features/epics become displayed one per line or several in the same line, then I would separate their ids with commas * if you prefer that each feature/epic appears in a single line, then I would suggest that you add '
' after the wiki link, for example: * [[FIWARE.Feature.IoT.Backend.ThingsManagement.Registration.simpleGeoScopes]]
* editorial: it was suggested that the name of each FI-WARE GE (listed in columns of each table and bullet lists in textual description) map to wiki links that points to the corresponding section in the "Materializing the FI-WARE vision" part of the public wiki. Check the contents of the Apps Chapter already available on the public wiki for reference. Once you have performed this final checks and editing tasks, please upload the contents into the publick wiki, replacing the current version of the Technical Roadmap at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Internet_of_Things_(IoT)_Services with the new one, then update the contents of the private wiki page informing that you have actually uploaded the contents. You can take as a reference the contents currently at the placeholder of the Cloud Hosting chapter in the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Cloud_(Resubmission) Last but not least, please drop Miguel and myself and email informing you are done. Thanks again for your great work in such a short timeframe. Best regards, -- Juanjo On 16/08/12 16:54, Tobias Jacobs wrote: Dear all, I made a revision according to Juanjo's suggestions below. - Moved everything about the Backend Device Manager to the 2nd major release - Added ALL epics of ALL GEs to a new column in the tables of the 2nd major release. @all: If you have time, please check if you are ok with it. In addition: - Removed (i.e. commented out) the high-level description of the Gateway Things Management GE. I do not think there will be one, will there? Best regards Tobias From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Donnerstag, 16. August 2012 12:01 To: Tobias Jacobs Cc: t.elsaleh at surrey.ac.uk; fiware-iot at lists.fi-ware.eu; jhierro >> "Juan J. Hierro" Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi, Let's extend the deadline until today EOB. Then I review and make the final editings so that we can officially deliver tomorrow. A couple of questions, that came to my mind while reviewing what was there: * My understanding is that we have to change everything related the Backend Device Management GE given the fact that NSN has dropped out and there will no implementation delivered. My guess would be to change every related feature to the 2nd Release ... * The table proposed in the template for the 2nd Release was slightly different. It deliberately included a column for Epics, so please use that one and place the Epics in the corresponding column * I don't see any feature related to the Backend nor Gateway Security GEs in any Release ... Then I would go for dropping its rows. If there are Epics identified for this GE, then I would go for having it in the second release since that table would include a column for Epics ... so therefore I would add the Epics there. Similar rule applies to any other GE Please try to fix the above points and collect any other additional input that may help to complete the roadmap description. 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 16/08/12 08:48, Tobias Jacobs wrote: Hi all, Thank for all contributions we received so far! As for the missing ones, I guess we now have to live with my guessings. I had a look into the tracker, and there most features were either assigned to release 1.3 or earlier or did not have an assigned release number at all. Juanjo, do you still want to edit something? (it looks like you did some editings, although your name does not appear in the edit history). Somebody else still wants to do something within the next few hours, let's say until noon? Otherwise I would send Miguel a message that the WP5 contribution is 'ready'. Oh, and sorry for not having reacted yesterday afternoon, for some reasons I did not receive any emails. Best regards Tobias From: JUAN JOSE HIERRO SUREDA [mailto:jhierro at tid.es] Sent: Mittwoch, 15. August 2012 15:36 To: t.elsaleh at surrey.ac.uk Cc: Tobias Jacobs; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap You don't need to duplicate the contents. It's fine if the wiki links just work once we upload the page into the public wiki Enviado desde mi iPhone El 15/08/2012, a las 14:00, "t.elsaleh at surrey.ac.uk" > escribi?: Hello Tobias, >From USurrey point of view, we have edited the Technical Roadmap deliverable wiki page to accommodate USurrey's Epics and Features headers to the table for the Backend Second Release. One question, can we just link these headers to their corresponding original Epic/Features pages, or do we have to duplicate the content as an internal link? Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: 15 August 2012 10:32 To: Juanjo Hierro; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi all, I just created a first version of the Revised Technical Roadmap. It might look nice at first glance, however the assignment of Features to Release number is nearly completely RANDOM, based on my GUESSING. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT_%28Resubmission%29 So please please, we need every partner to revise the page above, and I guess this is by today. It is a task that every GE owner can fulfill within fifteen minutes, so I would say we will not run into editing conflicts. Please send an email to this list when you are done editing, so that we have an overview. As many people are on holiday, the big question is what to do with the GEs owners who cannot do this task in time. Rather remove the features, or rather keep the random assignment to releases? Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 15. August 2012 11:04 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: Instructions for resubmission of FI-WARE Technical Roadmap Hi all, There were clear and precise instructions on how to deal with this deliverable since August 3rd. Please find them enclosed. Despite also an example was provided at that time, you may already check the contributions from the other chapters for reference. It's basically a matter of adding a number of tables, which make reference to the Epics/Features in the FI-WARE Backlog. In the case of the Things Management GEs, they can easily be created, and I could even do it myself, but I have no clear idea about the rest of GEs in the IoT chapter. Since we are in a rush and it will be rather difficult to organize parallel editing of the wiki at this point, I would kindly ask you to provide your input to such tables in some sort of spreadsheet and I can take care of the final editing of the page later tonight. Could NEC provide the template for that spreadsheet and distribute it to the rest of the IoT team so that they can return them filled by EOB today ? Cheers, -- Juanjo -------- Original Message -------- Subject: Instructions for resubmission of FI-WARE Technical Roadmap Date: Fri, 03 Aug 2012 10:02:26 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear colleagues, Please find here the instructions to be followed to generate a new version of the Technical Roadmap deliverable to be published on the public Wiki and be resubmitted to the EC. The instructions are pretty simple and the best way to explain them is by referring to the example I have created on the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Example_(Resubmission)_-_Reference_Example That example is based on the current contents of the Technical Roadmap linked to the Apps Chapter. Based on that, the steps to follow are: * Update the Introduction: * We should make a reference to contents of the FI-WARE Architecture and Open Specifications part of the wiki, rather than the FI-WARE Product Vision (at the time at which the first version of the Technical Roadmap, the Architecture and Open Specifications didn't exist, but this is no longer the case) * You should also refer to the page dealing with Release and Sprint numbering, with reference to calendar dates. * All of this may be done by simple copy&paste from the reference example. * Description of first Major Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that will be supported. The table shall be preceded by the paragraph: * For a more detailed description of features provided, you can refer to the following table which help to identify what Backlog Features will be supported for each FI-WARE GE: * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. Essentially, you just need to include the references to the Backlog Features that have been addressed in the first Release for each FI-WARE GE (note this list should also include Features supported by the baseline assets) * When you distinguished between the delivery by end of July and by end of September, the above three points indeed apply per each (section for the release by end of July and section for the release by end of September) * Description of second Mayor Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that have already been planned or the Epics that will be analyzed and further refine which it is foreseen will lead to specification of Features to be planned as part of the second release. The table shall be preceded by the paragraph: * For a more detailed description of features to be provided, you can refer to the following table which help to identify what Backlog Features have already been specified and planned for the second Major Release of FI-WARE (and indication of the minor release is provided). The table also contain Epics currently under analysis which most probably will lead to the identification of Backlog Features to be planned also in the second Major Release * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. However, since there were no Backlog Features still planned, I have just created some fictitious features to make the reference example complete. If a FI-WARE GE does have Epics, but not Features, then write down "(not yet specified)" in the column about Features. * Regarding links to Features/Epics. They should be wiki references, as they appear in the reference example. No problem if they do not resolve in the FI-WARE Private Wiki, they should work once translated into the public Wiki * Description of Future Releases: * I believe we can keep this part as it is now I have prepared a section with placeholders for your contributions at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4 Please get them ready by Tuesday 12:00pm CET. It shouldn't be that difficult if you made a good exercise updating Epic/Features in the Backlog. During the rest of August, you should update the stakeholder field of each Epic/Feature in the backlog. Please do it with the best of your knowledge. Put "FI-WARE partners" if an Epic/Feature doesn't come from an UC project but was there within our original plans. Add the name of a UC project if you already know they are looking for it (based, for example, on feedback from the educational sessions). We will ask UC projects in parallel to review the Epics/Features on the wiki and add the name of their project in the plan to use the GE and wish to use the functionality linked to that Epic/Feature. 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 ________________________________ 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 ________________________________ 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 Tobias.Jacobs at neclab.eu Wed Aug 29 10:12:58 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Wed, 29 Aug 2012 08:12:58 +0000 Subject: [Fiware-iot] review of I2ND chapter Message-ID: <8755F290097BD941865DC4245B335D2D294CEC45@PALLENE.office.hd> Hi Gianpiero, hi Sabrina, How are you! Long time no see (or even hear)! I am writing you because our IoT Work Package has been asked to do a review of the Architecture Description of the I2ND work package, see the attached E-Mails for details. Due to the holiday season and the absence of a WPA since this month, this review has not been taking place up to now. My feeling is that the I2ND chapter is close enough to your topics within the IoT work package so that you have the necessary expertise, and therefore I like to kindly ask you if TI could do the I2ND architecture review? Timeline would be by say this or the beginning of next week. Best regards Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: Juanjo Hierro Subject: Re: Actions pending on the side of the IoT chapter Date: Tue, 28 Aug 2012 12:48:26 +0000 Size: 18309 URL: -------------- next part -------------- An embedded message was scrubbed... From: Juanjo Hierro Subject: Fwd: Peer review of FI-WARE Open Specifications Date: Tue, 28 Aug 2012 04:49:35 +0000 Size: 11606 URL: -------------- next part -------------- An embedded message was scrubbed... From: Juanjo Hierro Subject: Fwd: Peer review of contents linked to FI-WARE Architecture Description Date: Tue, 28 Aug 2012 04:48:24 +0000 Size: 11435 URL: From sabrina.guerra at telecomitalia.it Wed Aug 29 11:23:56 2012 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Wed, 29 Aug 2012 11:23:56 +0200 Subject: [Fiware-iot] R: review of I2ND chapter In-Reply-To: <8755F290097BD941865DC4245B335D2D294CEC45@PALLENE.office.hd> References: <8755F290097BD941865DC4245B335D2D294CEC45@PALLENE.office.hd> Message-ID: <36A93B31228D3B49B691AD31652BCAE9A5A02E98A5@GRFMBX702BA020.griffon.local> Hi Tobias, yes we could do this review, and you are right that the I2ND chapter is close to our expertise. Maybe we will not be able to complete it by the end of this week (due to the short notice), but we will try to complete it by the beginning of next week. By the way, in order to review the I2ND architecture and open specifications, are these the correct pages to look at? ? https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications the links under the I2ND section, for the open specifications ? https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Interface_to_Networks_and_Devices_%28I2ND%29_Architecture the whole page and sub-links, for the architecture description Another info: do you know how the review should be done? Is it enough an e-mail, or is there any section in the wiki where to post the review? This is a minor point, just to know the form intended for this review. Best regards, Sabrina and Gian Piero Da: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Inviato: mercoled? 29 agosto 2012 10:13 A: Fici Gian Piero; Guerra Sabrina Cc: Juanjo Hierro; thierry.nagellen at orange.com; CARLOS RALLI UCENDO (ralli at tid.es); fiware-iot at lists.fi-ware.eu Oggetto: review of I2ND chapter Hi Gianpiero, hi Sabrina, How are you! Long time no see (or even hear)! I am writing you because our IoT Work Package has been asked to do a review of the Architecture Description of the I2ND work package, see the attached E-Mails for details. Due to the holiday season and the absence of a WPA since this month, this review has not been taking place up to now. My feeling is that the I2ND chapter is close enough to your topics within the IoT work package so that you have the necessary expertise, and therefore I like to kindly ask you if TI could do the I2ND architecture review? Timeline would be by say this or the beginning of next week. Best regards Tobias 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 Tobias.Jacobs at neclab.eu Wed Aug 29 12:26:51 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Wed, 29 Aug 2012 10:26:51 +0000 Subject: [Fiware-iot] review of I2ND chapter In-Reply-To: <36A93B31228D3B49B691AD31652BCAE9A5A02E98A5@GRFMBX702BA020.griffon.local> References: <8755F290097BD941865DC4245B335D2D294CEC45@PALLENE.office.hd> <36A93B31228D3B49B691AD31652BCAE9A5A02E98A5@GRFMBX702BA020.griffon.local> Message-ID: <8755F290097BD941865DC4245B335D2D294CECF6@PALLENE.office.hd> Dear Sabrina, Great, thank you so much for agreeing to do the review. About your questions: - I think there is no specific format for the comments, so sending an email should be perfectly fine - Yes, the two links you sent seem to me to be the correct ones to look at. (@anyone in cc: please correct me if I am wrong) Thanks again and best regards Tobias From: Guerra Sabrina [mailto:sabrina.guerra at telecomitalia.it] Sent: Mittwoch, 29. August 2012 11:24 To: Tobias Jacobs Cc: Juanjo Hierro; thierry.nagellen at orange.com; CARLOS RALLI UCENDO (ralli at tid.es); fiware-iot at lists.fi-ware.eu Subject: R: review of I2ND chapter Hi Tobias, yes we could do this review, and you are right that the I2ND chapter is close to our expertise. Maybe we will not be able to complete it by the end of this week (due to the short notice), but we will try to complete it by the beginning of next week. By the way, in order to review the I2ND architecture and open specifications, are these the correct pages to look at? ? https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications the links under the I2ND section, for the open specifications ? https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Interface_to_Networks_and_Devices_%28I2ND%29_Architecture the whole page and sub-links, for the architecture description Another info: do you know how the review should be done? Is it enough an e-mail, or is there any section in the wiki where to post the review? This is a minor point, just to know the form intended for this review. Best regards, Sabrina and Gian Piero Da: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Inviato: mercoled? 29 agosto 2012 10:13 A: Fici Gian Piero; Guerra Sabrina Cc: Juanjo Hierro; thierry.nagellen at orange.com; CARLOS RALLI UCENDO (ralli at tid.es); fiware-iot at lists.fi-ware.eu Oggetto: review of I2ND chapter Hi Gianpiero, hi Sabrina, How are you! Long time no see (or even hear)! I am writing you because our IoT Work Package has been asked to do a review of the Architecture Description of the I2ND work package, see the attached E-Mails for details. Due to the holiday season and the absence of a WPA since this month, this review has not been taking place up to now. My feeling is that the I2ND chapter is close enough to your topics within the IoT work package so that you have the necessary expertise, and therefore I like to kindly ask you if TI could do the I2ND architecture review? Timeline would be by say this or the beginning of next week. Best regards Tobias 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. [rispetta l'ambiente]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: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: