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

[Pezuela, Clara]

Ok, Thanks, I will then invite to join my colleague in charge of IoT Agents, when was needed a report. This is what I needed to know

Best regards

Clara Pezuela
Head of IT Market
Research and Innovation Group
ARI booklet<https://atos.net/wp-content/uploads/2017/01/atos-ari-2016.pdf>
Atos Spain SA
Clara.pezuela at atos.net<mailto:Clara.pezuela at atos.net>
+34 675 62 9974

[cid:7206F4B45C675D4FA60A576B4DAED2AE at mail.sis.atos.net]

From: Juanjo Hierro [mailto:juanjose.hierro at fiware.org]
Sent: Sunday, February 11, 2018 7:52 PM
To: Pezuela, Clara; José Manuel Cantera
Cc: fiware-technical-committee at lists.fiware.org
Subject: Re: [Fiware-technical-committee] FIWARE TSC elections and way of working of our TSC from now on


Hi Clara,

  My proposal was that there isn't people as such taking over the responsibility for each chapter as it was in the past, although we may discuss this tomorrow if people find it better.

  My proposal was more in the line of deciding what FIWARE GEs per chapter are we going to review in each session and ask the corresponding GE owner to arrive at the TSC to bring such report.   That's why scheduling presentations in advance would be, of course, important.  This advance schedule could be shared with the FIWARE ecosystem at large, so that interested people can join the TSC and know about developments regarding a given technology, etc.

  I will try to share a schedule proposal to this TSC.

  Cheers,

  Juanjo

On 11/02/2018 18:39, Pezuela, Clara wrote:
Juanjo,

In practical terms, if the report is per chapter, could you indicate the speakers for each of the new chapters? I mean who from the chapter is nominated for collecting and providing the report about the chapter.

If the report is per chapter, we need to know in advance, as some of the GEs caretakers do not belong to the TSC.

Thanks and Best regards

Clara Pezuela
Head of IT Market
Research and Innovation Group
ARI booklet<https://atos.net/wp-content/uploads/2017/01/atos-ari-2016.pdf>
Atos Spain SA
Clara.pezuela at atos.net<mailto:Clara.pezuela at atos.net>
+34 675 62 9974

[cid:7206F4B45C675D4FA60A576B4DAED2AE at mail.sis.atos.net]

From: fiware-technical-committee-bounces at lists.fiware.org<mailto:fiware-technical-committee-bounces at lists.fiware.org> [mailto:fiware-technical-committee-bounces at lists.fiware.org] On Behalf Of José Manuel Cantera
Sent: Friday, February 09, 2018 9:48 PM
To: Juanjo Hierro
Cc: fiware-technical-committee at lists.fiware.org<mailto:fiware-technical-committee at lists.fiware.org>
Subject: Re: [Fiware-technical-committee] FIWARE TSC elections and way of working of our TSC from now on

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:

     *   Context Management (Core) Chapter
     *   Data/API Management, Publication and Monetization Chapter
     *   Context Processing, Analysis and Visualisation Chapter
     *   Interface with IoT, robotics and third systems Chapter
     *   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>
[cid:image003.png at 01D3A372.3E068410]








This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional.
Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes.
Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional.
Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes.
Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20180211/444c8d1c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 4796 bytes
Desc: image001.jpg
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20180211/444c8d1c/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 4796 bytes
Desc: image002.jpg
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20180211/444c8d1c/attachment-0003.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 8201 bytes
Desc: image003.png
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20180211/444c8d1c/attachment-0001.png>