Robert Schmidt
8107939f08
- all RAN code, CI code, configuration files, dockerfiles, in CSSL v1.0
- all deployment code (openshift, charts, ancillary files like shell
scripts), in MIT
- documentation in CC-BY-4.0
- exceptions might apply and are listed in NOTICE
- there is a new LICENSES folder with all licenses
- CONTRIBUTIONS.md has been updated accordingly
For automated changes based on OAI PL v1.1:
perl -i~ -0pe 's/\/\*.*Licensed to the OpenAirInterface.*openairinterface.org\n#?/\/*\n * SPDX-License-Identifier: LicenseRef-CSSL-1.0\n/s' **/*.{c,h,cpp}
perl -i~ -0pe 's/\/\*.*Licensed to the OpenAirInterface.*openairinterface.org\n#?/\/*\n * SPDX-License-Identifier: LicenseRef-CSSL-1.0\n/s' **/*.ts
perl -i~ -0pe 's/<!--.*Licensed to the OpenAirInterface.*openairinterface.org\n.*-->/<!-- SPDX-License-Identifier: LicenseRef-CSSL-1.0 -->/s' **/*.xml
The rest (cmake, files with missing license, cmake) manually.
1.7 KiB
1.7 KiB
The OpenAirInterface software can be obtained from our gitLab server. You will need a git client to get the sources. The repository is used for main developments.
Prerequisites
You need to install git using the following commands:
sudo apt-get update
sudo apt-get install git
Clone the Git repository (for OAI Users without login to gitlab server)
The openairinterface5g repository holds the source code for the RAN (4G and 5G).
All users, anonymous access
Clone the RAN repository:
git clone https://gitlab.eurecom.fr/oai/openairinterface5g.git
For contributors
Configure git with your name/email address, important if you are developer and want to contribute by pushing code. Please put your full name and the e-mail address you use in Gitlab.
git config --global user.name "Your Name"
git config --global user.email "Your email address"
More information can be found in the contributing page.
Which branch to checkout?
develop: contains recent commits that are tested on our CI test bench. The update frequency is about once a week. 5G is only in this branch. It is the recommended and default branch.master: contains a known stable version.
You can find the latest stable tag release here.
The tag naming conventions are:
- On
masterbranch: vx.y.z - On
developbranchyyyy.wxxyyyyis the calendar yearxxthe week number within the year
More information on work flow and policies can be found in this document.