[Fiware-cloud] fiware cloud roadmap

[Kenneth Nagin]

We are being asked to create a roadmap.  Lets talk about this in our next 
meeting on Tuesday.

Best Regards,

Kenneth Nagin
Ph: +972-4-8296227
Cell: 054-6976227
Fx: +972-4- 8296114
http://researcher.ibm.com/view.php?person=il-NAGIN



----- Forwarded by Kenneth Nagin/Haifa/IBM on 06/02/2017 09:17 AM -----

From:   Juanjo Hierro <juanjose.hierro at fiware.org>
To:     "fiware-technical-committee at lists.fiware.org" 
<fiware-technical-committee at lists.fiware.org>
Date:   06/02/2017 02:18 AM
Subject:        [Fiware-technical-committee] Cancelation of todays' FIWARE 
TSC and preparation of technical roadmap for the new FIWARE release
Sent by:        fiware-technical-committee-bounces at lists.fiware.org



Dear all,
  Responsibles of the CEF programme have asked to setup a confcall to 
review the application we are completing for the inclusion of the FIWARE 
Context Broker GE as CEF Building Block and there were not many other 
choices that having it tomorrow, overlapping with the FIWARE TSC.   
Therefore, we suggest that it is canceled.
  There is an important task that leaders of each of the FIWARE chapters 
should start working on: the definition of the technical roadmap of each 
chapter for the new major release of FIWARE (release 6), including the 
definition of Epics and Features in the backlog of each FIWARE GE, or at 
chapter level, that will be addressed for the new major release of FIWARE 
and its minor releases.   
  FIWARE Chapter leaders should call for a regular call of members of the 
chapter where they can start working on the definition.   A first version 
of each chapter Technical Roadmap should be ready by February 13th so that 
we can review it at high-level during the TSC.   Please arrive with your 
homework done at the FIWARE TSC on Feb 13th.   During following TSCs we 
will start reviewing the technical roadmap of each chapter in detail and 
its status of development.
  Bear in mind that different members within a given chapter may have 
different means for funding their activities.   Therefore, by no means we 
are talking just about FI-Core.   Indeed, it is expected that each FIWARE 
GEri owner has its own plans regarding their roadmap, relying on different 
means of funding (private, public, or a mix).   However, chapter leaders 
should gather the information and push for definition of the roadmap, no 
matter how it will get funded.
  I would kindly ask each FIWARE chapter leader/co-leader to come back to 
me with a suggestion of day during the week and frequency of their chapter 
meetings.   I would try to be joining to them fron now on.   It would be 
nice if you could set up some of them on Friday or Mondays, so that there 
is less risk of overlapping with trips.
  Cheers,
-- 
Juanjo Hierro 
    

Chief Technology Officer
FIWARE Foundation 


email: juanjose.hierro at fiware.org
www: http://fiware.org
twitter: @JuanjoHierro @FIWARE 


__________________________________________________________________________________________

You can get more information about our cookies and privacy policies on the 
following links:
- 
http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy

- 
http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE


Fiware-technical-committee mailing list
Fiware-technical-committee at lists.fiware.org
https://lists.fiware.org/listinfo/fiware-technical-committee




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-cloud/attachments/20170206/4e2a20ee/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 5618 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-cloud/attachments/20170206/4e2a20ee/attachment.png>