A brief overview of OpenAirInterfaceTM corporate and project governance within the Alliance.
- OpenAirInterfaceTM Corporate Governance Overview
- Corporate Governance
- Technical Governance
- Marketing Governance
- OAI Org Chart
OpenAirInterfaceTM Software Alliance (OSA) is a French non-profit organization (“Fonds De Dotation”). It is governed by a set of bylaws in terms of its corporate actions. The board of directors are appointed by the strategic members and also one seat of board is nominated by the associated members.
The board sets the corporate policy which is executed by the officers. The board also sets the direction of 5G strategic areas and also approves the projects created within the strategic areas. The projects within the strategic areas can be proposed by any member of the Alliance, however the project has to be approved by the board.
OSA is run and managed like any other legal corporation. Here are the different roles in the organization. See Bylaws for the membership rules and detailed member description. There are three types of membership levels in the Alliance with varied responsibilities.
- Strategic Member: A corporation that donates significant amount of funds and sets the strategic direction of the Alliance. Each of the strategic members have one seat in OSA board of members
- Associated Member: A corporation that donates funds to the Alliance and participates in projects within the Alliance. Non-profit organizations currently can join the Alliance for free subject to the participation in the evolution of the OAI software.
- Ordinary (Individual) Members: These are independent individual members of the Alliance which form the major part of the community and actively develop and manage the OSA software.
Here are the different description of roles within the Alliance.
He/She is the representative of the strategic member organization or an elected representative from the associated members.
Currently the Alliance has three executive officers which are also members of the board:
- President: The President is the representative of the Board of Directors and is elected by the board among the members of the college of founders. He/she is elected for a renewable period of three years. The President alone represents the Alliance and acts in its name in accordance with the decisions taken by the Board of Directors.
- General Secretary: The general secretary is elected by the Board of Directors among its members for a duration of three years. He is in charge of aiding the President in performing his/her duties. The secretary is in charge of writing the minutes of the meetings of the Board of Directors, administrative declarations as well as all writings concerning the Alliance, with the exception of those concerning its finances. His/her purpose is to report on the conditions surrounding the preparation and organization of the Board’s work and submit an annual activity report to the local prefecture along with the annual accounts and auditor’s report.
- Treasurer: The treasurer is elected by the Board of Directors among its members for a duration of three years. He is in charge of aiding the President in performing his/her duties. The treasurer oversees revenue collection and payments on behalf of the Board of Directors. He regularly maintains under his control, or causes to be maintained, a record of all disbursements and renders an account to the Board of Directors which ratifies his account.
The OAI is structured technically in terms of projects which relate to the strategic areas of the Alliance. The outcome of these projects ultimately results in code contribution towards OpenAirInterfaceTM (OAI) repositories (openairinterface5g and openairCN). The board approves the 5G strategic areas within the OAI software. All the projects are structured technically into one of these areas.
TECHNICAL COMMITTEE (TC)
Technical committee(TC) comprises of strategic area leaders which are individuals working for alliance member organizations. Technical committee provides technical leadership to OpenAirInterface Software Alliance. Responsibilities include developing roadmaps for different strategic areas, align project goals with that of alliance, enforce code quality, testing, openness and transparency. TC periodically reports to the board on the status of different projects/strategic areas. Technical committee is nominated by the board and consists of following roles:
Technical Committee Chairman: He/She chairs the technical committee
Technical Manager: The main role of technical manager is to work with the technical committee and come up with concrete guidelines for coding, testing and quality of the projects. The technical manager also acts as an informal mentor for the projects to ensure their development gets merged periodically with the master branch.
Technical Committee Members: Technical committee members are typically members of the alliance and are also responsible in leading strategic areas.
The projects can be created by any member of the Alliance, but is subjected to the approval from the board. Each project has the following roles:
Project Management Committee (PMC) Chair: He/She is responsible for ensuring day-to-day working of the project and reports to either strategic area owner or subsystem owner depending on the location of the project within the Alliance organizational structure. PMC Chair is effectively the representative of the project management committee. PMC Chair has to be approved by the board.
Project Management Committee (PMC): It is a group of individuals responsible for setting project policies and managing the community related to the project. They also have to ensure that the outcome of the project can be merged even though partially to the main code and legal requirements for license, etc are appropriately met to mitigate litigation. One of the main roles of PMC is to also facilitate collaboration and peer review related to technical discussions. PMC members have to be approved by the board.
Developer/Contributor: A developer is a user who contributes to a project in the form of code or documentation. They take extra steps to participate in a project, are active on the developer mailing list, participate in discussions, provide patches, documentation, suggestions, and criticism. Each developer has to sign Contributor License Agreement (CLA) to contribute code to the OAI repository.
Committer: A committer is a developer that was given write access to the code repository and has a signed Contributor license agreement (CLA) on file. Not needing to depend on other people for the patches, they are actually making short-term decisions for the project. The PMC can (even tacitly) agree and approve it into permanency, or they can reject it.
MARKETING COMMITTEE (MC)
Marketing committee comprises of employees of strategic/associate members and are responsible for outbound marketing of the alliance for example, participating in trade shows, exhibitions, press releases, etc
Marketing Committee Chairman: He/She chairs the marketing committee
Marketing Committee Members: Marketing committee members are members of the alliance nominated by the board.
Our high-level OAI org chart best shows the separation between organizational governance (the board & members) and technical governance (PMCs and committers).