De : fiware-wg-leaders-bounces at lists.fi-ware.org [mailto:fiware-wg-leaders-bounces at lists.fi-ware.org] De la part de Juanjo Hierro Envoyé : mercredi 17 juin 2015 09:45 À : fiware at lists.fi-ware.org Cc : fiware-chapter-leaders at lists.fi-ware.org; fiware-chapter-architects at lists.fi-ware.org; fiware-wg-leaders at lists.fi-ware.org Objet : [Fiware-wg-leaders] Notes on the transition to a FIWARE Open Source Community Dear FIWARE partners, You are perfectly aware about our plans to transition FIWARE into an Open Source (OS) community. This is a necessary step towards building the ecosystem we aimed at creating when the FIWARE PPP initiative was launched. Creation of the FIWARE OS community will imply the definition of a new, open and transparent governance model, together with the tools that will help a fluent communication and support between members of the community. Our goal is to have the community running before August! This message is intended to give you an overview of the Governance Model we propose to put in place as well as some new tools that will be deployed. A detailed (and more formal) document describing the FIWARE OS Community Governance Model will be distributed in the coming days to gather feedback. We expect to produce the final version by beginning of July. This document will become the bylaws of the FIWARE Open Source community. I take this opportunity to give thanks to all members of the working group within FI-Core who have worked hard in the last months to produce the FIWARE OS Community Governance Model. This, as explained, is just an overview. Don't hesitate to spread the word to interested parties! I hope you will share our excitement about the process of profound transformation we are engaged with. We look for your constructive feedback and participation in the process !! 1. Principles The FIWARE OS Community Governance Model has been designed with the following principles in mind: * Openness: it should be open to those who have something to contribute (following well established procedures) * Based on meritocracy: active contributors should be recognized and only active contributors to technology would be able to govern decisions on the technology * Transparency: there should be well-defined, documented and publicly available procedures * Market oriented approach: those organizations committed to invest significant resources in supporting FIWARE adoption in the market will have a prominent role in the community Besides the above principles, we believe that we didn’t need to reinvent the wheel: we should leverage on the governance model and best practices of other successful OS communities. In this respect and after analysis of several OS communities, we found that the Governance Model adopted in OpenStack<http://www.openstack.org/legal/bylaws-of-the-openstack-foundation/> was a good basis. 2. FIWARE technical activities FIWARE technical activities within the FIWARE OS community will be organized in Technical Chapters: * Architecture Chapters, where FIWARE Generic Enabler (GE) specifications and open source reference implementations of FIWARE GEs are developed * Mission-Support Chapters, dealing with technical activities not specifically related to the specification and open source reference implementation of FIWARE GEs (e.g., the FIWARE Ops chapter or the FIWARE Lab chapters, coordinating the development of the FIWARE Ops suite of tools and the operation of the FIWARE Lab, respectively, are examples of FIWARE Mission Support Chapters) Individuals contributing technically to a chapter (e.g., contributors to FIWARE GEs developed under a FIWARE Architecture Chapter, or engineers operating a FIWARE Lab node) will be referred as FIWARE Chapter Active Contributors. Technical contribution to FIWARE GEs will not be limited to source code. Individuals can contribute to testing activities, specifications, the creation of better documentation/training materials, or by playing a prominent role answering to questions made by application developers etc in order to be recognized as FIWARE Chapter Active Contributor. Existing FIWARE Active Contributors will be those entitled to recognize new active contributors. The list of FIWARE Chapter Active contributors will be publicly available and keep updated. The intent is to stimulate and reward any kind of valuable contribution! FIWARE technical activities will be coordinated by a FIWARE Technical Committee (TC). There will be two seats per each of the FIWARE Technical Chapters plus a number of individual seats (1/3 of the total). Seats of the FIWARE TC will be elected by FIWARE Chapter Active Contributors: they will elect the representatives of their chapters in the TC as well as the individual seats of the TC for which any FIWARE Chapter Active Contributor may present a candidature. The FIWARE OS community will be open to contributions of new GEs as well as to the contribution to existing GEs. As an example, some enablers developed by Use Case projects under the FIWARE PPP, also referred as FI-PPP, may be eligible as FIWARE GEs. However, this option should not be limited to technology developed under the FIWARE PPP programme. Any organization will be able to submit a technology and apply for its adoption as FIWARE GE !! Some proposed technologies will become FIWARE GEs following an incubation process, which is a common practice in many OSS communities. Incubated GEs will become visible on the FIWARE Catalogue, although marked as such to be distinguished from FIWARE GEs. Organizations contributing incubated GEs would also need to provide support through the defined channels (e.g., the FIWARE Q&A platform or StackOverflow). A number of parameters will be monitored to support the decision about transitioning a GE from "incubated GE" to "FIWARE GE", e.g., level of adoption by the wide community of developers, compliance with best-practices agreed regarding development of FIWARE GEs, performance when solving tickets/questions formulated on the GE, etc. Some other proposed technologies will run a fast-track adoption process, which essentially applies where there is enough confidence on the maturity of the technology, the long-term support by the backing organization, as well as a clear vision on how the technology fits with the rest of FIWARE GEs, covering an existing gap. The FIWARE TC will own decisions linked to the process of incubation or fast-track adoption of GEs, as well as the deprecation of existing FIWARE GEs. It will also follow-up technical activities and solve technical conflicts that may be found. Note, however, that it will not decide on the individual roadmap of FIWARE or incubated GEs. Active contributors of a given FIWARE/incubated GE are the owners of such decisions. This is essential to stimulate contributions to FIWARE: no organization would like to propose their product for adoption as FIWARE GE if that means that technical decisions gets transferred to an external technical committee. It is a basic principle also adopted in well-established communities like OpenStack. The principles of openness, transparency and meritocracy will be preserved by all means !! 4. FIWARE ecosystem-support activities Technical activities are not the only kind of activities that need to be run and are key in building the road to success. There will be also several non-technical activities to be carried out within the FIWARE OS community which are fundamental in building the target ecosystem. As an example, we have the activities associated to already established FIWARE programmes: the FIWARE Accelerator programme, the FIWARE iHubs programme or the FIWARE Mundus programme. Still in an early stage, we may also refer to the FIWARE Academy programme. In addition, we have the activities linked to marketing and dissemination supported by the FIWARE Press Office. There are also activities dealing with legal matters. These kind of activities will be coordinated through non-technical Ecosystem Support Committees, a separate one per programme (FIWARE Accelerator, FIWARE iHubs, FIWARE Academy, FIWARE mundus, etc), an additional one linked to marketing activities supported by the Press Office. Activities in the Ecosystem Support Committees would be overseen by a Management Board of Directors. In order to be efficient in the daily operations, several officer positions could be defined such an Executive Officer, Operation Officer, Marketing Officer or Public-Affairs Officer. The scope of the activities in all these Committees would be global. Our aspiration is that FIWARE Accelerator initiatives or FIWARE iHub initiatives are not run only in Europe but in other regions who will share our same vision and ambition. Think global, act local will be the motto !! 5. FIWARE Membership There will be three categories of members: * Core Members, which are organizations that agree to invest a significant amount of resources in FIWARE activities (threshold still under discussion). * Regular Members, which are organizations also investing resources in FIWARE activities but at a lower level compared to FIWARE Core Members. * Individual Members, who are individuals contributing to activities within the FIWARE community on their own or as part of their paid employment One of the benefits of FIWARE Core Members is that they will have a seat assigned in the FIWARE Board of Directors. Their investment do not need to be on technical matters. There might be organizations that are focused on accelerator activities or training activities which may be Core members as far as their investment is actually significant (over the defined threshold). Regular Members, will be able to elect the rest of the seats. Individual Members can be candidates to those seats in the FIWARE Board of Directors that are subject to election. We are still deciding on the number of seats that will be in the FIWARE Board of Directors and the balance between seats assigned to FIWARE Core Members and seats elected by FIWARE Regular Members. All FIWARE Members will have to adhere to a FIWARE code of conduct. This means they will commit to advancing FIWARE in a constructive way, staying active in the community, and performing their duties with integrity, always knowing when to wear the FIWARE hat. This means being considerate, collaborative and respectful, so when you disagree, you consult others and when you are unsure, you ask for help using the defined channels. 6. Domain Technical Committees FIWARE GEs are general-purpose, therefore applicable in many domains/sectors. FIWARE GEs, combined with Domain-specific Enablers (SEs), can build the notion of platform for a given application domain. A patient record management system is an example of a Domain-specific Enabler (eHealth). We envision the creation of Domain Technical Committees tackling the definition and implementation of Domain-specific Enablers (SEs). Also the definition of standard data models to be used in those domains. An example could be a Domain Technical Committee for Smart Cities or Smart Agrifood. Domain Technical Committees would be organized similarly to the FIWARE Technical Committee. We expect that these Domain Technical Committees will be born at the light of initiatives engaging domain stakeholders and seeking for the adoption of FIWARE. 7. FIWARE Foundation It is foreseen and desirable that a legal entity is created to provide support to some of the activities of the FIWARE OS community. It is expected that this legal entity, typically referred as "FIWARE Foundation", will be created by end of 2015. The FIWARE Foundation will typically provide staff that gives support to activities of the FIWARE OS community. Some of the Officers positions indeed may become employees of the FIWARE Foundation. However, we have decided that the launch of the FIWARE OS community will not be delayed until the FIWARE Foundation is created. Existence of a Foundation is not indispensable to run activities of the FIWARE OS community under well-defined, open and transparent governance bodies and procedures which can start earlier. 8. Community support tools New tools will be put in place to support the activity of the community. We will also try to enhance the existing ones. Among them, I take the opportunity to announce that we will implement a Q&A platform based on Askbot. This Q&A platform will help to improve the exchange of knowlege not only regarding technical matters (how to use FIWARE GEs, questions on usage of the FIWARE Lab, etc) but also non-technical questions. Contribution to all parties in answering questions will be allowed and rewarded, following common best practices. This Q&A platform will complement the activities we are already carrying out in StackOverflow. Best regards, -- Juanjo Hierro ______________________________________________________ Coordinator and Chief Architect, FIWARE platform 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 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-sust-found/attachments/20150617/8133f9be/attachment.html> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: <https://lists.fiware.org/private/fiware-sust-found/attachments/20150617/8133f9be/attachment.txt>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy