Here it is. -----Message d'origine----- De : Alexandre Boeglin [mailto:alexandre.boeglin at inria.fr] Envoyé : jeudi 28 février 2013 14:56 À : BISSON Pascal Cc : MANUEL ESCRICHE VICENTE; Wolfgang.Steigerwald at telekom.de; robert.seidl at nsn.com; susana.gzarzosa at atosresearch.eu; francesco.di.cerbo at sap.com; GIDOIN Daniel; fiware-security at lists.fi-ware.eu Objet : Re: [Fiware-security] FIWARE - backlog review Sorry, but it seems that the email from Manuel you're referring to has not reached the fiware-security mailing list, and I'm unable to check this updated spreadsheet. Could you please forward it to me – or to the mailing list? Best regards, Alex Le jeudi 28 février 2013 à 13:53, BISSON Pascal a écrit: > Thanks Manuel. Indeed it can only help in our understanding and so us fixing the issues. > > So please anyone owner of a GE having still issues in view of this report please get them fixed by end of the day. > > I will perform a check on my side tonight and of course we will discuss this at our WP8 audio conf (hoping at that we could finally close being said for me the bulk of the work should now be reviewing draft contrib. to Architecture description for Release 2). > > Best Regards, > Pascal > > De : MANUEL ESCRICHE VICENTE [mailto:mev at tid.es] > Envoyé : mercredi 27 février 2013 20:33 > À : BISSON Pascal; Wolfgang.Steigerwald at telekom.de<mailto:Wolfgang.Steigerwald at telekom.de>; robert.seidl at nsn.com<mailto:robert.seidl at nsn.com>; susana.gzarzosa at atosresearch.eu<mailto:susana.gzarzosa at atosresearch.eu>; francesco.di.cerbo at sap.com<mailto:francesco.di.cerbo at sap.com>; GIDOIN Daniel > Cc : fiware-security at lists.fi-ware.eu<mailto:fiware-security at lists.fi-ware.eu>; MIGUEL CARRILLO PACHECO; JUAN JOSE HIERRO SUREDA > Objet : RE: FIWARE - backlog review > > Dear Pascal, > > Today, I've been able to enrich the input for easy mutual understanding. > Please, have a look at the spreadsheet, and let's see whether we can fix the issues. > > Kind regards, > Manuel > > From: MANUEL ESCRICHE VICENTE > Sent: miércoles, 27 de febrero de 2013 14:33 > To: 'BISSON Pascal'; Wolfgang.Steigerwald at telekom.de<mailto:Wolfgang.Steigerwald at telekom.de>; robert.seidl at nsn.com<mailto:robert.seidl at nsn.com>; susana.gzarzosa at atosresearch.eu<mailto:susana.gzarzosa at atosresearch.eu>; francesco.di.cerbo at sap.com<mailto:francesco.di.cerbo at sap.com>; GIDOIN Daniel > Cc: fiware-security at lists.fi-ware.eu<mailto:fiware-security at lists.fi-ware.eu>; MIGUEL CARRILLO PACHECO; JUAN JOSE HIERRO SUREDA > Subject: RE: FIWARE - backlog review > > Dear Wolfgang, > > Let me clarify I did the spreadsheet thinking on how to help focus on finding the errors. > I assumed all partners knew and were applying some naming rules. > http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_%28convention_to_follow%29 > > And then, the day to day work didn't allow it. > Some partners with only this help on focus were able to fix many errors. Cloud chapter has moved from 80% to 5% in a couple of days. > > I understand some more input may be helpful. But we're working with little time, > Most red marked issues as easy to identify if you are willing to have just a look. > Anyway, I'm improving on my side the report and I'm already including a line below each red KO giving additional input - after 4 o 5 error you find almost all errors are very similar. > > Please, send me the first error you don't understand and I'll give you quick feedback. > > Thanks for cooperation! > Kind regards, > Manuel > > > > > > From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] > Sent: miércoles, 27 de febrero de 2013 8:43 > To: Wolfgang.Steigerwald at telekom.de<mailto:Wolfgang.Steigerwald at telekom.de>; robert.seidl at nsn.com<mailto:robert.seidl at nsn.com>; susana.gzarzosa at atosresearch.eu<mailto:susana.gzarzosa at atosresearch.eu>; francesco.di.cerbo at sap.com<mailto:francesco.di.cerbo at sap.com>; GIDOIN Daniel > Cc: fiware-security at lists.fi-ware.eu<mailto:fiware-security at lists.fi-ware.eu>; MANUEL ESCRICHE VICENTE; MIGUEL CARRILLO PACHECO; JUAN JOSE HIERRO SUREDA > Subject: RE: FIWARE - backlog review > Importance: High > > Dear Wolfgang, > > Yes I understand and also support we need better explanations and hearing we have to go through the guidelines to find why the issues is definitely not we/I were expecting (of course we can find by chance if any but it is very efficient and for me we should focus on content first and second the form but not putting too much constraints and also targeting some automated correction of minor issues ...). > > Hope support here delivered by TID with Manuel joining the project to support in those Agile aspects will help us from that perspective. Also lessons learnt form the Wiki/Tracker update should be capitalized to avoid the problems for next update ... > > Best Regards, > Pascal > > PS: I put in cc Manuel, Miguel and Juanjo for information also actions for further improvements as requested based on experience we gained here. > > De : Wolfgang.Steigerwald at telekom.de<mailto:Wolfgang.Steigerwald at telekom.de> [mailto:Wolfgang.Steigerwald at telekom.de] > Envoyé : mardi 26 février 2013 20:51 > À : BISSON Pascal; robert.seidl at nsn.com<mailto:robert.seidl at nsn.com>; susana.gzarzosa at atosresearch.eu<mailto:susana.gzarzosa at atosresearch.eu>; francesco.di.cerbo at sap.com<mailto:francesco.di.cerbo at sap.com>; GIDOIN Daniel > Cc : fiware-security at lists.fi-ware.eu<mailto:fiware-security at lists.fi-ware.eu> > Objet : AW: FIWARE - backlog review > > Hello Pascal, > > I checked the spread sheet and found one issue, but I don't know why the other points are in red. For the future it would be better to say what is wrong instead to say there is something wrong. I'm sure the effort to find what is wrong was higher than to change something, especially if you don't find the issue. For the future I hope the way issues are reported are more clear, otherwise I think about to vote for leaving the project. There are cost cuttings, unclear communication in conjunction with the high efforts to manage EU-Projects. May be you can discuss this on your next management calls. > > Best regards > > Wolfgang > > > Von: fiware-security-bounces at lists.fi-ware.eu<mailto:fiware-security-bounces at lists.fi-ware.eu> [mailto:fiware-security-bounces at lists.fi-ware.eu] Im Auftrag von BISSON Pascal > Gesendet: Dienstag, 26. Februar 2013 19:48 > An: Seidl, Robert (NSN - DE/Munich); Susana Gonzalez Zarzosa; DI CERBO, Francesco; GIDOIN Daniel > Cc: 'fiware-security at lists.fi-ware.eu' > Betreff: [Fiware-security] TR: FIWARE - backlog review > Wichtigkeit: Hoch > > Dear Task leads, > > This email with the last review of Manuel regarding the Wiki/Tracker update please have a look at remaining issues pointed by Manuel and take necessary steps to get them addressed/fixed. > > Many thanks in advance and hoping with your support we could improve and get finally our wiki/tracker update be assessed as good enough to be finally released !!!. Our all hope !!! > > Thanks in advance. > > Best Regards, > Pascal > > PS: Get you task members /colleagues involved whenever appropriate. > PS2: @Xavier/ Orange please interact with Daniel as SecMon GE owner to discuss and agree on your update regarding Roadmap, Wiki and Tracker ... since so far you were not so present nor visible Xavier > > De : MANUEL ESCRICHE VICENTE [mailto:mev at tid.es] > Envoyé : mardi 26 février 2013 12:22 > À : BISSON Pascal > Objet : FIWARE - backlog review > > Hi Pascal, > > Find attached a new review of possible errors. > The rate improved, but is far from others chapters, around 5 - 7% rate > > I had a look at the errors most of them come from the variability your team is mapping the general enablers into the reference. > For example for Security Monitoring I find: > "Security Monitoring" > "Security_Monitoring" > "SecurityMonitoring" > "Security-Monitoring" > > I've found for all of them, there was some without whitespaces, which I've chosen for consistence validations. I copy the mapping below, which I thing will help you: > > To the left is the Column 12 (without spaces, which I use as key for the mapping) > To the right, the chain I look for in Column 13 > > "AccessControl" = "AccessControlGE" > "ContextbasedSecurityCompliance" = "Context-basedSecurityAndCompliance" > "DataHandling" = "DataHandling" > "IdentityManagement" = "IDM" > "Optionalsecurityservices" = "OptionalSecurityEnablers" > "Privacy" = "Privacy" > "SecurityMonitoring" = "SecurityMonitoring" > > If hope you find acceptable this mapping. > > Kind regards, > Manuel > > > ---------------------------- > Manuel Escriche Vicente > Agile Project Manager/Leader > FI-WARE Initiative > Telefónica Digital > Parque Tecnológico > C/ Abraham Zacuto, 10 > 47151 - Boecillo > Valladolid - Spain > Tfno: +34.91.312.99.72 > Fax: +34.983.36.75.64 > http://www.tid.es<http://www.tid.es/> > > > ________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. > This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > ________________________________ > > 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-security mailing list > Fiware-security at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-security -- Alexandre Boeglin Madynes project-team – http://madynes.loria.fr/ Inria – http://www.inria.fr/ -------------- next part -------------- A non-text attachment was scrubbed... Name: Security-tracker_report-2013-02-27 - debug.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 22283 bytes Desc: Security-tracker_report-2013-02-27 - debug.xlsx URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20130228/1fc4969c/attachment.xlsx>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy