From jhierro at tid.es Fri Sep 2 07:38:27 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 02 Sep 2011 07:38:27 +0200 Subject: [Fiware-wpl] Fwd: Plenary WPLs/WPAs confcall and next steps In-Reply-To: <4E567165.9020401@tid.es> References: <4E567165.9020401@tid.es> Message-ID: <4E606BD3.3020306@tid.es> Hi, This is a reminder of the confcall we are going to have this morning, starting at 10:00am CET. Thomas will circulate dial-in details later. Cheers, -- Juanjo -------- Original Message -------- Subject: Plenary WPLs/WPAs confcall and next steps Date: Thu, 25 Aug 2011 17:59:33 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, First thing I wanna say is that I have just come back from holidays. I hope you have already enjoyed yours ! Now that I came back, and the August period is almost finished, we will resume our follow-ups. We will start with a plenary confcall involving all WPLs/WPAs. Then, we will resume our WP-specific follow-up confcalls but will go for trying to have them bi-weekly. The plenary confcall would take place on Friday September 2nd at 10:00am CET. Please pencil this on your agendas. Dial-in details to be provided later. There, Thomas and me will share with you the process (and supporting tools) we will put in place for managing: a) Communication with UC projects regarding doubts, clarifications and any other sort of Technical Support. As an example, clarification of parts of the FI-WARE High-level Description (Product Vision) document b) creation and lifecycle of entries in the FI-WARE backlog Therefore, it is crucial that you attend this confcall. We will not only explain you the process but rather show you the tools we are configuring for this purpose. Then you should start using them to feed the FI-WARE backlog with the entries you are supposed to be working on these days (I remind you that deadline for first list of EPICs was planned for end of August, check my previous email on the matter) An early presentation of both the process and the tools has been made today to the rest of members of the FI-PPP Architecture Board and has been rather welcomed. Still we have to fine-tune a couple of things but we should have everything ready (at least regarding definition of the process) for our plenary confcall. Then we would collect your feedback and do any additional-final fine tuning until a presentation we have committed to make to UC project by September 7-8. As an advanced notice, prior to official distribution of the minutes of the AB meeting that took place today, we can tell you that UC projects are mostly in the process of finishing the requirements of their end users and are now in the process of performing the necessary analysis of those requirements as to be able to produce the first requests for entries to the FI-WARE backlog by end of September on the average (one project mentioned they will try to start providing input by mid September while some would be doing early in October, but most of them mentioned "end of September"). This matches pretty well with our current planning so that we should be able to endup with a collection of FI-WARE backlog entries by the end of September (part of it being generated by us on our own, part coming from the UC projects). Regarding the bi-weekly follow-up confcalls, we will keep them on Mondays and Fridays because this will allow us to resume weekly confcalls whenever is needed (hopefully not that frequently). The next three bi-weekly follow-up confcalls will be scheduled as follows: * for those on Mondays: September 5th, September 26th, October 10th * for those on Fridays: September 2nd, September 23th, October 7th Main topic for the first of these list of bi-weekly follow-up confcall will be to revise the status on collection of the EPICs related to your chapter as well as discussion on assets adopted as baseline for GEs in your chapter and issues about their integration. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From thomas.michael.bohnert at sap.com Fri Sep 2 09:06:51 2011 From: thomas.michael.bohnert at sap.com (Bohnert, Thomas Michael) Date: Fri, 2 Sep 2011 09:06:51 +0200 Subject: [Fiware-wpl] [Fiware-wpa] Fwd: Plenary WPLs/WPAs confcall and next steps In-Reply-To: <4E606BD3.3020306@tid.es> References: <4E567165.9020401@tid.es> <4E606BD3.3020306@tid.es> Message-ID: <771C9B001456D64783596DDC3801C6EA28163279FF@DEWDFECCR09.wdf.sap.corp> Hello, You have been invited to join Thomas Michael Bohnert in a Web Conference using SAP CONNECT. To join the meeting: https://sap.emea.pgiconnect.com/I056156 Participant Passcode: 664 291 2792 Argentina: 0800 444 1292 tel:08004441292x6642912792# Australia, Melbourne: +61 3 8687 0624 tel:+61386870624x6642912792# Australia, Sydney: +61 2 9009 0688 tel:+61290090688x6642912792# Australia: 1 800 651 017 tel:1800651017x6642912792# Austria, Vienna: +43 1 2530 21750 tel:+431253021750x6642912792# Austria: 0 800 006 088 tel:0800006088x6642912792# Bahrain, Manama: +973 1619 9392 tel:+97316199392x6642912792# Bahrain: 8000 4811 tel:80004811x6642912792# Belgium, Brussels: +32 2 404 0657 tel:+3224040657x6642912792# Belgium: 0800 39675 tel:080039675x6642912792# Botswana: 002 698 003 001 802 tel:002698003001802x6642912792# Brazil, Porto Alegre: +55 51 4063 8328 tel:+555140638328x6642912792# Brazil, Rio de Janeiro: +55 21 4063 5267 tel:+552140635267x6642912792# Brazil, Sao Paulo: +55 11 3163 0498 tel:+551131630498x6642912792# Bulgaria, Sofia: +359 2 491 7542 tel:+35924917542x6642912792# Bulgaria: 00 800 118 4451 tel:008001184451x6642912792# Canada, Montreal: +1 514 669 5883 tel:+15146695883x6642912792# Canada, Toronto: +1 416 915 3225 tel:+14169153225x6642912792# Canada: 1 877 252 4916 tel:18772524916x6642912792# Chile, Santiago: +56 2 599 4973 tel:+5625994973x6642912792# Chile: 123 0020 6704 tel:12300206704x6642912792# China, Beijing: +86 10 5904 5002 tel:+861059045002x6642912792# China, Northern Region: 10 800 650 0630 tel:108006500630x6642912792# China, Southern Region: 10 800 265 2601 tel:108002652601x6642912792# China: +400 120 0519 tel:+4001200519x6642912792# Colombia: 01 800 518 1236 tel:018005181236x6642912792# Croatia: 0800 222 228 tel:0800222228x6642912792# Cyprus, Nicosia: +357 2200 7933 tel:+35722007933x6642912792# Cyprus: 800 964 63 tel:80096463x6642912792# Czech Republic, Prague: +420 228 882 890 tel:+420228882890x6642912792# Czech Republic: 800 701 387 tel:800701387x6642912792# Denmark, Copenhagen: +45 32 71 16 49 tel:+4532711649x6642912792# Denmark: 80 701 624 tel:80701624x6642912792# Dominican Republic: 1 888 751 4814 tel:18887514814x6642912792# Estonia, Tallinn: +372 622 6444 tel:+3726226444x6642912792# Estonia: 8000 111 358 tel:8000111358x6642912792# Finland, Helsinki: +358 9 2310 1631 tel:+358923101631x6642912792# Finland: 0 800 770 120 tel:0800770120x6642912792# France, Paris: +33 1 70 70 17 77 tel:+33170701777x6642912792# France: 0800 946 522 tel:0800946522x6642912792# France: 0811 657 737 tel:0811657737x6642912792# Germany, Frankfurt: +49 69 2222 10764 tel:+4969222210764x6642912792# Germany, Munich: +49 89 7104 24682 tel:+4989710424682x6642912792# Germany: 0800 588 9331 tel:08005889331x6642912792# Greece, Athens: +30 21 1181 3805 tel:+302111813805x6642912792# Greece: 00800 128 573 tel:00800128573x6642912792# Hong Kong: +852 3051 2732 tel:+85230512732x6642912792# Hong Kong: 800 905 843 tel:800905843x6642912792# Hungary, Budapest: +36 1 778 9215 tel:+3617789215x6642912792# Hungary: 068 001 9390 tel:0680019390x6642912792# Iceland: 800 9901 tel:8009901x6642912792# India, Bangalore: +91 80 6127 5055 tel:+918061275055x6642912792# India, Delhi: +91 11 6641 1356 tel:+911166411356x6642912792# India, Mumbai: +91 22 6150 1743 tel:+912261501743x6642912792# India: 000 800 1007 702 tel:0008001007702x6642912792# Indonesia: 001 803 657 916 tel:001803657916x6642912792# Ireland, Dublin: +353 1 247 6192 tel:+35312476192x6642912792# Ireland: 1 800 937 869 tel:1800937869x6642912792# Ireland: 1890 907 125 tel:1890907125x6642912792# Israel, Tel Aviv: +972 3 763 0750 tel:+97237630750x6642912792# Israel: 1809 212 927 tel:1809212927x6642912792# Italy, Milan: +39 02 3600 9839 tel:+390236009839x6642912792# Italy, Rome: +39 06 4523 6623 tel:+390645236623x6642912792# Italy: 800 145 988 tel:800145988x6642912792# Japan, Osaka: +81 6 4560 2101 tel:+81645602101x6642912792# Japan, Tokyo: +81 3 4560 1261 tel:+81345601261x6642912792# Japan: 0120 639 800 tel:0120639800x6642912792# Jordan: 800 22813 tel:80022813x6642912792# Kazakhstan: 8800 333 4239 tel:88003334239x6642912792# Latvia, Riga: +371 6778 2556 tel:+37167782556x6642912792# Latvia: 8000 4247 tel:80004247x6642912792# Lithuania, Vilnius: +370 5205 5165 tel:+37052055165x6642912792# Lithuania: 8800 31308 tel:880031308x6642912792# Luxembourg: +352 2487 1454 tel:+35224871454x6642912792# Luxembourg: 800 27071 tel:80027071x6642912792# Malaysia,Kuala Lumpur: +60 3 7723 7221 tel:+60377237221x6642912792# Malaysia: 1 800 806 547 tel:1800806547x6642912792# Malta: 800 62208 tel:80062208x6642912792# Mauritius: 802 033 0006 tel:8020330006x6642912792# Mexico, Mexico City: +52 55 1207 7362 tel:+525512077362x6642912792# Mexico: 001 800 514 8609 tel:0018005148609x6642912792# Netherlands, Amsterdam: +31 20 716 8291 tel:+31207168291x6642912792# Netherlands: 0800 265 8462 tel:08002658462x6642912792# New Zealand, Auckland: +64 9 929 1760 tel:+6499291760x6642912792# New Zealand: 0800 885 018 tel:0800885018x6642912792# Norway, Oslo: +47 21 50 27 61 tel:+4721502761x6642912792# Norway: 800 510 67 tel:80051067x6642912792# Oman: 800 73655 tel:80073655x6642912792# Pakistan: 008 009 004 4138 tel:0080090044138x6642912792# Panama: 00 800 226 9817 tel:008002269817x6642912792# Peru: 0800 54 762 tel:080054762x6642912792# Philippines: 1 800 1651 0726 tel:180016510726x6642912792# Poland, Warsaw: +48 22 212 0699 tel:+48222120699x6642912792# Poland: 00 800 121 3995 tel:008001213995x6642912792# Portugal, Lisbon: +351 21 781 0275 tel:+351217810275x6642912792# Portugal: 800 784 425 tel:800784425x6642912792# Puerto Rico : 1 855 693 8763 tel:18556938763x6642912792# Romania, Bucharest: +40 21 529 3917 tel:+40215293917x6642912792# Romania: 0800 895 807 tel:0800895807x6642912792# Russia, Moscow: +7 495 213 17 63 tel:+74952131763x6642912792# Russia: 810 800 2106 2012 tel:81080021062012x6642912792# Saudi Arabia: 800 844 4276 tel:8008444276x6642912792# Singapore: +65 6654 9828 tel:+6566549828x6642912792# Singapore: 800 186 5015 tel:8001865015x6642912792# Slovakia, Bratislava: +421 2 3300 2610 tel:+421233002610x6642912792# Slovakia: 0800 001 825 tel:0800001825x6642912792# Slovenia, Ljubljana: +386 1 888 8261 tel:+38618888261x6642912792# Slovenia: 0800 80923 tel:080080923x6642912792# South Africa,Johannesberg : +27 11 019 7009 tel:+27110197009x6642912792# South Africa: 0800 984 011 tel:0800984011x6642912792# South Korea, Seoul: +82 2 3483 1901 tel:+82234831901x6642912792# South Korea: 007 986 517 503 tel:007986517503x6642912792# Spain, Barcelona: +34 93 800 0782 tel:+34938000782x6642912792# Spain, Madrid: +34 91 769 9443 tel:+34917699443x6642912792# Spain: 800 600 279 tel:800600279x6642912792# Sweden, Stockholm: +46 8 5033 6514 tel:+46850336514x6642912792# Sweden: 0200 883 436 tel:0200883436x6642912792# Switzerland, Geneva: +41 22 592 7995 tel:+41225927995x6642912792# Switzerland, Zurich: +41 43 456 9248 tel:+41434569248x6642912792# Switzerland: 0800 740 352 tel:0800740352x6642912792# Taiwan, Taipei: +886 2 2656 7307 tel:+886226567307x6642912792# Taiwan: 00 806 651 935 tel:00806651935x6642912792# Thailand: 001 800 658 151 tel:001800658151x6642912792# Turkey: 00800 448 825 462 tel:00800448825462x6642912792# UAE: 8000 444 1726 tel:80004441726x6642912792# UK, Belfast: +44 28 9595 0013 tel:+442895950013x6642912792# UK, Edinburgh: +44 13 1460 1125 tel:+441314601125x6642912792# UK, London: +44 20 3364 5639 tel:+442033645639x6642912792# UK, Reading: +44 11 8990 3053 tel:+441189903053x6642912792# UK: 0800 368 0635 tel:08003680635x6642912792# UK: 0845 351 2778 tel:08453512778x6642912792# Ukraine: 0800 500 254 tel:0800500254x6642912792# Uruguay: 0004 019 0509 tel:00040190509x6642912792# US and Canada: 1-866-312-7353 tel:18663127353x6642912792# US and Canada: 1-720-897-6637 tel:17208976637x6642912792# US and Canada: 1-646-434-0499 tel:16464340499x6642912792# US and Canada: 1-484-427-2544 tel:14844272544x6642912792# Venezuela: 0 800 100 8510 tel:08001008510x6642912792# Vietnam: 120 651 66 tel:12065166x6642912792# From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Freitag, 2. September 2011 07:38 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Fwd: Plenary WPLs/WPAs confcall and next steps Hi, This is a reminder of the confcall we are going to have this morning, starting at 10:00am CET. Thomas will circulate dial-in details later. Cheers, -- Juanjo -------- Original Message -------- Subject: Plenary WPLs/WPAs confcall and next steps Date: Thu, 25 Aug 2011 17:59:33 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, First thing I wanna say is that I have just come back from holidays. I hope you have already enjoyed yours ! Now that I came back, and the August period is almost finished, we will resume our follow-ups. We will start with a plenary confcall involving all WPLs/WPAs. Then, we will resume our WP-specific follow-up confcalls but will go for trying to have them bi-weekly. The plenary confcall would take place on Friday September 2nd at 10:00am CET. Please pencil this on your agendas. Dial-in details to be provided later. There, Thomas and me will share with you the process (and supporting tools) we will put in place for managing: a) Communication with UC projects regarding doubts, clarifications and any other sort of Technical Support. As an example, clarification of parts of the FI-WARE High-level Description (Product Vision) document b) creation and lifecycle of entries in the FI-WARE backlog Therefore, it is crucial that you attend this confcall. We will not only explain you the process but rather show you the tools we are configuring for this purpose. Then you should start using them to feed the FI-WARE backlog with the entries you are supposed to be working on these days (I remind you that deadline for first list of EPICs was planned for end of August, check my previous email on the matter) An early presentation of both the process and the tools has been made today to the rest of members of the FI-PPP Architecture Board and has been rather welcomed. Still we have to fine-tune a couple of things but we should have everything ready (at least regarding definition of the process) for our plenary confcall. Then we would collect your feedback and do any additional-final fine tuning until a presentation we have committed to make to UC project by September 7-8. As an advanced notice, prior to official distribution of the minutes of the AB meeting that took place today, we can tell you that UC projects are mostly in the process of finishing the requirements of their end users and are now in the process of performing the necessary analysis of those requirements as to be able to produce the first requests for entries to the FI-WARE backlog by end of September on the average (one project mentioned they will try to start providing input by mid September while some would be doing early in October, but most of them mentioned "end of September"). This matches pretty well with our current planning so that we should be able to endup with a collection of FI-WARE backlog entries by the end of September (part of it being generated by us on our own, part coming from the UC projects). Regarding the bi-weekly follow-up confcalls, we will keep them on Mondays and Fridays because this will allow us to resume weekly confcalls whenever is needed (hopefully not that frequently). The next three bi-weekly follow-up confcalls will be scheduled as follows: * for those on Mondays: September 5th, September 26th, October 10th * for those on Fridays: September 2nd, September 23th, October 7th Main topic for the first of these list of bi-weekly follow-up confcall will be to revise the status on collection of the EPICs related to your chapter as well as discussion on assets adopted as baseline for GEs in your chapter and issues about their integration. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Sep 5 01:21:59 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 05 Sep 2011 01:21:59 +0200 Subject: [Fiware-wpl] Minutes of last WPL/WPA plenary follow-up confcall Message-ID: <4E640817.7020809@tid.es> Hi all, Please find below the minutes of our follow-up confcall last Friday. Any comment or feedback is welcome. Cheers, -- Juanjo Attendees: Laurant (NSN), Denes (NSN), Thierry (Orange), Pier (TI), Maarten (Atos), Juan (Atos), Torsten (SAP), TMB (SAP), Juanjo (TID) Goal: Present the tool and process that has been identified for managing requests on technical support (doubts, feedback) to UC projects (and external world) as well as for managing creation and lifecycle of entries in the uncategorized and FI-WARE backlog. Background: A tool was required for interaction / management of requests to FI-WARE by any external organization (clarification on doubts, delivery of feedback, to the FI-WARE Product Vision and any other topic. A tool was also rerquired for implementing / supporting the FI-WARE Agile approach. AgileFant was initially chosen, proved of little added value and was thus dropped. The current approach is a slim combination of the tracker+wiki approach proposed / implemented so far. Demo: Thomas made a demo of the process/tools to be put in place regarding: + Global Technical Support + Request for entries to the FI-WARE Backlog A tracker tool has been defined for both so that for any request (technical support or for entries to be added in the backlog) a ticket is created. Trackers in FusionForge allow to manage the lifecycle of a ticket and create tasks a given points in time. Thomas elaborated on both trackers, starting first with the one dealing with Global Technical Support. Questions during demo about Global Technical Support: * Who should receive the automatic email once a ticket has been opened ? After some discussion, we agreed to go for a centralized approach in a first approach (tickets are assigned to caretakers by Admin users that will be Juanjo, Thomas and another person from TID who will join to support management activities in the project) and then decentralize (caretakers can assign/re-assign tickets themselves) if we find out the approach doesn't scale * Concern about combining task management tool and tracker instead of just a tracker was raised by Torsten. Why isn't a ticket to be handled by each WP created in their tracker system once a ticket for Global Technical Support is created ? Answer: that is actually the approach we would recommend for handling requests for features in the FI-WARE Backlog (see below), but we didn't want to go so far regarding handling of Global Technical Support requests. It would be up to the WPLs to decide whether handling of the tasks assigned to them should lead to creation of a ticket on their own WP tracker or not. Agreed to follow this approach for the time being. If it happens that all tickets on the Global Technical Support tracker lead to creation of a ticket in a tracker defined by WP project, then we will reconsider and check how to automate the ticket transference. Then a demo about management of requests for entries in the FI-WARE Backlog was made. A tracker linked to the FI-WARE project in FusionForge will be configured that will deal with request for features regarding Platform Enablers (still uncategorized). UC projects will be allowed to create tickets on that tracker and these tickets will be assigned to caretakers (WPLs/WPAs) by Juanjo, Thomas or the TID person mentioned before. Also a task to be carried out by caretakers will be linked to the ticket which will consist in discussing with the UC projects whatever is needed to first determine whether the feature fit within the scope of FI-WARE or not (i.e., should be considered as a feature of a "Common Specific Enabler" as opposed to "Generic Enabler"). If it is agreed that it may be linked to a FI-WARE GE, a ticket should be created in the corresponding FI-WARE Chapter's backlog (to be setup at the corresponding chapter project in FusionForge). It was pointed out that there will be several trackers. Backlogs will map to Trackers and Backlog entries will map to tickets on the corresponding trackers. Linked tasks may well map to tasks in Agile methodologies. There will be one for "uncategorized platform enablers" which will be the one where requests will be gathered and analyzed (request may come from UC projects as well as any other community) . On the other hand, there will be a tracker for the backlog linked to each of the FI-WARE chapters. One of the advantages to have separate trackers/backlog linked to "uncategorized platform enablers" and to "FI-WARE Chapters" is that we can assign different roles and privileges for UC projects in one case and the other. Thus, for instance, UC projects will be able to create tickets on the tracker helping to handle requests for entries in the FI-WARE Backlog (that is, the "uncategorized platform enablers" backlog) but not directly in the FI-WARE backlog(s) itself. The WPLs/WPAs present at the confcall provided a positive feedback on the solution that was presented during the confcall. So no objection to follow with the plan to implement the proposed processes and tools was raised. Thomas and Juanjo expect to get a final configuration setup during the week starting on September 5 and be able to make a general presentation to all members of FI-WARE during the plenary meeting in Turin. ________________________________ 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: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Tue Sep 6 09:13:46 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 06 Sep 2011 09:13:46 +0200 Subject: [Fiware-wpl] Fwd: FI-WARE: Doodle poll for first review meeting In-Reply-To: <7BACCBA4EE7D3946BF23FB79D9FD2E613CC47A@S-DC-EXM11.net1.cec.eu.int> References: <" <7BACCBA4EE7D3946BF23FB79D9FD2E613CC47A"@S-DC-EXM11.net1.cec.eu.int> Message-ID: <4E65C82A.7030109@tid.es> Hi all, Our PO wish to setup the date for the first review of the project, which intends to review the results of the first six months of the project. He has setup a doodle trying to find the right dates for such a review. In principle, Arian wish to see just a limited number of participants. IMHO, it should be limited to: * The Project Coordinator and FI-WARE's representative in the FI-PPP Steering Board: Jos? * The Project Technical Manager: me * The representatives of FI-WARE in the FI-PPP: Thomas and me (already in) * Working Package Leaders * Working Package Architects So unless anyone objects or wish to amend, that would be the plan. Therefore, those designated to attend are requested to cast their vote in the doodle poll set by Arian. Best regards, -- Juanjo -------- Original Message -------- Subject: FI-WARE: Doodle poll for first review meeting Date: Tue, 6 Sep 2011 08:38:49 +0200 From: Arian.ZWEGERS at ec.europa.eu To: JOSE JIMENEZ DELGADO , JUAN JOSE HIERRO SUREDA , "rdifrancesco at ymail.com" , "dgr at whitestein.com" , "msli at icfocus.co.uk" CC: Federica.TAGLIANI at ec.europa.eu , INFSO-ICT-285248 at ec.europa.eu , Annalisa.Bogliolo at ec.europa.eu Dear all, Please find below a link to a Doodle poll to determine the first review meeting. Please complete before Sept 13. @Jose, Juanjo: please distribute to those FI-WARE members you think should attend. Review meetings should not be an opportunity for participants to have a field day. Best regards, Arian. -----Original Message----- From: Doodle [mailto:mailer at doodle.com] Sent: Tuesday, September 06, 2011 8:29 AM To: ZWEGERS Arian (INFSO) Subject: Doodle: Link for poll "FI-WARE review 1 meeting" You have initiated a poll "FI-WARE review 1 meeting" at Doodle. The link to your poll is: http://doodle.com/cx3btby438pz6dmu Share this link with all those who should cast their votes. Do not forget to cast your vote, too. (If you did not initiate this poll, somebody must accidentally have used your e-mail address; simply ignore this e-mail, 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue Sep 6 09:50:15 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 06 Sep 2011 09:50:15 +0200 Subject: [Fiware-wpl] About First official review of the FI-WARE project In-Reply-To: <7BACCBA4EE7D3946BF23FB79D9FD2E613CC47C@S-DC-EXM11.net1.cec.eu.int> References: <" <7BACCBA4EE7D3946BF23FB79D9FD2E613CC47C"@S-DC-EXM11.net1.cec.eu.int> Message-ID: <4E65D0B7.7030404@tid.es> Hi all, This message from our PO should clarify the scope and goals of the review that will take place. I was also confirmed that the review will take just one day (I understand full day, starting at 09:00am, probably leaving not earlier than 17:00) Best regards, -- Juanjo -------- Original Message -------- Subject: RE: FI-WARE: Doodle poll for first review meeting Date: Tue, 6 Sep 2011 09:36:07 +0200 From: Arian.ZWEGERS at ec.europa.eu To: JUAN JOSE HIERRO SUREDA CC: JOSE JIMENEZ DELGADO , "Federica.TAGLIANI at ec.europa.eu" , "INFSO-ICT-285248 at ec.europa.eu" , "Annalisa.Bogliolo at ec.europa.eu" Dear Juanjo, This is what the official invitation says: "The objectives of the review, in particular, are to establish: - the degree of fulfilment of the project work plan for the relevant period and of the related deliverables; - the continued relevance of the objectives and breakthrough potential with respect to the scientific and industrial state of the art; - the resources planned and utilised in relation to the achieved progress, in a manner consistent with the principles of economy, efficiency and effectiveness; - the management procedures and methods of the project; - the beneficiaries? contributions and integration within the project; - the expected potential impact in economic, competition and social terms, and the beneficiaries' plan for the use and dissemination of foreground. " Deliverables are just one measure of progress. There should be progress without deliverables, and obviously the reviewers want to see that. This does not mean that every WP should present in detail what progress it has made. Best regards, Arian. -----Original Message----- From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Tuesday, September 06, 2011 9:09 AM To: ZWEGERS Arian (INFSO) Cc: JOSE JIMENEZ DELGADO; TAGLIANI Federica (INFSO); INFSO-ICT-285248; BOGLIOLO Annalisa (INFSO); jhierro >> "Juan J. Hierro" Subject: Re: FI-WARE: Doodle poll for first review meeting Dear Arian, My understanding is that goals of this first review would be to formally review of the results of the first six months of the project. Review of progress regarding deliverables beyond month 6 is outside scope. Is this correct ? Thanks, -- Juanjo On 06/09/11 08:38, Arian.ZWEGERS at ec.europa.eu wrote: > Dear all, > > Please find below a link to a Doodle poll to determine the first review meeting. > > Please complete before Sept 13. > > @Jose, Juanjo: please distribute to those FI-WARE members you think should attend. Review meetings should not be an opportunity for participants to have a field day. > > Best regards, > Arian. > > -----Original Message----- > From: Doodle [mailto:mailer at doodle.com] > Sent: Tuesday, September 06, 2011 8:29 AM > To: ZWEGERS Arian (INFSO) > Subject: Doodle: Link for poll "FI-WARE review 1 meeting" > > You have initiated a poll "FI-WARE review 1 meeting" at Doodle. The link to your poll is: > > http://doodle.com/cx3btby438pz6dmu > > Share this link with all those who should cast their votes. Do not forget to cast your vote, too. > (If you did not initiate this poll, somebody must accidentally have used your e-mail address; simply ignore this e-mail, 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 -- 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 juan.bareno at atosresearch.eu Tue Sep 6 11:20:38 2011 From: juan.bareno at atosresearch.eu (=?iso-8859-1?Q?Juan_Bare=F1o_Guerenabarrena?=) Date: Tue, 6 Sep 2011 11:20:38 +0200 Subject: [Fiware-wpl] 2011-09-02 FI-WARE Standardization_Kickoff_v0.1.pptx Message-ID: <06BEE166C7F75A47B257036739E29BF30298A9B3@INTMAIL02.es.int.atosorigin.com> Dear WPLeaders Please find here attached the presentation for the Standardization Kick off, prepared by NEC which will lead this 11.4 task, that will take place in Turin within the Exploitation session and a brief introduction of the background of Lindsay Frost from NEC, who will act as task leader and next goals, steps and events related with this Standardization task Please review it and be prepared aiming to get a fruitful f2f meeting in Turin Br Juan 1. Introduction Lindsay Frost has a Ph.D. in physics and - after working in European companies on computing and telematics and as a research manager in facilities in Germany, Italy and Australia - he joined NEC Laboratories Europe in Heidelberg (Germany) in 1999 to work on 3G telecommunications. After managing R&D teams for SIP, 3GPP, WiMAX and WLAN, including working as chairman of the Wi-Fi Alliances' WiFi-Mobile Convergence Marketing Task Group, he concentrated in the last years on standardization activities. Nominated as chairman of ETSI TISPAN WG5 for Home Networks standardization, he has encouraged work in the area of Smart Metering and energy efficiency and the collaboration with other groups such as ETSI M2M, ETSI ATTM, HGI, BBF, ITU-T. For example, he represented BBF in March at the HGI symposium on Home Energy Management and has helped promote M2M topics inside BBF. 2. Goals (a) European Commission has "Request for a FIWare standardization strategy" KPI: At least 3 significant standardization actions per year have to be proposed. Those requirements have to be fulfilled for the complete duration of the project and the requirements for first year can be moved to the following year. 3. Project Steps (a) Develop the Standard Plan 1) create xls of responsible persons from EPM (Executive Project Management) representative from each WP? representative from each company? main SDOs and delegates from each company? obtain "Champion" for each SDO selected 2) define Reporting and decision-making NEC reports to WP11 leader (Juan) NEC reports at f2f meetings NEC delivers reports to PCC, who needs to commit to agreed actions 3) propose and get consensus on contribution to SDOs from all partners Goal: Active Promotiong of FIWare and its activities NEC will propose and solicit input for consensus view on SDO gap analysis NEC will elicit proposals and collate plan for contributions of partners Partners will agree to some timeline of contributions NEC will monitor fulfillment 4) establish mailing-lists for active participants in standardization (b) Develop the SDO Gap Analysis Deliverable 1) propose and get solicit input for ToC * ToC: Introduction to FI-Ware concepts and architecture; - broad characteristics of reference points and protocols; significant SDOs; - overview of status for each significant SDO 2) NEC will contribute some information, and collate the whole report 3) NEC will draft conclusions of report and seek consensus view for final conclusions * which SDOs are significant * which specifications are /completed/getting consolidated/fully open/ * activities (if any) of Fi-WARE partners (c) Maintain an "SDO Events Catalogue" with participation monitoring 4. NLE Action Items (a) Events where NEC will start the SDO monitoring process - ETSI workshop on Future Network Technologies, Agora Building in Sophia Antipolis, France, on 26th - 27th September 2011. - The objective of the workshop is to identify potential subjects for standardization or pre-standardization of Future Network Technologies at ETSI. http://www.etsi.org/FUTURENETWORKTECHNOLOGIES - Delegate: Marcus Brunner (b) ETSI Workshop on M2M Sophia Antipolis, France, 26-27 October 2011 Delegate: Hans van der Veen ? Juan Bare?o Atos Research and Innovation T +34 912148859 juan.bareno at atos.net Albarrac?n 25 28037 Madrid Spain www.atos.net www.atosresearch.eu ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- A non-text attachment was scrubbed... Name: 2011-09-02 FI-WARE Standardization_Kickoff_v0.1.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 417292 bytes Desc: 2011-09-02 FI-WARE Standardization_Kickoff_v0.1.pptx URL: From jhierro at tid.es Sun Sep 11 10:08:48 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 11 Sep 2011 10:08:48 +0200 Subject: [Fiware-wpl] Agenda of FI-WARE Plenary (General Assembly) meeting in Turin Message-ID: <4E6C6C90.7030709@tid.es> Hi all, Please find enclosed the agenda for our Plenary (General Assembly) meeting in Turin. If you have any particular comment or request, don't hesitate to contact me. See you in Turin, -- 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 -------------- A non-text attachment was scrubbed... Name: FI-WARE GA Sep 2011 Agenda vfinal.xls Type: application/vnd.ms-excel Size: 26624 bytes Desc: not available URL: From pierangelo.garino at telecomitalia.it Mon Sep 12 09:54:14 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 12 Sep 2011 09:54:14 +0200 Subject: [Fiware-wpl] R: Agenda of FI-WARE Plenary (General Assembly) meeting in Turin In-Reply-To: <4E6C6C90.7030709@tid.es> References: <4E6C6C90.7030709@tid.es> Message-ID: Dear Juanjo, I send you a slightly modified agenda, which includes the 'events' organised on 15th, some suggestions to 'trim' the last session and make it easier attending such events, and the inclusion of the slot to transfer people from one location to the other (the final plenaries are taking place in the location of first day). 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: domenica 11 settembre 2011 10:09 A: fiware at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Agenda of FI-WARE Plenary (General Assembly) meeting in Turin Hi all, Please find enclosed the agenda for our Plenary (General Assembly) meeting in Turin. If you have any particular comment or request, don't hesitate to contact me. See you in Turin, -- 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. -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE GA Sep 2011 Agenda vfinal-PG.xls Type: application/vnd.ms-excel Size: 41984 bytes Desc: FI-WARE GA Sep 2011 Agenda vfinal-PG.xls URL: From juan.bareno at atosresearch.eu Mon Sep 12 10:40:16 2011 From: juan.bareno at atosresearch.eu (=?iso-8859-1?Q?Juan_Bare=F1o_Guerenabarrena?=) Date: Mon, 12 Sep 2011 10:40:16 +0200 Subject: [Fiware-wpl] Exploitation and Standardization issues at WP level Message-ID: <06BEE166C7F75A47B257036739E29BF3029DC861@INTMAIL02.es.int.atosorigin.com> Dear WPL, As exploitation leader we will ask you, if you could book a slot for Exploitation and Standardization issues during the parallel workshops for the individual work packages issues. Maybe by EOB on Wednesday or at the beginning of the Thursday, we have to arrange them properly for not overlapping. So as a tentative agenda I would propose the following: * Market Trends (each domain) and State of the Art by selected assets for the GE in each domain( (20 minutes) Generic Enabler Existing Assets Actors Exploited Resource Management - In the Market - To develop - Project investigation -Amazon - Separately - Bundle * SWOT Analysis (each domain) and Product attributes definition by selected assets for the GE in each domain (20 minutes) Generic Enabler Innovation/Disruption Added Value Target Market Resource Management - What innovation is provided? - What problem it solve? - Extra features provided? - Separated/bundle? - Potential users - Use Cases by Sector and interrelation with the PPP Projects * Standardization issues at domain level (20 minutes) For continuing this contact at domain level, after the meeting , we will have to appoint a representative for each domain for exploitation and standardization issues Any feedback from any side is welcome and please answer with your slot proposal Thanks Juan As I noticed there is already a meeting planned for Wednesday morning 9-12, where experts from Data, IoT, and Apps will come together. I believe there are other constellations that should meet, at least from the perspective of the Apps WP. f.e.: * Cloud - Apps * Security - Apps * Interface to the network - Apps I suggest to use the Wednesday morning timeslot for parallel cross WP sessions. This would also produce valuable details for the following backlog etc. discussions Regards, Torsten Dear Pier, We agree. If possible we would like to plan it for Thu morning, say 1 hour or 1.5 hours, from 9 AM. The parts of common interest we identified are: -cloud proxy, CE vs IoT gateway -device concept in I2ND (CDI) vs IoT device in IoT -points of contact/interfaces between I2ND and IoT So as a tentativa agenda I would propose the following: * I2ND elaborates on CDI and cloud proxy concepts + interfaces 1+2 (20 minutes) * IoT elaborates on IoT device and IoT gateway concepts + the IoT communications task (20 minutes) * Brainstorming discussion (10-20 minutes) * Conclusions, action items (10-20 minutes) Any feedback from any side is welcome. Thanks & Br, Lorant Juan Bare?o Atos Research and Innovation T +34 912148859 juan.bareno at atos.net Albarrac?n 25 28037 Madrid Spain www.atos.net www.atosresearch.eu ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 78 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 816 bytes Desc: image002.gif URL: From pierangelo.garino at telecomitalia.it Tue Sep 13 22:42:54 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 13 Sep 2011 22:42:54 +0200 Subject: [Fiware-wpl] Proposal for parallel sessions Message-ID: Hi All, this is the proposal for parallel sessions tomorrow (and Thursday morning), according to what discussed at the end of plenary session today and to the requests I received so far (rearrangements are in red). BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 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: FI-WARE GA Sep 2011 Agenda vfinal-PG3.xls Type: application/vnd.ms-excel Size: 59392 bytes Desc: FI-WARE GA Sep 2011 Agenda vfinal-PG3.xls 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 GLIKSON at il.ibm.com Tue Sep 13 23:08:12 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Wed, 14 Sep 2011 00:08:12 +0300 Subject: [Fiware-wpl] [Fiware] Proposal for parallel sessions Message-ID: Hi, >From Cloud perspective, we need interlocks with Security, I2ND, Data and Apps -- about 1 hour each. Regards, Alex From: Garino Pierangelo To: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Cc: "'fiware at lists.fi-ware.eu' (fiware at lists.fi-ware.eu)" Date: 13/09/2011 11:43 PM Subject: [Fiware] Proposal for parallel sessions Sent by: fiware-bounces at lists.fi-ware.eu Hi All, this is the proposal for parallel sessions tomorrow (and Thursday morning), according to what discussed at the end of plenary session today and to the requests I received so far (rearrangements are in red). BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations ? Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. [attachment "FI-WARE GA Sep 2011 Agenda vfinal-PG3.xls" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 677 bytes Desc: not available URL: From pascal.bisson at thalesgroup.com Wed Sep 14 09:42:16 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 14 Sep 2011 09:42:16 +0200 Subject: [Fiware-wpl] Proposal for parallel sessions In-Reply-To: References: Message-ID: <10483_1315986140_4E705ADB_10483_19291_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206085FB1E5@THSONEA01CMS04P.one.grp> Dear Pierangelo, As for Security we need to have joint session of one hour max (could be 45 mn) with each of the other ATs / Chapters. This as per demand/requests I formulated already to Juajno. So far I will have a joint session with IoT today from 5pm to 6pm And expect to have similar joint session with the other chapters tomorrow. Please could arrange and reflect for tomorrow. Thanks on in advance. Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Garino Pierangelo Envoy? : mardi 13 septembre 2011 22:43 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc : 'fiware at lists.fi-ware.eu' (fiware at lists.fi-ware.eu) Objet : [Fiware-wpl] Proposal for parallel sessions Hi All, this is the proposal for parallel sessions tomorrow (and Thursday morning), according to what discussed at the end of plenary session today and to the requests I received so far (rearrangements are in red). BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 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:image001.gif at 01CC72C2.96E406D0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From pierangelo.garino at telecomitalia.it Wed Sep 14 18:54:30 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 14 Sep 2011 18:54:30 +0200 Subject: [Fiware-wpl] Sessions allocation for tomorrow Message-ID: Dear All, here is some rearrangement for tomorrow's meetings, according to some further requests I got late this afternoon. If I don't get any objections, I'll allocate the rooms in this way. Please take in mind that any change is incurring the risk of causing extra troubles due to the fact the joint meeting might need the larger rooms, and this implies a lot of room swaps for the groups. Leonardo Michelangelo Tiziano Tintoretto Raffaello A2004 A2022 B3016 9:00-10:00 Cloud+I2ND Sec Data Expl Apps Tools IoT 10:00-11:00 Cloud+Sec I2ND Data Expl Apps Tools IoT 11:30-12:30 I2ND+Sec Cloud+Data Expl Apps Tools IoT 12:30-13:30 I2ND Data+Sec Expl Apps+Cloud Tools IoT 14:30:00-16:00 I2ND+Apps Sec Cloud Data Expl Tools IoT 16:30-17:30 I2ND Sec Cloud Data Expl Apps Tools IoT One last thing: we'll definitely stay in V. Olivetti the whole day tomorrow, as agreed by all groups. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 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 Ernoe.Kovacs at neclab.eu Wed Sep 14 12:58:50 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Wed, 14 Sep 2011 10:58:50 +0000 Subject: [Fiware-wpl] Exploitation and Standardization issues at WP level In-Reply-To: <06BEE166C7F75A47B257036739E29BF3029DC861@INTMAIL02.es.int.atosorigin.com> References: <06BEE166C7F75A47B257036739E29BF3029DC861@INTMAIL02.es.int.atosorigin.com> Message-ID: <8152E2132B13FB488CFD1947E2DEF19C1CFAC7F5@DAPHNIS.office.hd> Juan, for the WP11 talk today [happening ?], I prepared the attached document on the Standardization activities. @WP Leader: there is a small request for your meetings included in the last slide - Please identify possible SDO. - Please identifies GAPs where are no standard or no good enough standard - If you already have a caretaker for standardization in your WP, please nominate... Thank you - Ern? From: Juan Bare?o Guerenabarrena [mailto:juan.bareno at atosresearch.eu] Sent: Montag, 12. September 2011 10:40 To: fiware-wpl at lists.fi-ware.eu Cc: Ernoe Kovacs; Lindsay Frost; Nuria De-Lama Sanchez; Carmen Perea Escribano; Andrea Rossi Subject: Exploitation and Standardization issues at WP level Dear WPL, As exploitation leader we will ask you, if you could book a slot for Exploitation and Standardization issues during the parallel workshops for the individual work packages issues. Maybe by EOB on Wednesday or at the beginning of the Thursday, we have to arrange them properly for not overlapping. So as a tentative agenda I would propose the following: * Market Trends (each domain) and State of the Art by selected assets for the GE in each domain( (20 minutes) Generic Enabler Existing Assets Actors Exploited Resource Management - In the Market - To develop - Project investigation -Amazon - Separately - Bundle * SWOT Analysis (each domain) and Product attributes definition by selected assets for the GE in each domain (20 minutes) Generic Enabler Innovation/Disruption Added Value Target Market Resource Management - What innovation is provided? - What problem it solve? - Extra features provided? - Separated/bundle? - Potential users - Use Cases by Sector and interrelation with the PPP Projects * Standardization issues at domain level (20 minutes) For continuing this contact at domain level, after the meeting , we will have to appoint a representative for each domain for exploitation and standardization issues Any feedback from any side is welcome and please answer with your slot proposal Thanks Juan As I noticed there is already a meeting planned for Wednesday morning 9-12, where experts from Data, IoT, and Apps will come together. I believe there are other constellations that should meet, at least from the perspective of the Apps WP. f.e.: * Cloud - Apps * Security - Apps * Interface to the network - Apps I suggest to use the Wednesday morning timeslot for parallel cross WP sessions. This would also produce valuable details for the following backlog etc. discussions Regards, Torsten Dear Pier, We agree. If possible we would like to plan it for Thu morning, say 1 hour or 1.5 hours, from 9 AM. The parts of common interest we identified are: -cloud proxy, CE vs IoT gateway -device concept in I2ND (CDI) vs IoT device in IoT -points of contact/interfaces between I2ND and IoT So as a tentativa agenda I would propose the following: * I2ND elaborates on CDI and cloud proxy concepts + interfaces 1+2 (20 minutes) * IoT elaborates on IoT device and IoT gateway concepts + the IoT communications task (20 minutes) * Brainstorming discussion (10-20 minutes) * Conclusions, action items (10-20 minutes) Any feedback from any side is welcome. Thanks & Br, Lorant Juan Bare?o Atos Research and Innovation T +34 912148859 juan.bareno at atos.net Albarrac?n 25 28037 Madrid Spain www.atos.net www.atosresearch.eu [Description: atos_logotype] ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 78 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 816 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2011-09-02 FI-WARE Standardization_Kickoff_v0.2.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 420259 bytes Desc: 2011-09-02 FI-WARE Standardization_Kickoff_v0.2.pptx URL: From jhierro at tid.es Tue Sep 20 15:59:30 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 20 Sep 2011 15:59:30 +0200 Subject: [Fiware-wpl] Follow-up confcalls (joint and WP-focused) Message-ID: <4E789C42.9050303@tid.es> Hi all, As announced during our plenary meeting in Turin, I would like to setup a joint WPL/WPA confcall to address a number of cross-chapter points. The idea would be to alternate bi-weekly confcalls, so a joint WPL/WPA confcall will take place every two weeks and a bi-lateral WPL/WPA confcall will take place also every two weeks (but in a different week). Focus of the bi-weekly WPL/WPA confcall will be on cross-chapter issues (architectural, methodology, etc.) I would suggest that the first of these regular joint WPL/WPA confcalls take place on Monday September 26th. I have setup a doodle poll to agree on the best time at which we may start this first and following confcalls: http://www.doodle.com/bsq3sesudkc3zsi6 Following is a list of topics to be addressed in this first joint WPL/WPA meeting. Other topics you may wish to address are welcome: * Briefing of last f2f FI-PPP AB meeting * Guidelines/steps for development of FI-WARE website contents * Proposal on schedule of f2f WP meetings * Proposal on Agile tool by IBM (I expect some email giving us info about which to discuss along these days) * Definition of conventions/formalism to follow for Architecture Specifications / GE specifications * FI-WARE Operation Support Enablers: * Monitoring * others (suggestion are welcome) Regarding follow-up calls devoted to WPs, we will keep them as planned during Mondays and Fridays. In order to avoid overlapping with the joint WPL/WPA follow-up confcall, I have reviewed in the previously proposed schedule to the following one: * WPs followed-up on Mondays (IoT Service Enablement, Security, Cloud Hosting, Tools): Monday October 3, October 17, ... * WPs followed-up on Fridays (Data/Context Management, Apps/Services Ecosystem & Delivery, I2ND): September 30, October 14, ... * Joint WPLs/WPAs follow-ups: Monday September 26th, October 10, ... 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 Sep 21 08:32:16 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 21 Sep 2011 08:32:16 +0200 Subject: [Fiware-wpl] Follow-up confcalls (joint and WP-focused) In-Reply-To: <4E789C42.9050303@tid.es> References: <4E789C42.9050303@tid.es> Message-ID: <4E7984F0.70203@tid.es> Just would like to mention that I will close the doodle poll tonight (this way people will know in advance and will be able to pencil this into their agenda). Therefore, please cast your vote along today if you want your voice to be considered. Best regards, -- Juanjo On 20/09/11 15:59, Juanjo Hierro wrote: > Hi all, > > As announced during our plenary meeting in Turin, I would like to > setup a joint WPL/WPA confcall to address a number of cross-chapter > points. > > The idea would be to alternate bi-weekly confcalls, so a joint > WPL/WPA confcall will take place every two weeks and a bi-lateral > WPL/WPA confcall will take place also every two weeks (but in a > different week). Focus of the bi-weekly WPL/WPA confcall will be on > cross-chapter issues (architectural, methodology, etc.) > > I would suggest that the first of these regular joint WPL/WPA > confcalls take place on Monday September 26th. I have setup a doodle > poll to agree on the best time at which we may start this first and > following confcalls: > > http://www.doodle.com/bsq3sesudkc3zsi6 > > > Following is a list of topics to be addressed in this first joint > WPL/WPA meeting. Other topics you may wish to address are welcome: > > * Briefing of last f2f FI-PPP AB meeting > * Guidelines/steps for development of FI-WARE website contents > * Proposal on schedule of f2f WP meetings > * Proposal on Agile tool by IBM (I expect some email giving us info > about which to discuss along these days) > * Definition of conventions/formalism to follow for Architecture > Specifications / GE specifications > * FI-WARE Operation Support Enablers: > o Monitoring > o others (suggestion are welcome) > > Regarding follow-up calls devoted to WPs, we will keep them as > planned during Mondays and Fridays. In order to avoid overlapping > with the joint WPL/WPA follow-up confcall, I have reviewed in the > previously proposed schedule to the following one: > > * WPs followed-up on Mondays (IoT Service Enablement, Security, > Cloud Hosting, Tools): Monday October 3, October 17, ... > * WPs followed-up on Fridays (Data/Context Management, Apps/Services > Ecosystem & Delivery, I2ND): September 30, October 14, ... > * Joint WPLs/WPAs follow-ups: Monday September 26th, October 10, ... > > > 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 -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri Sep 23 08:35:26 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 23 Sep 2011 08:35:26 +0200 Subject: [Fiware-wpl] Follow-up confcalls (joint and WP-focused) In-Reply-To: <4E789C42.9050303@tid.es> References: <4E789C42.9050303@tid.es> Message-ID: <4E7C28AE.6090509@tid.es> Hi all, Based on results of the poll, our bi-weekly joint WPL/WPA confcall will be set up at 11:00am starting on Monday Sep 26. Some of you expressed you couldn't start at 11:00am but 11:30am. I hope that you will be able to rearrange things as to join 11:00am, otherwise you join and try to catch up at 11:30am. Please pencil this in your agendas. This Monday there will be a number of important things to address, so it will be relevant that you all don't miss this confcall. Dial-in details will be circulated before monday morning. Best regards, -- Juanjo On 20/09/11 15:59, Juanjo Hierro wrote: Hi all, As announced during our plenary meeting in Turin, I would like to setup a joint WPL/WPA confcall to address a number of cross-chapter points. The idea would be to alternate bi-weekly confcalls, so a joint WPL/WPA confcall will take place every two weeks and a bi-lateral WPL/WPA confcall will take place also every two weeks (but in a different week). Focus of the bi-weekly WPL/WPA confcall will be on cross-chapter issues (architectural, methodology, etc.) I would suggest that the first of these regular joint WPL/WPA confcalls take place on Monday September 26th. I have setup a doodle poll to agree on the best time at which we may start this first and following confcalls: http://www.doodle.com/bsq3sesudkc3zsi6 Following is a list of topics to be addressed in this first joint WPL/WPA meeting. Other topics you may wish to address are welcome: * Briefing of last f2f FI-PPP AB meeting * Guidelines/steps for development of FI-WARE website contents * Proposal on schedule of f2f WP meetings * Proposal on Agile tool by IBM (I expect some email giving us info about which to discuss along these days) * Definition of conventions/formalism to follow for Architecture Specifications / GE specifications * FI-WARE Operation Support Enablers: * Monitoring * others (suggestion are welcome) Regarding follow-up calls devoted to WPs, we will keep them as planned during Mondays and Fridays. In order to avoid overlapping with the joint WPL/WPA follow-up confcall, I have reviewed in the previously proposed schedule to the following one: * WPs followed-up on Mondays (IoT Service Enablement, Security, Cloud Hosting, Tools): Monday October 3, October 17, ... * WPs followed-up on Fridays (Data/Context Management, Apps/Services Ecosystem & Delivery, I2ND): September 30, October 14, ... * Joint WPLs/WPAs follow-ups: Monday September 26th, October 10, ... 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 -- 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 GLIKSON at il.ibm.com Sat Sep 24 16:09:29 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Sat, 24 Sep 2011 17:09:29 +0300 Subject: [Fiware-wpl] Agile tools Message-ID: Dear all, I have spent some time trying to figure out how to use FusionForge Tracker for the needs of keeping track of Agile aspects of the work done in each WP. Indeed, it is highly customizable in terms of custom fields. However, I don't see a reasonable way to visualize and manage several key aspects of Agile project management, such as grouping (e.g., within certain sprint) and hierarchy (e.g., Epics which contain Features which contain User Stories) of the different work items, their priorities, sizing, dependencies, progress (e.g., how much work do we have left until the end of the release, and whether we are on track), etc. You can find a good explanation of Agile project metrics and reporting at http://www.agilesparks.com/MetricsLecture. Of course, we don't have to be *that* granular -- but I think we must have *some* project tracking capabilities at the level of stories (which comprise sprints) and features (which comprise releases). I wonder whether it wouldn't make sense to invest some effort (and potentially money) in a reasonable Agile project management tool. After all, it is a 50M Euro project which will last for 3 years, and good tooling could make the difference. I've mentioned that IBM Rational Team Concert can be used for this purpose. I am sure there are other commercial tools out there (not sure regarding open source). Unfortunately, I can't investigate this in detail myself -- so all I can do right now is to suggest giving it a bit more thought. If we conclude that we can't afford this, I would recommend considering something like Excel or MS Project -- maybe in addition to FusionForge, for ongoing project management. Would be good to hear your thoughts on this, towards the meeting on Monday. Regards, Alex Glikson IBM Cloud Hosting lead P.S. can we have a quick poll, among people on these mailing lists (who would actually need to do the project management in each WP), especially those familiar with Agile, whether they think this is a real issue? -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Sep 26 09:50:15 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 26 Sep 2011 09:50:15 +0200 Subject: [Fiware-wpl] Dial-in/webex details for the joint WPLs/WPAs confcall this morning In-Reply-To: <256050680.1317018764558.JavaMail.nobody@jsj2wl013.webex.com> References: <256050680.1317018764558.JavaMail.nobody@jsj2wl013.webex.com> Message-ID: <4E802EB7.2080909@tid.es> Hi all, We will use powwownow for the confcall that we have setup starting at 11:00am. The powwownow PIN code is 050662 Dial-in local phone numbers in the .pdf attached. Details for the webex session attached below. Best regards, -- Juanjo -------- Original Message -------- Subject: Meeting invitation: FI-WARE joint WPLs/WPAs follow-up confcall Date: Mon, 26 Sep 2011 08:32:44 +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, September 26, 2011 Time: 10:45 am, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 964 527 932 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=182768697&UID=1252957457&PW=NNWVlNjMzOWVi&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=182768697&UID=1252957457&PW=NNWVlNjMzOWVi&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=182768697&UID=1252957457&ICS=MI&LD=1&RD=2&ST=1&SHA2=5oiCMdpsaU3/21rIYvGNZ63k9D3unUi5c-GRwHCvNdE=&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: -------------- 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 davide.dallecarbonare at eng.it Mon Sep 26 10:07:27 2011 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Mon, 26 Sep 2011 10:07:27 +0200 Subject: [Fiware-wpl] WP9 Questionnaire Message-ID: <4E8032BF.8040703@eng.it> Dear WP leaders, as you know in WP9 we have produced a first version of "FI-WARE DevComE Technical description" document and some parts of it has been discussed during the last plenary meeting in Turin. At the moment we are updating the document with the comments received during that discussion, and in order to better take into account the various WP needs we kindly ask you to answer to the attached questionnaire (very short) by October 3rd. I'm at your disposal for questions and comments ... thank you and Best Regards, Davide Dalle Carbonare -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE WP9 Questionnaire.odt Type: application/vnd.oasis.opendocument.text Size: 28458 bytes Desc: not available URL: From jhierro at tid.es Mon Sep 26 11:16:28 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 26 Sep 2011 11:16:28 +0200 Subject: [Fiware-wpl] Presentation to use during the confcall Message-ID: <4E8042EC.9010200@tid.es> Attached -- 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 -------------- A non-text attachment was scrubbed... Name: FI-WARE joint WPL-WPAs 11-09-26.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 429056 bytes Desc: not available URL: From jhierro at tid.es Wed Sep 28 01:32:14 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 28 Sep 2011 01:32:14 +0200 Subject: [Fiware-wpl] Actions from our joint WPL/WPA follow-up confcall Message-ID: <4E825CFE.3060901@tid.es> Dear all, Please find below the set of Action Points we have identified during our follow-up confcall: Davide: to check current ToC in the Wiki and suggest where the document on Tools would fit in. We will fix over the email the details Juanjo: Configuration of a Wiki linked to the "FI-WARE Private" will be put in the queue of work to be done by the FusionForge support team Juanjo: A tracker will be created for issuing requests to the FusionForge team Juanjo: Translate guidelines for use of the blog (populating contents of the website), internal minutes of chapters and tools that will serve for that purpose (deadline: end of this week) Juanjo: Add to presentation shared during the follow-up confcall activities during October dealing with definition of planning (activities/milestones) of the FI-WARE Testbed All: Task Force will be created for each technical chapter involving representatives of the chapter and representatives of the Security chapter, targeted to refine contents of the "Question Marks" section in every chapter related to Security. - October 7th: chapter teams to provide update on Security section contents within "Question Marks" sections - October 10th: Pascal to give us update on projects Security: A description about how Identity Management, Access Control and Privacy should be available on the wiki as update of the FI-WARE Product Vision by October 7th Security: Pascal will come with a proposal by October 10th on day when to have a virtual workshop with UC projects where FI-WARE will explain UC projects what will be the architecture that integrates the above core Security GEs (Identity, Access Control and Privacy Management) All: to make proposals over the email that can be taken as input for the discussion on the topic of Architecture notations/conventions during our next joint WPL/WPA follow-up All: Bring proposal on schedule of f2f WP meetings to the next joint WPL/WPA follow-up confcall Alex (Cloud), Pascal (Security) and Juanjo (Data): to come with a proposal on how to deal with Monitoring to our next joint WPL/WPA follow-up confcall All: Come to the next follow-up confcall with feedback about applicability of the selected tools (tracker+Wiki) for Backlog management. We will keep with usage of the tracker and the wiki and not change the plans unless there is negative feedback gathered by the teams Juanjo/Pascal: to setup virtual session between Security and Data/Context team next week -- 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 Sep 28 01:58:07 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 28 Sep 2011 01:58:07 +0200 Subject: [Fiware-wpl] Updated slides with very next steps and planning of activities during October in FI-WARE project In-Reply-To: <4E825CFE.3060901@tid.es> References: <4E825CFE.3060901@tid.es> Message-ID: <4E82630F.2060907@tid.es> Folks, I have updated the presentation we shared during our follow-up confcall on Monday so that we can use it as a term of reference for the work to be done (both very next steps and work during October) Please review it and, if you find anything is missing, please let me know. Also share it with your teams. 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 -------------- A non-text attachment was scrubbed... Name: FI-WARE joint WPL-WPAs 11-09-28.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 431145 bytes Desc: not available URL: From jhierro at tid.es Wed Sep 28 02:02:20 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 28 Sep 2011 02:02:20 +0200 Subject: [Fiware-wpl] [Fiware-wpa] Updated slides with very next steps and planning of activities during October in FI-WARE project In-Reply-To: <4E82630F.2060907@tid.es> References: <4E825CFE.3060901@tid.es> <4E82630F.2060907@tid.es> Message-ID: <4E82640C.1030600@tid.es> Hi, Please replace the presentation with the one now attached. Minor typos fixed. Apologize for sending it twice. Best regards, -- Juanjo On 28/09/11 01:58, Juanjo Hierro wrote: > Folks, > > I have updated the presentation we shared during our follow-up > confcall on Monday so that we can use it as a term of reference for the > work to be done (both very next steps and work during October) > > Please review it and, if you find anything is missing, please let me > know. > > Also share it with your teams. > > 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 -------------- A non-text attachment was scrubbed... Name: FI-WARE joint WPL-WPAs 11-09-28.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 429053 bytes Desc: not available URL: From jhierro at tid.es Wed Sep 28 03:23:49 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 28 Sep 2011 03:23:49 +0200 Subject: [Fiware-wpl] Fwd: FI-WARE: first review meeting on Nov 22 In-Reply-To: <7BACCBA4EE7D3946BF23FB79D9FD2E613CC51B@S-DC-EXM11.net1.cec.eu.int> References: <" <7BACCBA4EE7D3946BF23FB79D9FD2E613CC51B"@S-DC-EXM11.net1.cec.eu.int> Message-ID: <4E827725.1080001@tid.es> Hi, Tuesday Nov 22 has been finally selected as the date for our first six month review. Due to the relevance of this, we will have a rehearsal meeting starting on Monday Nov 21 at 09:00am. I know this will probably mean we have to travel on Sunday, but it has been the result of our own votes :-) Please book your trip in advance. Essentially, all WPs should be present. WPAs are also welcome. We will plan work/presentations to be done as the date approaches. Best regards, -- Juanjo -------- Original Message -------- Subject: FI-WARE: first review meeting on Nov 22 Date: Fri, 23 Sep 2011 12:02:02 +0200 From: Arian.ZWEGERS at ec.europa.eu To: JOSE JIMENEZ DELGADO , JUAN JOSE HIERRO SUREDA , "rdifrancesco at ymail.com" , "dgr at whitestein.com" , "msli at icfocus.co.uk" CC: Federica.TAGLIANI at ec.europa.eu , INFSO-ICT-285248 at ec.europa.eu , Annalisa.Bogliolo at ec.europa.eu Dear all, Looking at the Doodle poll, Nov 22 is the best date. I hereby confirm that the first FI-WARE review meeting will take place on Nov 22. More details will follow in due time. Best regards, Arian. -----Original Message----- From: ZWEGERS Arian (INFSO) Sent: Tuesday, September 06, 2011 8:39 AM To: JOSE JIMENEZ DELGADO; 'Juanjo Hierro'; 'Renaud Di francesco'; 'Dominic Greenwood'; 'Man-Sze Li' Cc: TAGLIANI Federica (INFSO); INFSO-ICT-285248; BOGLIOLO Annalisa (INFSO) Subject: FI-WARE: Doodle poll for first review meeting Dear all, Please find below a link to a Doodle poll to determine the first review meeting. Please complete before Sept 13. @Jose, Juanjo: please distribute to those FI-WARE members you think should attend. Review meetings should not be an opportunity for participants to have a field day. Best regards, Arian. -----Original Message----- From: Doodle [mailto:mailer at doodle.com] Sent: Tuesday, September 06, 2011 8:29 AM To: ZWEGERS Arian (INFSO) Subject: Doodle: Link for poll "FI-WARE review 1 meeting" You have initiated a poll "FI-WARE review 1 meeting" at Doodle. The link to your poll is: http://doodle.com/cx3btby438pz6dmu Share this link with all those who should cast their votes. Do not forget to cast your vote, too. (If you did not initiate this poll, somebody must accidentally have used your e-mail address; simply ignore this e-mail, 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed Sep 28 13:01:47 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 28 Sep 2011 13:01:47 +0200 Subject: [Fiware-wpl] Update on status with the Wiki/Trackers Message-ID: <4E82FE9B.3060302@tid.es> Hi all, An update on the matter: * The tracker for Global Technical Support is ready and the UC projects have received the invitation to start using it * A number of tutorials have been developed to help creating user accounts in FusionForge, joining a project and using the Global Technical Support tracker * We are still in the process of translating contents of the FI-WARE Product Vision to the Wiki. Here we are delayed from the defined plan but I expect this to be ready tomorrow early in the morning. * We are currently testing how to create Backlog entries following the tutorials developed by SAP. The goal is to have everything setup by tomorrow as planned. Any feedback is of course welcome. 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 Sep 28 15:02:19 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 28 Sep 2011 15:02:19 +0200 Subject: [Fiware-wpl] IMPORTANT Clarification Message-ID: <4E831ADB.2070809@tid.es> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas.michael.bohnert at sap.com Wed Sep 28 15:06:22 2011 From: thomas.michael.bohnert at sap.com (Bohnert, Thomas Michael) Date: Wed, 28 Sep 2011 15:06:22 +0200 Subject: [Fiware-wpl] [Fiware-wpa] IMPORTANT Clarification In-Reply-To: <4E831ADB.2070809@tid.es> Message-ID: <771C9B001456D64783596DDC3801C6EA281533FE5C@DEWDFECCR09.wdf.sap.corp> Mind that I have presented both options in Turin requesting feedback. The initial feedback, as I understood, was to go for one tracker/backlog per chapter. One of the compelling reasons is simply the admin overhead. Best, Thomas -- Please excuse smartphone brevity From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Wednesday, September 28, 2011 03:02 PM To: fiware-wpl at lists.fi-ware.eu ; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] IMPORTANT Clarification 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu Sep 29 08:10:05 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 29 Sep 2011 08:10:05 +0200 Subject: [Fiware-wpl] Update on status with the Wiki/Trackers In-Reply-To: <4E82FE9B.3060302@tid.es> References: <4E82FE9B.3060302@tid.es> Message-ID: <4E840BBD.2080300@tid.es> Hi all, Update on status: * The tracker for Global Technical Support is ready and the UC projects have received the invitation to start using it * A number of tutorials have been developed to help creating user accounts in FusionForge, joining a project and using the Global Technical Support tracker * We are still in the process of translating contents of the FI-WARE Product Vision to the Wiki. Here we are delayed from the defined plan but I expect to have a version along this morning (though most probably without figures). * We will elaborate a template for the sections on description of assets that Chapter teams should follow. We will provide it by EOB today. * A tutorial for adding the full description of backlog entries in the Wiki has been elaborated (thanks Torsten !). Chapter teams should start introducing entries in the Wiki from now on, trying to get this task done by tomorrow Sep 30 EOB. * We will define a tutorial for creating your chapter backlog tracker instead of creating it for you. I believe this will be better because, although may require a bit more time, this way knowledge about creating/configuring a tracker is shared (you'll see is not that difficult). I believe that creation of tickets for backlog entries should be postponed until we have their full description available in the Wiki, so let's plan this as a task to tackle afterwards, and extend the deadline for get it done until Oct 4 EOB. Any comment/feedback is welcome Best regards, -- Juanjo P.S.: Your feedback on question made in my message with subject "IMPORTANT Clarification" is also welcome. On 28/09/11 13:01, Juanjo Hierro wrote: Hi all, An update on the matter: * The tracker for Global Technical Support is ready and the UC projects have received the invitation to start using it * A number of tutorials have been developed to help creating user accounts in FusionForge, joining a project and using the Global Technical Support tracker * We are still in the process of translating contents of the FI-WARE Product Vision to the Wiki. Here we are delayed from the defined plan but I expect this to be ready tomorrow early in the morning. * We are currently testing how to create Backlog entries following the tutorials developed by SAP. The goal is to have everything setup by tomorrow as planned. Any feedback is of course welcome. 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 Sep 29 10:21:14 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 29 Sep 2011 10:21:14 +0200 Subject: [Fiware-wpl] Fwd: Update on status of FI-WARE Wiki/Tracker tools in FI-WARE In-Reply-To: <4E842A2A.5090402@tid.es> References: <4E842A2A.5090402@tid.es> Message-ID: <4E842A7A.9070408@tid.es> Hi, Find below the message I have just sent to representatives of the UC projects in the FI-PPP AB. From now on, we should start seeing activity on the trackers, etc from them. 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 -------- Original Message -------- Subject: Update on status of FI-WARE Wiki/Tracker tools in FI-WARE Date: Thu, 29 Sep 2011 10:19:54 +0200 From: Juanjo Hierro To: ab at fi-ppp.eu 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, -- 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 GLIKSON at il.ibm.com Thu Sep 29 11:41:17 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Thu, 29 Sep 2011 12:41:17 +0300 Subject: [Fiware-wpl] IMPORTANT Clarification In-Reply-To: <4E831ADB.2070809@tid.es> References: <4E831ADB.2070809@tid.es> Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas.michael.bohnert at sap.com Thu Sep 29 11:57:59 2011 From: thomas.michael.bohnert at sap.com (Bohnert, Thomas Michael) Date: Thu, 29 Sep 2011 11:57:59 +0200 Subject: [Fiware-wpl] IMPORTANT Clarification In-Reply-To: Message-ID: <771C9B001456D64783596DDC3801C6EA281533FE62@DEWDFECCR09.wdf.sap.corp> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas.michael.bohnert at sap.com Thu Sep 29 12:02:12 2011 From: thomas.michael.bohnert at sap.com (Bohnert, Thomas Michael) Date: Thu, 29 Sep 2011 12:02:12 +0200 Subject: [Fiware-wpl] IMPORTANT Clarification In-Reply-To: <771C9B001456D64783596DDC3801C6EA281533FE62@DEWDFECCR09.wdf.sap.corp> Message-ID: <771C9B001456D64783596DDC3801C6EA281533FE63@DEWDFECCR09.wdf.sap.corp> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas.michael.bohnert at sap.com Thu Sep 29 12:09:43 2011 From: thomas.michael.bohnert at sap.com (Bohnert, Thomas Michael) Date: Thu, 29 Sep 2011 12:09:43 +0200 Subject: [Fiware-wpl] IMPORTANT Clarification In-Reply-To: <771C9B001456D64783596DDC3801C6EA281533FE63@DEWDFECCR09.wdf.sap.corp> Message-ID: <771C9B001456D64783596DDC3801C6EA281533FE66@DEWDFECCR09.wdf.sap.corp> Juanjo, For clarification. Option two means 'multiple trackers' or 'one tracker + mutliple tickets' ? Best, Thomas -- Please excuse smartphone brevity From: Bohnert, Thomas Michael Sent: Thursday, September 29, 2011 12:02 PM 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 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Thu Sep 29 14:16:01 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Thu, 29 Sep 2011 15:16:01 +0300 Subject: [Fiware-wpl] IMPORTANT Clarification In-Reply-To: <771C9B001456D64783596DDC3801C6EA281533FE63@DEWDFECCR09.wdf.sap.corp> References: <771C9B001456D64783596DDC3801C6EA281533FE62@DEWDFECCR09.wdf.sap.corp> <771C9B001456D64783596DDC3801C6EA281533FE63@DEWDFECCR09.wdf.sap.corp> Message-ID: 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. 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. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefano.depanfilis at eng.it Thu Sep 29 15:28:11 2011 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Thu, 29 Sep 2011 15:28:11 +0200 Subject: [Fiware-wpl] Fwd: FI-WARE: first review meeting on Nov 22 In-Reply-To: <4E827725.1080001@tid.es> References: <7BACCBA4EE7D3946BF23FB79D9FD2E613CC51B@S-DC-EXM11.net1.cec.eu.int> <4E827725.1080001@tid.es> Message-ID: dear juanjo, it is not in your and any email, but it is easy to assume that the review will be in brussels, isn't it? ciao, stefano 2011/9/28 Juanjo Hierro > Hi, > > Tuesday Nov 22 has been finally selected as the date for our first six > month review. > > Due to the relevance of this, we will have a rehearsal meeting starting > on Monday Nov 21 at 09:00am. I know this will probably mean we have to > travel on Sunday, but it has been the result of our own votes :-) > > Please book your trip in advance. > > Essentially, all WPs should be present. WPAs are also welcome. > > We will plan work/presentations to be done as the date approaches. > > Best regards, > > -- Juanjo > > -------- Original Message -------- Subject: FI-WARE: first review meeting > on Nov 22 Date: Fri, 23 Sep 2011 12:02:02 +0200 From: > Arian.ZWEGERS at ec.europa.eu To: > JOSE JIMENEZ DELGADO , JUAN JOSE HIERRO > SUREDA , "rdifrancesco at ymail.com" > , "dgr at whitestein.com" > , "msli at icfocus.co.uk" > CC: > Federica.TAGLIANI at ec.europa.eu , > INFSO-ICT-285248 at ec.europa.eu , > Annalisa.Bogliolo at ec.europa.eu > > Dear all, > > Looking at the Doodle poll, Nov 22 is the best date. > I hereby confirm that the first FI-WARE review meeting will take place on Nov 22. > > More details will follow in due time. > > Best regards, > Arian. > > -----Original Message----- > From: ZWEGERS Arian (INFSO) > Sent: Tuesday, September 06, 2011 8:39 AM > To: JOSE JIMENEZ DELGADO; 'Juanjo Hierro'; 'Renaud Di francesco'; 'Dominic Greenwood'; 'Man-Sze Li' > Cc: TAGLIANI Federica (INFSO); INFSO-ICT-285248; BOGLIOLO Annalisa (INFSO) > Subject: FI-WARE: Doodle poll for first review meeting > > Dear all, > > Please find below a link to a Doodle poll to determine the first review meeting. > > Please complete before Sept 13. > > @Jose, Juanjo: please distribute to those FI-WARE members you think should attend. Review meetings should not be an opportunity for participants to have a field day. > > Best regards, > Arian. > > -----Original Message----- > From: Doodle [mailto:mailer at doodle.com ] > Sent: Tuesday, September 06, 2011 8:29 AM > To: ZWEGERS Arian (INFSO) > Subject: Doodle: Link for poll "FI-WARE review 1 meeting" > > You have initiated a poll "FI-WARE review 1 meeting" at Doodle. The link to your poll is: > http://doodle.com/cx3btby438pz6dmu > > Share this link with all those who should cast their votes. Do not forget to cast your vote, too. > (If you did not initiate this poll, somebody must accidentally have used your e-mail address; simply ignore this e-mail, please.) > > > > > -- > Juanjo Hierro > Chief Technologist on Software Technologies > Telefonica R&D Labs > > email: jhierro at tid.es > phone: +34 91 48 32932www.tid.estwitter.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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Thu Sep 29 19:33:09 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Thu, 29 Sep 2011 20:33:09 +0300 Subject: [Fiware-wpl] Fw: Request to Join Project FI-WARE Cloud Message-ID: Dear Juanjo, Is there a way to reject a request to join a project with a comment/explanation? I've rejected the request below, but wanted to clarify that GE requests should be opened against the 'root' FI-WARE project. Regards, Alex P.S. copying WP leads, as similar questions are likely to arise for their WP projects in Forge ----- Forwarded by Alex Glikson/Haifa/IBM on 29/09/2011 08:29 PM ----- From: noreply at forge.fi-ware.eu To: Alex Glikson/Haifa/IBM at IBMIL Date: 29/09/2011 05:06 PM Subject: Request to Join Project FI-WARE Cloud Nazila Gol mohammadi has requested to join your project. You can approve this request here: https://forge.fi-ware.eu/project/admin/users.php?group_id=14 Comments by the user: I need to join to this project in order to submit GE request by Finest -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu Sep 29 19:39:22 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 29 Sep 2011 19:39:22 +0200 Subject: [Fiware-wpl] FI-WARE - Urgent - delivrables to provide for tomorrow - request for clarification In-Reply-To: <11604_1317310005_4E848E35_11604_19713_1_dbe3da4f-b5c2-48c6-8289-09e06d6e3d7f@THSONEA01HUB06P.one.grp> References: <11604_1317310005_4E848E35_11604_19713_1_dbe3da4f-b5c2-48c6-8289-09e06d6e3d7f@THSONEA01HUB06P.one.grp> Message-ID: <4E84AD4A.3000106@tid.es> Hi, Thanks for your question. Find my answer below. I'm copying the fiware-wpl and fiware-wpa because I believe that the answer may be helpful for all. Best regards, -- Juanjo On 29/09/11 17:26, GIDOIN Daniel wrote: Dear Juanjo, I have any problem with the definition of AGILE terms and consequently with the deliverables to be provided for tomorrow. Product Backog: The Scrum Alliance provides this definition: ?The product backlog (or "backlog") is the requirements for a system, expressed as a prioritized list of product backlog Items. These included both functional and non-functional customer requirements, as well as technical team-generated requirements? EPICs Epics are large user stories, typically ones which are too big to implement in a single iteration and therefore they need to be disaggregated into smaller user stories at some point. (User stories are one of the primary development artifacts for Scrum and Extreme Programming (XP) project teams. A user story is a very high-level definition of a requirement, containing just enough information so that the developers can produce a reasonable estimate of the effort to implement it. This is fine, but take into account that saying that something is "high-level" is rather subjective, so that I would drop that part (parts in a definition that are subject to interpretation are not desirable in any definition). What is relevant, and more accurate, is not what you have underlined but the part where you say that a user story "contains just enough information so that the developers can produce a reasonable estimate of the effort to implement it". But I have to say even this definition is incomplete. In order to provide an even more accurate definition, you have to introduce the concept of user story as a requirement covered by a short-time development: "A user story is a definition of a requirement, containing just enough information so that the developers can produce a reasonable estimate of the effort to implement it and it doesn't go beyond the duration of a sprint" As you probably notice, a fundamental question to answer in order to complete this statement is ... what is the duration of a sprint ... because it would impact the level of granularity in definition of your requirement you have to provide that will give your development team enough confidence to assure that they will be able to cope with the requirement within the duration of a sprint. Remember the attributes of a User Story. Here it is how they relate to the description above: * Independent: A user story should not depend on another user story to get it done. If user story "A" depends on user story "B", then you should only plan "A" in the sprint after user story "B" is solved (in other words, user story "A" will only be addressed in sprint "Sx" only if user story "B" has been addressed in a sprint previous to sprint "Sx") * Negotiable: This is about the "just enough" in the definition above which was not there arbitrarely: you should stop refining a requirement once you have just enough information without delaying start of development until you get all the details solved. There may be still details to solve, but it is assumed that such details can be resolved during the sprint duration without this changing the estimate of the effort significantly (in the unlikely case this happen, the user story should turn back into an Epic, and moved out of the sprint in progress). * Valuable: A user story should include a description of what value it brings if covered by the product (rationale) * Estimatable: This is about being capable to "produce a reasonable estimate of the effort to implement it" * Small: This is about "not going beyond the duration of a sprint" * Testable: This is about providing info in the user story that will help to prepare the necessary test cases that allow to verify that the user story is covered by the product. In other words, the definition of a user story should cover the definition of concrete and measurable points you can test are fulfilled. Of this six attributes, indeed "Negotiable" and "Small" are rather the ones that are unique to user-stories, i.e., don't belong to Themes, Epics, or Features. "Estimatable" is also an attribute for "Features" with the only difference than in "Features" the estimated time should not go beyond the agreed duration of releases (typically 60-120 working days, in FI-WARE 60 working days). It's not an attribute of Themes or Epics. All of them (Themes, Epics, Features and User-stories) may be considered "Testeable" in the sense that a "Feature" would be considered tested once all user-stories in which it gets decomposed are tested. Similarly, an Epic would be considered tested once all Features/User-stories in which it gets decomposed are tested. "Valuable" is an attribute of all of them too, but there the explanation is pretty simple ... Agile is about developing things that really provide value. For you: ? Product backlog: It?s about keeping track of ?work to be done?, and keep it described in a way that makes sense to both users and development teams ? User Stories are simply description of ?work to be done? that is detailed enough as to be addressable by a development team along the duration of a sprint. ? EPICs relate to ?work to be done? you have to further split before being addressed in the next sprint? My experience is that many people who approaches Agile for the same time get scared because they believe that the concepts are "radically new" to anything they know before. But the true fact is that they aren't (in my honest opinion). The "work to be done" by a team who is developing a product is actually that: implementing the product. So there is absolute no contradiction between the statements you extract from me and what is said above. Actually, you could rephrase the definition as to say: "A user story is a definition of a requirement, containing just enough information about the work to be done in implementing the requirement so that the developers can produce a reasonable estimate of the effort to carry out that work and the duration of that work doesn't go beyond the duration of a sprint" I introduced the reference to "work to be done" because many people who have strong planning management skills understand then better what Agile is about and find that it is not that different compared with the usual task many of them use to carry out about keeping a spreadsheet with which they follow-up "work to be done / in-progress". I am not familiar with the Agile but I feel that the definitions are very different. Also I have trouble understanding what I need to deliver about it tomorrow. Could you enlighten me with a very specific example. I hope that this explanation is helpful. Regarding examples, I believe that I have given enough examples (take a look at the templates I distributed in August where there were examples of Epics and User Stories) ... but, nevertheless, this is another point to take into account: Don't become obsessed about whether an entry you have produced should be labeled as an Epic or as a User-story: * There will be Epics that will be like in the frontier. Shift them to become user-story or still keep it as an Epic is pretty simple: just ask your development team "can you give ensure me that you would be able to implement what is needed in the product to cover this entry in less than one month ?" If the answer is "no" or simply "well ... I would need more info" ... Then it's not a user-story and should remain being an Epic. * There will be entries you may wrongly label as user-story because, among other things, the development team believed they had enough information to implement what is needed in the product to cover it at the time the planning of the current sprint took place. But then ... during execution of the sprint they realize that there was much more information that was needed ... In such a case, you should stop implementing it and try to answer all the question so that, at least, it becomes a true user-story (you may then decide to address in next sprint) or a better documented Epic in the backlog. You may even realize that such user-story may need to transform into a user-story you can actually finish in the current sprint but an additional set of user-stories and Epics for following sprints. Best regards Daniel ________________________________ 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 Sep 29 20:11:02 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 29 Sep 2011 20:11:02 +0200 Subject: [Fiware-wpl] Fw: Request to Join Project FI-WARE Cloud In-Reply-To: References: Message-ID: <4E84B4B6.5090909@tid.es> Not sure you can add a message in the rejection ... I'll ask. Nevertheless, I will send an email to the FI-PPP AB mailing list (where representatives of all UC projects are registered) telling them that we will reject any request to join to projects different than the FI-WARE project. Probably they are asking to join because they need to be able to "read" the trackers linked to Chapter backlogs. But this is something we will allow anyone world-wide (that is my recall on the matter when we discussed it, but it's also what makes sense to me), therefore they will be able to monitor. What they won't be able to do (and they shouldn't) is to submit tickets directly to the Chapter backlogs. Some people may argue that we shouldn't even allow "observers" to read our chapter backlogs ... Well, I believe that publishing Epics/Features is not a big deal and we have to keep them publicly readable. I would even add that not doing so could bring some troubles to us in front of the EC (I believe it would not comply with what we committed in the DoW) On the other hand, I would be more flexible regarding User-stories and leave to chapter partners the decision about keeping user-stories in separate trackers (either a single one or one per GE) or not. It would then be feasible to keep such user-story oriented trackers fully private. The trade off, of course, is that such approach would mean more administrative burden for the chapter partners, but if they wish to live with that, it's fine to me. 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 19:33, Alex Glikson wrote: Dear Juanjo, Is there a way to reject a request to join a project with a comment/explanation? I've rejected the request below, but wanted to clarify that GE requests should be opened against the 'root' FI-WARE project. Regards, Alex P.S. copying WP leads, as similar questions are likely to arise for their WP projects in Forge ----- Forwarded by Alex Glikson/Haifa/IBM on 29/09/2011 08:29 PM ----- From: noreply at forge.fi-ware.eu To: Alex Glikson/Haifa/IBM at IBMIL Date: 29/09/2011 05:06 PM Subject: Request to Join Project FI-WARE Cloud ________________________________ Nazila Gol mohammadi has requested to join your project. You can approve this request here: https://forge.fi-ware.eu/project/admin/users.php?group_id=14 Comments by the user: I need to join to this project in order to submit GE request by Finest ________________________________ 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 Sep 29 22:00:37 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 29 Sep 2011 22:00:37 +0200 Subject: [Fiware-wpl] R: Fw: Request to Join Project FI-WARE Cloud In-Reply-To: <4E84B4B6.5090909@tid.es> References: <4E84B4B6.5090909@tid.es> Message-ID: Hi Juanjo, I got the same request (same person) for I2ND project. I think that would be worth sending the mail to the AB. Moreover, the reason to request joining the chapter project was 'to submit GE request by Finest': I believe the mail should also explain (maybe with the link to the relevant Wiki tutorial pages) what the UCPs can input, that is Feature requests in the FI-WARE backlog, not GEs. Two more questions about the capability to monitor our chapter backlogs, as I'm a bit confused: - If we have e.g. one 'public' backlog per chapter, visible to everybody, can we also have the 'private' trackers in parallel to it, not visible to users outside FI-WARE? - Why should we have EPICs/features in the chapter backlog, aren't they already in the FI-WARE Wiki backlog? I believe we could keep the single chapter backlogs private and devoted to the user-stories tracker(s) Did I mix something wrongly? 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? 29 settembre 2011 20:11 A: Alex Glikson Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: Re: [Fiware-wpl] Fw: Request to Join Project FI-WARE Cloud Not sure you can add a message in the rejection ... I'll ask. Nevertheless, I will send an email to the FI-PPP AB mailing list (where representatives of all UC projects are registered) telling them that we will reject any request to join to projects different than the FI-WARE project. Probably they are asking to join because they need to be able to "read" the trackers linked to Chapter backlogs. But this is something we will allow anyone world-wide (that is my recall on the matter when we discussed it, but it's also what makes sense to me), therefore they will be able to monitor. What they won't be able to do (and they shouldn't) is to submit tickets directly to the Chapter backlogs. Some people may argue that we shouldn't even allow "observers" to read our chapter backlogs ... Well, I believe that publishing Epics/Features is not a big deal and we have to keep them publicly readable. I would even add that not doing so could bring some troubles to us in front of the EC (I believe it would not comply with what we committed in the DoW) On the other hand, I would be more flexible regarding User-stories and leave to chapter partners the decision about keeping user-stories in separate trackers (either a single one or one per GE) or not. It would then be feasible to keep such user-story oriented trackers fully private. The trade off, of course, is that such approach would mean more administrative burden for the chapter partners, but if they wish to live with that, it's fine to me. 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 19:33, Alex Glikson wrote: Dear Juanjo, Is there a way to reject a request to join a project with a comment/explanation? I've rejected the request below, but wanted to clarify that GE requests should be opened against the 'root' FI-WARE project. Regards, Alex P.S. copying WP leads, as similar questions are likely to arise for their WP projects in Forge ----- Forwarded by Alex Glikson/Haifa/IBM on 29/09/2011 08:29 PM ----- From: noreply at forge.fi-ware.eu To: Alex Glikson/Haifa/IBM at IBMIL Date: 29/09/2011 05:06 PM Subject: Request to Join Project FI-WARE Cloud ________________________________ Nazila Gol mohammadi has requested to join your project. You can approve this request here: https://forge.fi-ware.eu/project/admin/users.php?group_id=14 Comments by the user: I need to join to this project in order to submit GE request by Finest ________________________________ 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 Sep 29 23:22:25 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 29 Sep 2011 23:22:25 +0200 Subject: [Fiware-wpl] R: Fw: Request to Join Project FI-WARE Cloud In-Reply-To: References: <4E84B4B6.5090909@tid.es> Message-ID: <4E84E191.6030204@tid.es> On 29/09/11 22:00, Garino Pierangelo wrote: Hi Juanjo, I got the same request (same person) for I2ND project. I think that would be worth sending the mail to the AB. Moreover, the reason to request joining the chapter project was ?to submit GE request by Finest?: I believe the mail should also explain (maybe with the link to the relevant Wiki tutorial pages) what the UCPs can input, that is Feature requests in the FI-WARE backlog, not GEs. This was communicated several times ... but seems like there is some sort of misscomunication within some UC projects. Nevertheless, I'll send the message to the AB right now. Two more questions about the capability to monitor our chapter backlogs, as I?m a bit confused: - If we have e.g. one ?public? backlog per chapter, visible to everybody, can we also have the ?private? trackers in parallel to it, not visible to users outside FI-WARE? - Why should we have EPICs/features in the chapter backlog, aren?t they already in the FI-WARE Wiki backlog? I believe we could keep the single chapter backlogs private and devoted to the user-stories tracker(s) Did I mix something wrongly? Maybe I was the source of confusion because I have used the term "backlog" where I should have used the term "tracker" to be more accurate. Essentially, the model we are currently deploying is like this: * Full description of entries linked to the different FI-WARE Chapter Backlogs is posted in the public Wiki (MediaWiki instance linked to the FI-WARE project in FusionForge). Note that everyone in the world is able to read the Public Wiki. Only members of the FI-WARE project in FusionForge (and this include UC projects) can edit its contents. * Full description of entries linked to the Unclassified Enablers Backlog is also posted in the public Wiki, therefore accessible by anyone in the world. Again, only members of the FI-WARE project in FusionForge can edit its contents. * The "FI-WARE Feature Request" tracker is accessible to anyone in the world and also anyone in the world may create tickets. However, they cannot perform other operations on the tracker (assigning tickets to people, etc) . Tickets should include a link to a Wiki where the proposed backlog entry is fully described. * There will be a tracker "Backlog" at each "FI-WARE " project used for managing lifecycle of entries in that FI-WARE Chapter Backlog (at least, Themes, Epics and Features). Everyone in the world can read tickets in that tracker but cannot create tickets nor change them. * FI-WARE Chapter teams will be able to also create tickets linked to User-Stories at the "Backlog" tracker at each "FI-WARE " project in FusionForge. In that case, User Stories will be also publicly accessible. However, they are free to create another tracker(s) to deal with management of User-Stories separately from Themes/Epics/Features. Then they can configure these user-story oriented trackers to be private (just accessible for members of the "FI-WARE " project in FusionForge) The only point that is a bit risky is that we are allowing members of the FI-WARE project at FusionForge to edit the Wiki, and this includes the UC projects ... and we are allowing this not only for parts of the Wiki that clearly UC projects need to edit (e.g., the Unclassified Enablers Backlog part) but other parts as well. If we don't trust they will not change anything that we maintain (Product Vision, Tutorials, etc) then we will probably had to combine two Wikis, I'm afraid ... Why do we want to keep a "Backlog" tracker at each "FI-WARE " project in FusionForge, if full description of entries of that FI-WARE Chapter Backlog are already recorded in the Wiki ? Aren't we repeating things twice (record the entry in the Wiki and in the tracker) ? Well ... because of the following: * The tracker helps us to handle assignments of entries to people in a more easy and flexible way * The way you keep track of history and trace changes in a ticketing system is more convenient than in a wiki. You may even monitor tickets or even entire trackers so that changes are reported to you via email. * You can more easily attach documents to tickets as well as establish "conversations" around tickets * You can link tickets to tasks, thus applying Agile methodology beyond management of backlogs * Personally, I believe it will be easier to present backlogs to reviewers and the external world browsing trackers than browsing wiki pages. Best regards, -- Juanjo 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? 29 settembre 2011 20:11 A: Alex Glikson Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: Re: [Fiware-wpl] Fw: Request to Join Project FI-WARE Cloud Not sure you can add a message in the rejection ... I'll ask. Nevertheless, I will send an email to the FI-PPP AB mailing list (where representatives of all UC projects are registered) telling them that we will reject any request to join to projects different than the FI-WARE project. Probably they are asking to join because they need to be able to "read" the trackers linked to Chapter backlogs. But this is something we will allow anyone world-wide (that is my recall on the matter when we discussed it, but it's also what makes sense to me), therefore they will be able to monitor. What they won't be able to do (and they shouldn't) is to submit tickets directly to the Chapter backlogs. Some people may argue that we shouldn't even allow "observers" to read our chapter backlogs ... Well, I believe that publishing Epics/Features is not a big deal and we have to keep them publicly readable. I would even add that not doing so could bring some troubles to us in front of the EC (I believe it would not comply with what we committed in the DoW) On the other hand, I would be more flexible regarding User-stories and leave to chapter partners the decision about keeping user-stories in separate trackers (either a single one or one per GE) or not. It would then be feasible to keep such user-story oriented trackers fully private. The trade off, of course, is that such approach would mean more administrative burden for the chapter partners, but if they wish to live with that, it's fine to me. 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 19:33, Alex Glikson wrote: Dear Juanjo, Is there a way to reject a request to join a project with a comment/explanation? I've rejected the request below, but wanted to clarify that GE requests should be opened against the 'root' FI-WARE project. Regards, Alex P.S. copying WP leads, as similar questions are likely to arise for their WP projects in Forge ----- Forwarded by Alex Glikson/Haifa/IBM on 29/09/2011 08:29 PM ----- From: noreply at forge.fi-ware.eu To: Alex Glikson/Haifa/IBM at IBMIL Date: 29/09/2011 05:06 PM Subject: Request to Join Project FI-WARE Cloud ________________________________ Nazila Gol mohammadi has requested to join your project. You can approve this request here: https://forge.fi-ware.eu/project/admin/users.php?group_id=14 Comments by the user: I need to join to this project in order to submit GE request by Finest ________________________________ 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:part1.05040805.06010600 at tid.es]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 677 bytes Desc: not available URL: From jhierro at tid.es Fri Sep 30 08:05:05 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 30 Sep 2011 08:05:05 +0200 Subject: [Fiware-wpl] Tutorials for configuragion of Backlog Management trackers in chapters Message-ID: <4E855C11.9000600@tid.es> Brief update: I'm still working on it, though I expect them to be before afternoon. Be patient. I do not want to make any mistake giving instruction about creation of trackers. In the meantime, just try to upload all backlog entries in your chapter section on the Wiki. You should have everything for that. 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 Sep 30 08:07:44 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 30 Sep 2011 08:07:44 +0200 Subject: [Fiware-wpl] IMPORTANT UPDATE: Requests for joining the chapter projects by UC projects Message-ID: <4E855CB0.6010506@tid.es> Hi, You may be receiving requests for joining the chapter projects by people from UC projects. Despite I told you yesterday you should reject them, please hold them. In checking this now, but maybe the best approach will be that of allowing them to join but with a very restricted role. This will be explained in the tutorials. 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 pascal.bisson at thalesgroup.com Fri Sep 30 09:13:09 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 30 Sep 2011 09:13:09 +0200 Subject: [Fiware-wpl] IMPORTANT UPDATE: Requests for joining the chapter projects by UC projects In-Reply-To: <4E855CB0.6010506@tid.es> References: <4E855CB0.6010506@tid.es> Message-ID: <3231_1317366792_4E856C08_3231_18215_1_53661005-8a92-4873-b5d0-e9279a8d7eec@THSONEA01HUB03P.one.grp> Dear Juanjo, At last GA we were told not to hold them, yesterday as well and now you told us to hold them and are even in favor to allow them to join. For me this is an important topic we should discuss at our next WPL/WPA audio. This to discuss the pros and cons and decide accordingly and collectively. End up with shared agreement on the topic. I don't want us to go too fast on this. ...We should go for a well structured and organized process both internally (with FI-WARE) and with Use Case projects. If not we will go into chaos and this is something we should absolutely avoid. This even more that in my view we have important things to discuss and collectively review before having them exposed (this is especially true as I said at GA for what concerns the Fi-WARE features backlog where there is still a number of concerns at least from my side (also the one of Daniel as WPA or WP8) but also from Alex and maybe some others ...). This just to say we need next WPL/WPA audio to discuss and align on all these important topics. Regards, Pascal -----Message d'origine----- De?: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy??: vendredi 30 septembre 2011 08:08 ??: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet?: [Fiware-wpl] IMPORTANT UPDATE: Requests for joining the chapter projects by UC projects Hi, You may be receiving requests for joining the chapter projects by people from UC projects. Despite I told you yesterday you should reject them, please hold them. In checking this now, but maybe the best approach will be that of allowing them to join but with a very restricted role. This will be explained in the tutorials. 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 From jhierro at tid.es Fri Sep 30 11:14:44 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 30 Sep 2011 11:14:44 +0200 Subject: [Fiware-wpl] IMPORTANT UPDATE: Requests for joining the chapter projects by UC projects In-Reply-To: <3231_1317366792_4E856C08_3231_18215_1_53661005-8a92-4873-b5d0-e9279a8d7eec@THSONEA01HUB03P.one.grp> References: <4E855CB0.6010506@tid.es> <3231_1317366792_4E856C08_3231_18215_1_53661005-8a92-4873-b5d0-e9279a8d7eec@THSONEA01HUB03P.one.grp> Message-ID: <4E858884.30507@tid.es> Pascal, Calm down. First, let me clarify that what we agreed was that they will be able to "read" our backlogs (at least to the Feature level). But their access would be "read-only" (that is, not able to issue tickets nor manage them, of course) Indeed, they have this "read" access already just by logging into the Wiki linked to the FI-WARE project in FusionForge. This is pragmatic but I would even say that "a must". Actually, UC projects have mentioned that they need to get access to the "official FI-WARE backlog" because they want to avoid repeating work and, for example, submit a request on a feature they realize we are taking care of already. That's a pretty reasonable request. We are members of a program targeted to achieve a clear goal . Creating unnecessary barriers to cooperation between FI-PPP projects doesn't have any sense. What we are right now analyzing whether we can play with member roles (you can assign roles to members of a FusionForge project) and create a "User" role with "read-only" privileges on tracker. I wanted to keep "on hold" any request for joining a project until we finish that analysis (today). That's all. If we find that it's not feasible, we will announce that we will reject them all (I would send an email to the FI-PPP AB list) and will execute that action. 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 30/09/11 09:13, BISSON Pascal wrote: > Dear Juanjo, > > At last GA we were told not to hold them, yesterday as well and now you told us to hold them and are even in favor to allow them to join. > > For me this is an important topic we should discuss at our next WPL/WPA audio. > > This to discuss the pros and cons and decide accordingly and collectively. End up with shared agreement on the topic. > > I don't want us to go too fast on this. ...We should go for a well structured and organized process both internally (with FI-WARE) and with Use Case projects. If not we will go into chaos and this is something we should absolutely avoid. > > This even more that in my view we have important things to discuss and collectively review before having them exposed (this is especially true as I said at GA for what concerns the Fi-WARE features backlog where there is still a number of concerns at least from my side (also the one of Daniel as WPA or WP8) but also from Alex and maybe some others ...). > > This just to say we need next WPL/WPA audio to discuss and align on all these important topics. > > Regards, > > Pascal > > > > -----Message d'origine----- > De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro > Envoy? : vendredi 30 septembre 2011 08:08 > ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Objet : [Fiware-wpl] IMPORTANT UPDATE: Requests for joining the chapter projects by UC projects > > Hi, > > You may be receiving requests for joining the chapter projects by > people from UC projects. > > Despite I told you yesterday you should reject them, please hold > them. In checking this now, but maybe the best approach will be that > of allowing them to join but with a very restricted role. This will be > explained in the tutorials. > > 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 From pascal.bisson at thalesgroup.com Fri Sep 30 13:35:22 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 30 Sep 2011 13:35:22 +0200 Subject: [Fiware-wpl] IMPORTANT UPDATE: Requests for joining the chapter projects by UC projects In-Reply-To: <4E858884.30507@tid.es> References: <4E855CB0.6010506@tid.es> <3231_1317366792_4E856C08_3231_18215_1_53661005-8a92-4873-b5d0-e9279a8d7eec@THSONEA01HUB03P.one.grp> <4E858884.30507@tid.es> Message-ID: <15916_1317382524_4E85A97C_15916_4154_1_390c631b-fff3-436d-bd91-a338217f1146@THSONEA01HUB03P.one.grp> Dear Juanjo, Ok it clarifies somehow what you intend to do for what concerns Use Case Projects. In the meantime will wait for your email for final decision proposed according to analysis you will have performed from your side. One more clarification I'd like to have from your side on this would visibility of our document to the outside world (i.e. anyone who has registered to the Fusion Forge - This especially for what concerns Wiki Content and so features backlog - I have no problem to have it shared with UC projects but for what concerns outside world I think we should proceed with caution and make informed decision on a shared and agreed basis - not only at the level of each AT but also at the level of the Project itself). This is was more or less the sense of my previous email. Sorry if you didn't get it right first. Hope this would have clarified the issue seen and help you to provide me/us with your answer. Last but not least I can only regret the fact that our WPL/WPA has been cancelled as it would have been an opportunity to clarify on this topic and others (see previous email from Daniel as WP8 Architect on EPICS vs user stories to figure out what to do after having look at what says Agile Methodology. To be on the safer side I would suggest to agree on the fact we are using a methodology inspired from Agile ...). So waiting for next WPL/WPA audio to further discuss this and others. Hearing from you. Regards, Pascal -----Message d'origine----- De?: Juanjo Hierro [mailto:jhierro at tid.es] Envoy??: vendredi 30 septembre 2011 11:15 ??: BISSON Pascal Cc?: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; GIDOIN Daniel; jhierro >> "Juan J. Hierro" Objet?: Re: [Fiware-wpl] IMPORTANT UPDATE: Requests for joining the chapter projects by UC projects Pascal, Calm down. First, let me clarify that what we agreed was that they will be able to "read" our backlogs (at least to the Feature level). But their access would be "read-only" (that is, not able to issue tickets nor manage them, of course) Indeed, they have this "read" access already just by logging into the Wiki linked to the FI-WARE project in FusionForge. This is pragmatic but I would even say that "a must". Actually, UC projects have mentioned that they need to get access to the "official FI-WARE backlog" because they want to avoid repeating work and, for example, submit a request on a feature they realize we are taking care of already. That's a pretty reasonable request. We are members of a program targeted to achieve a clear goal . Creating unnecessary barriers to cooperation between FI-PPP projects doesn't have any sense. What we are right now analyzing whether we can play with member roles (you can assign roles to members of a FusionForge project) and create a "User" role with "read-only" privileges on tracker. I wanted to keep "on hold" any request for joining a project until we finish that analysis (today). That's all. If we find that it's not feasible, we will announce that we will reject them all (I would send an email to the FI-PPP AB list) and will execute that action. 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 30/09/11 09:13, BISSON Pascal wrote: > Dear Juanjo, > > At last GA we were told not to hold them, yesterday as well and now you told us to hold them and are even in favor to allow them to join. > > For me this is an important topic we should discuss at our next WPL/WPA audio. > > This to discuss the pros and cons and decide accordingly and collectively. End up with shared agreement on the topic. > > I don't want us to go too fast on this. ...We should go for a well structured and organized process both internally (with FI-WARE) and with Use Case projects. If not we will go into chaos and this is something we should absolutely avoid. > > This even more that in my view we have important things to discuss and collectively review before having them exposed (this is especially true as I said at GA for what concerns the Fi-WARE features backlog where there is still a number of concerns at least from my side (also the one of Daniel as WPA or WP8) but also from Alex and maybe some others ...). > > This just to say we need next WPL/WPA audio to discuss and align on all these important topics. > > Regards, > > Pascal > > > > -----Message d'origine----- > De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro > Envoy? : vendredi 30 septembre 2011 08:08 > ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Objet : [Fiware-wpl] IMPORTANT UPDATE: Requests for joining the chapter projects by UC projects > > Hi, > > You may be receiving requests for joining the chapter projects by > people from UC projects. > > Despite I told you yesterday you should reject them, please hold > them. In checking this now, but maybe the best approach will be that > of allowing them to join but with a very restricted role. This will be > explained in the tutorials. > > 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