From juanjose.hierro at telefonica.com Fri Oct 10 01:16:41 2014 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Fri, 10 Oct 2014 01:16:41 +0200 Subject: [Fiware-friendly-testing-coordination] Start of activities linked to friendly testing of FIWARE by FEMTO-ST In-Reply-To: <54334D9E.1040006@telefonica.com> References: <54334D9E.1040006@telefonica.com> Message-ID: <54371759.5030904@telefonica.com> Dear Bruno, The following are the instructions to follow to start the activities in the FIWARE Friendly Testing Task Force. Please confirm urgently that this is ok. This Task Force is targeted to identify the issues that any developer may find when they try to approach FIWARE for the first time, even if (s)he hasn't had the opportunity to attend any of our Bootcamps or Technical Workshops. The difference here is that you are a friendly tester, that is, you will report and properly document the issues that you find (while other developers may decide to give up when they find the first issue). This will allow us to understand what has to be fixed. The Task Force will be organized in two phases: * In a first phase of the Task Force, which we expect (hopefully :-) that may last one or one and a half month, you will focus on: * Regarding the Cloud, Store, Mashup-Wirecloud, Data and Account Management portals available on the FIWARE Lab (http://lab.fiware.org) * Make sure that everything works fine and it is intuitive enough * Make sure that there is enough helpful and accurate documentation as well as video tutorials * Regarding individual FIWARE components (referred as FIWARE GEris which is the acronym of FIWARE Generic Enabler reference implementation) published in the FIWARE Catalogue (http://catalogue.fiware.org): * In a first step, make sure that their software can be downloaded, deployed, configured and used locally by a regular developer, using info available on the FIWARE Catalogue. * In a second step, make sure that they can be deployed and configured as dedicated instances on the FIWARE Lab (using dedicated VM images, recipes and blueprints) and both dedicated and global instances running on the FIWARE Lab can be used by a regular developer, using info available on the FIWARE Catalogue and the resources available on the FIWARE Lab * In a second phase (since end of first phase until the end of the year), you will focus on: * Develop and document the open source code for example applications you will be asked to develop (to be defined during the first phase) * Help to improve existing documentation and, overall, tutorials (written or video tutorials) I won't give you more details on how things can be done because part of your job is to try what third developers will try with not much more info than the above :-) Whenever you identify a problem to be fixed or a suggestion/request for an enhancement, please drop an email to the following help-desk addresses: * fiware-lab-help at lists.fi-ware.org: to be used when the problem/enhancement to be reported has to do with the FIWARE Lab environment * problem/enhancements on functionalities offered through any of the FIWARE Lab portals: Cloud, Store, Mashup, Account, Data, Help&Info * problem/enhancements trying to deploy (instantiate) and configure FIWARE GEri on the FIWARE Lab using Cloud deployment tools (creation of VM images with preinstalled GEris, usage of recipes, usage of blueprint templates) * problem/enhancements trying to get access to a FIWARE GEri instance available on the FIWARE Lab: either a private dedicated instance previously deployed by you or a global instance available for all developers * fiware-tech-help at lists.fi-ware.org: to be used when the problem/enhancement to be reported has to do with individual FIWARE components * downloading, installing and configuring a FIWARE GEri on your local premises, using available documentation * downloading, installing and configuring a FIWARE GEri on a VM previously deployed on the FIWARE Lab * getting access and programming with the APIs provided by FIWARE GEri instances you have deployed (you are asked to try the tutorials provided and then event try something on your own) Nevertheless, don't get too much worried about what mailing list you should use (third developers may also not perform the best choice ;-) We will deal with that and make sure things are handled properly. For your info, any time you send a message to any of the above channels, a ticket will be created in a JIRA HelpDesk ticketing system. Then the 1st and 2nd level support teams will analyze it, in the most trivial cases respond directly your request for help and if they don't know how to do it, they will pass the ticket to someone from the FIWARE development teams who will take care of it. You will see that the HelpDesk may answer you that you have asked to solve a problem they believe should be answered on StackOverflow for the sake of other programmers. If so, please formulate your question there. We have decided to use StackOverflow as our forum for developers. There are a number of tags, the more general "fiware" tag but also tags associated to the most popular FIWARE GEris like "fiware-orion", "fiware-wirecloud", you can use to ask question about FIWARE on StackOverflow. Of course, after some time, once you get more experienced using FIWARE, you may decide to go for asking the question directly on StackOverflow. Fernando L?pez will coordinate all the tests dealing with the Cloud, Store, Mashup-Wirecloud, Data and Account Management portals available on the FIWARE Lab. Leandro Guill?n will coordinate all the tests dealing with individual FIWARE components published on the FIWARE Catalogue. You may ask any question you may have by sending a message to fiware-friendly-testing-coordination at lists.fi-ware.org. If you don't get any answer, please contact Fernando and Leandro directly (they are in the mailing list though). If you believe your question maybe of interest to all friendly testers, not just your team, please send an email to fiware-friendly-testing at lists.fi-ware.org Regarding the tests to be carried out by FEMTO-ST, either Fernando or Leandro will soon contact you with specific instructions. We understand that, as discussed, you will involve two developers in the Task Force (the two whose CVs you forwarded to us). Some last remarks to pass to members of your team: * We know that you are a experienced developer. Therefore, you may infer how some little issue you find can be overcome. However, please report that issue so that we can fix it. Take into account that some third developers may not be so much experienced, therefore they may not be able to overcome the same issue. Of course, don't wait for the issue to get solved in order to continue with testing. * Issue your reports in english and try to provide as much details as possible to make our task easier and solve issues as fast as possible. * Any typo or improvement on language of available documentation is welcome. * Don't focus just on issues/problems. Any suggestion for enhancement is welcome. * If you are blocked at any point and you don't know how to continue, please let us know. Send an email to fiware-friendly-testing-coordination at lists.fi-ware.org If you believe your question maybe of interest to all friendly testers, send it to fiware-friendly-testing at lists.fi-ware.org. Let's rock !! Best regards, -- Juanjo Hierro ------------- Telefonica - Product Development and Innovation (PDI) website: www.tid.es email: juanjose.hierro at telefonica.com twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.org facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o -------------- next part -------------- An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Fri Oct 10 04:14:05 2014 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Fri, 10 Oct 2014 04:14:05 +0200 Subject: [Fiware-friendly-testing-coordination] Start of activities linked to friendly testing of FIWARE In-Reply-To: <54373606.1060903@onesource.pt> References: <543140FF.2020201@zhaw.ch> <5431A8B7.3020101@gmail.com> <5431C4E5.8000806@onesource.pt> <54334D9E.1040006@telefonica.com> <54338EDA.9090501@onesource.pt> <54373606.1060903@onesource.pt> Message-ID: <543740ED.1070704@telefonica.com> Dear Paulo, I have just added the people of your team to the fiware-friendly-testing mailing list. PLEASE stick to the concrete friendly testing plan of GEris and functionality of the FIWARE Lab that was assigned to your team. That was specified in the first message that I sent to you (subject "Start of activities linked to friendly testing of FIWARE") I frankly got scared when I read your statement "Meanwhile we started browsing the public websites and documentation, performing registration and downloading and performing ad-hoc experiments with a few enablers. Similar work has been started for the Labs, with some experiments performed by Patricio". If we do not coordinate the actions and stick to the distribution of work, we will end in chaos and replicating efforts among the different teams. Bear in mind that there are other teams different than yours also involved in this Task Force. We have carefully designed a distribution of the testing activities to be performed. Best regards, -- Juanjo ------------- Telefonica - Product Development and Innovation (PDI) website: www.tid.es email: juanjose.hierro at telefonica.com twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.org facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 10/10/14 03:27, Paulo Simoes wrote: Dear Fernando, all, Attached please find the names and contacts of the complete team. As for the PhC, I propose we try to reserve a weekly slot for regular PhC. Please provide 2 or 3 alternatives, so we can match them with our own availabilities. Meanwhile we started browsing the public websites and documentation, performing registration and downloading and performing ad-hoc experiments with a few enablers. Similar work has been started for the Labs, with some experiments performed by Patricio. We plan to create a journal to register all our findings and recommendations. Probably JIRA will be the right tool for this (with adequate configurations), and the question would be: a) to create this journal in the FIWARE JIRA, with support from the persons in charge of FIWARE's JIRA. b) to create a separate JIRA deployment at OneSource, also made accessible to selected FIWARE people. Meanwhile we drafted a first proposal for our workplan for Phase 1 (October 7 to November 14): Week 1 (starting 7/October): - registration, study of available documentation, downloads, ad-hoc local deployments, ad-hoc creation of virtual machines at the lab. Week 2-Week 3 (Phase 1, Step 1): - (week 2:) definition of KPIs, draft user stories, identification of all the GEris to cover in Phase 1, definition of structured outputs of our testing, definition of the roadmap for each of the 4 testers. - (week 2-3) testing of the enablers in local computers. - (week 2-3) testing of basic Lab setups Week 4-Week 5 (Phase 1, Step 2): - (week 4-5) testing of the enablers in Lab deployments. - (week 4-5) testing of advanced Lab setups - (end of week 5): production of an internal and interim deliverable reporting the work done so far (in addition to the journals, which are important to provide early feedback to the FIWARE team). Phase 2 (14/November to 31/December): - Development and documentation of open source code for example applications. (to be defined during the first phase) - Helping to improve existing documentation and, overall, tutorials (written or video tutorials) Regards, -- PS On 08/10/14 10:24, FERNANDO LOPEZ AGUILAR wrote: Dear Simoes, Like Juanjo mentioned in the previous email, I was coordinating the activities regarding the Cloud friendly testing. I suppose, that the person who will be working on it, should be Patricio, correct me if I am wrong. When the complete team is defined we will define the way of working and the different tasks to be developed in a PhC. Best regards, Fernando.- De: Paulo Simoes > Organizaci?n: OneSource Lda. Fecha: Tuesday 7 October 2014 07:57 Para: JUAN JOSE HIERRO SUREDA >, "Thomas.Bohnert at zhaw.ch" >, "luis.cordeiro at onesource.pt" > CC: fla >, Leandro Guillen >, MIGUEL CARRILLO PACHECO >, MANUEL ESCRICHE VICENTE > Asunto: Re: Start of activities linked to friendly testing of FIWARE Dear Juanjo, I confirm your proposal is fine with us. We will start this process immediately. Today we will organize the work internally and by the end of the day we'll provide more feedback on the team organization and on how we'll conduct our work and reporting. Regards, -- Paulo Sim?es On 07/10/14 03:19, Juanjo Hierro wrote: Dear Paulo, Let's start to work involving the resources you have listed plus one additional. We would like to involve 4 engineers. We understand that project management activities are not strictly necessary. There will be people from FIWARE assigned to coordination. Nevertheless, if you want to charge a bit % on those type of activities is fine. Since it is not true that we will spend exactly 4*3 = 12 PMs starting now until end of the year, I understand that we may go for allocating that effort of 9 PMs and assume that the % of coordination is part of that. Consequently, we would have an overall funding assigned of 6.000 ? * 12 PMs = 72.000 ?. Note that this would require that you add a fourth developer in a matter of few days, preferably this week. Is it fine with you? If so, the following are the instructions to follow to start the activity. Please confirm urgently that this is ok. This Task Force is targeted to identify the issues that any developer may find when they try to approach FIWARE for the first time, even if (s)he hasn't had the opportunity to attend any of our Bootcamps or Technical Workshops. The difference here is that you are a friendly tester, that is, you will report and properly document the issues that you find (while other developers may decide to give up when they find the first issue). This will allow us to understand what has to be fixed. The Task Force will be organized in two phases: * In a first phase of the Task Force, which we expect (hopefully :-) that may last one or one and a half month, you will focus on: * Regarding the Cloud, Store, Mashup-Wirecloud, Data and Account Management portals available on the FIWARE Lab (http://lab.fiware.org) * Make sure that everything works fine and it is intuitive enough * Make sure that there is enough helpful and accurate documentation as well as video tutorials * Regarding individual FIWARE components (referred as FIWARE GEris which is the acronym of FIWARE Generic Enabler reference implementation) published in the FIWARE Catalogue (http://catalogue.fiware.org): * In a first step, make sure that their software can be downloaded, deployed, configured and used locally by a regular developer, using info available on the FIWARE Catalogue. * In a second step, make sure that they can be deployed and configured as dedicated instances on the FIWARE Lab (using dedicated VM images, recipes and blueprints) and both dedicated and global instances running on the FIWARE Lab can be used by a regular developer, using info available on the FIWARE Catalogue and the resources available on the FIWARE Lab * In a second phase (since end of first phase until the end of the year), you will focus on: * Develop and document the open source code for example applications you will be asked to develop (to be defined during the first phase) * Help to improve existing documentation and, overall, tutorials (written or video tutorials) I won't give you more details on how things can be done because part of your job is to try what third developers will try with not much more info than the above :-) Whenever you identify a problem to be fixed or a suggestion/request for an enhancement, please drop an email to the following help-desk addresses: * fiware-lab-help at lists.fi-ware.org: to be used when the problem/enhancement to be reported has to do with the FIWARE Lab environment * problem/enhancements on functionalities offered through any of the FIWARE Lab portals: Cloud, Store, Mashup, Account, Data, Help&Info * problem/enhancements trying to deploy (instantiate) and configure FIWARE GEri on the FIWARE Lab using Cloud deployment tools (creation of VM images with preinstalled GEris, usage of recipes, usage of blueprint templates) * problem/enhancements trying to get access to a FIWARE GEri instance available on the FIWARE Lab: either a private dedicated instance previously deployed by you or a global instance available for all developers * fiware-tech-help at lists.fi-ware.org: to be used when the problem/enhancement to be reported has to do with individual FIWARE components * downloading, installing and configuring a FIWARE GEri on your local premises, using available documentation * downloading, installing and configuring a FIWARE GEri on a VM previously deployed on the FIWARE Lab * getting access and programming with the APIs provided by FIWARE GEri instances you have deployed (you are asked to try the tutorials provided and then event try something on your own) Nevertheless, don't get too much worried about what mailing list you should use (third developers may also not perform the best choice ;-) We will deal with that and make sure things are handled properly. For your info, any time you send a message to any of the above channels, a ticket will be created in a JIRA HelpDesk ticketing system. Then the 1st and 2nd level support teams will analyze it, in the most trivial cases respond directly your request for help and if they don't know how to do it, they will pass the ticket to someone from the FIWARE development teams who will take care of it. You will see that the HelpDesk may answer you that you have asked to solve a problem they believe should be answered on StackOverflow for the sake of other programmers. If so, please formulate your question there. We have decided to use StackOverflow as our forum for developers. There are a number of tags, the more general "fiware" tag but also tags associated to the most popular FIWARE GEris like "fiware-orion", "fiware-wirecloud", you can use to ask question about FIWARE on StackOverflow. Of course, after some time, once you get more experienced using FIWARE, you may decide to go for asking the question directly on StackOverflow. Fernando L?pez will coordinate all the tests dealing with the Cloud, Store, Mashup-Wirecloud, Data and Account Management portals available on the FIWARE Lab. Leandro Guill?n will coordinate all the tests dealing with individual FIWARE components published on the FIWARE Catalogue. You may ask any question you may have by sending a message to fiware-friendly-testing-coordination at lists.fi-ware.org. If you don't get any answer, please contact Fernando and Leandro directly (they are in the mailing list though). Regarding the tests to be done by Bitergia, we would like that your three developers focus on the following tasks: * Patricio Batista: testing of FIWARE Cloud functionalities on the FIWARE Lab * Jo?o Gon?alves: testing GEris of the Advanced Web-based UI chapter of FIWARE published on the FIWARE Catalogue (remember the two consecutive steps to be performed when carrying out testing of individual FIWARE components) * Hugo Fonseca: testing GEris of the Kurento FIWARE GEri published on the FIWARE Catalogue (remember the two consecutive steps to be performed when carrying out testing of individual FIWARE components) * OneSource developer 4: testing of the Complex Event Processing - ProTON GEris published on the FIWARE Catalogue (remember the two consecutive steps to be performed when carrying out testing of individual FIWARE components) Some last remarks: * We know that you are a experienced developer. Therefore, you may infer how some little issue you find can be overcome. However, please report that issue so that we can fix it. Take into account that some third developers may not be so much experienced, therefore they may not be able to overcome the same issue. Of course, don't wait for the issue to get solved in order to continue with testing. * Issue your reports in english and try to provide as much details as possible to make our task easier and solve issues as fast as possible. * Any typo or improvement on language of available documentation is welcome. * Don't focus just on issues/problems. Any suggestion for enhancement is welcome. * If you are blocked at any point and you don't know how to continue, please let us know. Send an email to fiware-friendly-testing-coordination at lists.fi-ware.org Let's rock !! Best regards, -- Juanjo Hierro ------------- Telefonica - Product Development and Innovation (PDI) website: www.tid.es email: juanjose.hierro at telefonica.com twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.org facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 06/10/14 00:23, Paulo Simoes wrote: On 05/10/14 21:23, Thomas Michael Bohnert wrote: Paulo, Can you add some info about the staff profiles that you plan to assign to this important task? (Software developers and System Engineers/Operators would be needed - ideally experiences ones). Thanks, Thomas Dear Thomas, all, (please excuse the long reply) The final selection of staff to involve still depends on assessing all the required skills and technologies that are required to use the FI-WARE components. Nevertheless, next I provide the profiles of three people that immediately came to my mind and may be assigned to the project. Hugo Fonseca. Before joining OneSource he worked for several years in the development of RCS and WebRTC platforms, including software design and development. Before that he was involved in quality assurance and software testing (mostly for unified communications suites and mobile banking applications). At OneSource Hugo is mostly involved with one of our clients, focusing on improving the security, QoS/QoE and functionalities of the white-label communications suites this client provides to several telcos worldwide (cloud-based managed PBX solutions, contact centers and rich communication suites for enterprise markets). Jo?o Gon?alves is mostly a software engineer. One of the most recent applications he has developed is an advanced live video-to-video (v2v) communications platform, integrated with operator?s resource management frameworks, that in the context of the Livecity PSP Project is being used in several applications with real users: telemedicine, support of first responder teams, education and remotely provided public services. In addition to the core and the plug-in interfaces of the v2v platform, Jo?o also designed and assembled the wearable v2v device that is being used by first responder teams in Ireland and Germany. This v2v platform was awarded as the Best Demonstration at FIA-2014 (Athens). Patricio Batista started his career as a network and systems administrator. Later on he evolved to systems design and integration. He is quite experienced on deploying, integrating, configuring and managing distributed systems, as well as on virtualized and cloud-based infrastructures. It is difficult to mention all the projects he has been involved in, but he has, for instance, designed a platform that one of our clients uses to receive and analyze in real-time (for risk and fraud prevention purposes) tenths of thousands of credit card transactions per second. In addition to people with these or similar profiles, we also intend to involve a project manager with experience on FP7 Projects, such as Bruno Sousa or Lu?s Cordeiro. Bruno Sousa owns a PhD in Information Science and Technology, and he authored tenths of research papers in journals, book chapters and conference proceedings. He has participated in European R&D projects such as FP6 EuQos, FP6 WEIRD, FP7 CityFlow, FP7 MCN and FP7 SALUS. Before returning to the University to get his PhD Bruno has led for several years the development and integration of backoffice applications for ?La Redoute/Redcats?, a large European home-shopping retailer. Luis Cordeiro has been actively involved in European research projects such as FP6 EUQOS, FP6 WEIRD, FP7 LiveCity, FP7 CityFlow, FP7 SALUS and FP7 Mobile Cloud Networks. He has several publications in journals, book chapters, conferences and Internet Drafts in the areas of Signaling, end-to-end QoS and Network Management. In addition to those research activities, he also led tenths of application development projects. Regards, -- Paulo ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o -------------- next part -------------- An HTML attachment was scrubbed... URL: From psimoes at onesource.pt Fri Oct 10 07:58:44 2014 From: psimoes at onesource.pt (Paulo Simoes) Date: Fri, 10 Oct 2014 06:58:44 +0100 Subject: [Fiware-friendly-testing-coordination] Start of activities linked to friendly testing of FIWARE In-Reply-To: <543740ED.1070704@telefonica.com> References: <543140FF.2020201@zhaw.ch> <5431A8B7.3020101@gmail.com> <5431C4E5.8000806@onesource.pt> <54334D9E.1040006@telefonica.com> <54338EDA.9090501@onesource.pt> <54373606.1060903@onesource.pt> <543740ED.1070704@telefonica.com> Message-ID: <54377594.9070704@onesource.pt> Dear Juanjo, I understand your point, and we will stick to the concrete testing plan that was assigned to us (in fact the we did not diverge so much from the plan as my sentence might suggest. Each of the testers was focused on assigned components - they were just given some time to better understand what was being asked them to do). Regards, -- PS On 10/10/14 03:14, Juanjo Hierro wrote: > Dear Paulo, > > I have just added the people of your team to the > fiware-friendly-testing mailing list. > > * PLEASE stick to the concrete friendly testing plan of GEris and > functionality of the FIWARE Lab**that was assigned to your team.** > That was specified in the first message that I sent to you (subject > "Start of activities linked to friendly testing of FIWARE")* > > I frankly got scared when I read your statement "Meanwhile we > started browsing the public websites and documentation, performing > registration and downloading and performing ad-hoc experiments with a > few enablers. Similar work has been started for the Labs, with some > experiments performed by Patricio". > > If we do not coordinate the actions and stick to the distribution of > work, we will end in chaos and replicating efforts among the different > teams. Bear in mind that there are other teams different than yours > also involved in this Task Force. We have carefully designed a > distribution of the testing activities to be performed. > > Best regards, > > -- Juanjo > ------------- > Telefonica - Product Development and Innovation (PDI) > website:www.tid.es > email:juanjose.hierro at telefonica.com > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Coordinator > and Chief Architect > > You can follow FI-WARE at: > website:http://www.fi-ware.org > facebook:http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter:http://twitter.com/FIware > linkedIn:http://www.linkedin.com/groups/FIWARE-4239932 > On 10/10/14 03:27, Paulo Simoes wrote: >> >> Dear Fernando, all, >> >> Attached please find the names and contacts of the complete team. >> >> As for the PhC, I propose we try to reserve a weekly slot for regular >> PhC. >> Please provide 2 or 3 alternatives, so we can match them with our own >> availabilities. >> >> Meanwhile we started browsing the public websites and documentation, >> performing registration and downloading and performing ad-hoc >> experiments with a few enablers. Similar work has been started for >> the Labs, with some experiments performed by Patricio. >> >> We plan to create a journal to register all our findings and >> recommendations. Probably JIRA will be the right tool for this (with >> adequate configurations), and the question would be: >> >> a) to create this journal in the FIWARE JIRA, with support from the >> persons in charge of FIWARE's JIRA. >> b) to create a separate JIRA deployment at OneSource, also made >> accessible to selected FIWARE people. >> >> Meanwhile we drafted a first proposal for our workplan for Phase 1 >> (October 7 to November 14): >> >> Week 1 (starting 7/October): >> - registration, study of available documentation, downloads, ad-hoc >> local deployments, ad-hoc creation of virtual machines at the lab. >> >> Week 2-Week 3 (Phase 1, Step 1): >> - (week 2:) definition of KPIs, draft user stories, identification of >> all the GEris to cover in Phase 1, definition of structured outputs >> of our testing, definition of the roadmap for each of the 4 testers. >> - (week 2-3) testing of the enablers in local computers. >> - (week 2-3) testing of basic Lab setups >> >> Week 4-Week 5 (Phase 1, Step 2): >> - (week 4-5) testing of the enablers in Lab deployments. >> - (week 4-5) testing of advanced Lab setups >> - (end of week 5): production of an internal and interim deliverable >> reporting the work done so far (in addition to the journals, which >> are important to provide early feedback to the FIWARE team). >> >> Phase 2 (14/November to 31/December): >> - Development and documentation of open source code for example >> applications. >> (to be defined during the first phase) >> - Helping to improve existing documentation and, overall, tutorials >> (written or video tutorials) >> >> Regards, >> >> -- PS >> >> On 08/10/14 10:24, FERNANDO LOPEZ AGUILAR wrote: >>> Dear Simoes, >>> >>> Like Juanjo mentioned in the previous email, I was coordinating the >>> activities regarding the Cloud friendly testing. I suppose, that the >>> person who will be working on it, should be Patricio, correct me if >>> I am wrong. When the complete team is defined we will define the way >>> of working and the different tasks to be developed in a PhC. >>> >>> Best regards, >>> Fernando.- >>> >>> De: Paulo Simoes > >>> Organizaci?n: OneSource Lda. >>> Fecha: Tuesday 7 October 2014 07:57 >>> Para: JUAN JOSE HIERRO SUREDA >> >, "Thomas.Bohnert at zhaw.ch >>> " >> >, "luis.cordeiro at onesource.pt >>> " >> > >>> CC: fla >> >, Leandro Guillen >>> >, >>> MIGUEL CARRILLO PACHECO >> >, MANUEL ESCRICHE >>> VICENTE >> > >>> Asunto: Re: Start of activities linked to friendly testing of FIWARE >>> >>> >>> Dear Juanjo, >>> >>> I confirm your proposal is fine with us. >>> >>> We will start this process immediately. Today we will organize the >>> work internally and by the end of the day we'll provide more >>> feedback on the team organization and on how we'll conduct our work >>> and reporting. >>> >>> Regards, >>> >>> -- Paulo Sim?es >>> >>> >>> On 07/10/14 03:19, Juanjo Hierro wrote: >>>> Dear Paulo, >>>> >>>> Let's start to work involving the resources you have listed plus >>>> one additional. We would like to involve 4 engineers. We >>>> understand that project management activities are not strictly >>>> necessary. There will be people from FIWARE assigned to >>>> coordination. Nevertheless, if you want to charge a bit % on >>>> those type of activities is fine. Since it is not true that we >>>> will spend exactly 4*3 = 12 PMs starting now until end of the year, >>>> I understand that we may go for allocating that effort of 9 PMs and >>>> assume that the % of coordination is part of that. Consequently, >>>> we would have an overall funding assigned of 6.000 ? * 12 PMs = >>>> 72.000 ?. Note that this would require that you add a fourth >>>> developer in a matter of few days, preferably this week. >>>> >>>> Is it fine with you? If so, the following are the instructions >>>> to follow to start the activity. Please confirm urgently that >>>> this is ok. >>>> >>>> This Task Force is targeted to identify the issues that any >>>> developer may find when they try to approach FIWARE for the first >>>> time, even if (s)he hasn't had the opportunity to attend any of our >>>> Bootcamps or Technical Workshops. The difference here is that you >>>> are a friendly tester, that is, you will report and properly >>>> document the issues that you find (while other developers may >>>> decide to give up when they find the first issue). This will >>>> allow us to understand what has to be fixed. >>>> >>>> The Task Force will be organized in two phases: >>>> >>>> * In a first phase of the Task Force, which we expect (hopefully >>>> :-) that may last one or one and a half month, you will focus on: >>>> o Regarding the Cloud, Store, Mashup-Wirecloud, Data and >>>> Account Management portals available on the FIWARE Lab >>>> (http://lab.fiware.org) >>>> + Make sure that everything works fine and it is >>>> intuitive enough >>>> + Make sure that there is enough helpful and accurate >>>> documentation as well as video tutorials >>>> o Regarding individual FIWARE components (referred as FIWARE >>>> GEris which is the acronym of FIWARE Generic Enabler >>>> reference implementation) published in the FIWARE Catalogue >>>> (http://catalogue.fiware.org): >>>> + In a first step, make sure that their software can be >>>> downloaded, deployed, configured and used locally by a >>>> regular developer, using info available on the FIWARE >>>> Catalogue. >>>> + In a second step, make sure that they can be deployed >>>> and configured as dedicated instances on the FIWARE Lab >>>> (using dedicated VM images, recipes and blueprints) and >>>> both dedicated and global instances running on the >>>> FIWARE Lab can be used by a regular developer, using >>>> info available on the FIWARE Catalogue and the >>>> resources available on the FIWARE Lab >>>> >>>> * In a second phase (since end of first phase until the end of >>>> the year), you will focus on: >>>> o Develop and document the open source code for example >>>> applications you will be asked to develop (to be defined >>>> during the first phase) >>>> o Help to improve existing documentation and, overall, >>>> tutorials (written or video tutorials) >>>> >>>> >>>> I won't give you more details on how things can be done because >>>> part of your job is to try what third developers will try with not >>>> much more info than the above :-) >>>> >>>> Whenever you identify a problem to be fixed or a >>>> suggestion/request for an enhancement, please drop an email to the >>>> following help-desk addresses: >>>> >>>> * fiware-lab-help at lists.fi-ware.org: to be used when the >>>> problem/enhancement to be reported has to do with the FIWARE >>>> Lab environment >>>> o problem/enhancements on functionalities offered through any >>>> of the FIWARE Lab portals: Cloud, Store, Mashup, Account, >>>> Data, Help&Info >>>> o problem/enhancements trying to deploy (instantiate) and >>>> configure FIWARE GEri on the FIWARE Lab using Cloud >>>> deployment tools (creation of VM images with preinstalled >>>> GEris, usage of recipes, usage of blueprint templates) >>>> o problem/enhancements trying to get access to a FIWARE GEri >>>> instance available on the FIWARE Lab: either a private >>>> dedicated instance previously deployed by you or a global >>>> instance available for all developers >>>> * fiware-tech-help at lists.fi-ware.org: to be used when the >>>> problem/enhancement to be reported has to do with individual >>>> FIWARE components >>>> o downloading, installing and configuring a FIWARE GEri on >>>> your local premises, using available documentation >>>> o downloading, installing and configuring a FIWARE GEri on a >>>> VM previously deployed on the FIWARE Lab >>>> o getting access and programming with the APIs provided by >>>> FIWARE GEri instances you have deployed (you are asked to >>>> try the tutorials provided and then event try something on >>>> your own) >>>> >>>> Nevertheless, don't get too much worried about what mailing list >>>> you should use (third developers may also not perform the best >>>> choice ;-) We will deal with that and make sure things are >>>> handled properly. >>>> >>>> For your info, any time you send a message to any of the above >>>> channels, a ticket will be created in a JIRA HelpDesk ticketing >>>> system. Then the 1st and 2nd level support teams will analyze it, >>>> in the most trivial cases respond directly your request for help >>>> and if they don't know how to do it, they will pass the ticket to >>>> someone from the FIWARE development teams who will take care of it. >>>> >>>> You will see that the HelpDesk may answer you that you have asked >>>> to solve a problem they believe should be answered on StackOverflow >>>> for the sake of other programmers. If so, please formulate your >>>> question there. We have decided to use StackOverflow as our forum >>>> for developers. There are a number of tags, the more general >>>> "fiware" tag but also tags associated to the most popular FIWARE >>>> GEris like "fiware-orion", "fiware-wirecloud", you can use to ask >>>> question about FIWARE on StackOverflow. Of course, after some >>>> time, once you get more experienced using FIWARE, you may decide to >>>> go for asking the question directly on StackOverflow. >>>> >>>> Fernando L?pez will >>>> coordinate all the tests dealing with the Cloud, Store, >>>> Mashup-Wirecloud, Data and Account Management portals available on >>>> the FIWARE Lab. >>>> >>>> Leandro Guill?n will coordinate all >>>> the tests dealing with individual FIWARE components published on >>>> the FIWARE Catalogue. >>>> >>>> You may ask any question you may have by sending a message to >>>> fiware-friendly-testing-coordination at lists.fi-ware.org. If you >>>> don't get any answer, please contact Fernando and Leandro directly >>>> (they are in the mailing list though). >>>> >>>> Regarding the tests to be done by Bitergia, we would like that >>>> your three developers focus on the following tasks: >>>> >>>> * Patricio Batista: testing of FIWARE Cloud functionalities on >>>> the FIWARE Lab >>>> * Jo?o Gon?alves: testing GEris of the Advanced Web-based UI >>>> chapter of FIWARE published on the FIWARE Catalogue (remember >>>> the two consecutive steps to be performed when carrying out >>>> testing of individual FIWARE components) >>>> * Hugo Fonseca: testing GEris of the Kurento FIWARE GEri >>>> published on the FIWARE Catalogue (remember the two consecutive >>>> steps to be performed when carrying out testing of individual >>>> FIWARE components) >>>> * OneSource developer 4: testing of the Complex Event Processing >>>> - ProTON GEris published on the FIWARE Catalogue (remember the >>>> two consecutive steps to be performed when carrying out testing >>>> of individual FIWARE components) >>>> >>>> Some last remarks: >>>> >>>> * We know that you are a experienced developer. Therefore, you >>>> may infer how some little issue you find can be overcome. >>>> However, please report that issue so that we can fix it. Take >>>> into account that some third developers may not be so much >>>> experienced, therefore they may not be able to overcome the >>>> same issue. Of course, don't wait for the issue to get solved >>>> in order to continue with testing. >>>> * Issue your reports in english and try to provide as much >>>> details as possible to make our task easier and solve issues as >>>> fast as possible. >>>> * Any typo or improvement on language of available documentation >>>> is welcome. >>>> * Don't focus just on issues/problems. Any suggestion for >>>> enhancement is welcome. >>>> * If you are blocked at any point and you don't know how to >>>> continue, please let us know. Send an email to >>>> fiware-friendly-testing-coordination at lists.fi-ware.org >>>> >>>> >>>> Let's rock !! >>>> >>>> Best regards, >>>> >>>> -- Juanjo Hierro >>>> ------------- >>>> Telefonica - Product Development and Innovation (PDI) >>>> website:www.tid.es >>>> email:juanjose.hierro at telefonica.com >>>> twitter: twitter.com/JuanjoHierro >>>> >>>> FI-WARE (European Future Internet Core Platform) Coordinator >>>> and Chief Architect >>>> >>>> You can follow FI-WARE at: >>>> website:http://www.fi-ware.org >>>> facebook:http://www.facebook.com/pages/FI-WARE/251366491587242 >>>> twitter:http://twitter.com/FIware >>>> linkedIn:http://www.linkedin.com/groups/FIWARE-4239932 >>>> On 06/10/14 00:23, Paulo Simoes wrote: >>>>> On 05/10/14 21:23, Thomas Michael Bohnert wrote: >>>>>> Paulo, >>>>>> >>>>>> Can you add some info about the staff profiles that you plan to >>>>>> assign to this important task? (Software developers and System >>>>>> Engineers/Operators would be needed - ideally experiences ones). >>>>>> >>>>>> Thanks, Thomas >>>>>> >>>>> >>>>> Dear Thomas, all, >>>>> (please excuse the long reply) >>>>> >>>>> The final selection of staff to involve still depends on assessing >>>>> all the required skills and technologies that are required to use >>>>> the FI-WARE components. Nevertheless, next I provide the profiles >>>>> of three people that immediately came to my mind and may be >>>>> assigned to the project. >>>>> >>>>> Hugo Fonseca. Before joining OneSource he worked for several years >>>>> in the development of RCS and WebRTC platforms, including software >>>>> design and development. Before that he was involved in quality >>>>> assurance and software testing (mostly for unified communications >>>>> suites and mobile banking applications). At OneSource Hugo is >>>>> mostly involved with one of our clients, focusing on improving the >>>>> security, QoS/QoE and functionalities of the white-label >>>>> communications suites this client provides to several telcos >>>>> worldwide (cloud-based managed PBX solutions, contact centers and >>>>> rich communication suites for enterprise markets). >>>>> >>>>> Jo?o Gon?alves is mostly a software engineer. One of the most >>>>> recent applications he has developed is an advanced live >>>>> video-to-video (v2v) communications platform, integrated with >>>>> operator?s resource management frameworks, that in the context of >>>>> the Livecity PSP Project is being used in several applications >>>>> with real users: telemedicine, support of first responder teams, >>>>> education and remotely provided public services. In addition to >>>>> the core and the plug-in interfaces of the v2v platform, Jo?o also >>>>> designed and assembled the wearable v2v device that is being used >>>>> by first responder teams in Ireland and Germany. This v2v platform >>>>> was awarded as the Best Demonstration at FIA-2014 (Athens). >>>>> >>>>> Patricio Batista started his career as a network and systems >>>>> administrator. Later on he evolved to systems design and >>>>> integration. He is quite experienced on deploying, integrating, >>>>> configuring and managing distributed systems, as well as on >>>>> virtualized and cloud-based infrastructures. It is difficult to >>>>> mention all the projects he has been involved in, but he has, for >>>>> instance, designed a platform that one of our clients uses to >>>>> receive and analyze in real-time (for risk and fraud prevention >>>>> purposes) tenths of thousands of credit card transactions per second. >>>>> >>>>> In addition to people with these or similar profiles, we also >>>>> intend to involve a project manager with experience on FP7 >>>>> Projects, such as Bruno Sousa or Lu?s Cordeiro. >>>>> >>>>> Bruno Sousa owns a PhD in Information Science and Technology, and >>>>> he authored tenths of research papers in journals, book chapters >>>>> and conference proceedings. He has participated in European R&D >>>>> projects such as FP6 EuQos, FP6 WEIRD, FP7 CityFlow, FP7 MCN and >>>>> FP7 SALUS. Before returning to the University to get his PhD Bruno >>>>> has led for several years the development and integration of >>>>> backoffice applications for ?La Redoute/Redcats?, a large European >>>>> home-shopping retailer. >>>>> >>>>> Luis Cordeiro has been actively involved in European research >>>>> projects such as FP6 EUQOS, FP6 WEIRD, FP7 LiveCity, FP7 CityFlow, >>>>> FP7 SALUS and FP7 Mobile Cloud Networks. He has several >>>>> publications in journals, book chapters, conferences and Internet >>>>> Drafts in the areas of Signaling, end-to-end QoS and Network >>>>> Management. In addition to those research activities, he also led >>>>> tenths of application development projects. >>>>> >>>>> Regards, >>>>> >>>>> -- Paulo >>>>> >>>>> >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> Este mensaje y sus adjuntos se dirigen exclusivamente a su >>>> destinatario, puede contener informaci?n privilegiada o >>>> confidencial y es para uso exclusivo de la persona o entidad de >>>> destino. Si no es usted. el destinatario indicado, queda notificado >>>> de que la lectura, utilizaci?n, divulgaci?n y/o copia sin >>>> autorizaci?n puede estar prohibida en virtud de la legislaci?n >>>> vigente. Si ha recibido este mensaje por error, le rogamos que nos >>>> lo comunique inmediatamente por esta misma v?a y proceda a su >>>> destrucci?n. >>>> >>>> The information contained in this transmission is privileged and >>>> confidential information intended only for the use of the >>>> individual or entity named above. If the reader of this message is >>>> not the intended recipient, you are hereby notified that any >>>> dissemination, distribution or copying of this communication is >>>> strictly prohibited. If you have received this transmission in >>>> error, do not read it. Please immediately reply to the sender that >>>> you have received this communication in error and then delete it. >>>> >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>>> destinat?rio, pode conter informa??o privilegiada ou confidencial e >>>> ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? >>>> vossa senhoria o destinat?rio indicado, fica notificado de que a >>>> leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode >>>> estar proibida em virtude da legisla??o vigente. Se recebeu esta >>>> mensagem por erro, rogamos-lhe que nos o comunique imediatamente >>>> por esta mesma via e proceda a sua destrui??o >>> >>> >>> ------------------------------------------------------------------------ >>> >>> Este mensaje y sus adjuntos se dirigen exclusivamente a su >>> destinatario, puede contener informaci?n privilegiada o confidencial >>> y es para uso exclusivo de la persona o entidad de destino. Si no es >>> usted. el destinatario indicado, queda notificado de que la lectura, >>> utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar >>> prohibida en virtud de la legislaci?n vigente. Si ha recibido este >>> mensaje por error, le rogamos que nos lo comunique inmediatamente >>> por esta misma v?a y proceda a su destrucci?n. >>> >>> The information contained in this transmission is privileged and >>> confidential information intended only for the use of the individual >>> or entity named above. If the reader of this message is not the >>> intended recipient, you are hereby notified that any dissemination, >>> distribution or copying of this communication is strictly >>> prohibited. If you have received this transmission in error, do not >>> read it. Please immediately reply to the sender that you have >>> received this communication in error and then delete it. >>> >>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>> destinat?rio, pode conter informa??o privilegiada ou confidencial e >>> ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? >>> vossa senhoria o destinat?rio indicado, fica notificado de que a >>> leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode >>> estar proibida em virtude da legisla??o vigente. Se recebeu esta >>> mensagem por erro, rogamos-lhe que nos o comunique imediatamente por >>> esta mesma via e proceda a sua destrui??o >> > > > ------------------------------------------------------------------------ > > Este mensaje y sus adjuntos se dirigen exclusivamente a su > destinatario, puede contener informaci?n privilegiada o confidencial y > es para uso exclusivo de la persona o entidad de destino. Si no es > usted. el destinatario indicado, queda notificado de que la lectura, > utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar > prohibida en virtud de la legislaci?n vigente. Si ha recibido este > mensaje por error, le rogamos que nos lo comunique inmediatamente por > esta misma v?a y proceda a su destrucci?n. > > The information contained in this transmission is privileged and > confidential information intended only for the use of the individual > or entity named above. If the reader of this message is not the > intended recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is strictly prohibited. > If you have received this transmission in error, do not read it. > Please immediately reply to the sender that you have received this > communication in error and then delete it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu > destinat?rio, pode conter informa??o privilegiada ou confidencial e ? > para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa > senhoria o destinat?rio indicado, fica notificado de que a leitura, > utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida > em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, > rogamos-lhe que nos o comunique imediatamente por esta mesma via e > proceda a sua destrui??o -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabrice.bouquet at femto-st.fr Fri Oct 10 17:20:07 2014 From: fabrice.bouquet at femto-st.fr (Fabrice Bouquet) Date: Fri, 10 Oct 2014 17:20:07 +0200 Subject: [Fiware-friendly-testing-coordination] Start of activities linked to friendly testing of FIWARE by FEMTO-ST In-Reply-To: <069001cfe454$e2fd4a70$a8f7df50$@femto-st.fr> References: <54334D9E.1040006@telefonica.com> <54371759.5030904@telefonica.com> <069001cfe454$e2fd4a70$a8f7df50$@femto-st.fr> Message-ID: <6308B22A-57C3-4679-8AD6-173F51BF0969@femto-st.fr> Dear Juanjo, I'm the technical project manager for the FEMTO-ST proposal. We agree with the tasks you propose. Maybe for the second step, the time is a little bit too short. - We can start the project the 27th October. - The end of the first step is end of november (at minima) - So we are only one month for the second step (without the holidays at the end of the year). For this step, we propose to finish by the end of January. Do you agree with this suggestion of the new ending ? Best regards, Fabrice ___________________________________________________ Pr Fabrice Bouquet - University of Franche-Comt? Departement of Computer Sciences http://disc.univ-fcomte.fr Tel : (33) 381 666 664 - 16 route de gray 25000 Besan?on FRANCE INRIA Projet Cassis : http://webloria.loria.fr/equipes/cassis > > > De : Juanjo Hierro [mailto:juanjose.hierro at telefonica.com] > Envoy? : vendredi 10 octobre 2014 01:17 > ? : bruno.legeard at femto-st.fr > Cc : fiware-friendly-testing-coordination at lists.fi-ware.org > Objet : Start of activities linked to friendly testing of FIWARE by FEMTO-ST > > Dear Bruno, > > The following are the instructions to follow to start the activities in the FIWARE Friendly Testing Task Force. Please confirm urgently that this is ok. > > This Task Force is targeted to identify the issues that any developer may find when they try to approach FIWARE for the first time, even if (s)he hasn't had the opportunity to attend any of our Bootcamps or Technical Workshops. The difference here is that you are a friendly tester, that is, you will report and properly document the issues that you find (while other developers may decide to give up when they find the first issue). This will allow us to understand what has to be fixed. > > The Task Force will be organized in two phases: > In a first phase of the Task Force, which we expect (hopefully :-) that may last one or one and a half month, you will focus on: > Regarding the Cloud, Store, Mashup-Wirecloud, Data and Account Management portals available on the FIWARE Lab (http://lab.fiware.org) > Make sure that everything works fine and it is intuitive enough > Make sure that there is enough helpful and accurate documentation as well as video tutorials > Regarding individual FIWARE components (referred as FIWARE GEris which is the acronym of FIWARE Generic Enabler reference implementation) published in the FIWARE Catalogue (http://catalogue.fiware.org): > In a first step, make sure that their software can be downloaded, deployed, configured and used locally by a regular developer, using info available on the FIWARE Catalogue. > In a second step, make sure that they can be deployed and configured as dedicated instances on the FIWARE Lab (using dedicated VM images, recipes and blueprints) and both dedicated and global instances running on the FIWARE Lab can be used by a regular developer, using info available on the FIWARE Catalogue and the resources available on the FIWARE Lab > In a second phase (since end of first phase until the end of the year), you will focus on: > Develop and document the open source code for example applications you will be asked to develop (to be defined during the first phase) > Help to improve existing documentation and, overall, tutorials (written or video tutorials) > > I won't give you more details on how things can be done because part of your job is to try what third developers will try with not much more info than the above :-) > > Whenever you identify a problem to be fixed or a suggestion/request for an enhancement, please drop an email to the following help-desk addresses: > fiware-lab-help at lists.fi-ware.org: to be used when the problem/enhancement to be reported has to do with the FIWARE Lab environment > problem/enhancements on functionalities offered through any of the FIWARE Lab portals: Cloud, Store, Mashup, Account, Data, Help&Info > problem/enhancements trying to deploy (instantiate) and configure FIWARE GEri on the FIWARE Lab using Cloud deployment tools (creation of VM images with preinstalled GEris, usage of recipes, usage of blueprint templates) > problem/enhancements trying to get access to a FIWARE GEri instance available on the FIWARE Lab: either a private dedicated instance previously deployed by you or a global instance available for all developers > fiware-tech-help at lists.fi-ware.org: to be used when the problem/enhancement to be reported has to do with individual FIWARE components > downloading, installing and configuring a FIWARE GEri on your local premises, using available documentation > downloading, installing and configuring a FIWARE GEri on a VM previously deployed on the FIWARE Lab > getting access and programming with the APIs provided by FIWARE GEri instances you have deployed (you are asked to try the tutorials provided and then event try something on your own) > Nevertheless, don't get too much worried about what mailing list you should use (third developers may also not perform the best choice ;-) We will deal with that and make sure things are handled properly. > > For your info, any time you send a message to any of the above channels, a ticket will be created in a JIRA HelpDesk ticketing system. Then the 1st and 2nd level support teams will analyze it, in the most trivial cases respond directly your request for help and if they don't know how to do it, they will pass the ticket to someone from the FIWARE development teams who will take care of it. > > You will see that the HelpDesk may answer you that you have asked to solve a problem they believe should be answered on StackOverflow for the sake of other programmers. If so, please formulate your question there. We have decided to use StackOverflow as our forum for developers. There are a number of tags, the more general "fiware" tag but also tags associated to the most popular FIWARE GEris like "fiware-orion", "fiware-wirecloud", you can use to ask question about FIWARE on StackOverflow. Of course, after some time, once you get more experienced using FIWARE, you may decide to go for asking the question directly on StackOverflow. > > Fernando L?pez will coordinate all the tests dealing with the Cloud, Store, Mashup-Wirecloud, Data and Account Management portals available on the FIWARE Lab. > > Leandro Guill?n will coordinate all the tests dealing with individual FIWARE components published on the FIWARE Catalogue. > > You may ask any question you may have by sending a message to fiware-friendly-testing-coordination at lists.fi-ware.org. If you don't get any answer, please contact Fernando and Leandro directly (they are in the mailing list though). If you believe your question maybe of interest to all friendly testers, not just your team, please send an email to fiware-friendly-testing at lists.fi-ware.org > > Regarding the tests to be carried out by FEMTO-ST, either Fernando or Leandro will soon contact you with specific instructions. We understand that, as discussed, you will involve two developers in the Task Force (the two whose CVs you forwarded to us). > > Some last remarks to pass to members of your team: > We know that you are a experienced developer. Therefore, you may infer how some little issue you find can be overcome. However, please report that issue so that we can fix it. Take into account that some third developers may not be so much experienced, therefore they may not be able to overcome the same issue. Of course, don't wait for the issue to get solved in order to continue with testing. > Issue your reports in english and try to provide as much details as possible to make our task easier and solve issues as fast as possible. > Any typo or improvement on language of available documentation is welcome. > Don't focus just on issues/problems. Any suggestion for enhancement is welcome. > If you are blocked at any point and you don't know how to continue, please let us know. Send an email to fiware-friendly-testing-coordination at lists.fi-ware.org > If you believe your question maybe of interest to all friendly testers, send it to fiware-friendly-testing at lists.fi-ware.org. > Let's rock !! > > Best regards, > > -- Juanjo Hierro > > ------------- > Telefonica - Product Development and Innovation (PDI) > website: www.tid.es > email: juanjose.hierro at telefonica.com > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Coordinator > and Chief Architect > > You can follow FI-WARE at: > website: http://www.fi-ware.org > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter: http://twitter.com/FIware > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > > > > Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. > > The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o -------------- next part -------------- An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Fri Oct 10 18:05:55 2014 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Fri, 10 Oct 2014 18:05:55 +0200 Subject: [Fiware-friendly-testing-coordination] Fwd: Re: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal In-Reply-To: <54380263.3070109@telefonica.com> References: <54380263.3070109@telefonica.com> Message-ID: <543803E3.8070808@telefonica.com> Hola Manuel, Ya se que tal vez est?s de viaje y que el lunes son vacaciones en Boecillo ... ?pero es posible hacer esto ? No s? si nos has dejado privilegios de administrador a Miguel o a m? como para poder crear un JIRA y configurarlo ... Por hacerlo simple, el formulario que usuario para un ticket en el JIRA sobre Friendly Testing que propongo crear tendr?a los siguientes campos: * Responsible: * Description: * Tested GE(s): * Environment: * Instance: El workflow puede ser el de un Work Item. Saludos, -- Juanjo -------- Original Message -------- Subject: Re: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal Date: Fri, 10 Oct 2014 17:59:31 +0200 From: Juanjo Hierro To: fiware-friendly-testing at lists.fi-ware.org Dear all, I haven't gone through the contents of the wiki but I just want to make a remark. It's perfectly fine that you keep track of what you have tested, because we should be able to trace what has been tested (positively), but I want to stress that issues should be reported sending an email to fiware-tech-help at lists.fi-ware.org or fiware-lab-help at lists.fi-ware.org which are the channels through which we will are also receiving issues from other users. Those messages automatically create a ticket on a JIRA system so that we can assign tickets to the teams who can solve them and follow-up progress. Eventually, one idea that I put on the table is that we may create a JIRA system for the Friendly Testing Task Force. Then you may create a ticket whenever you start some concrete test (the more fine-grained, the best) or you may create a battery of tickets for a plan of tests. Then you close a ticket whenever the test has been passed correctly. Otherwise, you send an issue to some mailing list (who means a ticket is created in the HelpDesk JIRA system). You may even link the ticket you had initially created for running a test with the ticket you create because sending the issue. Once the issue is solved, you may redo the test that was blocked pending of solving the issue and, eventually, close it. What do you think? It may require creating a JIRA for Friendly Testing, but I guess this may be ready on Monday/Tuesday ... Best regards, -- Juanjo ------------- Telefonica - Product Development and Innovation (PDI) website: www.tid.es email: juanjose.hierro at telefonica.com twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.org facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 10/10/14 11:44, Alvaro del Castillo wrote: Hi all! First report from Bitergia team. The goal of this email is not to talk about results, but about the methodology followed. During this week we have been working in the GEs assigned to our team, and also in the FIWARE Labs (filabs). We have defined a methodology that maybe could be useful for others. According to Juanjo email about how we should test the GEs there are five scenarios: local machine, own virtual machine in filabs, already exiting virtual machine with the GE in filabs, using Chef recipes and using blueprints. We have created a Wiki with a first table showing the state of each scenario for the GEs. For accesing: user: fiware password: fiware https://www.bitergia.net/redmine/projects/ficore-testing/wiki/TestingGEris For each GE we have created a Wiki page (linked from the summary table) with the description of the tests in each scenario. This description is standard for all the GEs. For example, for Orion Context Broker: https://www.bitergia.net/redmine/projects/ficore-testing/wiki/GE_Orion_Context The index we have defined for the templates are: GE Orion Context #4260 * Install process * From sources * Debian: Ubuntu 14.04, 64 bits * From packages * RPM: CentOS 6.5 * Debian * Test of available pre created images * Test of Chef Recipes * Test of Blue prints With this template (which is extensible), based on the experience for testing the 5 scenarios in the 4 GEs, we plan to deliver our work. So, any thoughts about that? Juanjo and the rest of Telefonica team, is it ok for you to deliver in this format our work? Probably we should move this Wiki to someplace in FICORE Mediawiki. Also, in the Wiki are the "clean" results. There are tickets linked with all the background work needed to reach the results. We are opening in stackoverflow and github some tickets. And we plan to start using the fiware mailing list to ask some specific issues we have for the GEs. Cheers ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o -------------- next part -------------- An HTML attachment was scrubbed... URL: From manuel.escrichevicente at telefonica.com Tue Oct 14 15:27:00 2014 From: manuel.escrichevicente at telefonica.com (MANUEL ESCRICHE VICENTE) Date: Tue, 14 Oct 2014 13:27:00 +0000 Subject: [Fiware-friendly-testing-coordination] [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal In-Reply-To: <543803E3.8070808@telefonica.com> References: <54380263.3070109@telefonica.com> <543803E3.8070808@telefonica.com> Message-ID: <84f92bdd7556482e9f806141190971ba@DB4PR06MB489.eurprd06.prod.outlook.com> Hola Juanjo, Perdonad, he estado de viaje el viernes, y el fin de semana. Miguel tiene permisos, pero es dif?cil montar esto sin cierta experiencia previa. Me pongo con ello. Por optimizar la creaci?n de campos, voy a hacerlo de la siguiente forma: ? Responsible -> Asignee ? Description -> Description ? Tested GE -> Component ? Environment ? es necesario crear un campo ? Instance ? es necesario crear un campo El workflow para workitems es el siguiente, que tambi?n creo puede ser adecuado. [cid:image001.jpg at 01CFE7C3.49B6A7E0] Un saludo. Manuel From: JUAN JOSE HIERRO SUREDA Sent: viernes, 10 de octubre de 2014 18:06 To: MANUEL ESCRICHE VICENTE Cc: fiware-friendly-testing-coordination at lists.fi-ware.org; MIGUEL CARRILLO PACHECO Subject: Fwd: Re: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal Hola Manuel, Ya se que tal vez est?s de viaje y que el lunes son vacaciones en Boecillo ... ?pero es posible hacer esto ? No s? si nos has dejado privilegios de administrador a Miguel o a m? como para poder crear un JIRA y configurarlo ... Por hacerlo simple, el formulario que usuario para un ticket en el JIRA sobre Friendly Testing que propongo crear tendr?a los siguientes campos: * Responsible: * Description: * Tested GE(s): * Environment: * Instance: El workflow puede ser el de un Work Item. Saludos, -- Juanjo -------- Original Message -------- Subject: Re: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal Date: Fri, 10 Oct 2014 17:59:31 +0200 From: Juanjo Hierro To: fiware-friendly-testing at lists.fi-ware.org Dear all, I haven't gone through the contents of the wiki but I just want to make a remark. It's perfectly fine that you keep track of what you have tested, because we should be able to trace what has been tested (positively), but I want to stress that issues should be reported sending an email to fiware-tech-help at lists.fi-ware.org or fiware-lab-help at lists.fi-ware.org which are the channels through which we will are also receiving issues from other users. Those messages automatically create a ticket on a JIRA system so that we can assign tickets to the teams who can solve them and follow-up progress. Eventually, one idea that I put on the table is that we may create a JIRA system for the Friendly Testing Task Force. Then you may create a ticket whenever you start some concrete test (the more fine-grained, the best) or you may create a battery of tickets for a plan of tests. Then you close a ticket whenever the test has been passed correctly. Otherwise, you send an issue to some mailing list (who means a ticket is created in the HelpDesk JIRA system). You may even link the ticket you had initially created for running a test with the ticket you create because sending the issue. Once the issue is solved, you may redo the test that was blocked pending of solving the issue and, eventually, close it. What do you think? It may require creating a JIRA for Friendly Testing, but I guess this may be ready on Monday/Tuesday ... Best regards, -- Juanjo ------------- Telefonica - Product Development and Innovation (PDI) website: www.tid.es email: juanjose.hierro at telefonica.com twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.org facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 10/10/14 11:44, Alvaro del Castillo wrote: Hi all! First report from Bitergia team. The goal of this email is not to talk about results, but about the methodology followed. During this week we have been working in the GEs assigned to our team, and also in the FIWARE Labs (filabs). We have defined a methodology that maybe could be useful for others. According to Juanjo email about how we should test the GEs there are five scenarios: local machine, own virtual machine in filabs, already exiting virtual machine with the GE in filabs, using Chef recipes and using blueprints. We have created a Wiki with a first table showing the state of each scenario for the GEs. For accesing: user: fiware password: fiware https://www.bitergia.net/redmine/projects/ficore-testing/wiki/TestingGEris For each GE we have created a Wiki page (linked from the summary table) with the description of the tests in each scenario. This description is standard for all the GEs. For example, for Orion Context Broker: https://www.bitergia.net/redmine/projects/ficore-testing/wiki/GE_Orion_Context The index we have defined for the templates are: GE Orion Context #4260 * Install process * From sources * Debian: Ubuntu 14.04, 64 bits * From packages * RPM: CentOS 6.5 * Debian * Test of available pre created images * Test of Chef Recipes * Test of Blue prints With this template (which is extensible), based on the experience for testing the 5 scenarios in the 4 GEs, we plan to deliver our work. So, any thoughts about that? Juanjo and the rest of Telefonica team, is it ok for you to deliver in this format our work? Probably we should move this Wiki to someplace in FICORE Mediawiki. Also, in the Wiki are the "clean" results. There are tickets linked with all the background work needed to reach the results. We are opening in stackoverflow and github some tickets. And we plan to start using the fiware mailing list to ask some specific issues we have for the GEs. Cheers ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6577 bytes Desc: image001.jpg URL: From miguel.carrillopacheco at telefonica.com Wed Oct 22 11:16:20 2014 From: miguel.carrillopacheco at telefonica.com (MIGUEL CARRILLO PACHECO) Date: Wed, 22 Oct 2014 11:16:20 +0200 Subject: [Fiware-friendly-testing-coordination] =?windows-1252?q?=5BFiware?= =?windows-1252?q?-lab-help=5D_=5BCloud=5D_=5BDesign=5D_Showing_=93importa?= =?windows-1252?q?nt_info=94_message_repeatedly?= In-Reply-To: References: Message-ID: <544775E4.7000300@telefonica.com> Esta persona es del friendly? Porque con correo gmail y sin dar m?s informaci?n, para m? esto es cr?ptico El 22/10/2014 11:13, Pablo Fern?ndez Moniz escribi?: Web Browser: Google Chrome version 38.0.2125.104 Operating System: OSX version 10.9.5 User id: cloudtestulpgc Tenant: 00000000000000000000000000006443 Description Display the ?important info? message each time you return to the cloud main page is a little annoying. Maybe it only should be shown only once per login. How to replicate: Click in the ?Cloud? menu element in the top of the page or refresh it. [important-info-message.tiff] _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help -- Please update your address book with my new e-mail address: miguel.carrillopacheco at telefonica.com ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: miguel.carrillopacheco at telefonica.com Follow FI-WARE on the net Website: http://www.fi-ware.org Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o -------------- next part -------------- An HTML attachment was scrubbed... URL: