[Fiware-technical-committee] FIWARE TSC elections and way of working of our TSC from now on

Juanjo Hierro juanjose.hierro at fiware.org
Mon Feb 12 09:59:46 CET 2018


Hi Joaquin,

   That would be great.  I have added to the agenda.

   Cheers,

   Juanjo



On 09/02/2018 22:02, Joaquín Salvachúa wrote:
> Hello,
>
> I can give a short report on what we are right now planning (evolve to 
> fast data components).
>
> Joaquin
>
>
>> El 9 feb 2018, a las 21:48, José Manuel Cantera 
>> <josemanuel.cantera at fiware.org 
>> <mailto:josemanuel.cantera at fiware.org>> escribió:
>>
>> Dejar Juanjo
>>
>> Is It per Chapter or per Ge? I Guess It is per Ge but grouping per 
>> chapter. In that case the owners of Sth and Cygnus should report as 
>> well. Joaquin. Given the short notice It would be without slides.
>>
>> I will be able to report on progress on Orión and standards activities.
>>
>> Thanks
>>
>> Best
>>
>>
>> On Friday, February 9, 2018, Juanjo Hierro 
>> <juanjose.hierro at fiware.org <mailto:juanjose.hierro at fiware.org>> wrote:
>>
>>     Dear all,
>>
>>       Now with Veronika fully on board as our Scrum Master at the
>>     FIWARE Foundation, we would like to introduce a number of changes
>>     in our Way of Working (WoW) at the FIWARE TSC:
>>
>>       * Veronika will send every tuesday after a FIWARE TSC, a draft
>>         agenda with link to pre-minutes for the following TSC
>>       * Members of the TSC will then be invited to propose additional
>>         topics until Thursday noon
>>       * Veronika will send a final version of the agenda and
>>         pre-minutes before Thursday EOB
>>       * People will have the opportunity to add input in the
>>         pre-minutes before the TSC
>>
>>       Once every month, we will send a mail to the FIWARE ecosystem
>>     reminding that individual members and people working for FIWARE
>>     Foundation member organizations are invited to join and that they
>>     can follow discussion through the publicly available minutes.
>>
>>       From now on and after the re-structuring of FIWARE chapters, we
>>     will organize our TSCs as follows:
>>
>>       * 1st hour: report on progress from GE owners in the various
>>         FIWARE chapters plus the chapter on FIWARE Lab and deployment
>>         tools:
>>           o Context Management (Core) Chapter
>>           o Data/API Management, Publication and Monetization Chapter
>>           o Context Processing, Analysis and Visualisation Chapter
>>           o Interface with IoT, robotics and third systems Chapter
>>           o FIWARE Lab and deployment tools
>>       * 2nd hour: proposed topics
>>
>>       We will be rotating among the chapters so each week we will
>>     focus on one. Topics/GEs to cover will be picked in advance. I'll
>>     come with a proposed calendar we all can review.
>>
>>       We would like to start with the Context Management (Core)
>>     Chapter this next TSC: José Manuel will be in charge of that.
>>
>>       Proposed topics for the second hour will change based on
>>     demand, but until Hannover-Messe we shall include an item to
>>     follow-up on progress of our Task Force regarding implementation
>>     of IDS architecture concepts:  20 mins will be booked for this.
>>
>>       The FIWARE Foundation General Assembly is coming and one of the
>>     questions we shall solve is that of running new elections of the
>>     TSC seats.  This will be one of the topics for our next TSC (2nd
>>     hour).   We have two choices:
>>
>>       * Rely on the bylaws, therefore go for election of 2
>>         representatives per chapter (we'll have now only 5) and then
>>         additional 3 individuals (platinum members choose who take
>>         their seats)
>>       * Ask for a change in the bylaws so that we run for elections
>>         of individual representatives, up to a number we find
>>         suitable, not linking them to existing chapters
>>
>>       So we will discuss what way to go at next TSC.  Your feedback
>>     in the meantime will be welcome.
>>
>>       Cheers,
>>
>>     -- 
>>     Juanjo Hierro
>>     Chief Technology Officer
>>     juanjose.hierro at fiware.org <mailto:juanjose.hierro at fiware.org>
>>     www.linkedin.com/in/jhierro <https://www.linkedin.com/in/jhierro>
>>     Twitter: @fiware <https://twitter.com/fiware> @JuanjoHierro
>>     <https://twitter.com/JuanjoHierro>
>>     <foundation-logo.png>
>>
>>
>>
>>
>>
>>
>>
>>
>> __________________________________________________________________________________________
>>
>> 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 
>> <mailto: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-technical-committee/attachments/20180212/147d91de/attachment.html>


More information about the Fiware-technical-committee mailing list

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