[Fiware-wpa] [Fiware-wpl] Actions Points to be Done

[BISSON Pascal]

Dear Colleagues,

I'm just forwarding you this email from Juanjo to remind you the Action Points Daniel and I on behalf of Security team were requesting from each of you.

Counting on you to work on those actions points and report to us asap.

Reading you soon.

Pascal / Daniel


 *   Address APs identified during Security plenary session:
    *   Each Chapter to provide their answers to the questions raised by the Security team for each of the Security GEs (the sooner, the better and no later than by end of this week so 3/02/2012)
    *   Each Chapters to consider integration of Security GEs within their Chapter architecture and whenever those are needed and at appropriate level (i.e. architecture level, GE level).   As a first step, this should lead to definition of at least one Epic by chapter and GEs to reflect this as ongoing work
    *   Each Chapter to analyze the interaction (sequence) diagram with the Security Monitoring GE to check, amend/complete and validate them (there is one for each of the Chapters that was elaborated by the Security team).   This is needed prior delivery of the information requested by the Security Chapter (i.e. log, security events, countermeasures, ....) by Security Monitoring GE (also gets the architecture of the chapter ready to have this information delivered). The Security chapter will provide other chapters with information needed by Security Monitoring GE (also format under which this information has to be provided)


De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro
Envoyé : mardi 31 janvier 2012 11:22
À : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Objet : [Fiware-wpl] Actions Points to be Done

Dear WPLs/WPAs,

  I plan to deliver more precise guidelines, including some templates sometime today but probably very late in the evening, effectively to be ready tomorrow morning because I'm currently very busy finalization of the publication of the first Open Call which was due by today.

  Apologize for any problem this may cause, but I hope you will understand.   In the meantime, please try to deal with the couple of urgent points that we revised during last week WPL/WPA meeting (some of them commented during our joint confcall yesterday).    We should not forget to address them:

 *   Provide complete and accurate minutes of the f2f meeting last week.   As announced, Miguel sent detailed instructions to follow regarding this (based on feedback by some partners, we will change the place where you should upload them, Miguel will send an email updating on this).   PLEASE don't forget to transform Actions Points you identified into WorkItems in the corresponding tracker (your chapter tracker or the FI-WARE-Private tracker).   Miguel will setup a Backlog Management tracker on the "FI-WARE Private" project so that you will be able to create WorkItems you believe that need to be addressed and followed-up at FI-WARE global level.
 *   Complete response to questionnaire distributed by the Testbed team.   This is urgent in order to complete the Testbed design.
 *   SAP: complete revision of Epics linked to BM&BE GE being considered in the first Open Call.
 *   Planning of sprint 4 (this requires the first point regarding identification of WorkItems to be done)
 *   Address APs identified during Security plenary session:
    *   Each Chapter to provide their answers to the questions raised by the Security team for each of the Security GEs (the sooner, the better and no later than by end of this week so 3/02/2012)
    *   Each Chapters to consider integration of Security GEs within their Chapter architecture and whenever those are needed and at appropriate level (i.e. architecture level, GE level).   As a first step, this should lead to definition of at least one Epic by chapter and GEs to reflect this as ongoing work
    *   Each Chapter to analyze the interaction (sequence) diagram with the Security Monitoring GE to check, amend/complete and validate them (there is one for each of the Chapters that was elaborated by the Security team).   This is needed prior delivery of the information requested by the Security Chapter (i.e. log, security events, countermeasures, ....) by Security Monitoring GE (also gets the architecture of the chapter ready to have this information delivered). The Security chapter will provide other chapters with information needed by Security Monitoring GE (also format under which this information has to be provided)
 *   Review status of UC project tickets to update them or make some progress.   Don't forget to change the assignee of a ticket to be the issuer whenever you change the state to "Needs revision by the issuer".
 *   Standardization Plan: please check latest requests on the matter ... there is info pending !

  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) Chief Architect



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-wpa/attachments/20120206/8cadabcb/attachment.html>