Hi, Do we really want to send the (self-)nominations to the entire fiware lists as suggested? I would prefer to have this sent only to the TSC, where it is gathered and put on a Web page for others to see when they want to (and the elections are up). We need to do this anyway (who?). Everyone getting many individual emails over a couple of weeks does not help in getting an overview of who is nominated for what post and thus is more confusing than helpful to everyone, I would think. Best, Philipp Am 27.06.2016 um 08:28 schrieb Juanjo Hierro: > Dear all, > > This mail is a call for candidatures to the FIWARE Technical Steering > Committee (TSC). > > The TSC will be formed by: > > * One representative of FIWARE Platinum Member (currently expected to > be Atos, Engineering, Orange and Telefónica) > * Two representatives of each FIWARE Technical Chapter, who are the > main and deputy Chapter Leaders. Representatives of each FIWARE > Technical Chapter are elected by FIWARE Chapter Active Contributors > (CACs) in the corresponding chapter. > * Individual members who have sent their candidatures and have been > elected by FIWARE Chapter Active Contributors. The number of > Individual Members to be elected through this mean can reach up to > 1/3 of the sum of representatives of FIWARE Platinum Members plus > representatives of FIWARE Technical Chapters. > > FIWARE Technical Chapters are: > > * Architecture Chapters: > o Cloud Hosting (Cloud) > o Data/Media and Context Management (Data) > o IoT Services Enablement (IoT) > o Applications/Services and Data Delivery (Apps) > o Advanced Web User Interface (Web UI) > o Security > o Advanced Middleware, Interface to Networks and Devices-Robots > (I2ND) > o Cross-chapter > * Other Technical Chapters: > o FIWARE Lab > o FIWARE Community Support Tools (Catalogue, Developers' Guides, > Academy, Agile, etc) > > > We are closing the census of FIWARE Chapter Active Contributors (CACs) > this week which was the first step necessary for running elections of > the FIWARE TSC seats. > > The list of FIWARE CACs will be used to generate a web page where > contributions of all FIWARE CACs will be recognized. Besides that, all > those FIWARE CACs who will adhere to the FIWARE Code of Conduct will be > entitled to vote in the elections of FIWARE TSC members. You will > soon receive information about how to adhere to the FIWARE Code of Conduct: > > https://www.fiware.org/fiware-governance/#chapter5 > > > > You can nominate yourself to be a representative of a given FIWARE > Technical Chapter and/or as Individual Member. You have to send your > candidature to fiware at lists.fiware.org copying the FIWARE TSC > (fiware-technical-committee at lists.fiware.org). You can elaborate on > rationale, intentions, etc in your candidature, therefore giving info > that can help voters to make their mind and support your candidature. > Candidates have to also adhere to the FIWARE Code of Conduct. > > Deadline for receiving candidatures will be July 8th (2 weeks from now). > > Soon we will also send info about how to cast votes and details about > the voting procedure. > > Looking for your active participation in this process. > > 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 > -- ------------------------------------------------------------------------- Deutsches Forschungszentrum für Künstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Geschäftsführung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) VAT/USt-Id.Nr.: DE 148 646 973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: philipp_slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20160627/dad05984/attachment.vcf>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy