From jhierro at tid.es Mon Oct 3 13:23:20 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 03 Oct 2011 13:23:20 +0200 Subject: [Fiware-data] Uploading full description of Backlog entries and creating tickets in the Backlog Management tracker Message-ID: <4E899B28.5090706@tid.es> Hi all, You should have everything now ready as to: * upload the full description of Backlog entries on the public Wiki * create tickets in the "Backlog Management" tracker that has been setup in the FI-WARE Data project Detailed tutorials about all this can be found in the Project Handbook that is available on the Wiki. You need to be logged in FusionForge to get access to the Wiki with editing privileges. Once you have logged in, you can either go directly to http://wiki.fi-ware.eu or go to the project home page and then click on the MediaWiki Tab. Please try to have everything regarding backlog entries linked to your assets available not later than tomorrow EOB. We are already late on this. Regarding upload of the "FI-WARE Product Vision" contents to the Wiki, this is still work in progress. I hope that it will get finished by tomorrow EOB if not earlier. 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 16:44:08 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 03 Oct 2011 16:44:08 +0200 Subject: [Fiware-data] Fwd: Re: [Fiware-wpl] IMPORTANT Clarification In-Reply-To: <4E89CA1E.80506@tid.es> References: <4E89CA1E.80506@tid.es> Message-ID: <4E89CA38.7000507@tid.es> FYI, 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: [Fiware-wpl] IMPORTANT Clarification Date: Mon, 03 Oct 2011 16:43:42 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu, "fiware-wpa at lists.fi-ware.eu" 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 Wed Oct 5 09:29:59 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 05 Oct 2011 09:29:59 +0200 Subject: [Fiware-data] Do not edit the FI-WARE Data part of the Backlog on the Wiki Message-ID: <4E8C0777.3020301@tid.es> I'm introducing some changes now ... -- 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:33 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 05 Oct 2011 10:52:33 +0200 Subject: [Fiware-data] Fwd: Instructions on how to proceed with assets soon In-Reply-To: <4E8C1ABC.1020405@tid.es> References: <4E8C1ABC.1020405@tid.es> Message-ID: <4E8C1AD1.7060902@tid.es> -------- Original Message -------- Subject: Instructions on how to proceed with assets soon Date: Wed, 05 Oct 2011 10:52:12 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed Oct 5 12:07:05 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 05 Oct 2011 12:07:05 +0200 Subject: [Fiware-data] Fwd: [Fiware-wpl] 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: <4E8C2C49.30401@tid.es> Hi all, Please find below the detailed instructions on how to proceed regarding description of assets. Note that we have also decided to change the structure based on which references to Wiki pages containing full description of entries in the backlogs will be found. I still see that there are many stuff missing regarding our chapter. Only entries for the BigData and CEP GEs have been introduced in the backlog. Please catch up asap. Regarding description of assets, try to get everything done by Thursday (tomorrow) EOB. Please be aware that info you upload to the Wiki will be publicly available. We will review status on our follow-up confcall this friday. Those who are unable to attend should send an email reporting what the status of their task with respect to uploading info on the Wiki and creation of tickets in the tracker. Don't hesitate to ask if you have any doubt. Best regards, -- juanjo -------- Original Message -------- Subject: [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further Date: Wed, 5 Oct 2011 12:01:31 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu Oct 6 23:11:19 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 06 Oct 2011 23:11:19 +0200 Subject: [Fiware-data] Fwd: Weekly follow-up confcall In-Reply-To: <4E7B4F9D.4030708@tid.es> References: <4E7B4F9D.4030708@tid.es> Message-ID: <4E8E1977.7060006@tid.es> Hi folks, Just a reminder that tomorrow we will have our regular follow-up confcall, from 09:30am - 11:00am We will use Powwownow and webex. Powwownow PIN code is 050662. Dial-in phone numbers attached. Main goal is to review status of homework. We are delayed so I would like to understand what are the barriers you are finding in finishing the homework ... 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 08:51:51 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Oct 2011 08:51:51 +0200 Subject: [Fiware-data] IMPORTANT: Change in dial-in bridge for the follow-up confcall this morning In-Reply-To: References: Message-ID: <4E8EA187.2020905@tid.es> Hi all, We will use the bridge below instead of our regular powwownow facility because this will allow Boris to call from where he is ... Thanks to Guy for providing the bridge !! Talk to you at 09:30am Cheers, -- Juanjo AT&T TeleConference Access Details ___________________________________________________ AT&T TeleConference Access Details... * Passcode:8188850 * USA Toll Free 888-426-6840 Toll 215-861-6239 Tie Line/ITN 650-6840 / 2650-6840 __________________________________________________ In countries with an Att Direct number listed below, participants should dial the Att Direct number first and, when prompted, dial the toll free number listed - Preferred - Country Local Number At&t Direct / Toll Free Angola: 808-000-011 / 1-888-426-6840 Antigua & Barbuba: 1-800-225-5288 / 1-888-426-6840 Argentina: 0800 222 1512 Australia: (0) 2 80318490 1 800 85 4950 Austria: (0) 1 253 0601 0 800 07-0079 Barbados: 1-800-225-5288 / 1-888-426-6840 Belgium: (0) 2 8946410 0 800-3-9022 Bermuda: (0) 2 8946410 1-800-225-5288 / 0 800-3-9022 Brazil: 0-800-888-8288 / 888-426-6840 Brazil: 0-800-890-0288 / 888-426-6840 Bulgaria: 00800-117-4514 Canada: 888-426-6840 Cayman Is: 1-800-225-5288 / 888-426-6840 Chile: 1230-020-0719 China: 4001-201-478 China Netcom Group: 10-800-711-1071 China Telecom South 10-800-110-0996 Colombia: 01-800-5-1-81588 Costa Rica: 0-800-011-4114 / 888-426-6840 Croatia: 0800-777-954 Czech Republic: 2-39016353 800-143-484 Denmark: 32711870 80-717000 Dominican Republic: 1-888-426-6480 Ecuador: 1-999-119 / 888-426-6840 Egypt, Cairo: 2510-0200 / 888-426-6840 Egypt: 02-2510-0200 / 888-426-6840 Finland: 0-9-72519565 0800-9-18357 France: 0-170911580 0800-94-0558 Germany: 0-69-2443-2290 800-000-1018 Ghana: 0191 / 888-426-6840 Greece: 0-80-11-006-7783 Hong Kong: 30713844 800-90-5535 Hungary: 0-1-7789195 06-800-19-306 Iceland: 800-9823 India (AT&T Direct): 000-117 then 888-426-6840 India Fixed: 33-558-811 India Mobile 2 digit city code: 0-XX-33-558-811 India Mobile 3 digit city code: 0-XXX-33-558-81 Indonesia: 001-803-1-006-7783 Ireland: 0-1-5264424 1-800-943-427 Israel: 1-809-417-783 Italy: 0-2-00621263 800-975100 Japan, KDD: 0-3-64042596 00531-11-0086 Japan, C&W: 0066-33-830321 Japan, NTT: 0034-800-900377 Kazakhstan: 8^800-121-4321 / 888-426-6840 Korea (south): 0-2-348-31399 0798-1-1-006-7783 Latvia: 8000 3906 Lithuania: 8-80031299 Luxembourg: 24871280 800-2-7910 Malaysia: 03-6207-4471 1-800-81-5412 Mexico: 01-800-288-2872 888-426-6840 Monaco: 800-93771 Morocco: 00-211-0011 / 888-426-6840 Netherlands: 0-20-7996800 0-800-363-6036 New Zealand: 09-912-7548 0800-442905 Norway: 23162149 800-16771 Panama: 001-888-426-6840 Peru: 0800-77-942 Philippines: 1-800-1-111-0558 Poland: 0-0-800-111-1929 Portugal: 800-7-80880 Romania: 0-800-896910 Russia-Other: 8^495-393-2400 / 888-426-6840 Russia: Moscow: 363-2400 / 888-426-6840 Russia-Other: 8^10-800-110-1011 / 888-426-6840 Saudi Arabia: 800-844-7929 Singapore: 66221594 800-110-1842 Slovakia: 0-800-000-101 / 888-426-6840 Slovenia: 0800-80768 South Africa: 0800-983-687 Spain: 9-1-7878580 900-8-01334 Sweden: 0-8-50515100 0200-12-5807 Switzerland: 0-43-2101240 0800-89-4800 Taiwan: 0-2-77457238 00801-10-4334 Thailand: 001-800-11-006-7783 Turkey: 0811-288-0001 / 888-426-6840 UAE: 0-800-121 / 888-426-6840 UAE (US Base): 0-800-151 / 888-426-6840 UK: 0-20-30596451 0800-368-0638 USA: 215-861-6239 888-426-6840 Uruguay: 0000-411-006-7783 Uzbekistan: 08^641-744-0010 / 888-426-6840 Venezuela: 0 800 102 9535 Vietnam: 1-201-0288 / 888-426-6840 Guy Sharon Manager Event-based Middleware & Solutions Group ________________________________ [cid:part1.08040204.00080706 at tid.es] Event-based Middleware & Solutions phone : +972 4 8296587 mobile : +972 54 6976417 address : IBM R&D Labs in Israel, Haifa University Campus, Mount Carmel, Haifa, 31905, Israel email : guysh at il.ibm.com From: Juanjo Hierro To: Guy Sharon/Haifa/IBM at IBMIL Date: 07/10/2011 07:32 Subject: Are you connecting to the confcall this morning ? ________________________________ Hi Guy, I understood that you would not connect to the confcall this morning because some special holidays in Israel, aren't you ? If I'm wrong, and you will definitively connect ... then I would appreciate if you can provide the bridge today, because Boris is in a place where he cannot connect using powwownow dial-in phone numbers ... Is this feasible ? Otherwise, I will se how I can manage ... though I'm not sure how ... Just let me know. 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2558 bytes Desc: not available URL: From jhierro at tid.es Fri Oct 7 09:41:28 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Oct 2011 09:41:28 +0200 Subject: [Fiware-data] Fwd: [Fiware-wpl] IMPORTANT Considerations regarding tasks to be done. In-Reply-To: <4E8EAB69.6060709@tid.es> References: <4E8EAB69.6060709@tid.es> Message-ID: <4E8EAD28.5040202@tid.es> -------- Original Message -------- Subject: [Fiware-wpl] IMPORTANT Considerations regarding tasks to be done. Date: Fri, 7 Oct 2011 09:34:01 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001..txt URL: From jhierro at tid.es Fri Oct 7 09:41:46 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Oct 2011 09:41:46 +0200 Subject: [Fiware-data] Fwd: [Fiware-wpl] Considerations about Wiki edition In-Reply-To: <4E8EAB71.4040903@tid.es> References: <4E8EAB71.4040903@tid.es> Message-ID: <4E8EAD3A.1030809@tid.es> -------- Original Message -------- Subject: [Fiware-wpl] Considerations about Wiki edition Date: Fri, 7 Oct 2011 09:34:09 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu 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 _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl . ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri Oct 7 09:42:11 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Oct 2011 09:42:11 +0200 Subject: [Fiware-data] Fwd: [Fiware-wpl] The Backlog is not about describing features that assets being adopted as baseline already implement In-Reply-To: <4E8EABF5.5000206@tid.es> References: <4E8EABF5.5000206@tid.es> Message-ID: <4E8EAD53.40709@tid.es> -------- Original Message -------- Subject: [Fiware-wpl] The Backlog is not about describing features that assets being adopted as baseline already implement Date: Fri, 7 Oct 2011 09:36:21 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001..txt URL: From jhierro at tid.es Fri Oct 7 09:42:33 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Oct 2011 09:42:33 +0200 Subject: [Fiware-data] Fwd: [Fiware-wpa] Usage of potentially confidential info in full description of backlog entries (particularly, User-Stories) In-Reply-To: <4E8EAC7C.2000303@tid.es> References: <4E8EAC7C.2000303@tid.es> Message-ID: <4E8EAD69.4070904@tid.es> -------- Original Message -------- Subject: [Fiware-wpa] Usage of potentially confidential info in full description of backlog entries (particularly, User-Stories) Date: Fri, 7 Oct 2011 09:38:36 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001..txt URL: From jhierro at tid.es Fri Oct 7 09:42:52 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Oct 2011 09:42:52 +0200 Subject: [Fiware-data] Fwd: [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: <4E8EAD7C.3060906@tid.es> -------- Original Message -------- Subject: [Fiware-wpa] How are we going to protect some Wiki contents from edition by UC projects Date: Fri, 7 Oct 2011 09:38:56 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu 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-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 Fri Oct 7 11:12:22 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Oct 2011 11:12:22 +0200 Subject: [Fiware-data] Fwd: [FI-PPP AB] FI events during FI-Week in Poznan In-Reply-To: References: Message-ID: <4E8EC276.2020406@tid.es> -------- Original Message -------- Subject: [FI-PPP AB] FI events during FI-Week in Poznan Date: Fri, 7 Oct 2011 10:16:41 +0200 From: Ana Garcia To: AB at fi-ppp.eu , SB at fi-ppp.eu , dwg at fi-ppp.eu CC: Petra Turkama2 Dear FI-PPP members of the SB, AB and DWG, Please find attached an overview of what will take place during the FI-Week in Poznan. We kindly ask you to circulate this within all your project partners so all the FIPPP community can get this information. Best regards, On behalf of the CONCORD project, Ana Garc?a Project Manager European Network of Living Labs ENoLL Office | Pleinlaan 9 | B 1050 Brussels | Belgium Mob:+32 470 193 118 | ana.garcia at enoll.org http://www.openlivinglabs.eu http://www.ibbt.be/en/disclaimer-and-privacy ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: unknown sender Subject: Future Internet Week in Poznan 24-28 October, registration open Date: Wed, 05 Oct 2011 12:13:57 +0200 Size: 439585 URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001..txt URL: From jhierro at tid.es Fri Oct 7 11:19:13 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Oct 2011 11:19:13 +0200 Subject: [Fiware-data] Fwd: Re: [Fiware-wpl] [Fiware-wpa] How are we going to protect some Wiki contents from edition by UC projects In-Reply-To: <4E8EC3F4.4050308@tid.es> References: <4E8EC3F4.4050308@tid.es> Message-ID: <4E8EC411.1020404@tid.es> -------- Original Message -------- Subject: Re: [Fiware-wpl] [Fiware-wpa] How are we going to protect some Wiki contents from edition by UC projects Date: Fri, 7 Oct 2011 11:18:44 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu 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 _______________________________________________ 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 11 18:29:31 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 11 Oct 2011 18:29:31 +0200 Subject: [Fiware-data] Fwd: Minutes of joint WPL/WPA follow-up confcall In-Reply-To: <4E946ED3.2060304@tid.es> References: <4E946ED3.2060304@tid.es> Message-ID: <4E946EEB.8010003@tid.es> FYI, -- Juanjo -------- Original Message -------- Subject: Minutes of joint WPL/WPA follow-up confcall Date: Tue, 11 Oct 2011 18:29:07 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu 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 Thu Oct 13 19:19:07 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 13 Oct 2011 19:19:07 +0200 Subject: [Fiware-data] FANO: You issued tickets linked to Pub/Sub in the wrong tracker Message-ID: <4E971D8B.2030702@tid.es> Dear Fano, I'm afraid that you have created the tickets linked to Epics/User-Stories linked to semantic support functionality associated to the Pub/Sub Broker GE in the wrong tracker !! You had to create them in the "Backlog Management" tracker of the "FI-WARE Data" chapter project in FusionForge. Not in the "Theme/Epic/Feature requests" tracker in the "FI-WARE" project !! This last tracker is the one where UC projects should submit their requests for additional entries in the FI-WARE Backlogs .... Please fix this ASAP. I copy the rest of the team to make sure we are on the same page ! 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 Fri Oct 14 04:11:17 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 14 Oct 2011 04:11:17 +0200 Subject: [Fiware-data] Follow-up confcall Message-ID: <4E979A45.9010102@tid.es> Hi, I believe we don't need to have the weekly follow-up confcall this morning. So we can skip it. What is required is that all take responsability of his homework and try to get it finished (I believe homework is clear and the status is clearly illustrated on the wiki and the tracker). I will send an email later today or along the weekend with my analysis on the status and a set of urgent Action Points to be done (related to identified pending work or things to be fixed) 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 boris.moltchanov at telecomitalia.it Wed Oct 19 12:08:01 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Wed, 19 Oct 2011 12:08:01 +0200 Subject: [Fiware-data] Follow-up confcall In-Reply-To: <4E979A45.9010102@tid.es> References: <4E979A45.9010102@tid.es> Message-ID: Dear All, I will be missing the (eventual, if not cancelled) call this Friday (travelling). However, for update, TI has already inserted 3 GE contributions (P/S, MA and SA) into the FI-WARE wiki and accomplished backlog insertion in FI-WARE track as well, for your eventual (cross-)check. We (Ti) might add something also to Location GE, however I remember it is under Thales lead and there is no yet contribution to stick with. In case of any related matter please contact me via email. Best Regards, Boris -----Original Message----- From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Friday, October 14, 2011 4:11 AM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Follow-up confcall Hi, I believe we don't need to have the weekly follow-up confcall this morning. So we can skip it. What is required is that all take responsability of his homework and try to get it finished (I believe homework is clear and the status is clearly illustrated on the wiki and the tracker). I will send an email later today or along the weekend with my analysis on the status and a set of urgent Action Points to be done (related to identified pending work or things to be fixed) 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-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data 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 remi.challamel at thalesaleniaspace.com Wed Oct 19 16:42:50 2011 From: remi.challamel at thalesaleniaspace.com (remi.challamel at thalesaleniaspace.com) Date: Wed, 19 Oct 2011 16:42:50 +0200 Subject: [Fiware-data] =?iso-8859-1?q?R=E9f=2E_=3A_Re=3A__Follow-up_confca?= =?iso-8859-1?q?ll?= In-Reply-To: Message-ID: <16767_1319035348_4E9EE1D4_16767_2317_1_OF295AA6FA.B5CF49B8-ONC125792E.0050BF59-C125792E.0050D375@thalesaleniaspace.com> Dear Boris I will take care of providing contribution for the location GE before end of the week. Thanks. Best regards |---------+------------------------------------> | | Moltchanov Boris | | | | | | Envoy? par : | | | fiware-data-bounces at lists| | | .fi-ware.eu | | | | | | | | | 19/10/2011 12:08 | |---------+------------------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | Pour : Juanjo Hierro | | "fiware-data at lists.fi-ware.eu" | | cc : | | Objet : Re: [Fiware-data] Follow-up confcall | >------------------------------------------------------------------------------------------------------------------------------| Dear All, I will be missing the (eventual, if not cancelled) call this Friday (travelling). However, for update, TI has already inserted 3 GE contributions (P/S, MA and SA) into the FI-WARE wiki and accomplished backlog insertion in FI-WARE track as well, for your eventual (cross-)check. We (Ti) might add something also to Location GE, however I remember it is under Thales lead and there is no yet contribution to stick with. In case of any related matter please contact me via email. Best Regards, Boris -----Original Message----- From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Friday, October 14, 2011 4:11 AM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Follow-up confcall Hi, I believe we don't need to have the weekly follow-up confcall this morning. So we can skip it. What is required is that all take responsability of his homework and try to get it finished (I believe homework is clear and the status is clearly illustrated on the wiki and the tracker). I will send an email later today or along the weekend with my analysis on the status and a set of urgent Action Points to be done (related to identified pending work or things to be fixed) 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-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data 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. _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data Meilleures salutations/Cordiali saluti/Best regards Sales&Marketing -- Project Manager Tel : fixed: +33 5 34 35 68 21 - cell: +33 6 74 33 82 58 / Fax : +33 5 34 35 43 39 Porte : P501 / E-Mail : remi.challamel at thalesaleniaspace.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: graycol.gif Type: image/gif Size: 105 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ecblank.gif Type: image/gif Size: 45 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pic17421.gif Type: image/gif Size: 1255 bytes Desc: not available URL: From jhierro at tid.es Fri Oct 21 02:00:05 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 21 Oct 2011 02:00:05 +0200 Subject: [Fiware-data] Follow-up confcall Message-ID: <4EA0B605.3020806@tid.es> Hi all, I believe that we can again skip the follow-up confcall this morning. I will review the status and produce an email with APs to be done to tackle points I find are still pending. In addition, I'll take a look at next steps and propose a plan how to organize things. I wonder how many of you are in Poznan next week. I would kindly ask you to reply to this message in the event you plan to be there. It could make sense that we meet there if there is enough quorum. 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 federico.alvarez at upm.es Fri Oct 21 09:03:37 2011 From: federico.alvarez at upm.es (=?ISO-8859-1?Q?Federico_=C1lvarez?=) Date: Fri, 21 Oct 2011 09:03:37 +0200 Subject: [Fiware-data] Follow-up confcall In-Reply-To: <4EA0B605.3020806@tid.es> References: <4EA0B605.3020806@tid.es> Message-ID: <4EA11949.1080005@upm.es> Hello Juanjo, I will be in Poznan from Monday afternoon until Thursday morning. Kind regards, Federico El 21/10/2011 2:00, Juanjo Hierro escribi?: > Hi all, > > I believe that we can again skip the follow-up confcall this morning. > > I will review the status and produce an email with APs to be done to > tackle points I find are still pending. In addition, I'll take a look > at next steps and propose a plan how to organize things. > > I wonder how many of you are in Poznan next week. I would kindly > ask you to reply to this message in the event you plan to be there. It > could make sense that we meet there if there is enough quorum. > > 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-data mailing list > Fiware-data at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-data From GUYSH at il.ibm.com Fri Oct 21 14:32:39 2011 From: GUYSH at il.ibm.com (Guy Sharon) Date: Fri, 21 Oct 2011 14:32:39 +0200 Subject: [Fiware-data] Follow-up confcall In-Reply-To: <4EA0B605.3020806@tid.es> References: <4EA0B605.3020806@tid.es> Message-ID: I will be in Poznan Tuesday evening until Thursday evening Guy Sharon Manager Event-based Middleware & Solutions Group Event-based Middleware & Solutions phone : +972 4 8296587 mobile : +972 54 6976417 address : IBM R&D Labs in Israel, Haifa University Campus, Mount Carmel, Haifa, 31905, Israel email : guysh at il.ibm.com From: Juanjo Hierro To: "fiware-data at lists.fi-ware.eu" Date: 21/10/2011 03:00 Subject: [Fiware-data] Follow-up confcall Sent by: fiware-data-bounces at lists.fi-ware.eu Hi all, I believe that we can again skip the follow-up confcall this morning. I will review the status and produce an email with APs to be done to tackle points I find are still pending. In addition, I'll take a look at next steps and propose a plan how to organize things. I wonder how many of you are in Poznan next week. I would kindly ask you to reply to this message in the event you plan to be there. It could make sense that we meet there if there is enough quorum. 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-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2558 bytes Desc: not available URL: