Dear Juanjo and All, Please find below my comment concerning the first point you mentioned in your mail. Currently the I2ND chapter includes a single active GE/GEri (Middleware/Kiara), while there are additional two which should be managed as incubated GE/GEris (Netfloc, Ofnic). The level of participation to the chapter has therefore decreased since last year. Personally (and as also Philipp said in his mail, this is a biased comment) I believe that there could be space for proposing new I2ND GEs by future contributors of the FIWARE community, as the networking (and even device) side might still provide helpful functionality to FIWARE. For what concerns active participation in TSC meetings, besides a few times where it clashed with company’s closures on Monday (we cannot modify them, they apply to whole company), I always attended the calls as Chapter leader although this should no longer be my role since last year; I volunteered anyway to ensure the proper representation of the chapter in the committee, with active involvement in case this was necessary (e.g. pushing among chapter members the ‘filling of application’ to become CACs). On the other hand, there aren’t active GE/GEris owned by TI in the chapter, so I expect that for the election of future TSC members I couldn’t personally be taken in account as possible candidate. BR Pier 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<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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20160610/3970c792/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20160610/3970c792/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy