[Fiware-security] FIWARE - backlog review

EGAN Richard Richard.Egan at uk.thalesgroup.com
Wed Feb 27 14:58:25 CET 2013


Francesco,

my understanding is the Technical Roadmap is focussed on Release 2 (and hence will contain a subset of epics/features from the Materialising wiki page) - so I agree with what you have stated below.

My observation for Robert was that it did not seem that IDM had been updated with Release 2 info yet in the Technical Roadmap (but I am not totally familiar with the GE). Most of the other GEs have been updated (judged on the basis that owners have identified which feature is in each release (2.1, 2.2, 2.3)).

Richard

From: DI CERBO, Francesco [mailto:francesco.di.cerbo at sap.com]
Sent: 27 February 2013 13:47
To: Seidl, Robert (NSN - DE/Munich); EGAN Richard; 'Susana Gonzalez Zarzosa'; WALLER Adrian; TRABELSI, Slim; DANGERVILLE Cyril; 'ext Wolfgang.Steigerwald at telekom.de'
Cc: 'fiware-security at lists.fi-ware.eu'
Subject: RE: [Fiware-security] FIWARE - backlog review

Hello Robert, Richard, Pascal

Sorry, maybe a naïve question :  shouldn't *only* epics and features (listed on "materializing security") being considered for a release, be part of the roadmap wiki page for that release?

Francesco

From: Seidl, Robert (NSN - DE/Munich) [mailto:robert.seidl at nsn.com]
Sent: mercredi 27 février 2013 12:31
To: ext EGAN Richard; 'Susana Gonzalez Zarzosa'; DI CERBO, Francesco; WALLER Adrian; TRABELSI, Slim; DANGERVILLE Cyril; 'ext Wolfgang.Steigerwald at telekom.de'
Cc: 'fiware-security at lists.fi-ware.eu'
Subject: RE: [Fiware-security] FIWARE - backlog review

Hi Pascal,
Richard touched a valid point.
Indeed there is a big mismatch between both WIKI pages.
Maybe not only for IDM.
How should we handle this?
Should we copy all relevant FEATURES, EPICS, ... from the "Materializing" to the "Roadmap of Security" in order to align both pages?
So far we kept the "Materializing" pages as reference.

Greetings
Robert

From: ext EGAN Richard [mailto:Richard.Egan at uk.thalesgroup.com]
Sent: Wednesday, February 27, 2013 12:15 PM
To: Seidl, Robert (NSN - DE/Munich); 'Susana Gonzalez Zarzosa'; 'DI CERBO, Francesco'; WALLER Adrian; 'TRABELSI, Slim'; DANGERVILLE Cyril; 'ext Wolfgang.Steigerwald at telekom.de'
Cc: 'fiware-security at lists.fi-ware.eu'
Subject: RE: [Fiware-security] FIWARE - backlog review

Robert,

Technical Roadmap: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Security#Second_Major_Release_.283Q_2013.29

Materalising: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Security_in_FI-WARE

Richard

From: Seidl, Robert (NSN - DE/Munich) [mailto:robert.seidl at nsn.com]
Sent: 27 February 2013 11:11
To: EGAN Richard; 'Susana Gonzalez Zarzosa'; 'DI CERBO, Francesco'; WALLER Adrian; 'TRABELSI, Slim'; DANGERVILLE Cyril; 'ext Wolfgang.Steigerwald at telekom.de<mailto:Wolfgang.Steigerwald at telekom.de>'
Cc: 'fiware-security at lists.fi-ware.eu'
Subject: RE: [Fiware-security] FIWARE - backlog review

Hi Richard,
Many thanks for the hint.
Could you copy me the links of both parts, so that I can check it?
As always the WIKI makes me quite confusing :(

Greetings
Robert

From: ext EGAN Richard [mailto:Richard.Egan at uk.thalesgroup.com]
Sent: Wednesday, February 27, 2013 11:52 AM
To: Seidl, Robert (NSN - DE/Munich); 'Susana Gonzalez Zarzosa'; 'DI CERBO, Francesco'; WALLER Adrian; 'TRABELSI, Slim'; DANGERVILLE Cyril; 'ext Wolfgang.Steigerwald at telekom.de<mailto:Wolfgang.Steigerwald at telekom.de>'
Cc: 'fiware-security at lists.fi-ware.eu'
Subject: RE: [Fiware-security] FIWARE - backlog review

Robert,

we have fixed 100 and 148 (the naming of the work items did not position them in the IDM GE)

BTW, for IDM I see a lot of Features in the "Materialising" part of the wiki but they are not in the "Technical Roadmap" section. In fact, there is a big lack of Features in the IDM Technical Roadmap - it is not part of Manuel's review but it is an important point.

Richard

From: 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] On Behalf Of Seidl, Robert (NSN - DE/Munich)
Sent: 27 February 2013 09:24
To: Susana Gonzalez Zarzosa; DI CERBO, Francesco; WALLER Adrian; EGAN Richard; TRABELSI, Slim; DANGERVILLE Cyril; ext Wolfgang.Steigerwald at telekom.de<mailto:Wolfgang.Steigerwald at telekom.de>
Cc: 'fiware-security at lists.fi-ware.eu'
Subject: Re: [Fiware-security] FIWARE - backlog review

Hi all,
I have checked the Excel table with respect to T8.2.

Following issues (lines in Excel table) are still open:

Francesco/Slim: 8, 34, 35, 36, 86, 181, 258
Susanna: 31
Adrian/Richard: 100, 148
Robert: 107
Cyril: 214
Wolfgang: 259, 260, 261, 262

Please have a look on this topics and if possible try to figure out what the issue behind could be.

Many thanks in advance
Robert

From: ext BISSON Pascal [mailto:pascal.bisson at thalesgroup.com]
Sent: Tuesday, February 26, 2013 7:48 PM
To: Seidl, Robert (NSN - DE/Munich); Susana Gonzalez Zarzosa; DI CERBO, Francesco; GIDOIN Daniel
Cc: BISSON Pascal; 'fiware-security at lists.fi-ware.eu'
Subject: TR: FIWARE - backlog review
Importance: High

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20130227/12853efb/attachment.html>


More information about the Old-Fiware-security mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy