[Fiware-apps] FW: [Fiware-wpa] Minutes of confcall today

[Leidig, Torsten]

Dear project partners,

please find attached the minutes of yesterday's WPL/WPA concall.

Please have a look at the schedule for the joint sessions in Madrid. We will use the slots left over for our own WP3 internal discussions. Please use the Streamwork Activity to enter your presence for the meeting week. Also put in your topics to be discussed during the meeting. We will derive a schedule then.

Best regards,
Torsten


Dr. Torsten Leidig
SAP Research Center CEC Karlsruhe
SAP AG
Vincenz-Prießnitz-Str. 1
76131 Karlsruhe
T +49 6227 7 52535
F +49 6227 78 29753
E torsten.leidig at sap.com
http://www.sap.com
Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx
Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.

This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.




From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro
Sent: Donnerstag, 12. Januar 2012 19:00
To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Subject: [Fiware-wpa] Minutes of confcall today

Dear all,

  Please find below the minutes of our joint WPL/WPA confcall.   Please share with your teams.


1. Debate on how to organize the agenda on Monday:

 *   From 09:00 to 11:00   IoT - Data Architecture Chapter discussion, taking advantage that Denes and Thierry will arrive at 09:00am
 *   From 11:00 to 12:00-13:00  Alex joins and then we carry out discussion about Accounting/Monitoring Architecture for the Cloud (ability to reuse aspects from IoT)


 *   The joint WPL/WPA meeting would start sharp at 13:00pm (temporarely, depending on the agenda we finally agree.  We may decide to start at 14:00 if there are not so many topics

 *   AP: Miguel: confirm there is a room available during the morning.
 *   AP: Juanjo to send an proposad agenda for the meeting to start after lunch
 *   AP: All to send topics they would like to include in the agenda


2. Allocation of joint WP sessions

 *   AP: All WPLs to work on closing when their joint WP sessions are going to take place before Tuesday 17th EOB.   Record agreements on Google Docs shared spreadsheet: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdFVQMzYzOFJvNzFncTR3YjdOVVNTVnc

 *   AP: All WPLs and for the benefit of people on their teams to fix the date and time at which they will have to leave taking into account potential joint sessions.   Juanjo: I would be very surprise if a chapter teams declares they can leave on Wednesday.    Deadline for this AP: end of this week.

 *   AP: WPLs to provide number of people from their WPs attending each slot, to both individual WP meetings and joint sessions.  Send information to Miguel following the spreadsheet he has distributed this morning.   Deadline: before Tuesday 17th EOB

3. Videos for dissemination

  We will plan to record videos with the WPLs that we can use later for dissemination
  purposes.

 *   AP: Carlos to distribute next week a kind of questionnaire/script for these interviews among WPLs + key messages to deliver


4. Backlog deliverable (fixing a number of issues)

  We generated a snapshot of the trackers for each chapter before Christmas in order to submit this deliverable which was planned by the end of November.  However,
while reviewing its contents, we found a number of typos, incosistencies, etc.

  Carlos is preparing a report that will be forwarded to all WPLs with fixes to be implemented on all the trackers and to be taken care of from now on in subsequent Sprints.


5. Architecture Specification deliverable

  Round table to check the status about this deliverable which is due by end of the month.

 *   Cloud:
    *   Expectations not clear.  Need some clarifications.  Not have started yet.
    *   AP: Alex to write down an email elaborating on the concrete concerns they have.

 *   Security:
    *   Difficulties to specify the Identity Management and Access Control Architecture Specifications.  Already in progress regarding optional GEs.
    *   Concerns on how to differentiate from what it was expected in month 9 and what is expected in month 12.  Juanjo: this was clear in the examples.  The CORBA Event Service spec whas a example of complete and detailed specification where some of the sections would be equivalent to what is now due in month 9 and the detailed OMG IDL specfications correspond to what would be delivered in month 12:
       *   detailed specifications of interfaces go to month 12: signatures of operations and detailed behavior description
       *   overview and description of what entities/interfaces exists, basic data models, name of operations and description of scenarios of interaction between the entities: this goes for month 9
    *   AP: Pascal to share the progress on the optional Security GEs and Juanjo will give feedback about approach they have adopted and whether they are going in the right direction from his perspective.  Let's discuss that feedback openly on the mailing list.   Hopefully what they have done could also work as reference example
    *   AP: Pascal to share concrete concerns (what is not understood in the examples provided ?) that Juanjo and others can discuss and reach an agreement how to address

 *   IoT:
    *   Denes show how they had approached this.   Seems like in the right direction and they have started using FMC convention.  We agreed to share this with the rest of WPs.
    *   Pier: Shoudln't we edit this deliverable in a common private wiki (the one linked to the "FI-WARE Private" project in FusionForge) ?  Juanjo: I would agree, but want to see there is no objection from others.  Denes: some partners may be reluctant to share.  Juanjo: there shouldn't be anything on the Architecture Specifications that is protected.  Remember this is a Public Deliverable.
    *   AP: Juanjo to raise discussion on how to approach editing of the Architecture Specifications (common vs per-chapter wikis).  Pier suggested to use the common private Wiki and Juanjo agrees

 *   I2ND:
    *   Not progress so far but share there are some concerns.  Juanjo: you should be explicit, otherwise there is no mean to answer.
    *   AP: Pier to send email raising concrete concerns/issues about format/scope

 *   Data: Carlos was not present but then came back.  Chapter is delayed on work.   Basic TOC to be put was going to be placed in private Wiki and teams have committed to start working by end of this week, early next one.
    *   AP: Carlos to be ready to change to the "FI-WARE Private" project Wiki if that is what is agreed.

 *   Apps: No one present at the moment.   There is no report.

 *   DevTools: Will plan to move some contents of their private wiki to the "FI-WARE Private" project wiki so that others can get an early access to deliverables being developed by this chapter.  Juanjo: this is a good idea in general for public deliverables.

6. Technical Roadmap deliverable

 *   AP: Juanjo to send an email on description of approach that could be followed to address this in a pragmatic way

7. AOB

Left for joint WPLs/WPAs meeting on Monday 23rd (not so urgent to be tackled):

+ Web portals style guide

+ First Open Call revision

+ Common Development tools - sw technology infrastructures (e.g. RDBMS, Web servers, Operating system, ...)






--

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

Juanjo Hierro



Product Development and Innovation (PDI) - Telefonica Digital

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/old-fiware-apps/attachments/20120113/84c9f551/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20120113/84c9f551/attachment.txt>