dear alex, indeed, yours are exactly the questions somehow i posed in my email ... absolutely nothing against the colleagues in the cross-chapter who all are doing a great job! ciao, stefano 2016-07-05 18:29 GMT+02:00 Alex Glikson <GLIKSON at il.ibm.com>: > In the *Chapter* Active Contributors census [1], we have 15 people listed > under 'cross-chapter'. IMO, it would be good to clarify what exactly do we > mean, and how does it fit the governance model. > Do we envision having a "special" chapter for activities not included in > any of the "named" chapters, kind of "Other"? > Is it OK to have chapters without explicit leadership? > How would we manage such activities in terms of agile dynamics and > everything else that is currently managed at the chapter level? > Etc > > Regards, > Alex > > > https://docs.google.com/spreadsheets/d/1vqx7mwcFFb4Z0pUAC5ghyTVSgEQdpraOXvCwlRawWPk/edit#gid=0 > > > > From: stefano de panfilis <stefano.depanfilis at eng.it> > To: Juanjo Hierro <juanjose.hierro at telefonica.com> > Cc: Alex Glikson/Haifa/IBM at IBMIL, FIWARE < > fiware-technical-committee at lists.fiware.org> > Date: 05/07/2016 07:14 PM > Subject: Re: [Fiware-technical-committee] Fw: [Fiware] Call for > candidatures to FIWARE Technical SteeringCommittee (TSC) > ------------------------------ > > > > dear juanjo, > > i do perfectly understand the vision you explained and i migth even agree > with it, but we, i mean the tsc, never defined the cross-chapter chapter, > nor even we ever announced to the wider public that such chapter exists. > > to avoid any miss interpretation, in particular from the outside, i'd > avoid. there are many pieces of work that eventually need to be introduced > there including qa and so on, which are, per se, even much better defined. > > i also understand that there are many colleagues in that limbo state, but > better defined eventually their tasks and position in the organisation > rather then have a pout-pourrie chapter. above all: who is the chapter > leader and who is the architect? for sure in that chapter the notion of > architect is somehow meaningless (anyway we avoid partially this problem as > in the gm we chapter and leader and deputy as recognised roles). > > ciao, > stefano > > 2016-07-04 19:39 GMT+02:00 Juanjo Hierro <*juanjose.hierro at telefonica.com* > <juanjose.hierro at telefonica.com>>: > > The vision was that the Cross-Chapter was kind of "another" chapter. > And, as such, it would have two representatives in the TSC. > > The individual members elected are not represented any chapter in > particular and they would be running for 1/3 of the TSC seats representing > chapters > > If we somehow assume that people playing a relevant role in > cross-chapter activities will most probably be elected as individual > members by all FIWARE CACs ... then I guess we don't need to have this > "Cross-Chapter" placeholder like kind of chapter level. > > I don't have a strong opinion and I can live either way. > > Cheers, > > -- Juanjo > > > On 04/07/16 15:13, Alex Glikson wrote: > Is "cross-chapter" the same as "individual" members? If not, do we really > need both? > > Regards, > Alex > > > ----- Forwarded by Alex Glikson/Haifa/IBM on 04/07/2016 04:11 PM ----- > > From: Juanjo Hierro *<juanjose.hierro at telefonica.com>* > <juanjose.hierro at telefonica.com> > To: *"fiware at lists.fiware.org"* <fiware at lists.fiware.org> > *<fiware at lists.fiware.org>* <fiware at lists.fiware.org> > Cc: *"fiware-technical-committee at lists.fiware.org"* > <fiware-technical-committee at lists.fiware.org> > *<fiware-technical-committee at lists.fiware.org>* > <fiware-technical-committee at lists.fiware.org> > Date: 27/06/2016 09:29 AM > Subject: [Fiware] Call for candidatures to FIWARE Technical > Steering Committee (TSC) > Sent by: *fiware-bounces at lists.fiware.org* > <fiware-bounces at lists.fiware.org> > ------------------------------ > > > > 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: > - Cloud Hosting (Cloud) > - Data/Media and Context Management (Data) > - IoT Services Enablement (IoT) > - Applications/Services and Data Delivery (Apps) > - Advanced Web User Interface (Web UI) > - Security > - Advanced Middleware, Interface to Networks and Devices-Robots > (I2ND) > - Cross-chapter > - Other Technical Chapters: > - FIWARE Lab > - 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* > <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>*fiware at lists.fiware.org* > <fiware at lists.fiware.org>copying the FIWARE TSC ( > <fiware-technical-committee at lists.fiware.org> > *fiware-technical-committee at lists.fiware.org* > <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* <juanjose.hierro at telefonica.com> > twitter: @JuanjoHierro > > You can follow FIWARE at: > website: *http://www.fiware.org* <http://www.fiware.org/> > twitter: @FIWARE > facebook: *http://www.facebook.com/pages/FI-WARE/251366491587242* > <http://www.facebook.com/pages/FI-WARE/251366491587242> > linkedIn: *http://www.linkedin.com/groups/FIWARE-4239932* > <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 mailing list > *Fiware at lists.fiware.org* <Fiware at lists.fiware.org> > *https://lists.fiware.org/listinfo/fiware* > <https://lists.fiware.org/listinfo/fiware> > > > > _______________________________________________ > Fiware-technical-committee mailing list > *Fiware-technical-committee at lists.fiware.org* > <Fiware-technical-committee at lists.fiware.org> > *https://lists.fiware.org/listinfo/fiware-technical-committee* > <https://lists.fiware.org/listinfo/fiware-technical-committee> > > > > ------------------------------ > > 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* > <Fiware-technical-committee at lists.fiware.org> > *https://lists.fiware.org/listinfo/fiware-technical-committee* > <https://lists.fiware.org/listinfo/fiware-technical-committee> > > > > > -- > Stefano De Panfilis > Chief Innovation Officer > Engineering Ingegneria Informatica S.p.A. > via Riccardo Morandi 32 > 00148 Roma > Italy > > tel (direct): +39-06-8759-4253 > tel (secr.): +39-068307-4513 > fax: +39-068307-4200 > cell: +39-335-7542-567 > skype: depa01 > twitter: @depa01 > > > > -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-06-8759-4253 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 skype: depa01 twitter: @depa01 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20160705/596ab35d/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy