From pascal.bisson at thalesgroup.com Fri Mar 1 14:34:58 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Fri, 1 Mar 2013 14:34:58 +0100
Subject: [Fiware-security] TR: [Fiware-wpl] Backlog - Sprint transition:
from S2.2.2-M22 to S2.2.3-M23
Message-ID: <29179_1362144905_5130AE89_29179_2673_1_98118543-06e3-474b-bff8-9df26b48a4ae@THSONEA01HUB06P.one.grp>
Dear All,
Please follow Manuel's instructions to update tickets on the tracker accordingly since indeed Sprint 2.2.2 is now over and we just entered Sprint 2.2.3. This update would be assessed at our next WP8 audio.
And Yes I will never say it enough it is important to keep entries (aka tickets) on the tracker up to date !
Best Regards,
Pascal
De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de MANUEL ESCRICHE VICENTE
Envoy? : vendredi 1 mars 2013 13:12
? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Objet : [Fiware-wpl] Backlog - Sprint transition: from S2.2.2-M22 to S2.2.3-M23
Dear Partners,
As you know yesterday we finished Sprint 2.2.2 corresponding to M22, today we start activities belonging to Sprint 2.2.3 corresponding to M23.
Please, update your backlog accordingly.
1. Close the tickets you finished along M22 (probably you already did these days when updating the tickets), otherwise, do it
2. Update tickets under execution to belong to Sprint 2.2.3-M23
During next week we should be able to identify and refine all content meant to be done during Sprint S2.2.3-M23.
Next week I'll contact you to understand how your backlog for S2.2.3 is defined.
During these months we'll improve the tools with a dashboard giving us visual views on how our backlog is evolving during sprints and realeases... for the different enablers, partners, etc.
As soon as I can I'll share the consistency rules to be applied to the backlog, so that we all have unanimous understanding and consensus.
If anything, please, don't hesitate to let me know.
Have a nice weekend!!
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
________________________________
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:
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL:
From pascal.bisson at thalesgroup.com Fri Mar 1 15:39:49 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Fri, 1 Mar 2013 15:39:49 +0100
Subject: [Fiware-security] FI-WARE - Security WP8 - Audio conf of today
(Minutes)
Message-ID: <27760_1362148796_5130BDBC_27760_5995_3_43e04d1c-9286-4e3a-bed4-e546229eeb37@THSONEA01HUB01P.one.grp>
Dear All,
This email to let you know that I've just uploaded on our Chapter repository the minutes of our weekly audio conf of today.
https://forge.fi-ware.eu/docman/view.php/19/1896/FI-WARE_WP8_Minutes_01_03_2013.doc
Please have a look and counting on you to perform your actions especially to:
1. close work by today on Technology Roadmap & Wiki/Tracker Update since TID will generate it by EOB today.
2. Get ready by early next week a complete for set of Chapter's contrib. for V2 Architecture Description.
Many thanks in advance to you ALL.
Best Regards,
Pascal
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From pascal.bisson at thalesgroup.com Fri Mar 1 17:49:33 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Fri, 1 Mar 2013 17:49:33 +0100
Subject: [Fiware-security] FI-WARE - Architecture description for V2
[reminding you the guidelines already provided]
Message-ID: <27040_1362156798_5130DCFE_27040_18488_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E2A9F785@THSONEA01CMS04P.one.grp>
Just to remind you guidelines which could be helpful to you with respect to Architecture Description for V2. This in addition to what we discussed already.
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions
BR
Pascal
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From pascal.bisson at thalesgroup.com Tue Mar 5 17:43:01 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Tue, 5 Mar 2013 17:43:01 +0100
Subject: [Fiware-security] TR: [Fiware-wpl] Monitoring of log/trace files
Message-ID: <6899_1362501789_5136209D_6899_124_1_8ec9b768-a31c-4205-bc7c-7fa53713084e@THSONEA01HUB05P.one.grp>
Dear All,
On behalf of Daniel's I would like to resend this to you. Can each one of the GE owners in the Security chapter send an example of the log files and/or traces to MARCEL at il.ibm.com and put me and Daniel in CC? Please do not forget to state the name of your GE when you send this.
Many thanks in advance,
Best Regards,
Pascal
De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Davide Dalle Carbonare
Envoy? : mardi 5 mars 2013 15:16
? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Objet : [Fiware-wpl] Monitoring of log/trace files
Dear partners,
I'd like to remind you one point we've on the minutes:
"Monitoring of log/trace files"
https://docs.google.com/document/d/1ml3Z1DidK1fW-vIgaUy9t06m0-VGdAOhmcQD8c3qBlk/edit#heading=h.kqxdoinbwzxy
@Juanjo, can you kindly send a feedback on what's your take on the
purpose and technology points reported on the minutes?
@WPAs, can you kindly forward to your GEi providers the request to
send an example of log/trace files produced by their GE implementations?
Please send the logs to Marcel Zalmanovici
and to the WPA mailing list.
I'm expecting to receive one example per GEi that will be available
for release 2.
Kind Regards,
Davide
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL:
From Richard.Egan at uk.thalesgroup.com Tue Mar 5 18:44:38 2013
From: Richard.Egan at uk.thalesgroup.com (EGAN Richard)
Date: Tue, 5 Mar 2013 17:44:38 +0000
Subject: [Fiware-security] [Fiware-wpl] Monitoring of log/trace files
In-Reply-To: <6899_1362501789_5136209D_6899_124_1_8ec9b768-a31c-4205-bc7c-7fa53713084e@THSONEA01HUB05P.one.grp>
References: <6899_1362501789_5136209D_6899_124_1_8ec9b768-a31c-4205-bc7c-7fa53713084e@THSONEA01HUB05P.one.grp>
Message-ID: <7C80A1EAA66A4F45BA3A574774382B9BA90A95CF7F@THSONEP02CMB01P.one-02-priv.grp>
Pascal,
I do not understand the request - could you explain the context briefly? How do we get these log files?
Richard
From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal
Sent: 05 March 2013 16:43
To: fiware-security at lists.fi-ware.eu
Subject: [Fiware-security] TR: [Fiware-wpl] Monitoring of log/trace files
Importance: High
Dear All,
On behalf of Daniel's I would like to resend this to you. Can each one of the GE owners in the Security chapter send an example of the log files and/or traces to MARCEL at il.ibm.com and put me and Daniel in CC? Please do not forget to state the name of your GE when you send this.
Many thanks in advance,
Best Regards,
Pascal
De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Davide Dalle Carbonare
Envoy? : mardi 5 mars 2013 15:16
? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Objet : [Fiware-wpl] Monitoring of log/trace files
Dear partners,
I'd like to remind you one point we've on the minutes:
"Monitoring of log/trace files"
https://docs.google.com/document/d/1ml3Z1DidK1fW-vIgaUy9t06m0-VGdAOhmcQD8c3qBlk/edit#heading=h.kqxdoinbwzxy
@Juanjo, can you kindly send a feedback on what's your take on the
purpose and technology points reported on the minutes?
@WPAs, can you kindly forward to your GEi providers the request to
send an example of log/trace files produced by their GE implementations?
Please send the logs to Marcel Zalmanovici
and to the WPA mailing list.
I'm expecting to receive one example per GEi that will be available
for release 2.
Kind Regards,
Davide
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From pascal.bisson at thalesgroup.com Wed Mar 6 09:46:57 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Wed, 6 Mar 2013 09:46:57 +0100
Subject: [Fiware-security] FI-WARE Architecture Description V2
Message-ID: <867_1362559851_5137036B_867_7470_4_552b0a94-99e8-48cb-909e-996b887f3678@THSONEA01HUB02P.one.grp>
Dear All,
As outlined below, we need to deliver a consolidated architecture document for our WP by the end of the week.
We plan to produce the consolidated draft on Friday EOB.
Please take necessary steps to get your GE Architecture Description ready for integration by Thursday and at the very latest by Friday EOB.
Once your GE is ready for integration please let us (me/Daniel) know
Please, let us know as soon as your GE is ready for integration also where to find is (provide us with the link not to force me/us to figure where it is - public, private wiki ...)
As for the rest and hopefully we will have our audio conference on Friday at 10am to properly check this and other topics we need to address.
Thanks for your cooperation and support
Pascal
Procedure for the Architecture review.
The calendar is the one agreed yesterday in the WPL/WPA call:
1. First draft of contributions by chapter ready for peer review: end of February
2. .docx first version of chapter ready by March 8
3. Comments on first draft (.docx with traced changes) due by March 13th
4. .docx second version of chapters ready for peer review: March 22nd
5. Comments on second draft due by April 2nd
6. Final version: April 10th
As already reminded, the guidelines for the Architecture doc are under: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions
The process will be like reflected on the FI-WARE Architecture peer-review cockpit:
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From mcp at tid.es Thu Mar 7 07:56:24 2013
From: mcp at tid.es (Miguel Carrillo)
Date: Thu, 07 Mar 2013 07:56:24 +0100
Subject: [Fiware-security] [Fiware-secure-cloud] Mailing list for
discusion on Security Monitoring in the Cloud
In-Reply-To:
References: <51359159.3010208@tid.es>
Message-ID: <51383A18.2080702@tid.es>
Good morning,
Done. This is what we have now:
[cid:part1.04050001.03010208 at tid.es]
Regards,
Miguel
El 07/03/2013 7:29, Alex Glikson escribi?:
> From: Juanjo Hierro
[...]
> Please let Miguel and me know who should be also in the
> list so that we can add them.
Please, subscribe the people in cc.
> Alex, you mentioned that two attack scenarios had been identified
> during the Cloud WP F2F meeting in Haifa, so I guess it would be nice if
> you share them in this mail list (once the whole list of subscriptors is
> done) and then discuss them on the mailing list.
Sure, will do.
Alex
> -- Juanjo
--
----------------------------------------------------------------------
_/ _/_/ Miguel Carrillo Pacheco
_/ _/ _/ _/ Telef?nica Distrito Telef?nica
_/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4
_/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N
_/ _/_/ 28050 Madrid (Spain)
Tel: (+34) 91 483 26 77
e-mail: mcp at tid.es
Follow FI-WARE on the net
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:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: abegfbjc.png
Type: image/png
Size: 7295 bytes
Desc: not available
URL:
From xavier.aghina at orange.com Fri Mar 8 08:30:07 2013
From: xavier.aghina at orange.com (xavier.aghina at orange.com)
Date: Fri, 8 Mar 2013 07:30:07 +0000
Subject: [Fiware-security] SecMon GE Architecture Description Review as
per Today
In-Reply-To: <2101_1362669959_5138B187_2101_12888_1_f5187426-c6a7-4162-bf8e-0d5b94a63840@THSONEA01HUB06P.one.grp>
References: <2101_1362669959_5138B187_2101_12888_1_f5187426-c6a7-4162-bf8e-0d5b94a63840@THSONEA01HUB06P.one.grp>
Message-ID: <6685_1362727808_51399380_6685_463_1_81FF741594681345A3FBB024B01054B90A1241@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Hello everyone, I'm off for the day and next week, I brought a lot of changes to the architecture folder (Wiki) which should have an impact on the document review (Rewiew of Architecture Description for Security Monitoring GE V2). Thank you for making me a return of your comments / questions. Good phone call.
Xavier.
De : BISSON Pascal [mailto:pascal.bisson at thalesgroup.com]
Envoy? : jeudi 7 mars 2013 16:22
? : EGAN Richard; susana.gzarzosa at atosresearch.eu; Alexandre Boeglin; MUSARAJ Kreshnik; AGHINA Xavier OLNC/OLPS; GASPARD Lucie
Cc : BISSON Pascal; GIDOIN Daniel
Objet : SecMon GE Architecture Description Review as per Today
Importance : Haute
Dear All,
Find attached to this email a review I performed of the SecMon GE Architecture Description for V2 as per today.
Please see my review comments.
As for the rest let's have this and other be discussed at tomorrow's audio.
Best Regards,
Pascal
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Review of Architecture Description for Security Monitoring GE V2-THA_PB.DOC
Type: application/msword
Size: 50176 bytes
Desc: Review of Architecture Description for Security Monitoring GE V2-THA_PB.DOC
URL:
From pascal.bisson at thalesgroup.com Fri Mar 8 11:06:30 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Fri, 8 Mar 2013 11:06:30 +0100
Subject: [Fiware-security] (no subject)
Message-ID: <31620_1362737311_5139B89F_31620_9905_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E3DB8616@THSONEA01CMS04P.one.grp>
http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Global_FI-WARE_functions
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From francesco.di.cerbo at sap.com Fri Mar 8 11:31:30 2013
From: francesco.di.cerbo at sap.com (DI CERBO, Francesco)
Date: Fri, 8 Mar 2013 10:31:30 +0000
Subject: [Fiware-security] Guidelines for Open Specification docs (used for
V1)
Message-ID: <6D11E010ED8E5B4B9D42045AC71F37E60707952F@DEWDFEMB18B.global.corp.sap>
Hello all,
At this link, it is possible to find all guidelines for creating the Open Specification documents.
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverables
best regards,
Francesco
___
Francesco Di Cerbo, PhD
SAP Next Business and Technology
Applied Research
Security & Trust
SAP Labs France
805, avenue Maurice Donat
Font de l'Orme
BP 1216
06250 Mougins Cedex
France
Tel. +33 4 92 28 64 45
e-mail: Francesco.Di.Cerbo at sap.com
From pascal.bisson at thalesgroup.com Mon Mar 11 19:13:59 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Mon, 11 Mar 2013 19:13:59 +0100
Subject: [Fiware-security] TR: FI-WARE / Security Chapter contrib to D2.3.2
ready for peer review
Message-ID: <1973_1363025645_513E1EE9_1973_19_1_2c110fcd-754d-42d3-b388-36a7ea7eb25e@THSONEA01HUB06P.one.grp>
FYI
Please let me know who is volunteer to peer-review Apps Chapter.
I need at least two volunteers. If no one volunteer by tomorrow lunch time I would appoint reviewers at the level of our team.
Hearing from you.
As for the rest I managed our Chapter contrib. has been produced and you have the link when accessing the peer review cockpit. The doc is here http://www.google.com/url?q=https://forge.fi-ware.eu/docman/view.php/27/1922/D232_WP8_v3_generated_2013-03-11.doc&usd=1&usg=ALhdy2-DK-NQZ05xUi8yq4lzgRbSw-Z-sA
Regarding peer review of this doc will keep you posted as soon as it arrives.
BR
Pascal
De : BISSON Pascal
Envoy? : lundi 11 mars 2013 19:08
? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Cc : BISSON Pascal; GIDOIN Daniel
Objet : FI-WARE / Security Chapter contrib to D2.3.2 ready for peer review
Importance : Haute
Dear Colleagues,
This email just to let you know that Security Chapter contrib. has been uploaded and is ready for peer review.
Cockpit has been updated accordingly with the link to the Doc (cf. https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0)
Best Regards,
Pascal
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From pascal.bisson at thalesgroup.com Tue Mar 12 10:01:49 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Tue, 12 Mar 2013 10:01:49 +0100
Subject: [Fiware-security] TR: [Fiware] Source code and binary packages
releasing procedure for FI-WARE Release 2
Message-ID: <26924_1363079156_513EEFF0_26924_62_3_CBBCD6C304123F4AB23FAAE3055C8C0E0206E40A60BB@THSONEA01CMS04P.one.grp>
Dear All,
Not sure I forwarded you this email but in the doubt I'm resending it to you since important for you to consider and more specifically the ones of you who have to deliver software release of their GEs for V2.
Counting on you all to have a look and bear in mind those guidelines and instructions provided when delivering you GE software release (time will come).
Best Regards,
Pascal
-----Message d'origine-----
De?: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] De la part de Ferm?n Gal?n M?rquez
Envoy??: mardi 5 f?vrier 2013 16:21
??: fiware at lists.fi-ware.eu
Objet?: [Fiware] Source code and binary packages releasing procedure for FI-WARE Release 2
Hi,
We have defined a guide on how to release source code and binary packages for FI-WARE release 2 and beyond, that can be found at:
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tutorial_releasing_fiware
(It is also linked from the Handbooks section in the FIWARE wiki main page)
This is the procedure that each GEi implementor must follow when releasing the software for Release 2. Although it will be at that time when you will need to follow it, we think a good idea to publish it in the wiki and send this email at the present moment so you can know it in advance and even use it for releasing any GEi release between now and Release 2 if you want.
We used SCM (i.e. Subversion) in the previous release due to problems with the "Files" tool on the forge that are solved now. The old delivery of Release 1 can stay as it is (there's no need to migrate) but the next ones will use the "Files" part of the forge, that is more adequate for our needs and gives a better impression, especially towards external developers communities.
Please, don't hesitate to contact me if you have any doubt or comment.
Thanks!
Best regards,
------
Ferm?n
________________________________
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 mailing list
Fiware at lists.fi-ware.eu
http://lists.fi-ware.eu/listinfo/fiware
From pascal.bisson at thalesgroup.com Wed Mar 13 12:34:07 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Wed, 13 Mar 2013 12:34:07 +0100
Subject: [Fiware-security] TR: [Fiware-standardization] Planning calendar
link exists, what kind of activity can _your_ Work Package propose ??
Message-ID: <27936_1363174457_51406433_27936_73_3_dd97fea6-60c7-4750-8f82-357d44944bf0@THSONEA01HUB02P.one.grp>
Dear All,
I'm forwarding you this important email received from Juan Bareno calling for action for any of you having previously stated interest (e.g. GE owners although not uniquely) and reported activities (e.g. IBM, INRIA) for what concerns Standardization.
Counting on you each of you to have a look and addressed it the way expected.
Will review this demand has been addressed at Friday's audio.
Thanks in advance for cooperation & support. And yes it is important and will not take that long to each of the expected contributors.
Best Regards,
Pascal
De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juan Bare?o Guerenabarrena
Envoy? : lundi 11 mars 2013 15:45
? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-standardization at lists.fi-ware.eu
Cc : Lindsay.Frost at neclab.eu
Objet : [Fiware-wpl] [Fiware-standardization] Planning calendar link exists, what kind of activity can _your_ Work Package propose ??
Dear All
Please find here enclosed the "Standardization calendar link" to fulfil with your WP contribution (presentation, demo, express FI-WARE support.......) to specific Standards. So, what kind of activity can _your_ Work Package propose ??"
https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Main_Page#FI-WARE_Exploitation
"The idea is to pick SDO meetings where your Work Package _intends_ to make some contribution or presentation or demo or even just "express FI-WARE support for a Work Item or agreed Specification".
This will show the EU commission and all FI-WARE partners that FI-WARE is impacting standards. Of course changes and delays etc will happen frequently, but it is important to start this.
Example: DRAFT SCHEDULE "OSGi Cloud proxy" Presentation and/or Demo of WP7 "Interfaces
to network" technology at HGI EVENT. Contact = luca.giacomello at telecomitalia.it
Thanks for your contribution
Juan
[cid:image001.png at 01CE1E6E.856B4A40]
Juan Bare?o
Group Innovation, Business Development & Strategy
Research & Innovation
+34 912148859
Calle Albarrac?n 25, 28037 Madrid
juan.bareno at atos.net
www.atos.net
[cid:image002.gif at 01CE1E6E.856B4A40]
From: fiware-standardization-bounces at lists.fi-ware.eu [mailto:fiware-standardization-bounces at lists.fi-ware.eu] On Behalf Of Lindsay Frost
Sent: jueves, 28 de febrero de 2013 16:29
To: fiware-standardization at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu
Cc: Nuria De-Lama Sanchez; 'lorant.farkas at nsn.com'; Ernoe Kovacs; Carmen Perea Escribano
Subject: Re: [Fiware-standardization] Planning calendar link exists, what kind of activity can _your_ Work Package propose ??
Dear all,
on request of management, because the link is FI-WARE_private
and looks "dead" to anyone from the public www, I have moved the
location of the link to our private wiki:
https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Main_Page#FI-WARE_Exploitation
at the section for FI-WARE Exploitation, saying:
Standardization (re-use of specs, contributions to SDOs) has a separate planning tool for coordination:
* SDO_Calendar_2013
thank you for any comments about using the tool ...
/Lindsay
From: fiware-standardization-bounces at lists.fi-ware.eu [mailto:fiware-standardization-bounces at lists.fi-ware.eu] On Behalf Of Lindsay Frost
Sent: Donnerstag, 28. Februar 2013 12:34
To: fiware-standardization at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu
Cc: Nuria De-Lama Sanchez; Ernoe Kovacs; 'Carmen Perea Escribano'; 'lorant.farkas at nsn.com'
Subject: [Fiware-standardization] Planning calendar link exists, what kind of activity can _your_ Work Package propose ??
Dear all,
with help from Miquel and others, there is now a "protected" link to the xls calendar
at: FI-WARE Exploitation. It is downloadable only by FI-WARE members and the EU commission.
As a FIRST example of using it, Luca Giacomello has kindly provided a DRAFT "activity" for the
date 09.12.2013. You should see it on the "Timeline" worksheet immediately on opening the
xlsm link at the text "SDO_Calendar_2013" on the FI-WARE Exploitation area (or at the first
hyperlink in this email):
DRAFT SCHEDULE "OSGi Cloud proxy" Presentation and/or Demo of WP7 "Interfaces
to network" technology at HGI EVENT. Contact = luca.giacomello at telecomitalia.it
The idea is to pick SDO meetings where your Work Package _intends_ to make some contribution or
presentation or demo or even just "express FI-WARE support for a Work Item or agreed Specification".
This will show the EU commission and all FI-WARE partners that FI-WARE is impacting standards.
Of course changes and delays etc will happen frequently, but it is important to start this.
So, what kind of activity can _your_ Work Package propose ?? Please ask your teams!
Please supply one or more simple texts like the example given above.
Thank you for replying to all when answering, so we can quickly see what objections or improvements
are needed.
best wishes
Lindsay
PS: Apologies to Luca! The old xls on the server does not match the desired message above.
I will fix it as soon as somebody has time to help me with some problems (a) my ignorance of proper
method, (b) lack of authorization, (c) both
PPS: I am happy to add also new SDO events, interesting workshops, national holidays, etc ... it should
be useful and interesting for everybody ;-) ... just email me privately and I will update.
------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended
solely for the addressee; it may also be privileged. If you receive
this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos
group liability cannot be triggered for the message content. Although
the sender endeavours to maintain a computer virus-free network,
the sender does not warrant that this transmission is virus-free and
will not be liable for any damages resulting from any virus transmitted.
Este mensaje y los ficheros adjuntos pueden contener informacion confidencial
destinada solamente a la(s) persona(s) mencionadas anteriormente
pueden estar protegidos por secreto profesional.
Si usted recibe este correo electronico por error, gracias por informar
inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos
no se hace responsable por su contenido. Su contenido no constituye ningun
compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes.
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
no puede garantizar nada al respecto y no sera responsable de cualesquiera
danos que puedan resultar de una transmision de virus.
------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 339 bytes
Desc: image001.png
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.gif
Type: image/gif
Size: 4064 bytes
Desc: image002.gif
URL:
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL:
From pascal.bisson at thalesgroup.com Wed Mar 13 14:10:18 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Wed, 13 Mar 2013 14:10:18 +0100
Subject: [Fiware-security] FI-WARE / Security Chapter contrib to D2.3.2
ready for peer review
In-Reply-To:
References:
Message-ID: <10320_1363180221_51407ABD_10320_6004_2_75743a0c-048c-4654-bdd3-8d0fa0325cf0@THSONEA01HUB03P.one.grp>
Dear all,
This email just to let you know that apart from Kreshnik who volunteered no one else did.
Meaning I will have to appoint some of you except if some of you want to candidate (please do it now).
As for the rest and being said the Apps chapter has not yet delivered its first draft I have to wait till it is done to trigger this peer review.
In any case please stay tuned since it will come.
Best Regards,
Pascal
De : BISSON Pascal
Envoy? : lundi 11 mars 2013 19:14
? : fiware-security at lists.fi-ware.eu
Cc : BISSON Pascal; GIDOIN Daniel
Objet : TR: FI-WARE / Security Chapter contrib to D2.3.2 ready for peer review
FYI
Please let me know who is volunteer to peer-review Apps Chapter.
I need at least two volunteers. If no one volunteer by tomorrow lunch time I would appoint reviewers at the level of our team.
Hearing from you.
As for the rest I managed our Chapter contrib. has been produced and you have the link when accessing the peer review cockpit. The doc is here http://www.google.com/url?q=https://forge.fi-ware.eu/docman/view.php/27/1922/D232_WP8_v3_generated_2013-03-11.doc&usd=1&usg=ALhdy2-DK-NQZ05xUi8yq4lzgRbSw-Z-sA
Regarding peer review of this doc will keep you posted as soon as it arrives.
BR
Pascal
De : BISSON Pascal
Envoy? : lundi 11 mars 2013 19:08
? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Cc : BISSON Pascal; GIDOIN Daniel
Objet : FI-WARE / Security Chapter contrib to D2.3.2 ready for peer review
Importance : Haute
Dear Colleagues,
This email just to let you know that Security Chapter contrib. has been uploaded and is ready for peer review.
Cockpit has been updated accordingly with the link to the Doc (cf. https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0)
Best Regards,
Pascal
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From robert.seidl at nsn.com Thu Mar 14 09:39:18 2013
From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich))
Date: Thu, 14 Mar 2013 08:39:18 +0000
Subject: [Fiware-security] certificates
Message-ID:
Hi all,
Is there somewhere in FI-WARE a WP dealing with nw-security?
If yes do we know if they provide or sign certificates?
Mit freundlichen Gr??en
Best regards
Seidl Robert
Nokia Siemens Networks Management International GmbH
CTO R SWS SDT
St.-Martin-Strasse 76
81541 Muenchen
phone +49 (0)89 5159 21106
mobile +49 (0)172 3652971
email robert.seidl at nsn.com
IDM Homepage incl. Blog & Wiki:
https://inside.nokiasiemensnetworks.com/global/Company/Organization/CTO/Research/SWS/ServConIdMgmt/IDMsite/Pages/idm.aspx
Nokia Siemens Networks Management International GmbH
Gesch?ftsleitung / Board of Directors: Andreas Sauer, Ralf Dietzel
Sitz der Gesellschaft: M?nchen / Registered office: Munich
Registergericht: M?nchen / Commercial registry: Munich, HRB 198081
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From pascal.bisson at thalesgroup.com Thu Mar 14 17:40:18 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Thu, 14 Mar 2013 17:40:18 +0100
Subject: [Fiware-security] TR: [Fiware-demo] Live Demo evolution kick-off
Message-ID: <6733_1363279465_5141FE68_6733_3134_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E4387DF2@THSONEA01CMS04P.one.grp>
FYI
De : fiware-demo-bounces at lists.fi-ware.eu [mailto:fiware-demo-bounces at lists.fi-ware.eu] De la part de Ferm?n Gal?n M?rquez
Envoy? : jeudi 14 mars 2013 13:52
? : fiware-demo at lists.fi-ware.eu
Objet : Re: [Fiware-demo] Live Demo evolution kick-off
Hi,
Please, find in the following URL the document that was used to define Live Demo Release 1:
https://docs.google.com/document/d/1DhFz9JLJ211ZXNIXUYNEdKyp0HdX46rEFWxn_B2XRWU/edit
However, take into account that this document was abandoned in some point during Live Demo Release 1 preparation, so it is not completely in sync.
Best regards,
------
Ferm?n
El 14/03/2013 10:39, Ferm?n Gal?n M?rquez escribi?:
Hi,
As discussed during WPL/WPA weekly calls (see https://docs.google.com/document/d/1VpWyuWl44m22l-swR1aQK1tsyZMoiIQCfrdWTPZvub8/edit#heading=h.a4ogm75ss3zu), this list has been created to discuss Live Demo evolution. I have been appointed to lead this cross chapter task force.
As you know, a first version of this Live Demo (let's name it "Live Demo Release1") was successfully performed during second year review at the end of 2012. Our goal now is to evolve an enrich this demo, to be used not only during the next review but also in any moment we need to show the work we are doing in FI-WARE project.
We will be using here the same Agile methodology that we use in the rest of the project (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Agile_Development_Methodology). We will have a backlog associated to the Live Demo. Topics not include in the backlog will not be discussed or taken into account at all for the Live Demo evolution. The basic procedure will be as follow:
* The backlog tracker is https://forge.fi-ware.eu/tracker/?atid=227&group_id=27&func=browse. Please, verify that you have access to the tracker and notify me if in negative case.
* We will start by including Epics in the backlog. Each new topic to be included in the Live Demo has to start with a Epic definition.
* Then, Epics will be discussed and refined to concrete Features that, in sequence, will be split in User Stories to be developed during the project sprints.
* Epics and Features have to be defined in the wiki and trac. For user Stories, it is not necessary.
* We will use the "FIWARE.{Type}.Cross.LiveDemo." prefix in our backlog items.
Manuel Escriche, Agile Project Manager in FI-WARE, will ensure that our practices are ok with project methodology. Manuel, don't hesitate to comment on the procedure that I have mention above (or tell us if I'm saying something wrong :)
Two first action points have to be accomplished as soon as possible:
* @all: to create Epics corresponding to elements that we want to include in the Live Demo. In this sense, you can have a look to this two examples of elements that (from TID's side) we would like to include.
* https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Epic.Cross.LiveDemo.IoTGEsIntegration
* https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Epic.Cross.LiveDemo.CEPIntegration
* @SAP, @TID, @UPM: create Features corresponding to the existing functionality in Live Demo, i.e. Live Demo Release 1, by the partners that were involved in that demo. From TID's side, we will do the part related with our GEs as soon as possible.
We will be using the private wiki and the "FIWARE Private" project in the Forge. A "home page" for Live Demo Evolution has been created at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Live_Demo_Evolution
Don't hesitate to contact me if you have any question on doubt, please.
Best regards,
------
Ferm?n
PD. The current subscribers list follows. If you miss somebody, please tell me so.
[cid:part7.01070305.01000805 at 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
_______________________________________________
Fiware-demo mailing list
Fiware-demo at lists.fi-ware.eu
https://lists.fi-ware.eu/listinfo/fiware-demo
________________________________
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:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ATT00001.png
Type: image/png
Size: 20159 bytes
Desc: ATT00001.png
URL:
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00002.txt
URL:
From alexandre.boeglin at inria.fr Thu Mar 14 18:22:50 2013
From: alexandre.boeglin at inria.fr (Alexandre Boeglin)
Date: Thu, 14 Mar 2013 18:22:50 +0100
Subject: [Fiware-security] TR: [Fiware-standardization] Planning
calendar link exists,
what kind of activity can _your_ Work Package propose ??
In-Reply-To: <27936_1363174457_51406433_27936_73_3_dd97fea6-60c7-4750-8f82-357d44944bf0@THSONEA01HUB02P.one.grp>
References: <27936_1363174457_51406433_27936_73_3_dd97fea6-60c7-4750-8f82-357d44944bf0@THSONEA01HUB02P.one.grp>
Message-ID: <20130314172249.GD2552@inria.fr>
Dear Pascal, All,
I see multiple problems with contributing to this document:
- I don't have sufficient permissions to update the excel sheet;
- even if I had, multiple people work on the same offline document are
likely to overwrite one another's modifications without even noticing;
- given the information already present in the document, it doesn't even
seem like it was intended to be used this way.
Best regards,
Alexandre
Le mercredi 13 mars 2013 ? 12:34, BISSON Pascal a ?crit:
> Dear All,
>
> I'm forwarding you this important email received from Juan Bareno calling for action for any of you having previously stated interest (e.g. GE owners although not uniquely) and reported activities (e.g. IBM, INRIA) for what concerns Standardization.
>
> Counting on you each of you to have a look and addressed it the way expected.
>
> Will review this demand has been addressed at Friday's audio.
>
> Thanks in advance for cooperation & support. And yes it is important and will not take that long to each of the expected contributors.
>
> Best Regards,
> Pascal
>
>
>
> De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juan Bare?o Guerenabarrena
> Envoy? : lundi 11 mars 2013 15:45
> ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-standardization at lists.fi-ware.eu
> Cc : Lindsay.Frost at neclab.eu
> Objet : [Fiware-wpl] [Fiware-standardization] Planning calendar link exists, what kind of activity can _your_ Work Package propose ??
>
> Dear All
>
> Please find here enclosed the "Standardization calendar link" to fulfil with your WP contribution (presentation, demo, express FI-WARE support.......) to specific Standards. So, what kind of activity can _your_ Work Package propose ??"
>
> https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Main_Page#FI-WARE_Exploitation
>
> "The idea is to pick SDO meetings where your Work Package _intends_ to make some contribution or presentation or demo or even just "express FI-WARE support for a Work Item or agreed Specification".
>
> This will show the EU commission and all FI-WARE partners that FI-WARE is impacting standards. Of course changes and delays etc will happen frequently, but it is important to start this.
>
> Example: DRAFT SCHEDULE "OSGi Cloud proxy" Presentation and/or Demo of WP7 "Interfaces
> to network" technology at HGI EVENT. Contact = luca.giacomello at telecomitalia.it
>
> Thanks for your contribution
>
> Juan
>
>
>
>
> [cid:image001.png at 01CE1E6E.856B4A40]
> Juan Bare?o
> Group Innovation, Business Development & Strategy
> Research & Innovation
> +34 912148859
> Calle Albarrac?n 25, 28037 Madrid
> juan.bareno at atos.net
> www.atos.net
> [cid:image002.gif at 01CE1E6E.856B4A40]
>
> From: fiware-standardization-bounces at lists.fi-ware.eu [mailto:fiware-standardization-bounces at lists.fi-ware.eu] On Behalf Of Lindsay Frost
> Sent: jueves, 28 de febrero de 2013 16:29
> To: fiware-standardization at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu
> Cc: Nuria De-Lama Sanchez; 'lorant.farkas at nsn.com'; Ernoe Kovacs; Carmen Perea Escribano
> Subject: Re: [Fiware-standardization] Planning calendar link exists, what kind of activity can _your_ Work Package propose ??
>
> Dear all,
> on request of management, because the link is FI-WARE_private
> and looks "dead" to anyone from the public www, I have moved the
> location of the link to our private wiki:
> https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Main_Page#FI-WARE_Exploitation
>
> at the section for FI-WARE Exploitation, saying:
> Standardization (re-use of specs, contributions to SDOs) has a separate planning tool for coordination:
> * SDO_Calendar_2013
>
> thank you for any comments about using the tool ...
> /Lindsay
>
>
>
>
> From: fiware-standardization-bounces at lists.fi-ware.eu [mailto:fiware-standardization-bounces at lists.fi-ware.eu] On Behalf Of Lindsay Frost
> Sent: Donnerstag, 28. Februar 2013 12:34
> To: fiware-standardization at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu
> Cc: Nuria De-Lama Sanchez; Ernoe Kovacs; 'Carmen Perea Escribano'; 'lorant.farkas at nsn.com'
> Subject: [Fiware-standardization] Planning calendar link exists, what kind of activity can _your_ Work Package propose ??
>
> Dear all,
>
> with help from Miquel and others, there is now a "protected" link to the xls calendar
> at: FI-WARE Exploitation. It is downloadable only by FI-WARE members and the EU commission.
>
> As a FIRST example of using it, Luca Giacomello has kindly provided a DRAFT "activity" for the
> date 09.12.2013. You should see it on the "Timeline" worksheet immediately on opening the
> xlsm link at the text "SDO_Calendar_2013" on the FI-WARE Exploitation area (or at the first
> hyperlink in this email):
>
> DRAFT SCHEDULE "OSGi Cloud proxy" Presentation and/or Demo of WP7 "Interfaces
> to network" technology at HGI EVENT. Contact = luca.giacomello at telecomitalia.it
>
> The idea is to pick SDO meetings where your Work Package _intends_ to make some contribution or
> presentation or demo or even just "express FI-WARE support for a Work Item or agreed Specification".
>
> This will show the EU commission and all FI-WARE partners that FI-WARE is impacting standards.
> Of course changes and delays etc will happen frequently, but it is important to start this.
>
> So, what kind of activity can _your_ Work Package propose ?? Please ask your teams!
> Please supply one or more simple texts like the example given above.
>
> Thank you for replying to all when answering, so we can quickly see what objections or improvements
> are needed.
>
> best wishes
> Lindsay
>
> PS: Apologies to Luca! The old xls on the server does not match the desired message above.
> I will fix it as soon as somebody has time to help me with some problems (a) my ignorance of proper
> method, (b) lack of authorization, (c) both
>
> PPS: I am happy to add also new SDO events, interesting workshops, national holidays, etc ... it should
> be useful and interesting for everybody ;-) ... just email me privately and I will update.
>
>
> ------------------------------------------------------------------
> This e-mail and the documents attached are confidential and intended
> solely for the addressee; it may also be privileged. If you receive
> this e-mail in error, please notify the sender immediately and destroy it.
> As its integrity cannot be secured on the Internet, the Atos
> group liability cannot be triggered for the message content. Although
> the sender endeavours to maintain a computer virus-free network,
> the sender does not warrant that this transmission is virus-free and
> will not be liable for any damages resulting from any virus transmitted.
>
> Este mensaje y los ficheros adjuntos pueden contener informacion confidencial
> destinada solamente a la(s) persona(s) mencionadas anteriormente
> pueden estar protegidos por secreto profesional.
> Si usted recibe este correo electronico por error, gracias por informar
> inmediatamente al remitente y destruir el mensaje.
> Al no estar asegurada la integridad de este mensaje sobre la red, Atos
> no se hace responsable por su contenido. Su contenido no constituye ningun
> compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes.
> Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
> no puede garantizar nada al respecto y no sera responsable de cualesquiera
> danos que puedan resultar de una transmision de virus.
> ------------------------------------------------------------------
> _______________________________________________
> Fiware-wpl mailing list
> Fiware-wpl at lists.fi-ware.eu
> https://lists.fi-ware.eu/listinfo/fiware-wpl
--
Alexandre Boeglin
Madynes project-team ? http://madynes.loria.fr/
Inria ? http://www.inria.fr/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3058 bytes
Desc: not available
URL:
From pascal.bisson at thalesgroup.com Fri Mar 15 09:14:01 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Fri, 15 Mar 2013 09:14:01 +0100
Subject: [Fiware-security] TR: [Fiware-standardization] Planning
calendar link exists,
what kind of activity can _your_ Work Package propose ??
In-Reply-To: <20130314172249.GD2552@inria.fr>
References: <27936_1363174457_51406433_27936_73_3_dd97fea6-60c7-4750-8f82-357d44944bf0@THSONEA01HUB02P.one.grp>
<20130314172249.GD2552@inria.fr>
Message-ID: <18434_1363335492_5142D943_18434_9_1_1ff13126-e137-413c-85f4-77df95bab5c1@THSONEA01HUB01P.one.grp>
Alexandre we will discuss this at our audio conf and see if this problem is shared by others.
In any case and to start with just drop me an email with what you'd like to contribute to this document in view of what is requested.
Hearing from you
And talk with you at our audio at 10am.
Best Regards,
Pascal
-----Message d'origine-----
De?: Alexandre Boeglin [mailto:alexandre.boeglin at inria.fr]
Envoy??: jeudi 14 mars 2013 18:23
??: BISSON Pascal
Cc?: fiware-security at lists.fi-ware.eu; GIDOIN Daniel; osb at zurich.ibm.com
Objet?: Re: TR: [Fiware-standardization] Planning calendar link exists, what kind of activity can _your_ Work Package propose ??
Dear Pascal, All,
I see multiple problems with contributing to this document:
- I don't have sufficient permissions to update the excel sheet;
- even if I had, multiple people work on the same offline document are
likely to overwrite one another's modifications without even noticing;
- given the information already present in the document, it doesn't even
seem like it was intended to be used this way.
Best regards,
Alexandre
Le mercredi 13 mars 2013 ? 12:34, BISSON Pascal a ?crit:
> Dear All,
>
> I'm forwarding you this important email received from Juan Bareno calling for action for any of you having previously stated interest (e.g. GE owners although not uniquely) and reported activities (e.g. IBM, INRIA) for what concerns Standardization.
>
> Counting on you each of you to have a look and addressed it the way expected.
>
> Will review this demand has been addressed at Friday's audio.
>
> Thanks in advance for cooperation & support. And yes it is important and will not take that long to each of the expected contributors.
>
> Best Regards,
> Pascal
>
>
>
> De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juan Bare?o Guerenabarrena
> Envoy? : lundi 11 mars 2013 15:45
> ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-standardization at lists.fi-ware.eu
> Cc : Lindsay.Frost at neclab.eu
> Objet : [Fiware-wpl] [Fiware-standardization] Planning calendar link exists, what kind of activity can _your_ Work Package propose ??
>
> Dear All
>
> Please find here enclosed the "Standardization calendar link" to fulfil with your WP contribution (presentation, demo, express FI-WARE support.......) to specific Standards. So, what kind of activity can _your_ Work Package propose ??"
>
> https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Main_Page#FI-WARE_Exploitation
>
> "The idea is to pick SDO meetings where your Work Package _intends_ to make some contribution or presentation or demo or even just "express FI-WARE support for a Work Item or agreed Specification".
>
> This will show the EU commission and all FI-WARE partners that FI-WARE is impacting standards. Of course changes and delays etc will happen frequently, but it is important to start this.
>
> Example: DRAFT SCHEDULE "OSGi Cloud proxy" Presentation and/or Demo of WP7 "Interfaces
> to network" technology at HGI EVENT. Contact = luca.giacomello at telecomitalia.it
>
> Thanks for your contribution
>
> Juan
>
>
>
>
> [cid:image001.png at 01CE1E6E.856B4A40]
> Juan Bare?o
> Group Innovation, Business Development & Strategy
> Research & Innovation
> +34 912148859
> Calle Albarrac?n 25, 28037 Madrid
> juan.bareno at atos.net
> www.atos.net
> [cid:image002.gif at 01CE1E6E.856B4A40]
>
> From: fiware-standardization-bounces at lists.fi-ware.eu [mailto:fiware-standardization-bounces at lists.fi-ware.eu] On Behalf Of Lindsay Frost
> Sent: jueves, 28 de febrero de 2013 16:29
> To: fiware-standardization at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu
> Cc: Nuria De-Lama Sanchez; 'lorant.farkas at nsn.com'; Ernoe Kovacs; Carmen Perea Escribano
> Subject: Re: [Fiware-standardization] Planning calendar link exists, what kind of activity can _your_ Work Package propose ??
>
> Dear all,
> on request of management, because the link is FI-WARE_private
> and looks "dead" to anyone from the public www, I have moved the
> location of the link to our private wiki:
> https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Main_Page#FI-WARE_Exploitation
>
> at the section for FI-WARE Exploitation, saying:
> Standardization (re-use of specs, contributions to SDOs) has a separate planning tool for coordination:
> * SDO_Calendar_2013
>
> thank you for any comments about using the tool ...
> /Lindsay
>
>
>
>
> From: fiware-standardization-bounces at lists.fi-ware.eu [mailto:fiware-standardization-bounces at lists.fi-ware.eu] On Behalf Of Lindsay Frost
> Sent: Donnerstag, 28. Februar 2013 12:34
> To: fiware-standardization at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu
> Cc: Nuria De-Lama Sanchez; Ernoe Kovacs; 'Carmen Perea Escribano'; 'lorant.farkas at nsn.com'
> Subject: [Fiware-standardization] Planning calendar link exists, what kind of activity can _your_ Work Package propose ??
>
> Dear all,
>
> with help from Miquel and others, there is now a "protected" link to the xls calendar
> at: FI-WARE Exploitation. It is downloadable only by FI-WARE members and the EU commission.
>
> As a FIRST example of using it, Luca Giacomello has kindly provided a DRAFT "activity" for the
> date 09.12.2013. You should see it on the "Timeline" worksheet immediately on opening the
> xlsm link at the text "SDO_Calendar_2013" on the FI-WARE Exploitation area (or at the first
> hyperlink in this email):
>
> DRAFT SCHEDULE "OSGi Cloud proxy" Presentation and/or Demo of WP7 "Interfaces
> to network" technology at HGI EVENT. Contact = luca.giacomello at telecomitalia.it
>
> The idea is to pick SDO meetings where your Work Package _intends_ to make some contribution or
> presentation or demo or even just "express FI-WARE support for a Work Item or agreed Specification".
>
> This will show the EU commission and all FI-WARE partners that FI-WARE is impacting standards.
> Of course changes and delays etc will happen frequently, but it is important to start this.
>
> So, what kind of activity can _your_ Work Package propose ?? Please ask your teams!
> Please supply one or more simple texts like the example given above.
>
> Thank you for replying to all when answering, so we can quickly see what objections or improvements
> are needed.
>
> best wishes
> Lindsay
>
> PS: Apologies to Luca! The old xls on the server does not match the desired message above.
> I will fix it as soon as somebody has time to help me with some problems (a) my ignorance of proper
> method, (b) lack of authorization, (c) both
>
> PPS: I am happy to add also new SDO events, interesting workshops, national holidays, etc ... it should
> be useful and interesting for everybody ;-) ... just email me privately and I will update.
>
>
> ------------------------------------------------------------------
> This e-mail and the documents attached are confidential and intended
> solely for the addressee; it may also be privileged. If you receive
> this e-mail in error, please notify the sender immediately and destroy it.
> As its integrity cannot be secured on the Internet, the Atos
> group liability cannot be triggered for the message content. Although
> the sender endeavours to maintain a computer virus-free network,
> the sender does not warrant that this transmission is virus-free and
> will not be liable for any damages resulting from any virus transmitted.
>
> Este mensaje y los ficheros adjuntos pueden contener informacion confidencial
> destinada solamente a la(s) persona(s) mencionadas anteriormente
> pueden estar protegidos por secreto profesional.
> Si usted recibe este correo electronico por error, gracias por informar
> inmediatamente al remitente y destruir el mensaje.
> Al no estar asegurada la integridad de este mensaje sobre la red, Atos
> no se hace responsable por su contenido. Su contenido no constituye ningun
> compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes.
> Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
> no puede garantizar nada al respecto y no sera responsable de cualesquiera
> danos que puedan resultar de una transmision de virus.
> ------------------------------------------------------------------
> _______________________________________________
> Fiware-wpl mailing list
> Fiware-wpl at lists.fi-ware.eu
> https://lists.fi-ware.eu/listinfo/fiware-wpl
--
Alexandre Boeglin
Madynes project-team ? http://madynes.loria.fr/
Inria ? http://www.inria.fr/
From francesco.di.cerbo at sap.com Fri Mar 15 11:12:32 2013
From: francesco.di.cerbo at sap.com (DI CERBO, Francesco)
Date: Fri, 15 Mar 2013 10:12:32 +0000
Subject: [Fiware-security] about ticket status
Message-ID: <6D11E010ED8E5B4B9D42045AC71F37E607085728@DEWDFEMB18B.global.corp.sap>
Hello all,
Apparently on the main the wiki page[1] that describes our agile methodology, there are no specific guidelines or policies on ticket status management. However, in the attached Manuel's email, it is requested to "Update tickets under execution to belong to Sprint 2.2.3-M23".
Therefore, it seems that there must be at least 1 under execution ticket per sprint, so please check that you are compliant with this requirement.
>From a quick check for T8.4: DB anonymizer and ContentBasedSecurity have tickets labelled as "under execution" for Sprint 2.2.3, this is not the case for INRIA's tickets (there are under execution tickets, but not for 2.2.3)
Best,
Francesco
[1]: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Agile_Development_Methodology
___
Francesco Di Cerbo, PhD
SAP Next Business and Technology
Applied Research
Security & Trust
SAP Labs France
805, avenue Maurice Donat
Font de l'Orme
BP 1216
06250 Mougins Cedex
France
Tel. +33 4 92 28 64 45
e-mail: Francesco.Di.Cerbo at sap.com
-------------- next part --------------
An embedded message was scrubbed...
From: BISSON Pascal
Subject: [Fiware-security] TR: [Fiware-wpl] Backlog - Sprint transition: from S2.2.2-M22 to S2.2.3-M23
Date: Fri, 1 Mar 2013 13:34:58 +0000
Size: 19488
URL:
From francesco.di.cerbo at sap.com Fri Mar 15 11:24:15 2013
From: francesco.di.cerbo at sap.com (DI CERBO, Francesco)
Date: Fri, 15 Mar 2013 10:24:15 +0000
Subject: [Fiware-security] Instructions for v2 deliverables
Message-ID: <6D11E010ED8E5B4B9D42045AC71F37E607085760@DEWDFEMB18B.global.corp.sap>
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverables
best,
Francesco
___
Francesco Di Cerbo, PhD
SAP Next Business and Technology
Applied Research
Security & Trust
SAP Labs France
805, avenue Maurice Donat
Font de l'Orme
BP 1216
06250 Mougins Cedex
France
Tel. +33 4 92 28 64 45
e-mail: Francesco.Di.Cerbo at sap.com
From pascal.bisson at thalesgroup.com Fri Mar 15 17:29:28 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Fri, 15 Mar 2013 17:29:28 +0100
Subject: [Fiware-security] FI-WARE Architecture description for V2 - peer
review perfomed by apps chapter done - please address comments received and
update accoridngly your GE arch desc.
Message-ID: <3955_1363365219_51434D63_3955_1052_2_0de866fa-25cd-4c56-b259-edc6bf8e7333@THSONEA01HUB03P.one.grp>
Dear Colleagues,
This email just to inform you that review of our chapter's contrib. to Architecture Description V2 deliverable has been performed by the reviewing chapter appointed (aka Data chapter). https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0
Being said this review has been performed per GE or block of GEs I would ask each of the GE owners to go to the review file of concern and address comments received (the sooner the better as usual, drop me an email once done ...)
Once each and every of you GE owners would have addressed their review comments on the wiki where their stuff is, I will generate a new version of the chapter docx for another check of peer reviewers appointed.
Many thanks in advance for your work and yes don't forget to drop me an email once revision of your GE has been performed.
Hearing from you.
Best Regards,
Pascal
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From pascal.bisson at thalesgroup.com Fri Mar 15 18:37:53 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Fri, 15 Mar 2013 18:37:53 +0100
Subject: [Fiware-security] [Fiware-demo] Live Demo evolution kick-off
In-Reply-To: <51419AC7.5040502@tid.es>
References: <51419AC7.5040502@tid.es>
Message-ID: <4094_1363369322_51435D6A_4094_4576_1_3e940f3a-5664-407a-9aa5-dfa8926f4008@THSONEA01HUB01P.one.grp>
Dear Ferm?n,
Could you please add from the Security Chapter side the colleagues hereafter (also in cc) to the fiware-demo list:
Robert Seidl : robert.seidl at nsn.com
Francesco Di Cerbo : francesco.di.cerbo at sap.com
Slim Trabelsi: slim.trabelsi at sap.com
Susana : susana.gzarzosa at atosresearch.eu
Richard Egan: Richard.egan at uk.thalesgroup.com
Alexandre Boeglin: alexandre.boeglin at inria.fr
Many thanks in advance.
Best Regards,
Pascal
PS : @Security colleagues in cc please see below the instructions already given to contribute ideas to the live demo. Please notice as told at toaday's audio we will follow Agile and so there is a tracker and you have to contribute there under EPIC format your demo ideas and there refine the way we are now used to ...
De : fiware-demo-bounces at lists.fi-ware.eu [mailto:fiware-demo-bounces at lists.fi-ware.eu] De la part de Ferm?n Gal?n M?rquez
Envoy? : jeudi 14 mars 2013 10:39
? : fiware-demo at lists.fi-ware.eu
Objet : [Fiware-demo] Live Demo evolution kick-off
Hi,
As discussed during WPL/WPA weekly calls (see https://docs.google.com/document/d/1VpWyuWl44m22l-swR1aQK1tsyZMoiIQCfrdWTPZvub8/edit#heading=h.a4ogm75ss3zu), this list has been created to discuss Live Demo evolution. I have been appointed to lead this cross chapter task force.
As you know, a first version of this Live Demo (let's name it "Live Demo Release1") was successfully performed during second year review at the end of 2012. Our goal now is to evolve an enrich this demo, to be used not only during the next review but also in any moment we need to show the work we are doing in FI-WARE project.
We will be using here the same Agile methodology that we use in the rest of the project (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Agile_Development_Methodology). We will have a backlog associated to the Live Demo. Topics not include in the backlog will not be discussed or taken into account at all for the Live Demo evolution. The basic procedure will be as follow:
* The backlog tracker is https://forge.fi-ware.eu/tracker/?atid=227&group_id=27&func=browse. Please, verify that you have access to the tracker and notify me if in negative case.
* We will start by including Epics in the backlog. Each new topic to be included in the Live Demo has to start with a Epic definition.
* Then, Epics will be discussed and refined to concrete Features that, in sequence, will be split in User Stories to be developed during the project sprints.
* Epics and Features have to be defined in the wiki and trac. For user Stories, it is not necessary.
* We will use the "FIWARE.{Type}.Cross.LiveDemo." prefix in our backlog items.
Manuel Escriche, Agile Project Manager in FI-WARE, will ensure that our practices are ok with project methodology. Manuel, don't hesitate to comment on the procedure that I have mention above (or tell us if I'm saying something wrong :)
Two first action points have to be accomplished as soon as possible:
* @all: to create Epics corresponding to elements that we want to include in the Live Demo. In this sense, you can have a look to this two examples of elements that (from TID's side) we would like to include.
* https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Epic.Cross.LiveDemo.IoTGEsIntegration
* https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Epic.Cross.LiveDemo.CEPIntegration
* @SAP, @TID, @UPM: create Features corresponding to the existing functionality in Live Demo, i.e. Live Demo Release 1, by the partners that were involved in that demo. From TID's side, we will do the part related with our GEs as soon as possible.
We will be using the private wiki and the "FIWARE Private" project in the Forge. A "home page" for Live Demo Evolution has been created at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Live_Demo_Evolution
Don't hesitate to contact me if you have any question on doubt, please.
Best regards,
------
Ferm?n
PD. The current subscribers list follows. If you miss somebody, please tell me so.
[cid:image001.png at 01CE21AB.216D52A0]
________________________________
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:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 20159 bytes
Desc: image001.png
URL:
From denis.butin at inria.fr Fri Mar 15 18:57:33 2013
From: denis.butin at inria.fr (Denis Butin)
Date: Fri, 15 Mar 2013 18:57:33 +0100 (CET)
Subject: [Fiware-security] about ticket status
In-Reply-To: <6D11E010ED8E5B4B9D42045AC71F37E607085728@DEWDFEMB18B.global.corp.sap>
Message-ID: <1418954668.4494007.1363370253355.JavaMail.root@inria.fr>
Hi Francesco,
We do have a workitem under execution for Sprint 2.2.3, it has ID 4007; you may have missed it because it is unassigned. In fact, when I submit new workitems, the "Assigned to" field never shows up; maybe someone could fix this permissions issue.
Regards,
Denis
----- Original Message -----
> From: "Francesco DI CERBO"
> To: fiware-security at lists.fi-ware.eu
> Sent: Friday, 15 March, 2013 11:12:32 AM
> Subject: [Fiware-security] about ticket status
>
> Hello all,
>
> Apparently on the main the wiki page[1] that describes our agile
> methodology, there are no specific guidelines or policies on ticket
> status management. However, in the attached Manuel's email, it is
> requested to "Update tickets under execution to belong to Sprint
> 2.2.3-M23".
>
> Therefore, it seems that there must be at least 1 under execution
> ticket per sprint, so please check that you are compliant with this
> requirement.
>
> From a quick check for T8.4: DB anonymizer and ContentBasedSecurity
> have tickets labelled as "under execution" for Sprint 2.2.3, this is
> not the case for INRIA's tickets (there are under execution tickets,
> but not for 2.2.3)
>
> Best,
>
> Francesco
From pascal.bisson at thalesgroup.com Fri Mar 15 19:05:03 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Fri, 15 Mar 2013 19:05:03 +0100
Subject: [Fiware-security] [Fiware-demo] Live Demo evolution kick-off
In-Reply-To: <514360D4.7010601@tid.es>
References: <51419AC7.5040502@tid.es>
<4094_1363369322_51435D6A_4094_4576_1_3e940f3a-5664-407a-9aa5-dfa8926f4008@THSONEA01HUB01P.one.grp>
<514360D4.7010601@tid.es>
Message-ID: <19083_1363370954_514363C9_19083_5809_4_e0adeb71-0730-4a04-b359-5b8d06e1c1ee@THSONEA01HUB04P.one.grp>
Ok excellent and yes took note.
De : Ferm?n Gal?n M?rquez [mailto:fermin at tid.es]
Envoy? : vendredi 15 mars 2013 18:57
? : BISSON Pascal
Cc : fiware-security at lists.fi-ware.eu; robert.seidl at nsn.com; DI CERBO, Francesco; TRABELSI, Slim; Susana Gonzalez Zarzosa; EGAN Richard; Alexandre Boeglin; GIDOIN Daniel
Objet : Re: [Fiware-demo] Live Demo evolution kick-off
Dear Pascal,
Done.
For additional subscription, take into account that anybody can subscribe himself/herself from https://lists.fi-ware.eu/listinfo/fiware-demo, using the "Subscribing to Fiware-demo" form.
Best regards,
------
Ferm?n
El 15/03/2013 18:37, BISSON Pascal escribi?:
Dear Ferm?n,
Could you please add from the Security Chapter side the colleagues hereafter (also in cc) to the fiware-demo list:
Robert Seidl : robert.seidl at nsn.com
Francesco Di Cerbo : francesco.di.cerbo at sap.com
Slim Trabelsi: slim.trabelsi at sap.com
Susana : susana.gzarzosa at atosresearch.eu
Richard Egan: Richard.egan at uk.thalesgroup.com
Alexandre Boeglin: alexandre.boeglin at inria.fr
Many thanks in advance.
Best Regards,
Pascal
PS : @Security colleagues in cc please see below the instructions already given to contribute ideas to the live demo. Please notice as told at toaday's audio we will follow Agile and so there is a tracker and you have to contribute there under EPIC format your demo ideas and there refine the way we are now used to ...
De : fiware-demo-bounces at lists.fi-ware.eu [mailto:fiware-demo-bounces at lists.fi-ware.eu] De la part de Ferm?n Gal?n M?rquez
Envoy? : jeudi 14 mars 2013 10:39
? : fiware-demo at lists.fi-ware.eu
Objet : [Fiware-demo] Live Demo evolution kick-off
Hi,
As discussed during WPL/WPA weekly calls (see https://docs.google.com/document/d/1VpWyuWl44m22l-swR1aQK1tsyZMoiIQCfrdWTPZvub8/edit#heading=h.a4ogm75ss3zu), this list has been created to discuss Live Demo evolution. I have been appointed to lead this cross chapter task force.
As you know, a first version of this Live Demo (let's name it "Live Demo Release1") was successfully performed during second year review at the end of 2012. Our goal now is to evolve an enrich this demo, to be used not only during the next review but also in any moment we need to show the work we are doing in FI-WARE project.
We will be using here the same Agile methodology that we use in the rest of the project (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Agile_Development_Methodology). We will have a backlog associated to the Live Demo. Topics not include in the backlog will not be discussed or taken into account at all for the Live Demo evolution. The basic procedure will be as follow:
* The backlog tracker is https://forge.fi-ware.eu/tracker/?atid=227&group_id=27&func=browse. Please, verify that you have access to the tracker and notify me if in negative case.
* We will start by including Epics in the backlog. Each new topic to be included in the Live Demo has to start with a Epic definition.
* Then, Epics will be discussed and refined to concrete Features that, in sequence, will be split in User Stories to be developed during the project sprints.
* Epics and Features have to be defined in the wiki and trac. For user Stories, it is not necessary.
* We will use the "FIWARE.{Type}.Cross.LiveDemo." prefix in our backlog items.
Manuel Escriche, Agile Project Manager in FI-WARE, will ensure that our practices are ok with project methodology. Manuel, don't hesitate to comment on the procedure that I have mention above (or tell us if I'm saying something wrong :)
Two first action points have to be accomplished as soon as possible:
* @all: to create Epics corresponding to elements that we want to include in the Live Demo. In this sense, you can have a look to this two examples of elements that (from TID's side) we would like to include.
* https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Epic.Cross.LiveDemo.IoTGEsIntegration
* https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Epic.Cross.LiveDemo.CEPIntegration
* @SAP, @TID, @UPM: create Features corresponding to the existing functionality in Live Demo, i.e. Live Demo Release 1, by the partners that were involved in that demo. From TID's side, we will do the part related with our GEs as soon as possible.
We will be using the private wiki and the "FIWARE Private" project in the Forge. A "home page" for Live Demo Evolution has been created at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Live_Demo_Evolution
Don't hesitate to contact me if you have any question on doubt, please.
Best regards,
------
Ferm?n
PD. The current subscribers list follows. If you miss somebody, please tell me so.
________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From pascal.bisson at thalesgroup.com Tue Mar 19 15:22:53 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Tue, 19 Mar 2013 15:22:53 +0100
Subject: [Fiware-security] TR: [Fiware-wpl] Information about relationship
between the date at which software is delivered and the date at which that
is software up and running on the FI-WARE Testbed
Message-ID: <4347_1363702990_514874CD_4347_1327_7_CBBCD6C304123F4AB23FAAE3055C8C0E0206E45E4215@THSONEA01CMS04P.one.grp>
FYI and clarification.
Best Regards,
Pascal
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 19 mars 2013 15:05
? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Objet : [Fiware-wpl] Information about relationship between the date at which software is delivered and the date at which that is software up and running on the FI-WARE Testbed
Hi,
Just for you reference, here it goes the page on the wiki page where relationship between the date at which software is delivered (through SVN or alternative approach), and the date at which that software is up and running on the FI-WARE Testbed, is explained:
http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates
There, it is said:
PLEASE NOTE that software associated to Minor Releases may be made available on the FI-WARE Testbed after completing that Minor Release, typically by the end of the following month. A revised version of the documentation accompanying software delivered after closing a Minor Release is also typically delivered by end of the following month.
Hope the relationship is clear. Please share with your teams just in case.
Best regards,
-- Juanjo
-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es
email: jhierro at tid.es
twitter: twitter.com/JuanjoHierro
FI-WARE (European Future Internet Core Platform) Coordinator
and 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:
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL:
From pascal.bisson at thalesgroup.com Thu Mar 21 15:12:45 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Thu, 21 Mar 2013 15:12:45 +0100
Subject: [Fiware-security] FI-WARE Architecture description for V2 -
peer review perfomed by apps chapter done - please address comments
received and update accoridngly your GE arch desc.
In-Reply-To:
References:
Message-ID: <18337_1363875441_514B1671_18337_520_1_294c2bb0-0a6f-44dc-a3c8-4226caa9487f@THSONEA01HUB04P.one.grp>
Dear Task leads/GE owners,
Please confirm you addressed on the wiki (where your published Architecture description V2 are located) the peer review comments we received.
For those who have not yet finalized please address urgently review comments received.
And yes this would be on the Agenda of tomorrow's audio conf.
Best Regards,
Pascal
De : BISSON Pascal
Envoy? : vendredi 15 mars 2013 17:29
? : fiware-security at lists.fi-ware.eu
Cc : BISSON Pascal; GIDOIN Daniel
Objet : FI-WARE Architecture description for V2 - peer review perfomed by apps chapter done - please address comments received and update accoridngly your GE arch desc.
Dear Colleagues,
This email just to inform you that review of our chapter's contrib. to Architecture Description V2 deliverable has been performed by the reviewing chapter appointed (aka Data chapter). https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0
Being said this review has been performed per GE or block of GEs I would ask each of the GE owners to go to the review file of concern and address comments received (the sooner the better as usual, drop me an email once done ...)
Once each and every of you GE owners would have addressed their review comments on the wiki where their stuff is, I will generate a new version of the chapter docx for another check of peer reviewers appointed.
Many thanks in advance for your work and yes don't forget to drop me an email once revision of your GE has been performed.
Hearing from you.
Best Regards,
Pascal
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From robert.seidl at nsn.com Thu Mar 21 17:20:03 2013
From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich))
Date: Thu, 21 Mar 2013 16:20:03 +0000
Subject: [Fiware-security] FI-WARE Architecture description for V2 -
peer review perfomed by apps chapter done - please address comments
received and update accoridngly your GE arch desc.
In-Reply-To: <18337_1363875441_514B1671_18337_520_1_294c2bb0-0a6f-44dc-a3c8-4226caa9487f@THSONEA01HUB04P.one.grp>
References:
<18337_1363875441_514B1671_18337_520_1_294c2bb0-0a6f-44dc-a3c8-4226caa9487f@THSONEA01HUB04P.one.grp>
Message-ID:
Hi Pascal,
for IDM and Privacy GE the comments are addressed except one comment for IDM GE, which I think is not relevant.
For Data Handling I expect that it is already done as well.
Here Francesco can report tomorrow.
Greetings
Robert
From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of ext BISSON Pascal
Sent: Thursday, March 21, 2013 3:13 PM
To: fiware-security at lists.fi-ware.eu
Subject: Re: [Fiware-security] FI-WARE Architecture description for V2 - peer review perfomed by apps chapter done - please address comments received and update accoridngly your GE arch desc.
Dear Task leads/GE owners,
Please confirm you addressed on the wiki (where your published Architecture description V2 are located) the peer review comments we received.
For those who have not yet finalized please address urgently review comments received.
And yes this would be on the Agenda of tomorrow's audio conf.
Best Regards,
Pascal
De : BISSON Pascal
Envoy? : vendredi 15 mars 2013 17:29
? : fiware-security at lists.fi-ware.eu
Cc : BISSON Pascal; GIDOIN Daniel
Objet : FI-WARE Architecture description for V2 - peer review perfomed by apps chapter done - please address comments received and update accoridngly your GE arch desc.
Dear Colleagues,
This email just to inform you that review of our chapter's contrib. to Architecture Description V2 deliverable has been performed by the reviewing chapter appointed (aka Data chapter). https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0
Being said this review has been performed per GE or block of GEs I would ask each of the GE owners to go to the review file of concern and address comments received (the sooner the better as usual, drop me an email once done ...)
Once each and every of you GE owners would have addressed their review comments on the wiki where their stuff is, I will generate a new version of the chapter docx for another check of peer reviewers appointed.
Many thanks in advance for your work and yes don't forget to drop me an email once revision of your GE has been performed.
Hearing from you.
Best Regards,
Pascal
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From antonio.garcia at atosresearch.eu Thu Mar 21 17:45:19 2013
From: antonio.garcia at atosresearch.eu (Antonio Garcia Vazquez)
Date: Thu, 21 Mar 2013 17:45:19 +0100
Subject: [Fiware-security] FI-WARE Architecture description for V2 -
peer review perfomed by apps chapter done - please address
comments received and update accoridngly your GE arch desc.
Message-ID: <8E18929A6C79354FB4BD9BD4636DCB06016D0418@INTMAIL03.es.int.atosorigin.com>
Good afternoon,
I?ve just include the modifications required for Context-based security & compliance GE
Best
************************************
* Antonio Garc?a-V?zquez *
* (+34) 91 214 9384 *
* antonio.garcia at atosresearch.eu *
************************************
From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal
Sent: jueves, 21 de marzo de 2013 15:13
To: fiware-security at lists.fi-ware.eu
Subject: Re: [Fiware-security] FI-WARE Architecture description for V2 - peer review perfomed by apps chapter done - please address comments received and update accoridngly your GE arch desc.
Dear Task leads/GE owners,
Please confirm you addressed on the wiki (where your published Architecture description V2 are located) the peer review comments we received.
For those who have not yet finalized please address urgently review comments received.
And yes this would be on the Agenda of tomorrow's audio conf.
Best Regards,
Pascal
De : BISSON Pascal
Envoy? : vendredi 15 mars 2013 17:29
? : fiware-security at lists.fi-ware.eu
Cc : BISSON Pascal; GIDOIN Daniel
Objet : FI-WARE Architecture description for V2 - peer review perfomed by apps chapter done - please address comments received and update accoridngly your GE arch desc.
Dear Colleagues,
This email just to inform you that review of our chapter's contrib. to Architecture Description V2 deliverable has been performed by the reviewing chapter appointed (aka Data chapter). https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0
Being said this review has been performed per GE or block of GEs I would ask each of the GE owners to go to the review file of concern and address comments received (the sooner the better as usual, drop me an email once done ...)
Once each and every of you GE owners would have addressed their review comments on the wiki where their stuff is, I will generate a new version of the chapter docx for another check of peer reviewers appointed.
Many thanks in advance for your work and yes don't forget to drop me an email once revision of your GE has been performed.
Hearing from you.
Best Regards,
Pascal
------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended
solely for the addressee; it may also be privileged. If you receive
this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos
group liability cannot be triggered for the message content. Although
the sender endeavours to maintain a computer virus-free network,
the sender does not warrant that this transmission is virus-free and
will not be liable for any damages resulting from any virus transmitted.
Este mensaje y los ficheros adjuntos pueden contener informacion confidencial
destinada solamente a la(s) persona(s) mencionadas anteriormente
pueden estar protegidos por secreto profesional.
Si usted recibe este correo electronico por error, gracias por informar
inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos
no se hace responsable por su contenido. Su contenido no constituye ningun
compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes.
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
no puede garantizar nada al respecto y no sera responsable de cualesquiera
danos que puedan resultar de una transmision de virus.
------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From robert.seidl at nsn.com Thu Mar 21 18:16:46 2013
From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich))
Date: Thu, 21 Mar 2013 17:16:46 +0000
Subject: [Fiware-security] FI-WARE Architecture description for V2 -
peer review perfomed by apps chapter done - please address comments
received and update accoridngly your GE arch desc.
References:
<18337_1363875441_514B1671_18337_520_1_294c2bb0-0a6f-44dc-a3c8-4226caa9487f@THSONEA01HUB04P.one.grp>
Message-ID:
Sorry to add:
I can be found here:
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Identity_Management_Generic_Enabler#SAML
From: Seidl, Robert (NSN - DE/Munich)
Sent: Thursday, March 21, 2013 5:20 PM
To: 'ext BISSON Pascal'
Cc: fiware-security at lists.fi-ware.eu
Subject: RE: [Fiware-security] FI-WARE Architecture description for V2 - peer review perfomed by apps chapter done - please address comments received and update accoridngly your GE arch desc.
Hi Pascal,
for IDM and Privacy GE the comments are addressed except one comment for IDM GE, which I think is not relevant.
For Data Handling I expect that it is already done as well.
Here Francesco can report tomorrow.
Greetings
Robert
From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of ext BISSON Pascal
Sent: Thursday, March 21, 2013 3:13 PM
To: fiware-security at lists.fi-ware.eu
Subject: Re: [Fiware-security] FI-WARE Architecture description for V2 - peer review perfomed by apps chapter done - please address comments received and update accoridngly your GE arch desc.
Dear Task leads/GE owners,
Please confirm you addressed on the wiki (where your published Architecture description V2 are located) the peer review comments we received.
For those who have not yet finalized please address urgently review comments received.
And yes this would be on the Agenda of tomorrow's audio conf.
Best Regards,
Pascal
De : BISSON Pascal
Envoy? : vendredi 15 mars 2013 17:29
? : fiware-security at lists.fi-ware.eu
Cc : BISSON Pascal; GIDOIN Daniel
Objet : FI-WARE Architecture description for V2 - peer review perfomed by apps chapter done - please address comments received and update accoridngly your GE arch desc.
Dear Colleagues,
This email just to inform you that review of our chapter's contrib. to Architecture Description V2 deliverable has been performed by the reviewing chapter appointed (aka Data chapter). https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0
Being said this review has been performed per GE or block of GEs I would ask each of the GE owners to go to the review file of concern and address comments received (the sooner the better as usual, drop me an email once done ...)
Once each and every of you GE owners would have addressed their review comments on the wiki where their stuff is, I will generate a new version of the chapter docx for another check of peer reviewers appointed.
Many thanks in advance for your work and yes don't forget to drop me an email once revision of your GE has been performed.
Hearing from you.
Best Regards,
Pascal
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From pascal.bisson at thalesgroup.com Thu Mar 21 18:42:10 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Thu, 21 Mar 2013 18:42:10 +0100
Subject: [Fiware-security] FI-WARE Architecture description for V2 -
peer review perfomed by apps chapter done - please address comments
received and update accoridngly your GE arch desc.
In-Reply-To:
References:
<18337_1363875441_514B1671_18337_520_1_294c2bb0-0a6f-44dc-a3c8-4226caa9487f@THSONEA01HUB04P.one.grp>
Message-ID: <32139_1363887732_514B4673_32139_5489_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E4734FC1@THSONEA01CMS04P.one.grp>
Ok thanks for your update and yes will discuss tomorrow.
De : Seidl, Robert (NSN - DE/Munich) [mailto:robert.seidl at nsn.com]
Envoy? : jeudi 21 mars 2013 17:20
? : BISSON Pascal
Cc : fiware-security at lists.fi-ware.eu
Objet : RE: [Fiware-security] FI-WARE Architecture description for V2 - peer review perfomed by apps chapter done - please address comments received and update accoridngly your GE arch desc.
Hi Pascal,
for IDM and Privacy GE the comments are addressed except one comment for IDM GE, which I think is not relevant.
For Data Handling I expect that it is already done as well.
Here Francesco can report tomorrow.
Greetings
Robert
From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of ext BISSON Pascal
Sent: Thursday, March 21, 2013 3:13 PM
To: fiware-security at lists.fi-ware.eu
Subject: Re: [Fiware-security] FI-WARE Architecture description for V2 - peer review perfomed by apps chapter done - please address comments received and update accoridngly your GE arch desc.
Dear Task leads/GE owners,
Please confirm you addressed on the wiki (where your published Architecture description V2 are located) the peer review comments we received.
For those who have not yet finalized please address urgently review comments received.
And yes this would be on the Agenda of tomorrow's audio conf.
Best Regards,
Pascal
De : BISSON Pascal
Envoy? : vendredi 15 mars 2013 17:29
? : fiware-security at lists.fi-ware.eu
Cc : BISSON Pascal; GIDOIN Daniel
Objet : FI-WARE Architecture description for V2 - peer review perfomed by apps chapter done - please address comments received and update accoridngly your GE arch desc.
Dear Colleagues,
This email just to inform you that review of our chapter's contrib. to Architecture Description V2 deliverable has been performed by the reviewing chapter appointed (aka Data chapter). https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0
Being said this review has been performed per GE or block of GEs I would ask each of the GE owners to go to the review file of concern and address comments received (the sooner the better as usual, drop me an email once done ...)
Once each and every of you GE owners would have addressed their review comments on the wiki where their stuff is, I will generate a new version of the chapter docx for another check of peer reviewers appointed.
Many thanks in advance for your work and yes don't forget to drop me an email once revision of your GE has been performed.
Hearing from you.
Best Regards,
Pascal
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From pascal.bisson at thalesgroup.com Thu Mar 21 18:42:10 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Thu, 21 Mar 2013 18:42:10 +0100
Subject: [Fiware-security] FI-WARE Architecture description for V2 -
peer review perfomed by apps chapter done - please address comments
received and update accoridngly your GE arch desc.
In-Reply-To: <8E18929A6C79354FB4BD9BD4636DCB06016D0418@INTMAIL03.es.int.atosorigin.com>
References: <8E18929A6C79354FB4BD9BD4636DCB06016D0418@INTMAIL03.es.int.atosorigin.com>
Message-ID: <26630_1363887732_514B4673_26630_396_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E4734FC2@THSONEA01CMS04P.one.grp>
Ok, good. Thanks Antonio.
De : Antonio Garcia Vazquez [mailto:antonio.garcia at atosresearch.eu]
Envoy? : jeudi 21 mars 2013 17:45
? : BISSON Pascal; fiware-security at lists.fi-ware.eu
Objet : RE: [Fiware-security] FI-WARE Architecture description for V2 - peer review perfomed by apps chapter done - please address comments received and update accoridngly your GE arch desc.
Good afternoon,
I?ve just include the modifications required for Context-based security & compliance GE
Best
************************************
* Antonio Garc?a-V?zquez *
* (+34) 91 214 9384 *
* antonio.garcia at atosresearch.eu *
************************************
From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal
Sent: jueves, 21 de marzo de 2013 15:13
To: fiware-security at lists.fi-ware.eu
Subject: Re: [Fiware-security] FI-WARE Architecture description for V2 - peer review perfomed by apps chapter done - please address comments received and update accoridngly your GE arch desc.
Dear Task leads/GE owners,
Please confirm you addressed on the wiki (where your published Architecture description V2 are located) the peer review comments we received.
For those who have not yet finalized please address urgently review comments received.
And yes this would be on the Agenda of tomorrow's audio conf.
Best Regards,
Pascal
De : BISSON Pascal
Envoy? : vendredi 15 mars 2013 17:29
? : fiware-security at lists.fi-ware.eu
Cc : BISSON Pascal; GIDOIN Daniel
Objet : FI-WARE Architecture description for V2 - peer review perfomed by apps chapter done - please address comments received and update accoridngly your GE arch desc.
Dear Colleagues,
This email just to inform you that review of our chapter's contrib. to Architecture Description V2 deliverable has been performed by the reviewing chapter appointed (aka Data chapter). https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0
Being said this review has been performed per GE or block of GEs I would ask each of the GE owners to go to the review file of concern and address comments received (the sooner the better as usual, drop me an email once done ...)
Once each and every of you GE owners would have addressed their review comments on the wiki where their stuff is, I will generate a new version of the chapter docx for another check of peer reviewers appointed.
Many thanks in advance for your work and yes don't forget to drop me an email once revision of your GE has been performed.
Hearing from you.
Best Regards,
Pascal
------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended
solely for the addressee; it may also be privileged. If you receive
this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos
group liability cannot be triggered for the message content. Although
the sender endeavours to maintain a computer virus-free network,
the sender does not warrant that this transmission is virus-free and
will not be liable for any damages resulting from any virus transmitted.
Este mensaje y los ficheros adjuntos pueden contener informacion confidencial
destinada solamente a la(s) persona(s) mencionadas anteriormente
pueden estar protegidos por secreto profesional.
Si usted recibe este correo electronico por error, gracias por informar
inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos
no se hace responsable por su contenido. Su contenido no constituye ningun
compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes.
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
no puede garantizar nada al respecto y no sera responsable de cualesquiera
danos que puedan resultar de una transmision de virus.
------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From slim.trabelsi at sap.com Thu Mar 21 21:00:01 2013
From: slim.trabelsi at sap.com (TRABELSI, Slim)
Date: Thu, 21 Mar 2013 20:00:01 +0000
Subject: [Fiware-security] FI-WARE Architecture description for V2 -
peer review perfomed by apps chapter done - please address comments
received and update accoridngly your GE arch desc.
In-Reply-To:
References:
<18337_1363875441_514B1671_18337_520_1_294c2bb0-0a6f-44dc-a3c8-4226caa9487f@THSONEA01HUB04P.one.grp>
Message-ID: <31F2B8F7A6BAD749A28AE406B8EF250968F6F192@DEWDFEMB13A.global.corp.sap>
Hi,
The DH GE is updated according to the review comments
Slim
From: 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: jeudi 21 mars 2013 17:20
To: ext BISSON Pascal
Cc: fiware-security at lists.fi-ware.eu
Subject: Re: [Fiware-security] FI-WARE Architecture description for V2 - peer review perfomed by apps chapter done - please address comments received and update accoridngly your GE arch desc.
Hi Pascal,
for IDM and Privacy GE the comments are addressed except one comment for IDM GE, which I think is not relevant.
For Data Handling I expect that it is already done as well.
Here Francesco can report tomorrow.
Greetings
Robert
From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of ext BISSON Pascal
Sent: Thursday, March 21, 2013 3:13 PM
To: fiware-security at lists.fi-ware.eu
Subject: Re: [Fiware-security] FI-WARE Architecture description for V2 - peer review perfomed by apps chapter done - please address comments received and update accoridngly your GE arch desc.
Dear Task leads/GE owners,
Please confirm you addressed on the wiki (where your published Architecture description V2 are located) the peer review comments we received.
For those who have not yet finalized please address urgently review comments received.
And yes this would be on the Agenda of tomorrow's audio conf.
Best Regards,
Pascal
De : BISSON Pascal
Envoy? : vendredi 15 mars 2013 17:29
? : fiware-security at lists.fi-ware.eu
Cc : BISSON Pascal; GIDOIN Daniel
Objet : FI-WARE Architecture description for V2 - peer review perfomed by apps chapter done - please address comments received and update accoridngly your GE arch desc.
Dear Colleagues,
This email just to inform you that review of our chapter's contrib. to Architecture Description V2 deliverable has been performed by the reviewing chapter appointed (aka Data chapter). https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0
Being said this review has been performed per GE or block of GEs I would ask each of the GE owners to go to the review file of concern and address comments received (the sooner the better as usual, drop me an email once done ...)
Once each and every of you GE owners would have addressed their review comments on the wiki where their stuff is, I will generate a new version of the chapter docx for another check of peer reviewers appointed.
Many thanks in advance for your work and yes don't forget to drop me an email once revision of your GE has been performed.
Hearing from you.
Best Regards,
Pascal
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From francesco.di.cerbo at sap.com Thu Mar 21 22:47:25 2013
From: francesco.di.cerbo at sap.com (DI CERBO, Francesco)
Date: Thu, 21 Mar 2013 21:47:25 +0000
Subject: [Fiware-security] FI-WARE Architecture description for V2 -
peer review perfomed by apps chapter done - please address comments
received and update accoridngly your GE arch desc.
In-Reply-To: <18337_1363875441_514B1671_18337_520_1_294c2bb0-0a6f-44dc-a3c8-4226caa9487f@THSONEA01HUB04P.one.grp>
References:
<18337_1363875441_514B1671_18337_520_1_294c2bb0-0a6f-44dc-a3c8-4226caa9487f@THSONEA01HUB04P.one.grp>
Message-ID: <6D11E010ED8E5B4B9D42045AC71F37E607086EBD@DEWDFEMB18B.global.corp.sap>
Hello Pascal,
The reviewer's comment for DB Anonymizer have been applied
Best
Francesco
From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal
Sent: jeudi 21 mars 2013 15:13
To: fiware-security at lists.fi-ware.eu
Subject: Re: [Fiware-security] FI-WARE Architecture description for V2 - peer review perfomed by apps chapter done - please address comments received and update accoridngly your GE arch desc.
Dear Task leads/GE owners,
Please confirm you addressed on the wiki (where your published Architecture description V2 are located) the peer review comments we received.
For those who have not yet finalized please address urgently review comments received.
And yes this would be on the Agenda of tomorrow's audio conf.
Best Regards,
Pascal
De : BISSON Pascal
Envoy? : vendredi 15 mars 2013 17:29
? : fiware-security at lists.fi-ware.eu
Cc : BISSON Pascal; GIDOIN Daniel
Objet : FI-WARE Architecture description for V2 - peer review perfomed by apps chapter done - please address comments received and update accoridngly your GE arch desc.
Dear Colleagues,
This email just to inform you that review of our chapter's contrib. to Architecture Description V2 deliverable has been performed by the reviewing chapter appointed (aka Data chapter). https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0
Being said this review has been performed per GE or block of GEs I would ask each of the GE owners to go to the review file of concern and address comments received (the sooner the better as usual, drop me an email once done ...)
Once each and every of you GE owners would have addressed their review comments on the wiki where their stuff is, I will generate a new version of the chapter docx for another check of peer reviewers appointed.
Many thanks in advance for your work and yes don't forget to drop me an email once revision of your GE has been performed.
Hearing from you.
Best Regards,
Pascal
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From Wolfgang.Steigerwald at telekom.de Fri Mar 22 10:55:01 2013
From: Wolfgang.Steigerwald at telekom.de (Wolfgang.Steigerwald at telekom.de)
Date: Fri, 22 Mar 2013 10:55:01 +0100
Subject: [Fiware-security] I have to leave
Message-ID:
Hello Pascal,
I have to switch to another meeting. I will be next week on vacation so we hear us after Eastern.
Best regards
Wolfgang
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From pascal.bisson at thalesgroup.com Mon Mar 25 09:36:22 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Mon, 25 Mar 2013 09:36:22 +0100
Subject: [Fiware-security] TR: [Fiware] End of 1st Open Call: new partners
in FI-WARE
Message-ID: <29778_1364200583_51500C87_29778_5144_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E47D6C54@THSONEA01CMS04P.one.grp>
FYI
De : fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo
Envoy? : vendredi 22 mars 2013 19:33
? : fiware at lists.fi-ware.eu
Objet : [Fiware] End of 1st Open Call: new partners in FI-WARE
Dear all,
This is to confirm that the new partners that are joining FI-WARE as a result of the 1st FI-WARE Open Call are fully part of our consortium now.
To be more precise:
* Proposal KIARA: 4 partners - ZHAW (leader), DFKI, USAAR-CISPA and EPROS.
* Proposal BEMES: one single partner - iMinds
Each new partner will get integrated in their respective workpackages. ZHAW, DFKI, USAAR-CISPA and EPROS will mainly work in WP6 (data) and iMinds will be basically in WP3 (Apps & Services)
They will progressively join our everyday activities and will start using the collaborative tools too.
FI-WARE has been running for 2 years now and the environment is complex, they will need our support to catch up. Please help them as much as you can, particularly the WPLs/WPAs will have to give them a bit of their time now.
Welcome aboard!
Miguel
--
----------------------------------------------------------------------
_/ _/_/ Miguel Carrillo Pacheco
_/ _/ _/ _/ Telef?nica Distrito Telef?nica
_/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4
_/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N
_/ _/_/ 28050 Madrid (Spain)
Tel: (+34) 91 483 26 77
e-mail: mcp at tid.es
Follow FI-WARE on the net
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:
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL:
From pascal.bisson at thalesgroup.com Thu Mar 28 10:19:11 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Thu, 28 Mar 2013 10:19:11 +0100
Subject: [Fiware-security] TR: [Fiware] Guidelines for Release 2
Message-ID: <7859_1364462621_51540C1B_7859_12_5_CBBCD6C304123F4AB23FAAE3055C8C0E0206E499D675@THSONEA01CMS04P.one.grp>
FYI = Guidelines for Release 2 (counting on you all to follow those guidelines & deliver according to the set deadline for review aka April 22 !)
De : fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo
Envoy? : jeudi 28 mars 2013 02:24
? : fiware at lists.fi-ware.eu
Objet : [Fiware] Guidelines for Release 2
Dear all,
Given the importance of the general guidelines for the delivery of the deliverables associated to the software and the absence of key components of the team due to the Easter holidays, this message is directly sent to all the consortium. Be ready for a long but extremely important message.
This is strictly about :
* Delivery of the Software itself
* Installation and Administration manual
* User and Programmer manual
* Unit Testing Plan and report
The date for delivery to the EC is the end of April so we will need to have all complete and ready for review by April, 22 , as agreed in the past WPL/WPA call.
The guidelines are available on the private wiki (if you do not have access, ask your WPL or WPA to fix it) . The link to the detailed guidelines is here(you need to this them before editing the deliverables):
* https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2
Please note that:
* The guidelines for the docs are basically the same ones as for Release 1
* The guidelines for the software delivery are completely different and were sent by Ferm?n to this list ages ago
Please use the placeholders to edit each document (linked from the guidelines page). Most of the chapters have not started this work, they must use the private wiki following the links under the placeholder section in the guidelines. Exceptionally, if someone has started editing the changes somewhere else (I am only aware of some GEs in WP3), carry on working there but this place must be linked from the placeholders, so make them point at the right location where you actually work . If you start working now you must use the links provided and the private wiki. I will ask to revert any unauthorised changes in the public wiki, I insist that you must use the private wiki (the public wiki should only have definite manuals, not intermediate stuff).
Be aware that this time moving pages across different wikis (figures included) is done in a matter of seconds thanks to a tool developed by SAP. Your WPL must have access to it (or can ask for access to it if he has not done so yet)
* This will ease the work of copying the definite versions of the manuals to their final destinations.
* Also, if you need to use a previous version on the manual as the basis for the coming issue of the docs, this tool can be used to take a copy of the current wiki pages to the private wiki prior to the start of your work.
Check with your WPL/WPA if you have any doubts, I will only answer queries routed via the WPL/WPAs to ensure a good synchronisation of the whole process.
Best regards,
Miguel
________________________________
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:
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL:
From pascal.bisson at thalesgroup.com Thu Mar 28 16:12:56 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Thu, 28 Mar 2013 16:12:56 +0100
Subject: [Fiware-security] TR: [Fiware-wpl] Backlog - Sprint transition:
from S2.2.3-M23 to S2.3.1-M24 -Release 2.2 is finished - Release2.3 is
opened
Message-ID: <10018_1364483844_51545F04_10018_3657_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E49E7391@THSONEA01CMS04P.one.grp>
@All
I'm forwarding you this email received from Manual for you to update tracker accordingly since Sprint 2.2.3 is ending and that we would be entering Sprint 2.3.1 (M24) on 1st of April.
Counting on you to perform the update requested and yes will check at our next audio.
BR
Pascal
De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de MANUEL ESCRICHE VICENTE
Envoy? : mercredi 27 mars 2013 16:33
? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Objet : [Fiware-wpl] Backlog - Sprint transition: from S2.2.3-M23 to S2.3.1-M24 -Release 2.2 is finished - Release2.3 is opened
Dear Partners,
As you know we are about to finish Sprint 2.2.3 corresponding to M23. This sprint closes Release 2.2
Next 1.April (M24) Sprint 2.3.1 (1st sprint of Release 2.3) is opened.
Please, update your backlog items accordingly.
1. Close the tickets you finished along M23 (if not already done)
2. Update tickets under execution not finished to belong to Sprint 2.3.1
3. Open those new tickets you have scheduled/planned for Release 2.3 Sprint 2.3.1 - be aware Release 2.3 is the last release available for the current reporting period.
Let me stress agile is obsessed with delivery, so there's need to commit to the backlog content allocated for a sprint (step 3), then few tickets are moved to next sprint (step 2).
During this month we have updated the wiki templates for the public backlog items, please, check your content is consistent. Now there're fewer fields than before but still some content is missing or not correct.
The templates have categories, please, check your team is using them properly.
If anything, please, let me know.
Thanks for cooperation!
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
________________________________
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:
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL:
From pascal.bisson at thalesgroup.com Thu Mar 28 16:41:28 2013
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Thu, 28 Mar 2013 16:41:28 +0100
Subject: [Fiware-security] =?utf-8?q?Annul=C3=A9=3A_FI-WARE_WP8_Weekly_aud?=
=?utf-8?q?io_conf?=
Message-ID: <10018_1364485557_515465B5_10018_4843_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E49E74EF@THSONEA01CMS04P.one.grp>
Quand : vendredi 29 mars 2013 10:00-12:00 (GMT+01:00) Bruxelles, Copenhague, Madrid, Paris.
Emplacement : Meeting Room Number: 391581
Remarque : le d?calage GMT ci-dessus ne tient pas compte des r?glages de l'heure d'?t?.
*~*~*~*~*~*~*~*~*~*
Liste des num?ros LocalConnect:
Australia Australia Toll Free 1800 005 574
Australia Sydney +61 (0) 282 239 767
Austria Vienna +43 (0) 2682 205 6609
Belgium Brussels +32 (0) 2 789 8678
Denmark Copenhagen +45 3271 4340
Finland Helsinki +358 (0) 923 142 830
France Lyon +33 (0) 426 840 285
France Marseille +33 (0) 488 915 385
France Paris +33 (0) 170 994 816
Germany Berlin +49 (0) 3072 616 7342
Germany D?sseldorf +49 (0) 2115 407 3902
Germany Frankfurt +49 (0) 6971 044 5635
Germany Hamburg +49 (0) 4080 902 0684
Germany Munich +49 (0) 8924 443 2893
Germany Stuttgart +49 (0) 7111 856 2130
Greece Greece Toll Free 0080 012 6344
Hong Kong Hong Kong +852 301 145 59
Hungary Budapest +36 (06) 1-889-3286
Ireland Dublin +353 (0) 14 860 780
Israel Israel Toll Free 1809 245 981
Italy Milan +39 0 230 413 017
Italy Rome +39 0 645 217 056
Italy Turin +39 0 112 179 2159
Japan Japan Toll Free 005 311 212 65
Japan Tokyo +81 (0) 357 675 025
Korea, Republic Of Seoul +82 (0) 234 831 224
Luxembourg Luxemburg City +352 2700 41 42
Malaysia Kuala Lumpur +60 (0) 377 124 640
Netherlands Amsterdam +31 (0) 207 948 529
New Zealand Auckland +64 (0) 9 919 2428
Norway Oslo +47 2153 3919
Poland Poland Toll Free 0080 0121 1304
Portugal Portugal Toll Free 800 814 183
Russia Russia Toll Free 81080 02209 4011
Singapore Singapore +65 6622 1068
Spain Barcelona +34 93 492 3235
Spain Madrid +34 91 788 9908
Sweden Stockholm +46 (0) 850 520 145
Switzerland Geneva +41 (0) 225 927 428
United Kingdom Birmingham +44 (0) 121 260 4686
United Kingdom London +44 (0) 207 153 9902
United Kingdom Manchester +44 (0) 161 250 0679
United States USA & Canada Toll Free 1888 249 0050
United States USA Toll +1 954 334 1559
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 4360 bytes
Desc: not available
URL: