Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
openairinterface5G
openairinterface5G
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Merge Requests 24
    • Merge Requests 24
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Commits
  • oai
  • openairinterface5Gopenairinterface5G
  • Wiki
    • Policy
  • project roles

project roles

Last edited by Remi Hardy Oct 07, 2020
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 the product management and the development process.
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.

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

Clone repository
  • 5g nr development and setup
  • ALUProject
  • AskQuestions
  • AutoBuild
  • CBMIMO1Integ
  • CardList
  • Cbmimo1Flash
  • Chorist3Nodes
  • ChoristMplsIPv6072008
  • Configure_simplestreams_for_a_private_cloud
  • CoreBasebandAndRF
  • CoreNetworking
  • DebugTools
  • DeployOpenStackHeat
  • DisablingInterrupts
View All Pages