From jhierro at tid.es Sat Oct 1 11:43:14 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Sat, 01 Oct 2011 11:43:14 +0200 Subject: [Fiware-wpa] Fwd: Re: Update on status of FI-WARE Wiki/Tracker tools in FI-WARE In-Reply-To: <4E86E0A0.4050509@tid.es> References: <4E86E0A0.4050509@tid.es> Message-ID: <4E86E0B2.7040802@tid.es> Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain -------- Original Message -------- Subject: Re: Update on status of FI-WARE Wiki/Tracker tools in FI-WARE Date: Sat, 01 Oct 2011 11:42:56 +0200 From: Juanjo Hierro To: ab at fi-ppp.eu Hi all, We have realized that several members of UC projects are requested to join the different projects at FusionForge that are linked to FI-WARE chapters. They are the projects named as "FI-WARE ". Please inform to your teams that THIS IS NOT WHAT THEY SHOULD DO to submit tickets asking for incorporation of any Theme/Epic/Feature/User-Story in the FI-WARE Backlog. They should request to join just the "FI-WARE" project in FusionForge where they should find everything that they need: * A tracker for asking questions/doubts or issue any sort request for help: "FI-WARE General Support" tracker * A tracker for submitting your request to add Themes/Epics/Features in the FI-WARE Backlog: "FI-WARE Theme/Epic/Feature Requests" tracker * A space in the public Wiki where you should place the full description of the Themes/Epics/Features you wish to incorporate to the FI-WARE Backlog: * http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Unclassified_Enablers Note that we have changed the name of the tracker for submitting request for addition of entries in the FI-WARE Backlog. Previously it was named as "FI-WARE Feature Requests" but this introduced some missunderstanding because of the collision with the term "Feature" used in Agile. We have decided to name it now as "FI-WARE Theme/Epic/Feature Requests" Note that you will also be able to see the full description of ALL entries in the FI-WARE backlog being introduced from the FI-WARE chapters in the Wiki. Therefore, you will have full visibility of what is the work being tackled by the FI-WARE project. That's why you don't need to gain further access to the "FI-WARE " projects. Full description of entries in the FI-WARE backlog can be found the Wiki of the FI-WARE project, currently in: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Unclassified_Enablers We will review all requests to join the "FI-WARE " and reject those request to join that were wrongly submitted. Best regards, Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain On 29/09/11 10:19, Juanjo Hierro wrote: Hi all, Right know, you should have access to comprehensive tutorials explaining you how to: * Creating a FusionForge account * Joining a FI-WARE project in FusionForge * Asking questions or providing feedback to the FI-WARE team * Adding the full description of backlog entries to the Wiki * Creating requests for FI-WARE features So you should have everything you need to start interacting with FI-WARE As per the translation of the FI-WARE Product Vision document into the Wiki, we are still working on it (translation of figures is getting a bit painful and we also have to pretty-print some contents manually). I hope it will be ready tomorrow early in the morning. However, this shouldn't block you because you may still refer to sections of the document by title in any ticket you submit. Any feedback is, of course, welcome (maybe worth providing it through the tracker ;-) But, anyways, we can use this list for the very early doubts/questions/comments you may have. Best regards, ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Oct 3 02:27:37 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 03 Oct 2011 02:27:37 +0200 Subject: [Fiware-wpa] Creation of Backlog Management Trackers in FusionForge Message-ID: <4E890179.1000108@tid.es> Hi all, Now, everything is ready for setting up the trackers for your Chapter projects in FusionForge. I have created a comprehensive and exhaustive tutorial on how to create and configure trackers that is now part of the Project Handbook available on the Wiki: https://wiki.fi-ware.eu I have also updated the name of Roles in all chapter projects so that: * previous "Admin" role remains the same * previous "Senior Developer" Role becomes "FI-WARE Chapter Project Member" * previous "Junior Developer" Role becomes "FI-WARE Project Member" * previous "Doc Writer" Role becomes "FI-WARE Reviewer" (this is a placehoder for allowing reviewers to the project to get access to different spaces in FusionForge) * previous "Tech Support" Role becomes "FI-WARE Tester" (may be helpful once we setup the FI-WARE Testbed) As per now, most of the chapters only have users that are either "Admin" or "FI-WARE Chapter Project Member". I would suggest that you assign the "FI-WARE Chapter Project Member" just to people from partners that have resources in your Chapter, assigning the rest of them a "FI-WARE Project Member" Role. Pascal: I have found that you have created an "Observer" Role in your chapter that you seem to have assigned to other FI-WARE project members. For consistency reasons, I would suggest you use the new "FI-WARE Project Member" Role for this users (but check that the privileges are assigned as you wish) As a reminder of the "very next steps" we were carrying out regarding the FI-WARE Backlogs: * You should have uploaded to the Wiki the full description of Themes/Epics/Features/User-Stories of your Backlog (everything was set and ready since Thursday) * You should now configure your "Backlog Management" trackers. There may exist some trackers already in your Chapter project in FusionForge. I recommend to delete them all (I would also delete the forums if you are not using them) * Once the "Backlog Management" tracker is created and properly configured for your chapter (see tutorial on how to) you should start creating the tickets for each and every Theme/Epic/Feature/User-Story you uploaded to the Wiki * Once we upload the "Product Vision" on the Wiki, you should upload information about the Assets selected as baseline for the implementation of FI-WARE GEs. We will provide a template for this. If you have any doubt, please ask. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Oct 3 09:57:56 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 03 Oct 2011 09:57:56 +0200 Subject: [Fiware-wpa] IMPORTANT: Alignment on trackers for Backlog Management in the different FI-WARE Chapter projects Message-ID: <4E896B04.2080602@tid.es> Hi all, ALL Projects in FusionForge were created with several trackers by default. I believe they were one for Support, one for "Feature Requests" and another one maybe for Bugs. PLEASE note that the "Feature Requests" IS NOT the tracker you should use for Backlog Management. Probably it was our fault not to delete all default trackers but it is also true that we mentioned that we would give detailed instructions on how to configure trackers for the backlog management and that you shouldn't do anything prior to that. PLEASE stick to the tutorials defined in the FI-WARE wiki regarding creation of the Backlog Management tracker, etc. Same for uploading the full description of entries in the FI-WARE Chapter Backlogs on the Wiki. Please stick to what is described in the tutorials. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From GLIKSON at il.ibm.com Mon Oct 3 10:19:47 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Mon, 3 Oct 2011 10:19:47 +0200 Subject: [Fiware-wpa] Creation of Backlog Management Trackers in FusionForge In-Reply-To: <4E890179.1000108@tid.es> References: <4E890179.1000108@tid.es> Message-ID: Well done! Few comments regarding custom fields in Backlog tracker: 1) I would recommend defining the Releases and Sprints as Multi-Select box rather than text area -- it is important to make sure that the project schedule is aligned across WPs. For example, the releases could be coded as follows: "R0.1 M9 - Jan12", "R1.0 M12 - Apr12", "R1.1 M15 - Jul12", "R1.2 M18 - Oct12", "R1.3 M21 - Jan13", "R2.0 M24 - Apr13", and sprints: "M07 - Nov11", "M08 - Dec11", etc 2) I would suggest the following set of Status choices: New, Scheduled, In Progress, Ready/Pending, Done. This could make the tracking & reporting a bit easier. 3) I am still struggling to figure out how to easily track the hierarchy of GEs --> Themes --> Epics --> Features. We can define queries to see work items of a specific GE, but this would potentially show tens if not hundreds of items (for larger GEs), combining themes, epics and features.. One possible way to handle this is to define an additional custom field, "Parent", of type "Relation" -- which would allow specifying the ID of the parent item and using it in queries. Thoughts? Also, regarding the Backlog Wiki -- having the list of ALL the work items on a single Wiki page could be an issue, especially when there are many editors who might potentially make their changes in parallel. Wiki is typically not designed to handle concurrent changes, and does not have any locking or merging capabilities. Perhaps, it could make sense to have a separate page per Chapter. Regards, Alex From: Juanjo Hierro To: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Date: 03/10/2011 02:27 AM Subject: [Fiware-wpa] Creation of Backlog Management Trackers in FusionForge Sent by: fiware-wpa-bounces at lists.fi-ware.eu Hi all, Now, everything is ready for setting up the trackers for your Chapter projects in FusionForge. I have created a comprehensive and exhaustive tutorial on how to create and configure trackers that is now part of the Project Handbook available on the Wiki: https://wiki.fi-ware.eu I have also updated the name of Roles in all chapter projects so that: previous "Admin" role remains the same previous "Senior Developer" Role becomes "FI-WARE Chapter Project Member" previous "Junior Developer" Role becomes "FI-WARE Project Member" previous "Doc Writer" Role becomes "FI-WARE Reviewer" (this is a placehoder for allowing reviewers to the project to get access to different spaces in FusionForge) previous "Tech Support" Role becomes "FI-WARE Tester" (may be helpful once we setup the FI-WARE Testbed) As per now, most of the chapters only have users that are either "Admin" or "FI-WARE Chapter Project Member". I would suggest that you assign the "FI-WARE Chapter Project Member" just to people from partners that have resources in your Chapter, assigning the rest of them a "FI-WARE Project Member" Role. Pascal: I have found that you have created an "Observer" Role in your chapter that you seem to have assigned to other FI-WARE project members. For consistency reasons, I would suggest you use the new "FI-WARE Project Member" Role for this users (but check that the privileges are assigned as you wish) As a reminder of the "very next steps" we were carrying out regarding the FI-WARE Backlogs: You should have uploaded to the Wiki the full description of Themes/Epics/Features/User-Stories of your Backlog (everything was set and ready since Thursday) You should now configure your "Backlog Management" trackers. There may exist some trackers already in your Chapter project in FusionForge. I recommend to delete them all (I would also delete the forums if you are not using them) Once the "Backlog Management" tracker is created and properly configured for your chapter (see tutorial on how to) you should start creating the tickets for each and every Theme/Epic/Feature/User-Story you uploaded to the Wiki Once we upload the "Product Vision" on the Wiki, you should upload information about the Assets selected as baseline for the implementation of FI-WARE GEs. We will provide a template for this. If you have any doubt, please ask. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Oct 3 12:59:58 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 03 Oct 2011 12:59:58 +0200 Subject: [Fiware-wpa] Creation of Backlog Management Trackers in FusionForge In-Reply-To: References: <4E890179.1000108@tid.es> Message-ID: <4E8995AE.6070403@tid.es> Hi Alex, Thanks for your constructive comments ! See mine between lines ... On 03/10/11 10:19, Alex Glikson wrote: Well done! Few comments regarding custom fields in Backlog tracker: 1) I would recommend defining the Releases and Sprints as Multi-Select box rather than text area -- it is important to make sure that the project schedule is aligned across WPs. For example, the releases could be coded as follows: "R0.1 M9 - Jan12", "R1.0 M12 - Apr12", "R1.1 M15 - Jul12", "R1.2 M18 - Oct12", "R1.3 M21 - Jan13", "R2.0 M24 - Apr13", and sprints: "M07 - Nov11", "M08 - Dec11", etc Sure. Since we are still not close to the time at which we should plan what goes to the first Release and Sprint, I suggest that we cover this and agree on a formula during our next joint follow-up confcall. 2) I would suggest the following set of Status choices: New, Scheduled, In Progress, Ready/Pending, Done. This could make the tracking & reporting a bit easier. As per today: Open = New Close = Done May you elaborate why you need to distinguish between Scheduled, In Progress and Ready/Pending ? I didn't want to define a very much complex workflow ... 3) I am still struggling to figure out how to easily track the hierarchy of GEs --> Themes --> Epics --> Features. We can define queries to see work items of a specific GE, but this would potentially show tens if not hundreds of items (for larger GEs), combining themes, epics and features.. One possible way to handle this is to define an additional custom field, "Parent", of type "Relation" -- which would allow specifying the ID of the parent item and using it in queries. Thoughts? As mentioned in one of my previous emails, I would go for devoting a single "Backlog Management" for Themes/Epics/Features (this would be the initial tracker we are now setting up for each chapter). But let's try to keep everything, including User-Stories, in that same tracker and then see how it goes ... If we find out that it cannot be handle because of scale, then we should agree on how to agree but probably a nice approach would be that of creating dedicated trackers for GEs holding User-Stories (the nice part of such approach is that we may then go to reviewers and UC projects as to tell them: "you just need to take a look at the 'Backlog Management' tracker" and we may even keep the GE trackers holding User-Stories as privates). Anyways, there is a nice feature supported by FusionForge trackers that we may take advantage of if we find out that we are running out of scale and decide that we need more trackers: you can easily transfer a ticket from one tracker to another tracker within a given project. It's pretty straightforward. Note that you will always need an additional tracker besides trackers for GEs to cope with Epics/Features that are defined over more than one GE. So, definitively, starting with a single "Backlog Management" tracker is the right thing to do at this point. Also, regarding the Backlog Wiki -- having the list of ALL the work items on a single Wiki page could be an issue, especially when there are many editors who might potentially make their changes in parallel. Wiki is typically not designed to handle concurrent changes, and does not have any locking or merging capabilities. Perhaps, it could make sense to have a separate page per Chapter. That's a good point. I will create a separate page per Chapter tonight (to avoid any potential clash you may be doing today) Cheers, -- Juanjo Regards, Alex From: Juanjo Hierro To: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Date: 03/10/2011 02:27 AM Subject: [Fiware-wpa] Creation of Backlog Management Trackers in FusionForge Sent by: fiware-wpa-bounces at lists.fi-ware.eu ________________________________ Hi all, Now, everything is ready for setting up the trackers for your Chapter projects in FusionForge. I have created a comprehensive and exhaustive tutorial on how to create and configure trackers that is now part of the Project Handbook available on the Wiki: https://wiki.fi-ware.eu I have also updated the name of Roles in all chapter projects so that: * previous "Admin" role remains the same * previous "Senior Developer" Role becomes "FI-WARE Chapter Project Member" * previous "Junior Developer" Role becomes "FI-WARE Project Member" * previous "Doc Writer" Role becomes "FI-WARE Reviewer" (this is a placehoder for allowing reviewers to the project to get access to different spaces in FusionForge) * previous "Tech Support" Role becomes "FI-WARE Tester" (may be helpful once we setup the FI-WARE Testbed) As per now, most of the chapters only have users that are either "Admin" or "FI-WARE Chapter Project Member". I would suggest that you assign the "FI-WARE Chapter Project Member" just to people from partners that have resources in your Chapter, assigning the rest of them a "FI-WARE Project Member" Role. Pascal: I have found that you have created an "Observer" Role in your chapter that you seem to have assigned to other FI-WARE project members. For consistency reasons, I would suggest you use the new "FI-WARE Project Member" Role for this users (but check that the privileges are assigned as you wish) As a reminder of the "very next steps" we were carrying out regarding the FI-WARE Backlogs: * You should have uploaded to the Wiki the full description of Themes/Epics/Features/User-Stories of your Backlog (everything was set and ready since Thursday) * You should now configure your "Backlog Management" trackers. There may exist some trackers already in your Chapter project in FusionForge. I recommend to delete them all (I would also delete the forums if you are not using them) * Once the "Backlog Management" tracker is created and properly configured for your chapter (see tutorial on how to) you should start creating the tickets for each and every Theme/Epic/Feature/User-Story you uploaded to the Wiki * Once we upload the "Product Vision" on the Wiki, you should upload information about the Assets selected as baseline for the implementation of FI-WARE GEs. We will provide a template for this. If you have any doubt, please ask. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx_______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Oct 3 13:02:23 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 03 Oct 2011 13:02:23 +0200 Subject: [Fiware-wpa] [Fiware-wpl] IMPORTANT Clarification In-Reply-To: References: <4E831ADB.2070809@tid.es> Message-ID: <4E89963F.7080607@tid.es> Hi, As mentioned in previous emails, yes option 2 would be the way I would go, not only because it would ease to handle the scalability but because would allow to avoid showing the User-Story trackers to reviewers. Nevertheless, let's start with option 1. and go for option 2 if needed. Regards, Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain On 29/09/11 11:41, Alex Glikson wrote: Option 2 sounds reasonable. This way we also don't need to represent individual sprints in that tracker - just releases (minor and major), and mapping of features to releases. Regards, Alex P.S. BTW, do we need to keep the internal management of individual sprints and stories public? From: Juanjo Hierro To: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Date: 28/09/2011 04:03 PM Subject: [Fiware-wpl] IMPORTANT Clarification Sent by: fiware-wpl-bounces at lists.fi-ware.eu ________________________________ Hi, I believe there is a point that we didn't clearly fixed during our meeting in Turin. It is about the relationship between trackers and Backlogs. The notion of Backlog is someway "abstract" from my point of view. A backlog is just a set of related Themes/EPICs/Features/User-Stories. This means that we may well talk about the "Data/Context Management Chapter Backlog" as well as the "Publish/Subscribe Broker GE Backlog", being the second a subset of the first one. However, this doesn't mean that we have to use a separate tracker per each of the GE backlogs. I would like to agree on a common, consistent approach to share across the different chapters. I see several options: 1. Have a single Chapter tracker where keep track of the whole set of Themes/EPICs/Features/User-Stories associated to all GEs in the Chapter. By defining advanced queries on fields related to name of the GE, as well as the kind of entry, users may get different views, depending on their needs. 2. Have a single Chapter tracker where keep track of the whole set of Themes/EPICs/Features associated to all GEs in the Chapter. Then have a tracker per GEs dealing with User Stories for each and every GE in the chapter 3. Have multiple trackers, one per GE in the Chapter, each keeping track of the whole set of Themes/EPICs/Features/User-Stories associated to a given GE In my honest opinion, I would go for option 2. because it would make it easier to keep a reasonable large (but not that big) backlog just for Themes/EPICs/Features while the more fine-grained work is handled separately (given partners responsible of a given GE enough independence in managing the Backlog for the GE they are implementing). It may also make our life easier in front of reviewers and even UC projects who probably may just need to deal with entries at the level of granularity of EPICs/Features ... Any opinion ? If I don't hear about any objection, I would go for option 2 :-) Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx_______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Mon Oct 3 14:14:53 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 3 Oct 2011 14:14:53 +0200 Subject: [Fiware-wpa] R: [Fiware-wpl] IMPORTANT Clarification In-Reply-To: <4E89963F.7080607@tid.es> References: <4E831ADB.2070809@tid.es> <4E89963F.7080607@tid.es> Message-ID: For me it's fine to start using the option 1, then check later whether we should implement option 2 or not. BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: luned? 3 ottobre 2011 13:02 A: Alex Glikson Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: Re: [Fiware-wpl] IMPORTANT Clarification Hi, As mentioned in previous emails, yes option 2 would be the way I would go, not only because it would ease to handle the scalability but because would allow to avoid showing the User-Story trackers to reviewers. Nevertheless, let's start with option 1. and go for option 2 if needed. Regards, Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain On 29/09/11 11:41, Alex Glikson wrote: Option 2 sounds reasonable. This way we also don't need to represent individual sprints in that tracker - just releases (minor and major), and mapping of features to releases. Regards, Alex P.S. BTW, do we need to keep the internal management of individual sprints and stories public? From: Juanjo Hierro To: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Date: 28/09/2011 04:03 PM Subject: [Fiware-wpl] IMPORTANT Clarification Sent by: fiware-wpl-bounces at lists.fi-ware.eu ________________________________ Hi, I believe there is a point that we didn't clearly fixed during our meeting in Turin. It is about the relationship between trackers and Backlogs. The notion of Backlog is someway "abstract" from my point of view. A backlog is just a set of related Themes/EPICs/Features/User-Stories. This means that we may well talk about the "Data/Context Management Chapter Backlog" as well as the "Publish/Subscribe Broker GE Backlog", being the second a subset of the first one. However, this doesn't mean that we have to use a separate tracker per each of the GE backlogs. I would like to agree on a common, consistent approach to share across the different chapters. I see several options: 1. Have a single Chapter tracker where keep track of the whole set of Themes/EPICs/Features/User-Stories associated to all GEs in the Chapter. By defining advanced queries on fields related to name of the GE, as well as the kind of entry, users may get different views, depending on their needs. 2. Have a single Chapter tracker where keep track of the whole set of Themes/EPICs/Features associated to all GEs in the Chapter. Then have a tracker per GEs dealing with User Stories for each and every GE in the chapter 3. Have multiple trackers, one per GE in the Chapter, each keeping track of the whole set of Themes/EPICs/Features/User-Stories associated to a given GE In my honest opinion, I would go for option 2. because it would make it easier to keep a reasonable large (but not that big) backlog just for Themes/EPICs/Features while the more fine-grained work is handled separately (given partners responsible of a given GE enough independence in managing the Backlog for the GE they are implementing). It may also make our life easier in front of reviewers and even UC projects who probably may just need to deal with entries at the level of granularity of EPICs/Features ... Any opinion ? If I don't hear about any objection, I would go for option 2 :-) Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx_______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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:00000000000000000000000000000001 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_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jhierro at tid.es Mon Oct 3 16:43:42 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 03 Oct 2011 16:43:42 +0200 Subject: [Fiware-wpa] [Fiware-wpl] IMPORTANT Clarification In-Reply-To: References: <771C9B001456D64783596DDC3801C6EA281533FE62@DEWDFECCR09.wdf.sap.corp> <771C9B001456D64783596DDC3801C6EA281533FE63@DEWDFECCR09.wdf.sap.corp> Message-ID: <4E89CA1E.80506@tid.es> On 29/09/11 14:16, Alex Glikson wrote: I'm a bit concerned that the fine-grained details of individual stories and tasks might potentially reveal internal details of our background assets -- some of which are not supposed to get exposed to the public. Also, it might be just too many details for anyone outside the development team. So, I think we should look for a reasonable level of details in the public tracker of each Chapter (and the corresponding Wiki space). It seems to me that the level of minor releases (3 months long) and features associated with each of them (as well as the prioritized backlog of unassigned features, grouped by Themes) is just about right granularity. I will respond on this in another mail. Regarding using Forge tasks for management of user stories and sprints -- in addition to the privacy issue above (e.g., we might want to keep them in Forge spaces of individual WPs), I'm not sure it is customizable enough. For example, I haven't found a way to define a custom field that would refer to the Sprint (using start/end dates is not very convenient). Also, I haven't found a way to filter tasks by Epic/Theme, which might be convenient. And there are few other limitations. This is a comment I do not understand very well. You should still work with the tracker for many of the things that deal with management of user-stories and sprints ... That is, for example, planning a user story for a given sprint. That's indeed the reason why you should assign the Sprint Id of the next sprint to a User-Story when it becomes planned for that sprint ... This should allow you to easy browse/monitor what user-stories are part of the current sprint. Creation of tasks is analogous to creation of tasks in Agile. And the Task Manager is just a useful tool that is at your service for handling tasks you would typically carry out in the context of a sprint following Agile. As simple as that. Therefore, I wouldn't rely on the Task Manager to search for the User-Stories that are being tackled in the current Sprint. I would browse/query the tracker for that purpose. Last but not least, I would consider usage of the Task Manager even something not strictly mandatory to GE development teams. It's up to you to decide whether to use it or not. Furthermore, you should use it if you really find it helpful. We have to be pragmatic and realize that we are bringing on the table a set of assets, each of which is being developed in the lab of some partner and not necessarily just for FI-WARE. I would even say that if it were only for FI-WARE I would be a bit worried :-) because it is supposed that they are asset considered strategic in their respective companies, therefore having other "customers". It will be "naive" to think that the development teams behind those assets are going to adapt the way the work to FI-WARE methodologies and tools. They may be using JIRA (for example) and therefore may be managing the tasks dealing with implementation of a user-story in a given sprint using the tools for task management that JIRA provides. Does it make sense that they throw it away their tools and start using the FusionForge Task Management instead ? Probably not. Therefore, the FusionForge Task Manager tool is there to help but not to create additional burden. Of course, what WP Leaders have to do is to negotiate with development teams behind each and every GE how they can follow-up progress of the development teams during the current sprint. Again there, is where usage of the FusionForge Task Manager tool can be evaluated to find out whether it would be helpful or not. Hope this answer helps. Best regards, -- Juanjo Regards, Alex From: "Bohnert, Thomas Michael" To: Alex Glikson/Haifa/IBM at IBMIL, "'jhierro at tid.es'" Cc: "'fiware-wpl at lists.fi-ware.eu'" , "'fiware-wpa at lists.fi-ware.eu'" Date: 29/09/2011 01:02 PM Subject: Re: [Fiware-wpl] IMPORTANT Clarification ________________________________ About maintaining sprints. Recall that the reason for this solution was exactly the possibility to maintain sprints associated via associating tasks (per sprint/user story) with a tracker (generic enabler/epic/feature/release) Best, Thomas -- Please excuse smartphone brevity From: Bohnert, Thomas Michael Sent: Thursday, September 29, 2011 11:57 AM To: 'GLIKSON at il.ibm.com' ; 'jhierro at tid.es' Cc: 'fiware-wpl at lists.fi-ware.eu' ; 'fiware-wpa at lists.fi-ware.eu' Subject: Re: [Fiware-wpl] IMPORTANT Clarification Alex, Yes - we promised to provide 'some level' of transparency in order to apease usage areas a bit at the first place, and secondly to maintain a means to keep the expectations on fi-ware reasonable. One can hardly argue for additional requests if the current workload is close to upper limits. Best, Thomas -- Please excuse smartphone brevity From: Alex Glikson [mailto:GLIKSON at il.ibm.com] Sent: Thursday, September 29, 2011 11:41 AM To: Juanjo Hierro Cc: fiware-wpl at lists.fi-ware.eu ; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpl] IMPORTANT Clarification Option 2 sounds reasonable. This way we also don't need to represent individual sprints in that tracker - just releases (minor and major), and mapping of features to releases. Regards, Alex P.S. BTW, do we need to keep the internal management of individual sprints and stories public? From: Juanjo Hierro To: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Date: 28/09/2011 04:03 PM Subject: [Fiware-wpl] IMPORTANT Clarification Sent by: fiware-wpl-bounces at lists.fi-ware.eu ________________________________ Hi, I believe there is a point that we didn't clearly fixed during our meeting in Turin. It is about the relationship between trackers and Backlogs. The notion of Backlog is someway "abstract" from my point of view. A backlog is just a set of related Themes/EPICs/Features/User-Stories. This means that we may well talk about the "Data/Context Management Chapter Backlog" as well as the "Publish/Subscribe Broker GE Backlog", being the second a subset of the first one. However, this doesn't mean that we have to use a separate tracker per each of the GE backlogs. I would like to agree on a common, consistent approach to share across the different chapters. I see several options: 1. Have a single Chapter tracker where keep track of the whole set of Themes/EPICs/Features/User-Stories associated to all GEs in the Chapter. By defining advanced queries on fields related to name of the GE, as well as the kind of entry, users may get different views, depending on their needs. 2. Have a single Chapter tracker where keep track of the whole set of Themes/EPICs/Features associated to all GEs in the Chapter. Then have a tracker per GEs dealing with User Stories for each and every GE in the chapter 3. Have multiple trackers, one per GE in the Chapter, each keeping track of the whole set of Themes/EPICs/Features/User-Stories associated to a given GE In my honest opinion, I would go for option 2. because it would make it easier to keep a reasonable large (but not that big) backlog just for Themes/EPICs/Features while the more fine-grained work is handled separately (given partners responsible of a given GE enough independence in managing the Backlog for the GE they are implementing). It may also make our life easier in front of reviewers and even UC projects who probably may just need to deal with entries at the level of granularity of EPICs/Features ... Any opinion ? If I don't hear about any objection, I would go for option 2 :-) Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx_______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue Oct 4 08:25:15 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 04 Oct 2011 08:25:15 +0200 Subject: [Fiware-wpa] Product Vison on the Wiki Message-ID: <4E8AA6CB.3070506@tid.es> Hi all, I'm now translating the Product Vision document to the Wiki. Please don't edit it while I'm editing too (I have the impression someone else was editing the document while I was implementing changes) Do not edit it until I tell you can. Thanks, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Wed Oct 5 10:52:12 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 05 Oct 2011 10:52:12 +0200 Subject: [Fiware-wpa] Instructions on how to proceed with assets soon Message-ID: <4E8C1ABC.1020405@tid.es> Hi all, In less than one hour, I will provide detailed instructions on how to incorporate information about the assets and continue with the task regarding recording of entries the FI-WARE Backlogs. It will imply certain re-arrangements on the Wiki, so maybe it's worth that you stop any editing on the Wiki until the detailed instructions come. Apologize for any inconvenience this may cause. Please, be patient. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Wed Oct 5 12:01:31 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 05 Oct 2011 12:01:31 +0200 Subject: [Fiware-wpa] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further Message-ID: <4E8C2AFB.2020302@tid.es> Hi all, After careful consideration, I have came with a way description of assets, the FI-WARE vision and entries of the FI-WARE backlog can be nicely structured on the Wiki and linked together. Assets are clearly linked to FI-WARE Backlog entries, so it clearly makes sense to document them closely together. Notice that many of the already identified Themes/Epics/Features/User-Stories are indeed linked to selected assets. Note that Features/User-Stories should map to assets because they correspond to concrete software development that has to be carried over assets and will lead to delivery of some new version of the asset in the course of a release or a sprint, respectively. However, while there are Themes/Epics that can be mapped to assets (still high-level to map into actual developments on the asset) others may be general to the chapter, corresponding still to topics under discussion which may potentially affect several assets. They should derive on Themes/Epics/Features/User-Stories on selected assets as a result of the discussion. We should take this into account when structuring the Wiki. Based on the above, the structure we will adopt is described as follows: * A chapter titled "Materializing the FI-WARE Vision", linked to a Wiki page, has been added to the FI-WARE Wiki, following right after the "FI-WARE Product Vision". * The Wiki page for this new chapter has been created and, for the time being, is structured as a list of subchapters, one per chapter of FI-WARE, each subchapter having its own Wiki page. * We have created each of the "Materializing the in FI-WARE" Wiki pages. They contain: * An introduction section you don't need to edit. You will see it establish a link to the corresponding chapter in the FI-WARE Product Vision * A section per GE in the chapter. A template is provided for this sections that you should replicate for each GE in your chapter (at least for those for which backlog entries have been identified). The section is structured as follows: * Baseline assets: Here you should enumerate the assets that will be considered for implementing the GE. If not yet decided, please explain. For each asset, a link to a dedicated Wiki page should be created, describing the asset. * Check the general structure for this section looking at the example for the "BigData Analysis" GE in the Data/Context Management Chapter (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#Baseline_Assets_3) * In order to build the Wiki page associated to an asset, you should replicate the structure for the Wiki page linked to the SAMSON asset in the "BigData Analysis GE" (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/SAMSON_Platform) * Themes: You should add here the link to the proper Themes you had previously listed in the FI-WARE Backlog chapter * Epics: You should add here the link to the proper Epics you had previously listed in the FI-WARE Backlog chapter * Features: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter * User-Stories: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter * A section titled "Topics still being addressed at high-level": Here, you should add the Themes and Epics you should have produced as a result of mapping any of the following: * issues identified in the Question Mark section of the FI-WARE Product Vision. * sketched solution for integration of some assets, as a result of discussions taking place in Turin The "FI-WARE Backlog" chapter you currently find in the FI-WARE wiki home page will be deprecated and finally dropped in a matter of days. I hope that the instructions are clear. It shouldn't change much of what you had done. Of course, the wiki pages you created for the full description of backlog entries will still be valid in the new structure. And the URL links to them will still be valid so any tickets you may have created on the trackers should still work. You can take a look at how the info has been structured for the Data/Context Management chapter for reference. Don't hesitate to ask if you have any doubt. Apologizes for the delay in communicating this but I gave it a careful thought and only after some time considering different possibilities, I came with the final proposal. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ 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 Oct 5 18:40:31 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 05 Oct 2011 18:40:31 +0200 Subject: [Fiware-wpa] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further In-Reply-To: <4E8C2AFB.2020302@tid.es> References: <4E8C2AFB.2020302@tid.es> Message-ID: <4E8C887F.5040300@tid.es> Hi, I would like that each and every WPL send me an email confirm that he has received and processed the email I sent this morning and has planned the corresponding actions. So far, I haven't seen any change on the Wiki and I still see people working in the old (to be deprecated) "FI-WARE Backlog" chapter. Looking forward your responses, Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain On 05/10/11 12:01, Juanjo Hierro wrote: Hi all, After careful consideration, I have came with a way description of assets, the FI-WARE vision and entries of the FI-WARE backlog can be nicely structured on the Wiki and linked together. Assets are clearly linked to FI-WARE Backlog entries, so it clearly makes sense to document them closely together. Notice that many of the already identified Themes/Epics/Features/User-Stories are indeed linked to selected assets. Note that Features/User-Stories should map to assets because they correspond to concrete software development that has to be carried over assets and will lead to delivery of some new version of the asset in the course of a release or a sprint, respectively. However, while there are Themes/Epics that can be mapped to assets (still high-level to map into actual developments on the asset) others may be general to the chapter, corresponding still to topics under discussion which may potentially affect several assets. They should derive on Themes/Epics/Features/User-Stories on selected assets as a result of the discussion. We should take this into account when structuring the Wiki. Based on the above, the structure we will adopt is described as follows: * A chapter titled "Materializing the FI-WARE Vision", linked to a Wiki page, has been added to the FI-WARE Wiki, following right after the "FI-WARE Product Vision". * The Wiki page for this new chapter has been created and, for the time being, is structured as a list of subchapters, one per chapter of FI-WARE, each subchapter having its own Wiki page. * We have created each of the "Materializing the in FI-WARE" Wiki pages. They contain: * An introduction section you don't need to edit. You will see it establish a link to the corresponding chapter in the FI-WARE Product Vision * A section per GE in the chapter. A template is provided for this sections that you should replicate for each GE in your chapter (at least for those for which backlog entries have been identified). The section is structured as follows: * Baseline assets: Here you should enumerate the assets that will be considered for implementing the GE. If not yet decided, please explain. For each asset, a link to a dedicated Wiki page should be created, describing the asset. * Check the general structure for this section looking at the example for the "BigData Analysis" GE in the Data/Context Management Chapter (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#Baseline_Assets_3) * In order to build the Wiki page associated to an asset, you should replicate the structure for the Wiki page linked to the SAMSON asset in the "BigData Analysis GE" (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/SAMSON_Platform) * Themes: You should add here the link to the proper Themes you had previously listed in the FI-WARE Backlog chapter * Epics: You should add here the link to the proper Epics you had previously listed in the FI-WARE Backlog chapter * Features: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter * User-Stories: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter * A section titled "Topics still being addressed at high-level": Here, you should add the Themes and Epics you should have produced as a result of mapping any of the following: * issues identified in the Question Mark section of the FI-WARE Product Vision. * sketched solution for integration of some assets, as a result of discussions taking place in Turin The "FI-WARE Backlog" chapter you currently find in the FI-WARE wiki home page will be deprecated and finally dropped in a matter of days. I hope that the instructions are clear. It shouldn't change much of what you had done. Of course, the wiki pages you created for the full description of backlog entries will still be valid in the new structure. And the URL links to them will still be valid so any tickets you may have created on the trackers should still work. You can take a look at how the info has been structured for the Data/Context Management chapter for reference. Don't hesitate to ask if you have any doubt. Apologizes for the delay in communicating this but I gave it a careful thought and only after some time considering different possibilities, I came with the final proposal. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Thu Oct 6 09:58:49 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 6 Oct 2011 09:58:49 +0200 Subject: [Fiware-wpa] [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further In-Reply-To: <4E8C887F.5040300@tid.es> References: <4E8C2AFB.2020302@tid.es> <4E8C887F.5040300@tid.es> Message-ID: <25065_1317887930_4E8D5FBA_25065_8613_1_CBBCD6C304123F4AB23FAAE3055C8C0E02063AB37AC7@THSONEA01CMS04P.one.grp> Dear Juanjo, This just to confirm that I have received your email and instructed the Security team accordingly. At tomorrow's WP8 follow-up audio conf I will assess progress achieved by the Security Team according to new instructions given. Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mercredi 5 octobre 2011 18:41 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : Re: [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further Hi, I would like that each and every WPL send me an email confirm that he has received and processed the email I sent this morning and has planned the corresponding actions. So far, I haven't seen any change on the Wiki and I still see people working in the old (to be deprecated) "FI-WARE Backlog" chapter. Looking forward your responses, Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain On 05/10/11 12:01, Juanjo Hierro wrote: Hi all, After careful consideration, I have came with a way description of assets, the FI-WARE vision and entries of the FI-WARE backlog can be nicely structured on the Wiki and linked together. Assets are clearly linked to FI-WARE Backlog entries, so it clearly makes sense to document them closely together. Notice that many of the already identified Themes/Epics/Features/User-Stories are indeed linked to selected assets. Note that Features/User-Stories should map to assets because they correspond to concrete software development that has to be carried over assets and will lead to delivery of some new version of the asset in the course of a release or a sprint, respectively. However, while there are Themes/Epics that can be mapped to assets (still high-level to map into actual developments on the asset) others may be general to the chapter, corresponding still to topics under discussion which may potentially affect several assets. They should derive on Themes/Epics/Features/User-Stories on selected assets as a result of the discussion. We should take this into account when structuring the Wiki. Based on the above, the structure we will adopt is described as follows: * A chapter titled "Materializing the FI-WARE Vision", linked to a Wiki page, has been added to the FI-WARE Wiki, following right after the "FI-WARE Product Vision". * The Wiki page for this new chapter has been created and, for the time being, is structured as a list of subchapters, one per chapter of FI-WARE, each subchapter having its own Wiki page. * We have created each of the "Materializing the in FI-WARE" Wiki pages. They contain: * An introduction section you don't need to edit. You will see it establish a link to the corresponding chapter in the FI-WARE Product Vision * A section per GE in the chapter. A template is provided for this sections that you should replicate for each GE in your chapter (at least for those for which backlog entries have been identified). The section is structured as follows: * Baseline assets: Here you should enumerate the assets that will be considered for implementing the GE. If not yet decided, please explain. For each asset, a link to a dedicated Wiki page should be created, describing the asset. * Check the general structure for this section looking at the example for the "BigData Analysis" GE in the Data/Context Management Chapter (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#Baseline_Assets_3) * In order to build the Wiki page associated to an asset, you should replicate the structure for the Wiki page linked to the SAMSON asset in the "BigData Analysis GE" (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/SAMSON_Platform) * Themes: You should add here the link to the proper Themes you had previously listed in the FI-WARE Backlog chapter * Epics: You should add here the link to the proper Epics you had previously listed in the FI-WARE Backlog chapter * Features: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter * User-Stories: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter * A section titled "Topics still being addressed at high-level": Here, you should add the Themes and Epics you should have produced as a result of mapping any of the following: * issues identified in the Question Mark section of the FI-WARE Product Vision. * sketched solution for integration of some assets, as a result of discussions taking place in Turin The "FI-WARE Backlog" chapter you currently find in the FI-WARE wiki home page will be deprecated and finally dropped in a matter of days. I hope that the instructions are clear. It shouldn't change much of what you had done. Of course, the wiki pages you created for the full description of backlog entries will still be valid in the new structure. And the URL links to them will still be valid so any tickets you may have created on the trackers should still work. You can take a look at how the info has been structured for the Data/Context Management chapter for reference. Don't hesitate to ask if you have any doubt. Apologizes for the delay in communicating this but I gave it a careful thought and only after some time considering different possibilities, I came with the final proposal. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Thu Oct 6 11:34:47 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 6 Oct 2011 11:34:47 +0200 Subject: [Fiware-wpa] R: [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further In-Reply-To: <4E8C887F.5040300@tid.es> References: <4E8C2AFB.2020302@tid.es> <4E8C887F.5040300@tid.es> Message-ID: Hi Juanjo, I confirm that I have informed the I2ND team about the new 'rules' below, and we're going to act according to your instructions. BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: mercoled? 5 ottobre 2011 18:41 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: Re: [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further Hi, I would like that each and every WPL send me an email confirm that he has received and processed the email I sent this morning and has planned the corresponding actions. So far, I haven't seen any change on the Wiki and I still see people working in the old (to be deprecated) "FI-WARE Backlog" chapter. Looking forward your responses, Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain On 05/10/11 12:01, Juanjo Hierro wrote: Hi all, After careful consideration, I have came with a way description of assets, the FI-WARE vision and entries of the FI-WARE backlog can be nicely structured on the Wiki and linked together. Assets are clearly linked to FI-WARE Backlog entries, so it clearly makes sense to document them closely together. Notice that many of the already identified Themes/Epics/Features/User-Stories are indeed linked to selected assets. Note that Features/User-Stories should map to assets because they correspond to concrete software development that has to be carried over assets and will lead to delivery of some new version of the asset in the course of a release or a sprint, respectively. However, while there are Themes/Epics that can be mapped to assets (still high-level to map into actual developments on the asset) others may be general to the chapter, corresponding still to topics under discussion which may potentially affect several assets. They should derive on Themes/Epics/Features/User-Stories on selected assets as a result of the discussion. We should take this into account when structuring the Wiki. Based on the above, the structure we will adopt is described as follows: * A chapter titled "Materializing the FI-WARE Vision", linked to a Wiki page, has been added to the FI-WARE Wiki, following right after the "FI-WARE Product Vision". * The Wiki page for this new chapter has been created and, for the time being, is structured as a list of subchapters, one per chapter of FI-WARE, each subchapter having its own Wiki page. * We have created each of the "Materializing the in FI-WARE" Wiki pages. They contain: * An introduction section you don't need to edit. You will see it establish a link to the corresponding chapter in the FI-WARE Product Vision * A section per GE in the chapter. A template is provided for this sections that you should replicate for each GE in your chapter (at least for those for which backlog entries have been identified). The section is structured as follows: * Baseline assets: Here you should enumerate the assets that will be considered for implementing the GE. If not yet decided, please explain. For each asset, a link to a dedicated Wiki page should be created, describing the asset. * Check the general structure for this section looking at the example for the "BigData Analysis" GE in the Data/Context Management Chapter (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#Baseline_Assets_3) * In order to build the Wiki page associated to an asset, you should replicate the structure for the Wiki page linked to the SAMSON asset in the "BigData Analysis GE" (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/SAMSON_Platform) * Themes: You should add here the link to the proper Themes you had previously listed in the FI-WARE Backlog chapter * Epics: You should add here the link to the proper Epics you had previously listed in the FI-WARE Backlog chapter * Features: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter * User-Stories: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter * A section titled "Topics still being addressed at high-level": Here, you should add the Themes and Epics you should have produced as a result of mapping any of the following: * issues identified in the Question Mark section of the FI-WARE Product Vision. * sketched solution for integration of some assets, as a result of discussions taking place in Turin The "FI-WARE Backlog" chapter you currently find in the FI-WARE wiki home page will be deprecated and finally dropped in a matter of days. I hope that the instructions are clear. It shouldn't change much of what you had done. Of course, the wiki pages you created for the full description of backlog entries will still be valid in the new structure. And the URL links to them will still be valid so any tickets you may have created on the trackers should still work. You can take a look at how the info has been structured for the Data/Context Management chapter for reference. Don't hesitate to ask if you have any doubt. Apologizes for the delay in communicating this but I gave it a careful thought and only after some time considering different possibilities, I came with the final proposal. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 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_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jhierro at tid.es Thu Oct 6 19:01:15 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 06 Oct 2011 19:01:15 +0200 Subject: [Fiware-wpa] Confirm whether the following people are members of FI-WARE Message-ID: <4E8DDEDB.6070903@tid.es> Hi all, Could you tell me who in the following list is working in any of your WPs ? I'm not sure whether they are working in FI-WARE or in a UC project. In the second case, I would reject their request to join the FI-WARE project because they haven't followed the convention proposed for user accounts related to UC projects: define a login name which takes the form: _ Thanks, [cid:part1.06000706.02050202 at tid.es] -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ 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: afifbfeh.png Type: image/png Size: 22196 bytes Desc: not available URL: From pascal.bisson at thalesgroup.com Thu Oct 6 19:06:27 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 6 Oct 2011 19:06:27 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Confirm whether the following people are members of FI-WARE In-Reply-To: <4E8DDEDB.6070903@tid.es> References: <4E8DDEDB.6070903@tid.es> Message-ID: <8161_1317920789_4E8DE015_8161_9043_1_5d45ae7a-fd0f-4cd3-926a-7483c63f286d@THSONEA01HUB04P.one.grp> Hi Juanjo, This just to let you know that Alexandra (DT) , Francesco (SAP) and Peter Scholta (DT) are Security Chapter Project members. I added them today as per request of SAP and DT representatives to Security WP. As for the others I have no cue ... Hope it helps you. Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : jeudi 6 octobre 2011 19:01 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Confirm whether the following people are members of FI-WARE Hi all, Could you tell me who in the following list is working in any of your WPs ? I'm not sure whether they are working in FI-WARE or in a UC project. In the second case, I would reject their request to join the FI-WARE project because they haven't followed the convention proposed for user accounts related to UC projects: define a login name which takes the form: _ Thanks, [cid:image001.png at 01CC845B.0CB5C070] -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ 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: 22196 bytes Desc: image001.png URL: From pierangelo.garino at telecomitalia.it Thu Oct 6 22:10:50 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 6 Oct 2011 22:10:50 +0200 Subject: [Fiware-wpa] R: [Fiware-wpl] Confirm whether the following people are members of FI-WARE In-Reply-To: <4E8DDEDB.6070903@tid.es> References: <4E8DDEDB.6070903@tid.es> Message-ID: Hi Juanjo, none of them is working in I2ND as far as I know. BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: gioved? 6 ottobre 2011 19:01 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Confirm whether the following people are members of FI-WARE Hi all, Could you tell me who in the following list is working in any of your WPs ? I'm not sure whether they are working in FI-WARE or in a UC project. In the second case, I would reject their request to join the FI-WARE project because they haven't followed the convention proposed for user accounts related to UC projects: define a login name which takes the form: _ Thanks, [cid:image001.png at 01CC8474.CEB62CA0] -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 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: image001.png Type: image/png Size: 22196 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jhierro at tid.es Fri Oct 7 00:15:13 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Oct 2011 00:15:13 +0200 Subject: [Fiware-wpa] REMINDER: joint WPLs/WPAs confcall on Monday October 10th In-Reply-To: <4E802EB7.2080909@tid.es> References: <4E802EB7.2080909@tid.es> Message-ID: <4E8E2871.5040706@tid.es> Hi all, This is a reminder that we will have a joint WPL/WPA confcall starting at 11:00am on October 10th. We will use powwownow for the confcall. The powwownow PIN code is 050662 Dial-in local phone numbers in the .pdf attached. Details for the webex session will be distributed the same morning. Best regards, -- Juanjo Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- A non-text attachment was scrubbed... Name: powownow-dial-in-numbers.pdf Type: application/pdf Size: 61661 bytes Desc: not available URL: From jhierro at tid.es Fri Oct 7 09:26:06 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Oct 2011 09:26:06 +0200 Subject: [Fiware-wpa] Be aware that contents uploaded on the Wiki are going to be public Message-ID: <4E8EA98E.8030201@tid.es> Self-explanatory. Bear it on mind, please. -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Fri Oct 7 09:34:01 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Oct 2011 09:34:01 +0200 Subject: [Fiware-wpa] IMPORTANT Considerations regarding tasks to be done. Message-ID: <4E8EAB69.6060709@tid.es> Hi, I have collected the answer to some questions that some of you have made, together with additional recommendations, in a number of messages that will follow: * Considerations about Wiki edition * The Backlog is not about describing features that assets being adopted as baseline already have * Be aware that contents uploaded on the Wiki are going to be public * Usage of potentially confidential info in full description of backlog entries (particularly, User-Stories) * How are we going to protect some Wiki contents from edition by UC projects I will try to transform some of these clarifications in actual contents that I will upload somewhere into the Wiki (in the FAQ, in the description about how we are using Agile, somewhere else ...) But I wanted to send it first to the list so you can take them into consideration. Last but not least, PLEASE try to push things forward because I believe we are still far from the target goal. Try to get things done for the review we will carry out during our joint WPL/WPA follow-up confcall on Monday. Cheers, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ 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 Oct 7 09:34:09 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Oct 2011 09:34:09 +0200 Subject: [Fiware-wpa] Considerations about Wiki edition Message-ID: <4E8EAB71.4040903@tid.es> Hi, Wikis are a nice tool but certainly they have limitations you should bear in mind while editing ... otherwise, it can be a disaster. In particular, parallel editing should be avoided, because what one writes could be overwitten by another ... We should be able to avoid much of this risk by editing specific sections where not so many people should be working in parallel. This should offer enough granularity as to avoid conflicting edition. A particular practice we should avoid is that of editing an entire Wiki page (clicking on the "edit" tab at the top). As said before, try to edit just specific sections (edit link on the right of each editable section). Some of you may argue that I didn't need to send this warning because this is something you already know, but I'm mentioning it because some people have had sad experiences editing the FI-WARE Wiki precisely because of this. Cheers, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Fri Oct 7 09:36:21 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Oct 2011 09:36:21 +0200 Subject: [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Message-ID: <4E8EABF5.5000206@tid.es> Hi all, As I have mentioned several times, the Backlog in a product development project is fundamentally about functionality that has to be developed in the product. Seeking for clarity, and because I have found it helpful when explaining Agile concepts, I have referred to it as "work to be done" because actually what you have to do when developing a software product is developing your functionality. On the other hand, we have to deal with a fundamental characteristic of this project: it is not about developing from the scratch but from a baseline formed by selected products (assets) generated in previous projects. And most of them hadn't been developed using Agile so far. If we had developed every GE from the scratch, the backlogs would contain Themes/Epics/Features/User-stories that, all together, would summarize the whole functionality of the GE. But this is not the case. You should consider that the backlog for each and every GE should contain the Themes/Epics/Features/User-stories that, at the current moment, is "pending functionality" (or development) still to be addressed. It is not the intent that, by reading all entries in the backlog, you should have a complete view on the functionality of the GE. Someone who wants to have a detailed picture of all target functionality should: * read the FI-WARE Product Vision, in order to understand what is overall expected for the GE * read the documentation available for the baseline assets used for materializing the GE: this should give the reader a clear picture of what is already there * read the backlog, to understand what's going on and is somehow on the roadmap The exercise we are doing is about setting the Agile backlogs that will drive our future developments. It's not about documenting what he have done during many years in our respective labs. A last comment: some Agile authorized experts go up to the point that they believe that Backlogs should not only contain info about the functionality to be developed in the product but any "work to be done" by the development team of a product, thus, using Agile for managing every activities in a project. That's why they mention that entries in a Backlog should be indeed named as "Work Items" rather than "User-stories" ... but that is, of course, a matter of taste. What is mandatory is to document the Themes/Epics/Features/User-stories that will drive developments on selected assets (this include developments required for integrating the different assets, of course). This is what should be uploaded on the Wiki and referred from tickets in the "Backlog Management" tracker. You may create another "Backlog" trackers for additional activities (like documentation, etc.). That's why I created a "Task Force Management" tracker in addition. Remember: Agile is about creating stuff that is useful in the development, not stuff for satisfying reviewers. Regards, -- Juanjo ________________________________ 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 Oct 7 09:38:36 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Oct 2011 09:38:36 +0200 Subject: [Fiware-wpa] Usage of potentially confidential info in full description of backlog entries (particularly, User-Stories) Message-ID: <4E8EAC7C.2000303@tid.es> Hi, According to Agile, a Feature (or an User-Story) should contain all the information that is enough as to allow the development team to warrant that development can be complemented with the duration of a Release (Sprint). This would go in the "Detailed Description" field of the corresponding entry in the Backlog. I don't want to elaborate more on this, unless some of you believe I should, because I have already elaborated a lot in previous emails (particularly relevant, those referring to INVEST properties). What comes next will be elaborated around User-Stories, but also apply to Features. Of course, it is also helpful that development teams use the User-Story entry as a placeholder for any valuable info that will help to guide the development, even in addition to that one which may be considered "enough". It would be a way to avoid dispersing the information. Then the following questions come: * I may have part of the information that I should introduce into the detailed description that I may have in internal documents that also hold some confidential information I don't want to disclose ... and I don't want to re-write those parts in the backlog. What should I do ? * I may be using Agile inside my company to carry out development on my asset ... but I'm not using FusionForge tools for this purpose ... I may even be using a kind of tracker, but not the one in FusionForge ... Should I replicate what I have in place for driving the development ? * I may even be fine with writing some parts in the detailed description (they are not documented anywhere else I can provide an URL link to) but I would like to be careful because I maybe disclosing confidential info about how my particular implementation is developed I believe we should be pragmatic ... even to the risk of annoying our reviewers :-) Remember: the backlog should be useful for us in driving our developments. Therefore, I would recommend following the principles below: * You may structure info in the "Detailed description" field in the entry of a backlog into two sections: * public: there you provide all the description that users would require to confirm that the functionality you are describing is also "enough" for them. Remember, that an Agile principle we also have to preserve is that the backlog should become a major communication tool between users and the development team. So don't get crazy and suddenly make everything private, come on. * private: there you will provide URL links to places that are private (even links that may only work if you are on your private network). I would highly recommend that this section comes with an initial statement such as "Following is a list of private URL resources that include additional valuable information for the development team that should be preserved as private" * Among other things, we will setup a private Wiki (actually, a Wiki instance linked to some project in FusionForge only partners in the FI-WARE project will get access to). You can also use it to bring stuff you will refer from the public backlog but relates to info you can share with the rest of the partners but still want to keep as non-accessible from the rest of the world. This way, I believe we can manage with all confidentiality and other practical concerns (particularly, avoid cloning what you have internally). Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ 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 Oct 7 09:38:56 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Oct 2011 09:38:56 +0200 Subject: [Fiware-wpa] How are we going to protect some Wiki contents from edition by UC projects Message-ID: <4E8EAC90.6000304@tid.es> Hi, As some of you have already realized, we are playing a bit risky the way we are working because some UC projects' users may accidentally delete/modify some of the contents we have uploaded to the Wiki. In order to fix this, we have setup a "FI-WARE Private" project which will have associated its own Wiki. The idea is that there, only us own editing privileges. Then, contents on the "FI-WARE" project that are being developed by us should come from our "FI-WARE Private" Wiki. Whether contents should be linked by reference (so that changes in the "FI-WARE Private" Wiki b For the time being, and while the solution comes, please -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email:jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Fri Oct 7 11:18:44 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Oct 2011 11:18:44 +0200 Subject: [Fiware-wpa] How are we going to protect some Wiki contents from edition by UC projects In-Reply-To: <4E8EAC90.6000304@tid.es> References: <4E8EAC90.6000304@tid.es> Message-ID: <4E8EC3F4.4050308@tid.es> On 07/10/11 09:38, Juanjo Hierro wrote: > Hi, > > As some of you have already realized, we are playing a bit risky the > way we are working because some UC projects' users may accidentally > delete/modify some of the contents we have uploaded to the Wiki. > > In order to fix this, we have setup a "FI-WARE Private" project which > will have associated its own Wiki. The idea is that there, only us own > editing privileges. Then, contents on the "FI-WARE" project that are > being developed by us should come from our "FI-WARE Private" Wiki. > Whether contents should be linked by reference (so that changes in the > "FI-WARE Private" Wiki b > > For the time being, and while the solution comes, please ... continue working on the current environement. (it seems like I pressed the "send" buttom too early this time. Cheers, -- Juanjo Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From pierangelo.garino at telecomitalia.it Fri Oct 7 11:50:07 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 7 Oct 2011 11:50:07 +0200 Subject: [Fiware-wpa] R: [Fiware-wpl] How are we going to protect some Wiki contents from edition by UC projects In-Reply-To: <4E8EAC90.6000304@tid.es> References: <4E8EAC90.6000304@tid.es> Message-ID: Hi Juanjo, don't know if it's a mail delivery problem: the last message I received from you is incomplete (see below). Can you send it again, thanks. BR Pier -----Messaggio originale----- Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: venerd? 7 ottobre 2011 09:39 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] How are we going to protect some Wiki contents from edition by UC projects Hi, As some of you have already realized, we are playing a bit risky the way we are working because some UC projects' users may accidentally delete/modify some of the contents we have uploaded to the Wiki. In order to fix this, we have setup a "FI-WARE Private" project which will have associated its own Wiki. The idea is that there, only us own editing privileges. Then, contents on the "FI-WARE" project that are being developed by us should come from our "FI-WARE Private" Wiki. Whether contents should be linked by reference (so that changes in the "FI-WARE Private" Wiki b For the time being, and while the solution comes, please -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email:jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl 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. From jhierro at tid.es Fri Oct 7 12:57:37 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Oct 2011 12:57:37 +0200 Subject: [Fiware-wpa] People awaiting for approval to join FI-WARE project Message-ID: <4E8EDB21.2030003@tid.es> Hi, (BTW: Several UC projects have already joined the FI-WARE project in FusionForge, be aware of that) Still the following two person are awaiting for approval to join the FI-WARE project. I'm providing more details about them so you can figure out better the potential relationship with your WPs (probably their email address is helpful) . [cid:part1.08080705.02070300 at tid.es] [cid:part2.06060003.01090400 at tid.es] Please let us know if we should approve their requests Cheers, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ 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: gbbcffdf.png Type: image/png Size: 28226 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: agjfghha.png Type: image/png Size: 29798 bytes Desc: not available URL: From jhierro at tid.es Mon Oct 10 00:13:26 2011 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Mon, 10 Oct 2011 00:13:26 +0200 Subject: [Fiware-wpa] Joint FI-WARE WPLs/WPAs follow-up confcall Message-ID: <4FE737A7257DB84C8CB36B7DFAFCC1CB7F162609A8@EXCLU2K7.hi.inet> When: Occurs on Monday every other week from 11:00 AM to 12:30 PM effective 10/10/2011. (GMT+01:00) Sarajevo, Skopje, Warsaw, Zagreb *~*~*~*~*~*~*~*~*~* ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2245 bytes Desc: not available URL: From jhierro at tid.es Mon Oct 10 08:12:20 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 10 Oct 2011 08:12:20 +0200 Subject: [Fiware-wpa] REMAINDER and AGENDA of Joint FI-WARE WPLs/WPAs follow-up confcall starting on 11:00am In-Reply-To: <4E8E1977.7060006@tid.es> References: <4E8E1977.7060006@tid.es> Message-ID: <4E928CC4.4050500@tid.es> Hi folks, Just a reminder that we will have a joint WPL/WPA follow-up confcall, from 11:00am - 12:30pm. We will use Powwownow and webex. Powwownow PIN code is 050662. Dial-in phone numbers attached. I hope that I will be able to provide with the Webex info enough in advance. Main goal is to review the status regarding identification+description of assets (I remind you that this was one of the main updates of the deliverable about Product Vision) as well as recording of entries for the different FI-WARE Chapter Backlogs (full description of entries on the Wiki + issuing corresponding tickets on the tracker) Besides, we will address other topics and will review APs from our last confcall as to conform the following: AGENDA: 1. Briefing on status of FI-PPP Use Case projects joining FusionForge/FI-WARE and submitting requests 2. Quick revision of APs identified as next steps during our last joint confcall which has been done: * Creation of FI-WARE Private project * Contents of first release of the FI-WARE Product Vision uploaded to the Wiki * Tutorials defined on the Wiki (will be part of the "Project Management Handbook" deliverable) 3. Work still on progress (meaning delay): * Description of assets * full description of backlog entries (including entries linked to "Question Marks") * creation of backlog tickets on chapter trackers * How we will review this: * Round table briefing on status, each pointing to issues for joint discussion or barriers found we have to solve * Joint discussion on identified issues and how to solve identified barriers 4. Discussions/doubts raised over email since last confcall: * Backlog is only about future development on assets or issuance of Open Calls (work) * Handling of confidential information in full description of backlog entries * Format in submission of deliverables (this is currently a hot discussion with the EC) 5. APs on Security Chapter: * Pascal to give us update on revision of Security section within FI-WARE Product Vision by the different chapters * Pascal to give us update on revised sections dealing description of overall solution for Identity, Access Control and Privacy Management in FI-WARE Product Vision document * Pascal to provide proposal about date at which virtual workshop with UC projects may be celebrated so that we can call UC projects. 6. Additional APs (not still critical, probably best to be handled in FI-WARE Private Wiki from their start): * Proposal on where to fit it the Dev Tools chapter in the FI-WARE Product Vision * Dissemination and Standardization entries on the Wiki * Exploitation * Confcall between TID/Engineering regarding planning of activities/milestones regarding the FI-WARE Testbed Best regards, -- Juanjo ________________________________ 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: powownow-dial-in-numbers.pdf Type: application/pdf Size: 61661 bytes Desc: not available URL: From jhierro at tid.es Mon Oct 10 10:20:27 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 10 Oct 2011 10:20:27 +0200 Subject: [Fiware-wpa] Webex detail for FI-WARE joint WPLs/WPAs follow-up confcall In-Reply-To: <251811646.1318230858343.JavaMail.nobody@jsj2wl016.webex.com> References: <251811646.1318230858343.JavaMail.nobody@jsj2wl016.webex.com> Message-ID: <4E92AACB.9070708@tid.es> Attached, -- Juanjo -------- Original Message -------- Subject: Meeting invitation: FI-WARE joint WPLs/WPAs follow-up confcall Date: Mon, 10 Oct 2011 09:14:18 +0200 From: Gestor i-Reunion webex9100 Reply-To: Webex9100 at tid.es To: JUAN JOSE HIERRO SUREDA Hello , Gestor i-Reunion webex9100 invites you to attend this online meeting. Topic: FI-WARE joint WPLs/WPAs follow-up confcall Date: Monday, October 10, 2011 Time: 11:00 am, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 963 233 772 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=186926982&UID=1254347272&PW=NZDA5ZDVkZTAy&RT=MiMyMw%3D%3D 2. Enter your name and email address. 3. Enter the meeting password: 1234abcD 4. Click "Join Now". To view in other time zones or languages, please click the link: https://telefonica.webex.com/telefonica-en/j.php?ED=186926982&UID=1254347272&PW=NZDA5ZDVkZTAy&ORT=MiMyMw%3D%3D ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/mc 2. On the left navigation bar, click "Support". You can contact me at: Webex9100 at tid.es To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://telefonica.webex.com/telefonica-en/j.php?ED=186926982&UID=1254347272&ICS=MI&LD=1&RD=2&ST=1&SHA2=DIYj8Rnmqk-pQdYQ1NF-fAwS-6sMbG5gR83H04QmHXE=&RT=MiMyMw%3D%3D The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://telefonica.webex.com/telefonica-en/systemdiagnosis.php Sign up for a free trial of WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, do not join the session. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Oct 10 17:46:59 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 10 Oct 2011 17:46:59 +0200 Subject: [Fiware-wpa] Fwd: RE: FI-WARE: CVs of suggested reviewers In-Reply-To: <7BACCBA4EE7D3946BF23FB79D9FD2E613CC5B1@S-DC-EXM11.net1.cec.eu.int> References: <7BACCBA4EE7D3946BF23FB79D9FD2E613CC5B1@S-DC-EXM11.net1.cec.eu.int> Message-ID: <4E931373.6060400@tid.es> Hi, Does anyone knows Mr. Piet Bel ? Any objection to have him on the list of reviewers ? I hope you pay the required attention to this. Cheers, Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain -------- Original Message -------- Subject: RE: FI-WARE: CVs of suggested reviewers Date: Mon, 10 Oct 2011 17:41:18 +0200 From: Arian.ZWEGERS at ec.europa.eu To: JUAN JOSE HIERRO SUREDA , JOSE JIMENEZ DELGADO CC: Annalisa.Bogliolo at ec.europa.eu , Federica.TAGLIANI at ec.europa.eu Dear Jose, Juanjo, Please find enclosed for your approval the CV of the 4th expert that I would like to invite as FI-WARE reviewer. His name is Piet Bel. Best regards, Arian. ________________________________ On 23/05/11 21:46, Arian.ZWEGERS at ec.europa.eu wrote: Dear Jose, Juanjo, As discussed in Budapest, please find enclosed for your approval the CVs of 3 experts that I would like to suggest as FI-WARE reviewers. As mentioned, I would like to come to a way-of-working based on fast feedback / suggestion cycles. This will be largely realised using remote reviews, possibly complemented by phone conferences with some key FI-WARE people, if deemed useful or necessary. In case of remote reviews, feedback will be rather informal. The main (only?) point of attention for the reviewers will be industrial relevance of the project outcomes. I might want to suggest a fourth name with expertise in IoT and software development in a later stage. Best regards, Arian. PS. During my absence, starting now, please send emails to me with Annalisa and Federica in cc. <> <> <> <> ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Bel.pdf Type: application/pdf Size: 11885 bytes Desc: not available URL: From jhierro at tid.es Mon Oct 10 23:05:28 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 10 Oct 2011 23:05:28 +0200 Subject: [Fiware-wpa] IMPORTANT: Create tickets on the right tracker Message-ID: <4E935E18.2000604@tid.es> Hi all, I have found that some of the tickets that should go to the tracker of a specific chapter ... have been issued to the "FI-WARE" "Theme/Epic/Feature Request" tracker. I remind you that the "Theme/Epic/Feature Request" tracker is for UC projects. They will submit there their request for functionality they would like to see supported in FI-WARE GEs. You should submit tickets that have been identified inside FI-WARE in the corresponding "Backlog Management" tracker. Unfortunately, the wording in the "How to create entries in the "Backlog Management" Tracker of a FI-WARE Chapter" tutorial available on the Wiki was not the best one and may lead to confusion ... I have fixed the wording and hopefully there won't be further confusion. Apologize for any inconvenience this may have caused. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From mcp at tid.es Tue Oct 11 14:49:59 2011 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 11 Oct 2011 14:49:59 +0200 Subject: [Fiware-wpa] Maintenance in the wiki Message-ID: <4E943B77.4060407@tid.es> Dear all, We are doing some maintenance works on the wiki on Thursday from 4pm onwards. It will be available by Friday at 9am. We are basically making changes in the templates and restructuring contents. Sorry for the inconveniences this may cause. Best regards Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Tue Oct 11 16:48:25 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 11 Oct 2011 16:48:25 +0200 Subject: [Fiware-wpa] Discussion about format of deliverables in FI-WARE project In-Reply-To: <4E945508.5040603@tid.es> References: <4E945508.5040603@tid.es> Message-ID: <4E945739.6000207@tid.es> Hi all, Just to let you know that we are carrying out a debate with the EC regarding format of deliverables. We wish to get rid of unnecessary paperwork and the typical burocracy of EC FP projects. We believe that FI-WARE should not only make the difference in terms of quality and impact of results, but the way the project is managed and followed-up/reviewed by the EC. Not allowing to submit an URL to a Wiki as a deliverable makes no sense nowadays. We believe this battle can be won since there is not strict legal/contractual arguments against the proposed approach and, more important, is common-sense. But, of course, we have to show strong, altogether pressing on the same direction. Any reference you may have about projects where the approach we are pushing for has been accepted would be welcome (we found one, SENSEI, it a first searching). It may add arguments in favor of our position in this debate. Best regards, -- Juanjo -------- Original Message -------- Subject: On the issue about deliverables Date: Tue, 11 Oct 2011 16:39:04 +0200 From: Juanjo Hierro To: Peter.Fatelnig at ec.europa.eu , Arian.ZWEGERS at ec.europa.eu CC: jhierro >> "Juan J. Hierro" Dear Peter and Arian, Thanks for the time discussing the issue about deliverables of the FI-WARE project. It was helpful to understand your major concerns on the matter. I hope it was also helpful for you to understand ours. There are two major issues you raised during our conversation: * Ability to audit reviews of Wiki-based deliverables * How to deal with a "moving target" while reviewing a very dynamic deliverable like the ones we have in FI-WARE Let me elaborate on both and how things we honestly believe they can be handled. Regarding ability to audit reviews of Wiki-based deliverables, we should be able to produce a snapshot of the Wiki contents (standard export MediaWiki functions) from FI-WARE. Such snapshot can be later replicated (standard import MediaWiki function) on any independent and standard MediaWiki installation (that the EC may own, for instance). By comparing contents of two subsequent snapshots, you would be able to demostrate existence of deliverables and how review of a given deliverable was addressed. We believe this will solve the issue. Regarding review of Wiki-based deliverables, we can do two things (non-exclusive): * Setup a MediaWiki instance based on the snapshot that we had generated for a given deliverable submission. Such instance would be stable (no content change) for a reviewing period. This instance would be accessible for reviewers who want to stick to a frozen version of the deliverable, which matches the version which was officially submitted. * Allow that some FI-WARE reviewers perform their review on the contents of the dynamic, linked to the FI-WARE website, version of the Wiki if they wish. The first approach would be an approach fully aligned with the "traditional" approach, with the corresponding advantages/disadvantages: * On one had they will know that they are reviewing a "frozen" document (don't know what is the advantage of this to be honest, but let's admit that they would have a better control about when they have finish the review of a given section) * On the other hand, they may be reviewing contents available on day "X" (the date at which the deliverable was submitted) and at the time they start to review chapter "a", say it on date "Y", "Y" > "X", they will miss the opportunity to review the updated contents of chapter "a" that may have already been implemented in the public, linked to the FI-WARE website, version of the Wiki. This is a disadvantage and they may even waist their time providing advice on how to solve some issue, when the fact is that issue may have already been solved (already detected by the FI-WARE team and fixed in the time period [X, Y)). Note that this is something that is going to happen even if we are submitting deliverables in MS Word / .pdf format (you cannot prevent that the FI-WARE team keeps working on a document right after they have submitted it) The second approach would be optional but I guess preferred by some reviewers (I tell you it would be clearly the preferred one for me if I were a reviewer of a project like this). It may have the following advantages * The disadvantage mentioned in the second bullet of last paragraph simply goes away. * Some reviewers won't be able to devote time to read a full deliverable the day after it has been submitted. They will typically organize their time and, for large documents, will organize their time so that they review a deliverable submitted on date "X" so that they deal with chapter "a" in date "Y", chapter "b" in date "Z", etc. X < Y < Z ... By being able to review the most updated version of a given chapter, at the time they start to review it, their revision is more effective and more valuable. I hope you can see this with the eyes of who tries to make things more effective and useful while still being open to comply with some requirements. There is a lot of expectation about this project and the PPP as a whole not just on the results that will be delivered but also on the way the program will be managed. People is eager that there will be sign of change for something better than we have today in terms of processes and methodologies. We shouldn't miss the opportunity. We shouldn't let them down. BTW, for your convenience, I send you a copy of an official deliverable that was linked to a Wiki in a FP7 project (SENSEI) Best regards, -- Juanjo ________________________________ 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: SENSEI_WP5_D5.3.pdf Type: application/pdf Size: 88703 bytes Desc: not available URL: From jhierro at tid.es Tue Oct 11 17:29:29 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 11 Oct 2011 17:29:29 +0200 Subject: [Fiware-wpa] On assignment of tracker tickets and creation of tasks Message-ID: <4E9460D9.3080104@tid.es> Hi Folks, The Wiki and the trackers are at top speed because of teams working hard on reaching the milestone on Wednesday, so congratulations. Hope it will be definitively reached. I would like to send this email to answer some questions regarding assignment of tickets and creation of tasks. I believe we should follow same conventions and practices, that's the reason for this email. First of all, I suggest that we deal with development tasks (i.e., task derived from taking care of entries in the backlog) in the pure sense of Agile, i.e., in the course of a sprint. Since we haven't yet started the first sprint (it will start on Nov 1th) ... please don't create development tasks yet. We will forward you concrete and precise hints on when/how to create tasks and what Task subprojects to create linked to your Chapter Projects maybe in one week. Of course, detailed tutorials will be provided then. This doesn't prevent you to assign tickets to people in your teams so that they can deal with them and you can organize the work. You shoud all have "Admin" role in your respective project, thus owning "Tech&Admin" privileges on the Backlog Management tracker. Note that the rest of the team in your projects, who have the "FI-WARE Chapter Project Member" role, are even able to reassign tickets while rest of FI-WARE project members that have the "FI-WARE Project Member" Role will only be able to solve/handle the tickets (if you have followed the suggestions made on the tutorials). You may decide to decide to assign different privileges at your will, all that is explained on the tutorial. Some of you wish to assign tickets to some members of your Chapter team so that they keep working on them, either refining them (and eventually produce Features or User-Stories) or just providing additional info that is currently missing. Let's use the assignment operation supported by trackers for the time being and not create tasks yet. Tasks linked to Backlog entries are rather easy to create (you just need to build a task relation to a ticket) and can be useful to monitor progress of an assignment at a rather fine-grain level, i.e., monitoring % of progress and hours devoted, but we have to think carefully what conventions we should all follow in order to achieve some level of homogeneity across the project. Don't hesitate to ask if you have any further question. Best regards, -- Juanjo Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Tue Oct 11 18:29:07 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 11 Oct 2011 18:29:07 +0200 Subject: [Fiware-wpa] Minutes of joint WPL/WPA follow-up confcall Message-ID: <4E946ED3.2060304@tid.es> Hi, Following are my notes on our last joint WPL/WPA follow-up confcall. Please make any comment if you find there was something missing or wrong. Best regards, -- Juanjo 1. Briefing on status of FI-PPP Use Case projects joining FusionForge/FI-WARE and submitting requests Everything has been setup for Use Case project to join FusionForge/FI-WARE and start submitting their requests for Themes/Epics/Features or simply formulate questions. The first accounts have been created, but no relevant activity seems to be taking place for the time being. 2. Quick revision of APs identified as next steps during our last joint confcall which has been done: The following APs have been covered: * Creation of FI-WARE Private project: soon there will be instructions on how to deal with it. * Contents of first release of the FI-WARE Product Vision uploaded to the Wiki * Tutorials defined on the Wiki as part of "Project Handbook" section (which will become the "Project Management Handbook" deliverable) 3. Work still on progress (meaning delay): We haven't yet finished the work on: * Description of assets * Full description of backlog entries (including entries linked to "Question Marks") * Creation of backlog tickets on chapter trackers We made a round table briefing on status, each pointing to issues for joint discussion or barriers found we have to solve Data/Context (Juanjo): Work in progress. We expect to get everything finished by EOB Tuesday Oct 11. No issue regarding Wiki, Tracker, tools overall IoT (Thierry): No assest description because they are still fully devoted to selection of assets. Expect to reach a conclusion on selection of assets (first take at least) by end of this week. Consequently, description of assets will not be available until all of this process finishes. Dealing with creation of entries linked to the Backlog. Could meet deadline on Wednesday October 12th morning. Team is trying to document a rationale for the selection of assets Issue with the Wiki: Some partners do not agree that description/documentation of assets become available on the Wiki Juanjo asked whether there is any task dealing with definition of positioning with regard to relevant standardization efforts (mostly OMA, OGC). Thierry commented this was being addressed. Apps/Service: Working in process. No major issue. Fine with deadline Wednesday October 12th morning. Recommendation: Adopt a convention for the title of the page describing an asset. Interface to Network and Device: Late on description of assets. Just a placeholder at this point. Addressing issue on Cloud-proxy. Should all activities be covered just in the I2ND chapter ? This will affect at least Technicolor because they have to know where to upload information about entries in the backlog. AP on Juanjo: to comment on mail sent by Technicolor. Still some concerns about what should be considered as an Epic despite the explanations. Intel partner with skills in Agile has joined that may help so he can be helpful. Juanjo: please review the hints provided in several emails. Issue with the Wiki: Sometimes navigation, specially going back to the previous page is a bit cumbersome. AP on Juanjo: Try to find out whether there is something we can configured on the Wiki for this. Feel confident to get backlogs entries uploaded on to the Wiki plus tickets on the tracker by Wednesday. Not sure about description of assets which may require a few more days (end of this week). Security: Team working to complete the work. Description of assets ongoing driven by the task leads. Also work on Backlog entries ongoing. Issue with the Wiki: concerns about the fact that some of the info becomes publicly available: * description of some assets * detailed description linked to some user stories Believe that deadline on Wednesday Oct 12 could be met. Major issue is the fact that problems with making some info publicly available on the Wiki may mean some entries may look still empty. Joint discussion on issues mentioned during the round table and how to solve identified barriers The main issue is that about public access to information published on the wiki. Juanjo: We can differentiate and have information not disclosed (the how) while other parts are open (the what). A given entry in the backlog may have contents in the detailed description that is public (that one we consider enough for a user to understand what we are talking about) while links to hints on the how that will not work if you don't have the proper privileges (e.g., will navigate to another website that only developers can access to). This shouldn't be a problem. Everyone seems to feel comfortable with such approach. Still it would be nice to have some resources linked to FusionForge that can be only visible to members of the FI-WARE project. AP: Juanjo to explain what tools the chapter teams can use to keep part of the information private (e.g., private Wikis) Some people raised during the discussion the need to have a unstable version of the Wiki which would be private to FI-WARE partners and where editing of the Wiki continuously takes place, while the current become more stable since it will be available to anyone on the Internet. AP: Juanjo to come with a process for reviewing contents of the Wiki previous to publish, combining unstable and stable versions of the Wiki. 4. APs on Security Chapter (Pascal): 4.1 Update on revision of Security section within FI-WARE Product Vision by the different chapters Pascal has no receive any input from the Chapter teams but IoT. AP: Juanjo to send a URGENT reminder to the chapter leaders 4.2 Pascal to give us update on revised sections dealing description of overall solution for Identity, Access Control and Privacy Management in FI-WARE Product Vision document Have reviewed but still continue being reviewed. Today EOB will the content of the Product Vision document on the Wiki will be updated. 4.3 Pascal to provide proposal about date at which virtual workshop with UC projects may be celebrated so that we can call UC projects. No date yet. Expect to be able to setup a virtual workshops: monday Oct 17, Oct 19, Oct 20. AP: Juanjo to share with UC projects and create a doodle for them to cast their availability. 5. Additional APs (not still critical, probably best to be handled in FI-WARE Private Wiki from their start): 5.1 Proposal on where to fit it the Dev Tools chapter in the FI-WARE Product Vision (Davide): Dealing with revision of the document. Still configuring the tracker within their chapter. They have sent an email making a proposal on where the document would fit within the overall Product Vision. AP: Juanjo to make sure that specific sections on the Wiki are available for uploading the Dev Tool contents Ericsson will not host the catalogue linked to the Ericsson Lab. Therefore, we have to develop our own catalogue. Ericsson will help to design this, which is the phase where we are. 5. 2 Answer on Questionnaire on Dev Tools No answer has been received by the other chapter teams AP: Juanjo to send a reminder to chapters to fill the questionnaire distributed by the Dev Tool team The following questions couldn't be address for lack of time and will be postponed until next joint WPL/WPA follow-up confcall: * Dissemination and Standardization entries on the Wiki * Exploitation * Confcall between TID/Engineering regarding planning of activities/milestones regarding the FI-WARE Testbed 6. AOB (Any Other Business) No other business identified so we closed the confcall ________________________________ 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 Oct 12 12:38:16 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 12 Oct 2011 12:38:16 +0200 Subject: [Fiware-wpa] Admin privileges in FI-WARE project at FusionForge Message-ID: <4E956E18.8000304@tid.es> Hi all, You are currently registered as members of the FI-WARE project in FusionForge with the "Chapter Lead" Role. I have changed the "Chapter Lead" Role so that it nows holds Admin privileges of the project. This doesn't mean that we have changed the privileges of "Chapter Lead" members with respect to trackers. Still only Thomas, Miguel and me have the right to assign tickets that UC projects may have issued. However, it allows you to recover some of the Admin privileges, such as administration of users, that will make us more agile. Of course, you can take advantage of the new Admin privileges to change your privileges on the tracker :-) ... but please don't do that ;-) As per now, I remind you that there are still some requests for joining the FI-WARE project that are pending of acceptance. Please take your time to check whether any of them corresponds to someone from your chapter/wp. [cid:part1.09050702.05020600 at tid.es] I also kindly ask you to be extremely carefully accepting requests to join the project. There are members of UC projects that are requesting to join. Just leave acceptance of them to us so that we can check whether they have fulfilled the rules regarding username and they get assigned the right Role (FI-WARE User). Just simply take care of requests to join coming from members of your teams. Today is holiday in Spain so that you will see lack of responsiveness from TID members. Please take this into account if you make any request to us. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ 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: dddigfci.png Type: image/png Size: 74282 bytes Desc: not available URL: From jhierro at tid.es Thu Oct 13 00:26:24 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 13 Oct 2011 00:26:24 +0200 Subject: [Fiware-wpa] Administering registration in FusionForge and mailing list Message-ID: <4E961410.5060506@tid.es> Hi all, This is to let you know that you have now all what is needed for administering users both in the FI-WARE project at FusionForge and the fiware at lists.fi-ware.eu mailing list. This should help us to be more agile. Regarding the fiware mailing list, you know that we have a mailman setup. The passwd for administering the list is erawif-ppp (fiware in reverse order plus -ppp) Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From mcp at tid.es Thu Oct 13 13:53:11 2011 From: mcp at tid.es (Miguel Carrillo) Date: Thu, 13 Oct 2011 13:53:11 +0200 Subject: [Fiware-wpa] Maintenance in the wiki In-Reply-To: <4E943B77.4060407@tid.es> References: <4E943B77.4060407@tid.es> Message-ID: <4E96D127.9020906@tid.es> Dear all, This is just to let you know that this has been cancelled. I will let you know the new date in advance. My apologies Miguel El 11/10/2011 14:49, Miguel Carrillo escribi?: > Dear all, > > We are doing some maintenance works on the wiki on Thursday from 4pm > onwards. It will be available by Friday at 9am. We are basically > making changes in the templates and restructuring contents. > > Sorry for the inconveniences this may cause. > > Best regards > > Miguel > -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 Mobile: (+34) 616 213 607 e-mail: mcp at tid.es ---------------------------------------------------------------------- Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Thu Oct 13 21:34:59 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 13 Oct 2011 21:34:59 +0200 Subject: [Fiware-wpa] On one of the Security-related APs from our joint WPL/WPA follow-up confcall In-Reply-To: <4E946ED3.2060304@tid.es> References: <4E946ED3.2060304@tid.es> Message-ID: <4E973D63.3000100@tid.es> On 11/10/11 18:29, Juanjo Hierro wrote: 4.3 Pascal to provide proposal about date at which virtual workshop with UC projects may be celebrated so that we can call UC projects. No date yet. Expect to be able to setup a virtual workshops: monday Oct 17, Oct 19, Oct 20. AP: Juanjo to share with UC projects and create a doodle for them to cast their availability. I have think a bit on this and I believe that it would be better that we devote one of these days to an actual workshop ... but internal, thus, explaining the proposed solution to WPLs and WPAs of the FI-WARE project (or whoever they want to invite) in the first place. This will allow us to confirm that the proposed solution for Identity, Access Control and Privacy Management is understood and accepted inside the FI-WARE project first. Then, afterwards, we can present this to the UC projects. Feedback from WPLs and WPAs will for sure be valuable to prepare such workshop even better. Therefore, my suggestion is to adopt the following plan: 1. Have a virtual workshop internal to FI-WARE first where the Security team explain the rest of chapter teams the proposed approach for Identity, Access Control and Privacy Management in FI-WARE. I will setup a doodle for finding a slot on Oct 17, 18 or 19 (I wouldn't be able to make it on Oct 20) 2. Propose the workshop to the UC projects during the AB meeting in Poznan on Oct 25. I would try to close a date for such workshop during the meeting. 3. Celebrate the workhsop with UC projects in the date agreed with UC projects Pascal, please confirm this sounds like a reasonable plan to you. Best regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Mon Oct 17 09:50:14 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 17 Oct 2011 09:50:14 +0200 Subject: [Fiware-wpa] [Fiware-wpl] On one of the Security-related APs from our joint WPL/WPA follow-up confcall In-Reply-To: <4E973D63.3000100@tid.es> References: <4E946ED3.2060304@tid.es> <4E973D63.3000100@tid.es> Message-ID: <31119_1318837818_4E9BDE3A_31119_81_1_3e865717-3d80-4035-9944-8501b469906e@THSONEA01HUB05P.one.grp> Dear Juanjo, This just to answer your proposal that I discussed on last Friday at Security Team weekly audio conf we had. I must say that if we can agree on your new plan (aka to have our Core Generic Enablers [Id Mgt, Privacy & Data control] as now described in M5 release of HLA description document (Product Vision) be presented to other ATs before having them presented to Use Cases projects we also think it is too short notice to have this done this week for what concerns the meeting with the ATs nor the week after to have it done in turn with UC projects. This simply because I was not planning to attend the AB nor members of my team who had no plan to be in Poznan and that I'd like to have at this meeting (Task leads - especially T8.2 lead (Robert in cc) and Core GEs owners) This just to say that if we can agree on the new plan we can't agree on the dates announced/proposed to have it done since unrealistic from our perspective. [People we need having other commitments now at the dates proposed.] Being said that and to go with your plan which I support could you please propose us through doodles, (realistic) dates we could go for these two meetings. This in order to have the dates of those two meetings set asap. Many thanks in advance. Hearing from you. Best Regards, Pascal PS: Please confirm and provide me with the details of WPL/WPA audio conf of today. Presumably there is one De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : jeudi 13 octobre 2011 21:35 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] On one of the Security-related APs from our joint WPL/WPA follow-up confcall On 11/10/11 18:29, Juanjo Hierro wrote: 4.3 Pascal to provide proposal about date at which virtual workshop with UC projects may be celebrated so that we can call UC projects. No date yet. Expect to be able to setup a virtual workshops: monday Oct 17, Oct 19, Oct 20. AP: Juanjo to share with UC projects and create a doodle for them to cast their availability. I have think a bit on this and I believe that it would be better that we devote one of these days to an actual workshop ... but internal, thus, explaining the proposed solution to WPLs and WPAs of the FI-WARE project (or whoever they want to invite) in the first place. This will allow us to confirm that the proposed solution for Identity, Access Control and Privacy Management is understood and accepted inside the FI-WARE project first. Then, afterwards, we can present this to the UC projects. Feedback from WPLs and WPAs will for sure be valuable to prepare such workshop even better. Therefore, my suggestion is to adopt the following plan: 1. Have a virtual workshop internal to FI-WARE first where the Security team explain the rest of chapter teams the proposed approach for Identity, Access Control and Privacy Management in FI-WARE. I will setup a doodle for finding a slot on Oct 17, 18 or 19 (I wouldn't be able to make it on Oct 20) 2. Propose the workshop to the UC projects during the AB meeting in Poznan on Oct 25. I would try to close a date for such workshop during the meeting. 3. Celebrate the workhsop with UC projects in the date agreed with UC projects Pascal, please confirm this sounds like a reasonable plan to you. Best regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue Oct 18 16:09:58 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 18 Oct 2011 16:09:58 +0200 Subject: [Fiware-wpa] Overview of status Message-ID: <4E9D88B6.1060105@tid.es> Hi all, End of October is approaching and I want to remind you the major goals we have to meet by the end of the month: * Update of the FI-WARE Product Vision. We should address: * as many of the comments on the first release of the FI-WARE Product Vision by the reviewers as possible * what we committed to do as delta against the first version of this deliverable according to the DoW : "?what are the baseline projects whose results will be considered for integration in FI-WARE together with an explanation on what results may be used why and how they plan to be integrated together. It also will include a description of projects whose progress will be monitored to determine their further adoption in planned releases of FI-WARE. * Creation of the backlog linked to each chapter and GE, including: * Epics describing functionality still at high level, thus requiring further analysis in parallel to sprints * Features, including those we commit to address during first minor release of FI-WARE (starting November 1st and scheduled to end mid February) * User-Stories, including those we plan to develop during first Sprint (starting November 1st, lasting one month) Regarding second bullet of the first point, that is the description of assets, Miguel Carrillo will send to each of you a detailed report on things we are missing or things we will request you to fix in order to achieve a minimum of homogeneity regarding contents published on the Wiki. Please review Miguel's requests carefully and try to implement them as soon as possible. Bear in mind that we should have all this done by end of September and we are running late. Regarding the backlog, apart from finishing the uploading of all the identified Epics associated to chapters/GEs, you should work trying to refine them up to produce the first set of features and user-stories. You should also take a look in parallel to requests made by the UC projects. Thomas and me will take a look at them and assign them to you when we find them suitable for your analysis. Don't hesitate to ask any question. Please share this info with your teams. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ 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 Wed Oct 19 16:57:28 2011 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 19 Oct 2011 16:57:28 +0200 Subject: [Fiware-wpa] Private wikis for each one of the chapters Message-ID: <4E9EE558.8020206@tid.es> Dear all, We have set up private wikis for each Chapter. This means that a user that comes from outside FI-WARE and therefore cannot log on the forge will not be able to see the contents of these wikis. You will see a new link to the right of your project page on FusionForge. [cid:part1.00000002.04040205 at tid.es] The idea is that each WP will be able to use their wiki: * as a sandbox * to store private info that can be shared within the project but that cannot be made publicly available * to produce draft pages before uploading them to the public wiki The new wikis are located on: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/apps/index.php/Main_Page * https://forge.fi-ware.eu/plugins/mediawiki/wiki/cloud/index.php/Main_Page * https://forge.fi-ware.eu/plugins/mediawiki/wiki/iot/index.php/Main_Page * https://forge.fi-ware.eu/plugins/mediawiki/wiki/data/index.php/Main_Page * https://forge.fi-ware.eu/plugins/mediawiki/wiki/i2nd/index.php/Main_Page * https://forge.fi-ware.eu/plugins/mediawiki/wiki/security/index.php/Main_Page * https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/Main_Page Please note that direct login is not possible, the only way to access them is logging in on the forge. The public wiki remains open to the outside world (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Main_Page). FI-WARE members can edit pages and anonymous users can just read them. We will continue using this wiki to describe the Assets, Epics, etc. in order to build the final deliverables. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- ________________________________ 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: moz-screenshot-30.png Type: image/png Size: 11379 bytes Desc: not available URL: From jhierro at tid.es Wed Oct 19 17:16:14 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 19 Oct 2011 17:16:14 +0200 Subject: [Fiware-wpa] IMPORTANT: Enhancing Question Marks sections in FI-WARE Product Vision, overall with respect to Security issues, and translating issues into Epics in the FI-WARE backlogs Message-ID: <4E9EE9BE.2080701@tid.es> Hi all, One of the APs that we agreed on during one of our last joint follow-up confcalls had to do with reviewing the sections dealing with description of Security issues in your respective chapters (this being part of the "Question Marks" section). A reference example of the level of development we should accomplish can be found taking a look at the contents of the "Security Issues" section of the Data and Apps chapters. Once you enhance the "Question Marks" section, you should try to map each relevant topic/issue into an Theme/Epic I would recommend to add under the "Topics still being addressed at high-level" section of the "Materializing *" page of the Wiki linked to your chapter. This work has to be done by mid next week and cannot be further delayed. It will be relevant not only in order to show progress to reviewers but in order to get work to be done properly organized. Miguel will pencil this as one of the items to review regarding each of the chapters. Best regards, -- Juanjo Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Sun Oct 23 09:16:45 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 23 Oct 2011 09:16:45 +0200 Subject: [Fiware-wpa] Workshop YOU SHOULD ATTEND on FI-WARE Identity, Access Control and Privacy Management Architecture Message-ID: <4EA3BF5D.50602@tid.es> Dear colleagues, As you my remember, one of the APs from our last joint follow-up confcall was to setup a workshop with UC projects regarding description of the soluction we have defined for the core Security GEs dealing with Identity, Access Control and Privacy Management in FI-WARE. After some discussion, we have decided that we will first celebrate a internal workshop, involving only FI-WARE partners, and then afterwards and once we compile the internal feedback, celebrate the final workshop with the UC projects. The internal FI-WARE workshop will be virtual, i.e., a combination of confcall and webex. Regarding the internal FI-WARE workshop, we need to accomodate it in the week starting November 7th. A number of dates/times have been selected that week and recorded in the following doodle: http://www.doodle.com/5mkp668qtc43hwwz Please cast your vote so that we can close the date for the virtual workshop. Note that voting a starting time means agreement to stay for 3 hours starting at that time, since 3 hours would be the estimated duration for this workshop. You are welcome to invite any member of your team that you believe is relevant. Note that Identity, Access Control and Privacy Management are three crucial aspects we definitively need to resolve the best way in FI-WARE. Deadline for voting is Wednesday Oct 26th. We will then announce the final date/time on Thursday Oct 27. Cheers, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Sun Oct 23 09:23:46 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 23 Oct 2011 09:23:46 +0200 Subject: [Fiware-wpa] Identification of Open Call objectives Message-ID: <4EA3C102.9070808@tid.es> Dear colleagues, According to the project planning, we should identify the topics around which the first Open Call will be issued by mid November. This mail is to setup an AP on all WPLs to prepare a first list of topics on behalf of their respective WPs and submit it to me no later than November 1st, EOB. This list should be derived relatively easily from the current exercise we are closing regarding selection of baseline assets, since obviously a criteria would be to include calls for those GEs, or components in a GE, for which baseline assets have not been identified. We will celebrate a confcall dedicated to review the received input and plan the necessary steps on November 3, starting at 16:30. Please pencil this date/time on your agendas. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ 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 Sun Oct 23 09:31:33 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 23 Oct 2011 09:31:33 +0200 Subject: [Fiware-wpa] Identification of Open Call objectives In-Reply-To: <4EA3C102.9070808@tid.es> References: <4EA3C102.9070808@tid.es> Message-ID: <4EA3C2D5.60601@tid.es> FYI, This is the schedule for the first Open Call, according to the DoW: [cid:part1.04010005.02040609 at tid.es] Dates refer to end of a month, that is, M5 means "End of September". This doesn't mean that we cannot change it slightly, but we should stick to the plan if possible. Best regards, -- Juanjo On 23/10/11 09:23, Juanjo Hierro wrote: Dear colleagues, According to the project planning, we should identify the topics around which the first Open Call will be issued by mid November. This mail is to setup an AP on all WPLs to prepare a first list of topics on behalf of their respective WPs and submit it to me no later than November 1st, EOB. This list should be derived relatively easily from the current exercise we are closing regarding selection of baseline assets, since obviously a criteria would be to include calls for those GEs, or components in a GE, for which baseline assets have not been identified. We will celebrate a confcall dedicated to review the received input and plan the necessary steps on November 3, starting at 16:30. Please pencil this date/time on your agendas. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ 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: fjagjbcc.png Type: image/png Size: 60596 bytes Desc: not available URL: From jhierro at tid.es Sun Oct 23 09:43:20 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 23 Oct 2011 09:43:20 +0200 Subject: [Fiware-wpa] Joint WPL/WPA follow-up Message-ID: <4EA3C598.1060101@tid.es> Dear all, Next week many of us are going to be in Poznan, travelling on Monday. Therefore, the joint follow-up confcall on Monday will be cancelled. We will celebrate our next follow-up confcall on November 11th, as planned. There, main topic of the agenda will be preparation of the upcoming 1st official review planned for November 22nd (I remind you that rehearsal is mandatory to attend and scheduled to start on Nov 21, 09:00am). Some instructions and preparatory work will be send to you while I'm in Poznan. Thomas and me will meet and work on the matter. I would like to remind you that it is CRUCIAL that you cope with all what was planned to be finished by end of October (we are indeed one month late since we are talking about topics that should be ready by end of September). In particular, review of the FI-WARE Product Vision deliverable (structured as review of current contents as well as development of the "Materializing the FI-WARE Product Vision" chapter). A first list of points to be solved was sent by Miguel Carrillo to you recently, please try to follow his directions and share any issue/barrier you may face. Additional instructions may follow so please stay tuned. As you know from a previous mail from me, we will have a confcall dedicated to the 1st Open Call on Thursday November 3th, 16:30. We may address any urgent matter also there if needed. However, we should try working off-line and take advantage of the dedicated follow-up confcalls focused on your WP for this purpose. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Mon Oct 24 02:30:22 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 24 Oct 2011 02:30:22 +0200 Subject: [Fiware-wpa] IMPORTANT Next steps regarding planning of first release and sprint Message-ID: <4EA4B19E.90009@tid.es> Dear colleagues, This is a reminder that you should devote these last days until end of October to identify/select the User Stories that will be addressed in the first development sprint of FI-WARE. You should also define the Features that you plan to address during the first release of the project. Here, we have a small issue because we defined (minor) releases as 3 months long and we wanted to split the first major release of FI-WARE (scheduled to finish by end of Abril, according to the DoW) into two (minor) releases. I had proposed finishing the first release by mid February during our last joint WPL/WPA follow-up confcall but now I believe like it would be better if we close the first (minor) release by end of February (given the fact is the first) and keep the second (minor) release a bit shorter. Some of you still have some doubts about how to identify Features. On the other hand, you have already identified a bunch of Epics so it seems like there is definitively no problem identifying Epics. Well ... if that is the case then I tell you that It's a matter of just naming as Features those Epics you expect to address in the first minor release (scheduled to be finished by end of February as I have just said). As simple as that. Note that being able to state that you expect a given functionality described as an Epic to be implemented in your product by the end of a release simply means that you have enough information about the functionality as to feel confident that you will be able to refine it to the level of User-Stories which, in turn, can be addressed in development sprints, all during the course of the first (minor) release. But that is actually the definition of a Feature. Therefore, the proposal I would make is that you simply review the Epics you have already identified and select those you expect/plan to address by end of February (or earlier). Then change those Epics and name them as Features. That's all. It will imply updating the Id both at the Wiki and the tracker. Also the location in the proper section at the Wiki. I know. But it's not a big deal. Those Epics you don't turn into Features will of course remain being named as Epics. Why are we then dealing with Features in addition to Epics ? Because it gives hints about what functionality we expect to address within a certain period o time and this is important for the overall management of the project and for interaction with customers. Particularly the UC Projects, who need to know what functionality is going to be available when, so that they can plan their developments better. Other than this, you may think on Features as just Epics you have committed to address before some given date. Hope these hints help you to identify the Features for the first (minor) release of FI-WARE. Don't hesitate to ask if you still have doubts or questions. Please find enclosed a paper from the recognized Agile expert Dean Leffingwell where a more elaborated description of Epics, Features, User-Stories is given. I hope it will also be helpful. DON'T FORGET: Try to identify the User-Stories for the first sprint and the Features for the first release no later than end of October. Cheers, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ 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: a-lean-and-scalable-requirements-information-model-for-agile-enterprises.pdf Type: application/pdf Size: 1463988 bytes Desc: not available URL: From stefano.depanfilis at eng.it Mon Oct 24 12:28:33 2011 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Mon, 24 Oct 2011 12:28:33 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Joint WPL/WPA follow-up In-Reply-To: <4EA3C598.1060101@tid.es> References: <4EA3C598.1060101@tid.es> Message-ID: dear juanjo, what about starting the work for wp10??? ciao, stefano 2011/10/23 Juanjo Hierro : > Dear all, > > ?Next week many of us are going to be in Poznan, travelling on > Monday. ? ?Therefore, the joint follow-up confcall on Monday will be > cancelled. > > ?We will celebrate our next follow-up confcall on November 11th, as > planned. ? There, main topic of the agenda will be preparation of the > upcoming 1st official review planned for November 22nd (I remind you > that rehearsal is mandatory to attend and scheduled to start on Nov 21, > 09:00am). ? ?Some instructions and preparatory work will be send to you > while I'm in Poznan. ? Thomas and me will meet and work on the matter. > > ?I would like to remind you that it is CRUCIAL that you cope with all > what was planned to be finished by end of October (we are indeed one > month late since we are talking about topics that should be ready by end > of September). ? ?In particular, review of the FI-WARE Product Vision > deliverable (structured as review of current contents as well as > development of the "Materializing the FI-WARE Product Vision" > chapter). ? A first list of points to be solved was sent by Miguel > Carrillo to you recently, please try to follow his directions and share > any issue/barrier you may face. ? Additional instructions may follow so > please stay tuned. > > ?As you know from a previous mail from me, we will have a confcall > dedicated to the 1st Open Call on Thursday November 3th, 16:30. ? We may > address any urgent matter also there if needed. ? However, we should try > working off-line and take advantage of the dedicated follow-up confcalls > focused on your WP for this purpose. > > ?Best regards, > > -- > Juanjo Hierro > Chief Technologist on Software Technologies > Telefonica R&D Labs > > email: jhierro at tid.es > phone: +34 91 48 32932 > www.tid.es > twitter.com/JuanjoHierro > > Oeste 1, Planta 5. Distrito C > Ronda de la Comunicacion s/n > Madrid 28050 > Spain > > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar > nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace > situado m?s abajo. > This message is intended exclusively for its addressee. We only send and > receive email on the basis of the terms set out at. > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpl > > -- Stefano De Panfilis Research and Development Laboratories Department Director Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567