Skip to content

openairinterface5G
openairinterface5G

project roles

Last edited by Raphael Defosseux
Page history
OAI Software Alliance Project Roles

Table of Contents

  1. Technical Committee
  2. Contributor / Developer
  3. Integrator
  4. Project Lead

The Open Air Interface project includes individuals working in a variety of roles. OSA is responsible for product management and the development process; however, the project considers contributions from any source.
This page describes the kinds of roles that interested parties can take on.

1. Technical Committee

The Technical Committee (TC) is composed of representatives of OSA Members who are technical experts and have in depth experience of the OAI code.
The TC is responsible for the following tasks:

  1. Review ticket upon creation to ensure Ticket Policy Guidelines are followed
  2. Add a new project card in the “In Progress” projects in OAI Weekly Developers Meeting to track progress of Issue opened in the Ticket
  3. In OAI Weekly Developers Meeting, track progress of all open issues and manage lifetime of branches
  4. In case of a Merge-Request(MR)/Pull-Request(PR), monitor CI outcome of the MR/PR
    • Coordinate with contributor/developer to resolve conflicts in case of failure
  5. In case of successful CI result of a MR/PR,
    • one or several TC members are tasked to perform a "human" code review to ensure that policies / guidelines are followed:
    • Accept MR/PR into the latest develop branch state.
    • Coordinate with contributor/developer in case of conflicts.
  6. Close tickets and delete branches upon task completion.
  7. Review all the policies to be in-line with state-of-the-art development tools

TC Members are using a private dedicated Slack channel as a communication tool.

If you represent an OSA Member and wish to participate in the Technical Committee, please contact Raphael Defosseux at raphael.defosseux@openairinterface.org

2. Contributor / Developer

"Contributors" are those making contributions to the OAI source code, including employees of OSA partners, as well as individual developers who are contributing to OAI on their own behalf.
There is no distinction between contributors who are employed by a partner and those who are not; all engineers use the same tools (git), follow the same code review process, and are subject to the same requirements on code style and so on.

"Developers" are another term used for "Contributors".

3. Integrator

"Integrators" are those bringing together the component sub-systems into one system (an aggregation of subsystems cooperating so that the system is able to deliver the overarching functionality) and ensuring that the subsystems function together as a system.

4. Project Lead