Hi miguel, i will book a gotomeeting session for thursday 9th from 11.00 to 13.00. I believe the call will be much shorter, but i'm book 2 hours just in case. See you tomorrow. On Tue, Feb 7, 2017 at 6:00 PM, Miguel Jimenez <mjimenez at fi.upm.es> wrote: > Hi all, > > Till thursday morning Fran will not be available. Could it be possible to > hold a planning meeting around 11 on thursday? If not, please suggest > another option. > > Best regards, > > ─────────────────────────── > Miguel Jiménez Gañán, PhD. > Dpto. Lenguajes y Sistemas Informáticos e Ingeniería de Software > Escuela Técnica Superior de Ingenieros Informáticos > Universidad Politécnica de Madrid (UPM) > ─────────────────────────── > > On Mon, Feb 6, 2017 at 9:56 AM, Alessandro Portosa < > alessandro.portosa at eng.it> wrote: > >> Dear all, >> I think we should have a chapter meeting this week and talk about the >> technical roadmap. What do you think? >> >> Regards, >> Alessandro >> >> ---------- Forwarded message ---------- >> From: Juanjo Hierro <juanjose.hierro at fiware.org> >> Date: Mon, Feb 6, 2017 at 1:16 AM >> Subject: [Fiware-technical-committee] Cancelation of todays' FIWARE TSC >> and preparation of technical roadmap for the new FIWARE release >> To: "fiware-technical-committee at lists.fiware.org" < >> fiware-technical-committee 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 >> [image: 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 >> >> >> >> >> ____________________________________________________________ >> ______________________________ >> >> 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-apps mailing list >> Fiware-apps at lists.fiware.org >> https://lists.fiware.org/listinfo/fiware-apps >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-apps/attachments/20170208/2a5c013b/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE Foundation Logo edited.png Type: image/png Size: 5618 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-apps/attachments/20170208/2a5c013b/attachment.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy