[Fiware-data] RV: [Fiware] VERY IMPORTANT: Last call for registering as FIWARE Chapter Active Contributor

[SANTIAGO MARTINEZ GARCIA]

Dear all,

As discussed during some of the previous chapter calls, the process for being recognized as FIWARE Chapter Active Contributor is described the email below.

In principle, all developers contributing to any of the GEs in the chapter (except the incubated ones for the moment), should request to be recognized as CACs.

Please have a look at https://docs.google.com/spreadsheets/d/1vqx7mwcFFb4Z0pUAC5ghyTVSgEQdpraOXvCwlRawWPk/edit#gid=0

If you or some of your development colleagues are not already listed there, you should follow the process described below.

Many thanks,
Santiago.

De: fiware-bounces at lists.fiware.org [mailto:fiware-bounces at lists.fiware.org] En nombre de Juanjo Hierro
Enviado el: lunes, 25 de abril de 2016 9:21
Para: fiware at lists.fiware.org
Asunto: [Fiware] VERY IMPORTANT: Last call for registering as FIWARE Chapter Active Contributor

Dear all,

  Apparently, our original request asking for applications to be recognized as FIWARE Chapter Active Contributors (CAC) didn't reach all the potential candidates because they were not registered in the fiware at lists.fiware.org<mailto:fiware at lists.fiware.org> mailing list.    On the other hand, it seems like it was not very clear whether the original request was only targeted to gather information about FIWARE Chapter/GEris Top Contributors.

  For these reasons, we have decided to extend the deadline for applications to be recognized as FIWARE Chapter Active Contributors (CACs) until May 5th.   Please note that applications are not for the identification of top contributors but any relevant contributors.   Candidatures will be assessed by the already FIWARE Chapter/GEris Top Contributors.

  On the other hand, we kindly ask FIWARE Chapter/GEris Top Contributors to forward this message to all potential FIWARE CACs since this message may not reach them.

  Registering as FIWARE CACs is a great opportunity to participate in the technical direction of the FIWARE platform.   Actually, FIWARE Chapter Active Contributors will be able to elect FIWARE Technical Committee members as well as nominate themselves to represent their chapter in the FIWARE Technical Committee (TC).   They can of course also nominate themselves to run for some of the seats at the FIWARE TC that will be assigned to FIWARE Community Individual members (see https://www.fiware.org/fiware-governance/#chapter4_4)

  As a reminder, those who want to be recognized as FIWARE CAC will have to submit their application by sending a message to: fiware-active-contributor-application at lists.fiware.org<mailto:fiware-active-contributor-application at lists.fiware.org>

  *   Subject of their messages shall adopt the following pattern:
[chapter: <name of chapter>] [GEri: <name of GEri or relevant activity>] <name of person> (<name of organization if applicable>)

where: <name of chapter> and <name of GEri or relevant activity> shall correspond to a valid chapter and GEri name or relevant activity, respectively, as listed in:
https://docs.google.com/spreadsheets/d/1vqx7mwcFFb4Z0pUAC5ghyTVSgEQdpraOXvCwlRawWPk/edit?usp=sharing

examples:
     "[chapter: Data/Media Context Management] [GEri: Cosmos] Francisco Romero (Telefónica)"
     "[chapter: FIWARE Ops] Silvio Cretti (Create-Net)"
     "[chapter: FIWARE Cross-chapter level] Federico Facca (Martel Consulting)"

  *   Body of the messages shall bring the rationale behind the candidature.

  The list of FIWARE CACs within a FIWARE Architecture Chapter will be made by adding the list of FIWARE CACs per each GE/GEri within the Architecture Chapter as well as the list of FIWARE CACs at overall chapter level.   For each of the Mission Support Chapters and Cross-chapter level activities there will be only a list of FIWARE CACs.

  Candidatures for FIWARE CACs will be assessed by FIWARE CACs already identified as FIWARE Chapter/GEri Top Contributors (also listed in the shared google docs provided above).

  Don't miss the opportunity to apply as FIWARE CACs and convince others who also deserve to be recognized to also send their applications !!

  Best regards,



-- Juanjo Hierro



______________________________________________________



Coordinator and Chief Architect, FIWARE platform

IoT Unit, Telefónica



email: juanjose.hierro at telefonica.com<mailto: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

________________________________

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-data/attachments/20160426/91348a53/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <https://lists.fiware.org/private/fiware-data/attachments/20160426/91348a53/attachment.txt>