Hi Juanjo,
The point you are raising is for sure right for the direction who is coordinating - I even opted that in the task description of 10.5 this does not make sense at all and should be dropped - Miguel and Javier declined this request.
But the initial statement given in the DoW and that was agreed with me should point to the ones that produce the documentation - I just discovered that you again changed this without letting me know. :(
The statement that was agreed is attached - it must be clear that Task 10.5 can't provide the information and training material itself on the operation of a testbed instance (this information is just not part of the 10.5 task as - operation and therefore as well documentation of operation is in scope of 10.2 and 10.3 or perhaps 10.4 - but for sure not 12.4 and not 10.5.).
ð If we do not shift this text away from Task 10.5 (as I was initially proposing) then I still want to have reflected in the task description that task 10.5 does not provide the information itself. And therefore the initial statement agreed with Javier and Miguel should be suitable
"The documentation and training material will be ultimately provided by 10.X and 10.Y"
and yes: please drop this part completely in this task description and write it to the relevant task in 10.X - my impression was that it was just misplaced in the first place - but do not leave it in the task that is primarily focusing on validation.
Thanks for letting me know your thoughts.
/Thorsten
PS: I dropped the WP9 list from the cc
[cid:image002.jpg at 01CE45EF.91129EE0]
It
--
Thorsten Sandfuchs
SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com<http://www.sap.com/>
Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx
Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.
This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
Please consider the environment before printing this mail!
From: Juanjo Hierro [mailto:jhierro at tid.es]
Sent: Mittwoch, 15. Mai 2013 11:07
To: Sandfuchs, Thorsten
Cc: Andrea Manieri; fiware-testbed at lists.fi-ware.eu; Javier de Pedro Sanchez; Davide Dalle Carbonare; fiware-tools at lists.fi-ware.eu
Subject: Re: [Fiware-testbed] Revised versions of WP9 and WP10 to incorporate in amendment 4 of the DoW
Dear Thorsten,
I'm afraid you are not right. Indeed, this was one of thing that I found had to be fixed in the previous version of the WP10 description.
If you take a look to the description of Task 12.4, which is there since the very first DoW, you will find:
Training material will be generated in WP03-WP10 and used in specific events such as the FI-WARE developer's day. This will allow communities to be involved in the training process on a continuous basis, thus helping others to use the results of the project, including, but not restricted to usage area projects. Training material will include but will not be limited to:
* A set of training resources primarily composed of PowerPoint slide sets which may be used as training workshops organized around the FI-WARE Testbed.
* A selected number of tutorials using some sort of webcasting technology. This will typically involve production of online streaming webcasts in a format which links the video footage of a speaker with the presented PowerPoint slides.
Somehow, it was considered that training material should be generated in the WPs itself while coordination of training activities (e.g., Developers' days but we may also consider the Architects Weeks or the webinars organized for UC projects) would be considered in task 12.4.
Apparently, when you generated the previous version of WP10, you were not aware that coordination of the generation of training material was already considered as part of Task 12.4 since the very first DoW. That's what Miguel told me. It was clear that you wanted to make it explicit that responsibility of task 10.5 was only to "offer pointers" and this was something I agreed to, but fixing reference to the tasks where coordination of the elaboration of the training material, as well as organization of webinars, etc, will take place, which should not be any task in WP10 (as you originally proposed) but task 12.4 as considered in the original DoW
Cheers,
-- Juanjo
-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es<http://www.tid.es>
email: jhierro at tid.es<mailto:jhierro at tid.es>
twitter: twitter.com/JuanjoHierro
FI-WARE (European Future Internet Core Platform) Coordinator
and Chief Architect
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
On 15/05/13 10:30, Sandfuchs, Thorsten wrote:
Hi Andrea, Juanjo
Sorry for not finding time to comment here earlier - I think there is a small _editorial_ problem in the task-description of 10.5:
This task will also offer Usage Areas pointers to specific documentation and dedicated training resources that may help them to setup and configure as well as to operate FI-WARE GEi instances. Such training can be materialised, depending on the specific needs, through dedicated workshops and material organized as part of Task 12.4.
This task will also offer Usage Areas pointers to specific documentation and dedicated training resources that may help them to setup and configure as well as to operate FI-WARE GEi instances. Such training can be materialised, depending on the specific needs, through dedicated workshops and material organized as part of Task 10.4.
Best,
/Thorsten
-----Original Message-----
From: fiware-testbed-bounces at lists.fi-ware.eu<mailto:fiware-testbed-bounces at lists.fi-ware.eu> [mailto:fiware-testbed-bounces at lists.fi-ware.eu] On Behalf Of Andrea Manieri
Sent: Dienstag, 14. Mai 2013 22:15
To: Juanjo Hierro
Cc: fiware-testbed at lists.fi-ware.eu<mailto:fiware-testbed at lists.fi-ware.eu>; Javier de Pedro Sanchez; Davide Dalle Carbonare; fiware-tools at lists.fi-ware.eu<mailto:fiware-tools at lists.fi-ware.eu>
Subject: Re: [Fiware-testbed] Revised versions of WP9 and WP10 to incorporate in amendment 4 of the DoW
Dear Juanjo, All,
here the final version, after an internal check of respective WPs
(partners explicitly approving are listed in the filename).
If agreed with the changes, you can simply accept all and remove comments.
Best,
A.
Il 14/05/2013 03:11, Juanjo Hierro ha scritto:
> Dear Davide and Andrea,
>
> Please find enclosed the revised versions of the WP9 and WP10
> description forms with all the changes I believe would be needed to make
> it clear the goals and scope of activities in both WPs.
>
> The WP10 is actually the same I already sent to you last week. I
> have reviewed once again and I believe it doesn't require additional
> changes to the ones I originally proposed. I understood that the
> proposed changes were ok for you but just wanted to double-check.
>
> In the reviewed WP9, I would say that the changes mostly clarify the
> scope and goals. I believe that the scope of activities in task 9.1
> was rather hard to understand in the existing version. I hope you will
> agree with most (if not all) of the changes. The rest of changes in
> 9.2 and 9.3 are minor.
>
> Please come back to us with a final revised version during today
> (tuesday) so that we can submit by the evening a version of the DoW for
> final approval by our deputy PO, Ragnar Bergstrom.
>
> Please don't accept the changes you agree with since we will have to
> submit the WPs with changes highlighted to our PO. Just modify or add
> new changes if you don't agree with them or consider them not
> sufficient. Then return back the resulting final version. We will
> consider that those changes we have proposed that remain in the returned
> WP description forms are there because they were ok for you.
>
> Best regards,
>
> -- Juanjo
>
> -------------
> Product Development and Innovation (PDI) - Telefonica Digital
> website: www.tid.es<http://www.tid.es>
> email: jhierro at tid.es<mailto:jhierro at tid.es>
> twitter: twitter.com/JuanjoHierro
>
> FI-WARE (European Future Internet Core Platform) Coordinator
> and Chief Architect
>
> 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
________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-testbed/attachments/20130515/e5f4994b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 82265 bytes
Desc: image001.jpg
URL: <https://lists.fiware.org/private/old-fiware-testbed/attachments/20130515/e5f4994b/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy