[Fiware-idm-ge] Task Force to push things forward regarding FI-WARE GE open specifications

[BISSON Pascal]

Hi Juanjo,

Thanks for the set-up of this dedicated mailing list we agreed to set-up at last WPL/WPA audio conf to discuss IdM GE topics we have to accross chapter in view of what has been specified and/or implemented from both sides (i.e. Cloud (IdM GE UPM) and Security Chapter (IdM GE NSN/DT and Access Control/THA).

And yes I confirm I received your message (in fact twice). So it works.
Please confirm us the next audio conf on IdM GE for enlisted people to secure their participation and in case some couldn't make it to find another slot.

As for SecMon topics we also have to address across chapter (starting first with Cloud) please let us know once the dedicated mailing has been created and also inform enrolled people for the next audio on the topic. Could be next Monday afternoon since Daniel I think this time would be there.

Regards,
Pascal


De : fiware-idm-ge-bounces at lists.fi-ware.eu [mailto:fiware-idm-ge-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro
Envoyé : mercredi 18 septembre 2013 11:08
À : fiware-idm-ge at lists.fi-ware.eu
Objet : [Fiware-idm-ge] Task Force to push things forward regarding FI-WARE GE open specifications

Hi,

  I'm resending this message just in case it didn't pass through in a firs shot.

  Cheers,

-- Juanjo

-------- Original Message --------
Subject:

Task Force to push things forward regarding FI-WARE GE open specifications

Date:

Wed, 18 Sep 2013 11:03:50 +0200

From:

Juanjo Hierro <jhierro at tid.es><mailto:jhierro at tid.es>

To:

fiware-idm-ge at lists.fi-ware.eu<mailto:fiware-idm-ge at lists.fi-ware.eu>



Hi all,

  As per agreement reached in the WPL/WPA follow-up confcall yesterday, we have setup a Task Force targeted to solve the issues still present regarding IdM GE specifications and IdM GEis documentation in FI-WARE.

  This Task Force will have associated a mailing list to carry out efficient discussion on the matter, which is the one this email has been forwarded to.

  Pascal will be responsible of keep things moving and meet the milestones and I will personally keep a close eye to progress.   Eventually, we will setup some dedicated confcalls, some of them to be co-located as part of the afternoon session of the weekly WPLs/WPAs follow-up confcall scheduled to be every Monday from 14:30 to 16:00.

  The first very urgent action to perform has to do with fixing the status of the FI-WARE IdM GE open specifications.   As per now, what is there cannot be considered complete and in some aspect, clearly wrong:

 *   It is not the intend to replicate specifications that are standard and public.   Links to them are enough, BUT, we should clearly document what parts of those specs are going to be supported (and if they are completely supported, say it explicitly)
 *   There shouldn't be only specs to high-level abstract standard specs but also links to the REST API bindings where available.   If no standard REST API is available, we should specify one.
 *   We should include the references to SCIM at least in terms of documenting what we intend to support regarding them.
 *   Publication of URL of service end points linked to particular instances of a IdM GEi - GE implementation product doesn't make sense as part of a specification
 *   There shouldn't appear references to particular products of companies.

  The second urgent action has to do with fixing the way the backlog linked to IdM GEis is being approached.   It is fine to have a single set of Epics and Features shared by all the IdM GEis if we are mapping those Epics and Features to functions linked to standards to be supported, although this would imply certain level of synchronization that may slow you so you have to think this carefully.   However, if you ALL agree to keep dealing with a single set of Epics and Features, then there should be a) different entries per each of the GEi in the Technical Roadmap because I can anticipate that the speed of development by the teams working in each GEi (i.e., the NSN, DT and UPM teams) will not be the same.   Besides this, the mapping of features into user stories should lead to different entries in the backlog tracker for each of the teams because precisely the same reason.

  The third urgent action has to do with reviewing documentation linked to each of the IdM GEis in the FI-WARE Catalogue (in the case of UPM, they will have to create a new entry documenting their product).

  The fourth action has to do with making sure that the software being delivered complies with the requirements established linked to documentation and unit testing.

  There may come some additional urgent actions in the meantime, but this are at least the ones I would like to focus on in the short term.

  If you have any doubts, don't hesitate to ask.

  Following is the table of current members of the Task Force.   If you wish to add someone else, don't hesitate to tell me so that I can add him/her.


[cid:image002.jpg at 01CEB462.44499230]


  I hope that a fruitful discussion will take place and we will soon arrive to the status where we should be for this crucial GE in FI-WARE.

  Best regards,



-- Juanjo



-------------

Product Development and Innovation (PDI) - Telefonica Digital

website: www.tid.es<http://www.tid.es>

email: jhierro at tid.es<mailto:jhierro at tid.es>

twitter: twitter.com/JuanjoHierro



FI-WARE (European Future Internet Core Platform) Coordinator

and Chief Architect



FI-PPP Architecture Board chairman



You can follow FI-WARE at:

  website:  http://www.fi-ware.eu

  facebook: http://www.facebook.com/pages/FI-WARE/251366491587242

  twitter:  http://twitter.com/FIware

  linkedIn: http://www.linkedin.com/groups/FIWARE-4239932


________________________________

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/fiware-idm-ge/attachments/20130918/15e0a954/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 53085 bytes
Desc: image002.jpg
URL: <https://lists.fiware.org/private/fiware-idm-ge/attachments/20130918/15e0a954/attachment.jpg>