[Fiware-cloud] Fw: [Fiware-wpl] TASK FORCE for FI-WARE GEi owners towards the 2nd year project review

Alex Glikson GLIKSON at il.ibm.com
Fri Jun 7 20:22:24 CEST 2013


As expected, below is an urgent task towards next week's review. Please, 
follow the guidelines and let me know when done. Deadline is EOB Monday.

Thanks,
Alex


====================================================================================================
Alex Glikson
Manager, Cloud Operating System Technologies, IBM Haifa Research Lab
http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | 
http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml 
Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: 
+972-54-6466667 | Fax: +972-4-8296112

----- Forwarded by Alex Glikson/Haifa/IBM on 07/06/2013 09:20 PM -----

From:   Juanjo Hierro <jhierro at tid.es>
To:     "fiware at lists.fi-ware.eu" <fiware at lists.fi-ware.eu>, 
Cc:     "fiware-wpl at lists.fi-ware.eu" <fiware-wpl at lists.fi-ware.eu>, 
"fiware-wpa at lists.fi-ware.eu" <fiware-wpa at lists.fi-ware.eu>
Date:   07/06/2013 01:38 PM
Subject:        [Fiware-wpl] TASK FORCE for FI-WARE GEi owners towards the 
2nd year        project review
Sent by:        fiware-wpl-bounces at lists.fi-ware.eu



Dear all,

  As you know, we are facing the 2nd year official project review next 
week.

  During the last preparation meeting we had this Wednesday, we agreed to 
prepare a revision of the FI-WARE GEi planned availability and usage 
cockpit that we are currently sharing with the UC projects.   This 
revision would be enriched with information about status, planned terms 
and conditions in the different environments, base line assets, etc.

  Please we need to complete this task force by EOB Monday at the latest.  
It is a pretty simple exercise, so it won't take so much time.

  I have prepared a shared spreadsheet in Google docs that will help us to 
work in the new version of the cockpit without creating so much noise in 
front of the UC projects.   You can find it available at the following 
link:
https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEQ4TlBJT1JwT1ZfMVUwQzhzRWExOEE#gid=8

  You have to complete columns N (already filled, just double-check) and 
the new columns, namely columns O to X.

  Columns O-Q deal with info about availability for the FI-PPP partners 
(which includes availability on the FI-WARE Testbed being used by UC 
projects to run their experiments).  All relevant notes that will help you 
to complete your exercise are provided.  Please read them carefully and 
try to follow them. 

  Columns R-T deal with info about availability within the FI-WARE Open 
Innovation Lab (OIL).   I guess you all know about the FI-WARE OIL so I 
don't need to elaborate.   Despite the concrete legal terms and conditions 
are under definition, you can assume that this will be an environment 
where GEis will be offered (in whatever mode is decided per GEi) for free 
to third parties (i.e., anyone) who wish to experiment with the 
technology.  The GEis will be provided "as-is" without no warranty and 
only committing a best-effort support.   They will be provided for 
non-comercial experimental-only use by those third parties.   All relevant 
notes that will help you to complete your exercise are provided.  Please 
read them carefully and try to follow them. 

  Why is there a distinction between availability within the FI-PPP and 
within OIL ?    Mainly because the mode in which you will offer a GEi may 
vary.   Actually, within the FI-PPP you are more constrained and have to 
comply with the signed Collaboration Agreement.    Thus, you may decide to 
support "Dedicated SaaS instance, binaries" for FI-PPP partners, but may 
decide to only support "Dedicated SaaS instance" to users of the FI-WARE 
OIL.

  Columns U-V deal with info about availability beyond the FI-PPP. Again, 
all relevant notes that will help you to complete your exercise are 
provided.  Please read them carefully and try to follow them. 

  Column W has to contain a link to the place in the "materializing the 
FI-WARE vision" part of the wiki where you described the baseline assets 
used for your GEi.   Adding the proper link is pretty straight forward. Go 
to the wiki page associated to "materializing the FI-WARE vision" for your 
chapter and then, click on the "Baseline assets" section of your GEi in 
the Table of Contents of that wiki page.   That action, besides it will 
place you at the right place in the wiki page, will imply that the URL in 
your browser will then be precisely pointing to that section.

  Column X has to contain the link to the corresponding entry in the 
FI-WARE Catalogue.   I guess I don't need to explain how to fill it.

  WPLs are encouraged to follow-up this process and make sure it gets 
finalized on time for GEis in their chapters.

  Don't hesitate to ask if you have any doubt on how to fill the 
spreadsheet.

  Cheers,

-- 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
_______________________________________________
Fiware-wpl mailing list
Fiware-wpl at lists.fi-ware.eu
https://lists.fi-ware.eu/listinfo/fiware-wpl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20130607/e9c55297/attachment.html>


More information about the Old-Fiware-cloud mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy