Dear Juanjo, Happy to serve the tc as co-chair. Ciao Stefano Il 11/Gen/2016 15:05, "Juanjo Hierro" <juanjose.hierro at telefonica.com> ha scritto: > Dear all, > > Based on results of the doodle poll, the first interim FIWARE TC > confcall will take place tomorrow Tuesday January 12 at 15:00 CET. > > We will use our usual powwownow bridge: > > - PIN: 050662 > - Local dial-in phone numbers at: > http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf > > > For your convenience, please find enclosed the first message which > provides sort of background info. Link to the pre-minutes can be found at: > > > https://docs.google.com/document/d/1NxE8WlQNl42-cCEyleNbH2SqaYny7nipseX9j5f_VvA/edit?usp=sharing > > > If there is any additional point you wish to add to the agenda, please > do so. In that case, please also provide some input in the corresponding > subsection within section "Addressed topics". > > Cheers, > > -- Juanjo > > ______________________________________________________ > > Coordinator and Chief Architect, FIWARE platform > CTO Industrial IoT, 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 > > > > -------- Forwarded Message -------- Subject: FIWARE Open Community > Kick-off Date: Fri, 8 Jan 2016 11:35:18 +0100 From: Juanjo Hierro > <juanjose.hierro at telefonica.com> <juanjose.hierro at telefonica.com> To: > fiware-technical-committee at lists.fiware.org > > Dear all, > > As you know, one of the major goals in 2016 has to do with an effective > transition from an open source initiative, as we have been working so far, > into a truly FIWARE Open Community whose governance is based on the > principles of: > > - *Openness*: able to engage those who have something to contribute > (following procedures) > - *Transparency*: well-defined, documented and publicly available > procedures > - *Based on meritocracy*: only active technology contributors would be > able to govern decisions on the technology > - *Market-oriented approach*: Those committed to transfer results to > the market gain a prominent role > - *Don’t reinvent the wheel*: follow models and best practices from > successful OSS communities (concretely, OpenStack) > > > As you know, a Governance Model was defined and it is currently > available on our website: > > https://www.fiware.org/fiware-governance/ > > > You can download an updated version of the slide deck summarizing major > concepts behind this new governance model using the following link: > > > https://forge.fiware.org/docman/view.php/7/5410/FIWARE+Sustainability+presentation+-+transition+to+OS+community.pptx > > > Now, it is the goal to kick-off the FIWARE Community and one of the > first steps will be to establish the Membership as well as the FIWARE > Technical Committee (TC). We will put in place the necessary actions to > move ahead during January. > > In the meantime, let's start working at least in the technical front, > following the defined process through an *interim* FIWARE TC. This > FIWARE TC will be formed by two representatives per Technical Chapter > (following the principles established in the FIWARE Community Governance > Model) as well as some individuals. For practical reasons, we will start > with the following structure: > > - FIWARE Architecture Chapters: it will be the current chapter leader > and architect (if one person assumes both roles, please nominate one > additional, I believe this is the case of Philipp) > - FIWARE Mission Support Chapters: > - FIWARE Ops: Silvio and Federico (Silvio: please confirm) > - FIWARE Lab: Stefano and Alfonso (Stefano: please confirm) > - FIWARE Community Support Tools: Davide and José Manuel Cantera > - interim FIWARE Technical Committee chair: Juanjo Hierro > > > You can check the current members of this interim FIWARE TC by means of > simply checking the members of this fiware-technical-committee mailing we > have created and used for this email (you will probably need to enter the > password that will be sent to you as member of the list): > > https://lists.fiware.org/admin/fiware-technical-committee/members > > > Please note that absolutely ALL seats of this interim FIWARE TC will > have to run through elections to be completed by mid February. There will > be more seats in the FIWARE Technical Committee according to the defined > Governance Model, mostly because of 1/3 of the seats have to be taken by > individuals who will nominate. Note also that once members of the FIWARE > Technical Committee are elected, they will run an election of the chairman > (until then, I will simply run this role as interim). > > Besides being able to deal with necessary interim decisions, one of the > goals of the interim FIWARE TC will be to migrate from the current somehow > "benevolent dictatorship" model we have now to a more "collegiate > decision-making" model run by members of the FIWARE TC. This will be > implemented "by example", meaning that Action Points identified during the > FIWARE Technical Committees will have to be taken care by members and > assignment of those action points will be distributed among members, > seeking for an equally distribution. Rules will be defined to assess the > performance of FIWARE TC members (i.e., establishing karma mechanisms) so > that those who fail in their duties (because it is found they don't > accumulate significant karma or negative karma) will loose their seat. > One of the first decisions of the FIWARE TC will be about deciding what > these rules could be. Similarly, there will be rules monitoring > attendance to the meetings, etc. Another decision to be taken by the > interim FIWARE TC will be that of designating two co-chairs, who will help > the chair in taking minutes, can replace the chair not only in taking > actions and can replace him in case of absence. With this measures and > other that the FIWARE TC may progressively define and implement, we expect > that this transition from "benevolent dictatorship" to "collegiate > decision-making" model will take place. > > The first meeting of the interim FIWARE TC will take place next week. > Since many of you just arrive on Monday, I have setup a doodle for deciding > on the best date/time. I believe all of us read remain connected along > the weekend (although this effectively means not really working so much). > Therefore, I will wait until Sunday 13:00 to announce the final > date/time. Please note that you will vote to decide the start time of the > meeting which is expected to last 2 hours. > > http://doodle.com/poll/gwtmrwbw3ndwq8qi > > > I will circulate pre-minutes of the meeting soon so that you can propose > (and elaborate on) items. Please wait until I send the link to the > pre-minutes to propose new items. So far, I have identified the following > points: > > - Scope of decisions (we have to establish what kind of decisions are > run in the TC as opposed to sprint planning and milestones/deliverable > management meetings which will remain separate on Monday afternoons) > - Rules for meetings and for the assignment of karma to FIWARE TC > members > - Election of co-chairs > - Steps to setup elections of FIWARE TC members > - FIWARE Open Source Licenses > - Status of QA activities > > > One of the first decisions to be taken is what is the preferred time and > day of the week for this meetings to take place. > > Cheers, > > -- Juanjo > > ______________________________________________________ > > Coordinator and Chief Architect, FIWARE platform > CTO Industrial IoT, 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20160114/a54d082b/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy