[Fiware-technical-committee] Questions before launching the call for candidatures to be elected as member of the FIWARE TSC

[Silvio Cretti]

Hi all,
regarding point 2 (FIWARE OPS integrated into FIWARE Lab), it makes a lot
of sense from my point of view.
Best regards
   silvio

On Mon, Jun 6, 2016 at 11:58 AM, Juanjo Hierro <
juanjose.hierro at telefonica.com> wrote:

> Hi all,
>
>   Before launching the call for candidatures for election of members of
> the FIWARE TSC, I would like to hear your opinion about a number of matters:
>
>    - How do we expect that the "Interface to Networks and Devices"
>    Chapter will evolve?  I haven't seen any active participation in FIWARE TSC
>    meetings so far ...
>    - Shouldn't we integrate the FIWARE Ops chapter into the FIWARE Lab
>    chapter?   I tend to see activities within the FIWARE Ops chapter as
>    activities very much linked to the FIWARE Lab, actually dealing with
>    creation of tools used in FIWARE Lab operations.
>    - I understand that the FIWARE Community Support Tools chapter
>    comprises both the FIWARE Catalogue and Academy
>    - Shouldn't we define a FIWARE QA Lab chapter since we aim at carrying
>    out this QA activities aside (although obviously connected) to the
>    chapters?
>
>   Please feel free to share any other question you believe it is worth
> discussing regarding the taxonomy of FIWARE Chapters.
>
>   Best regards,
>
> -- Juanjo
>
> ______________________________________________________
>
> Coordinator and Chief Architect, FIWARE platform
> IoT Unit, Telefónica
>
> email: juanjose.hierro at telefonica.com
> twitter: @JuanjoHierro
>
> You can follow FIWARE at:
>   website:  http://www.fiware.org
>   twitter:  @FIWARE
>   facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
>   linkedIn: http://www.linkedin.com/groups/FIWARE-4239932
>
>
> ------------------------------
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
> puede contener información privilegiada o confidencial y es para uso
> exclusivo de la persona o entidad de destino. Si no es usted. el
> destinatario indicado, queda notificado de que la lectura, utilización,
> divulgación y/o copia sin autorización puede estar prohibida en virtud de
> la legislación vigente. Si ha recibido este mensaje por error, le rogamos
> que nos lo comunique inmediatamente por esta misma vía y proceda a su
> destrucción.
>
> The information contained in this transmission is privileged and
> confidential information intended only for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited. If you have received
> this transmission in error, do not read it. Please immediately reply to the
> sender that you have received this communication in error and then delete
> it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário,
> pode conter informação privilegiada ou confidencial e é para uso exclusivo
> da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário
> indicado, fica notificado de que a leitura, utilização, divulgação e/ou
> cópia sem autorização pode estar proibida em virtude da legislação vigente.
> Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique
> imediatamente por esta mesma via e proceda a sua destruição
>
> _______________________________________________
> Fiware-technical-committee mailing list
> Fiware-technical-committee at lists.fiware.org
> https://lists.fiware.org/listinfo/fiware-technical-committee
>
>


-- 
Silvio Cretti,
Distributed Computing and Information Processing (DISCO)
Area Head
CREATE-NET Research Center
Via alla Cascata 56 D
38123 Povo, Trento - Italy
email: silvio.cretti at create-net.org
Tel: +39-0461-312433
Mobile: +39-338-6738175
www.create-net.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20160610/3be14bfc/attachment.html>