2021
Company | Functions/Components implemented by contribution | Running Platform/ Environment | Source code repos | Description | License | committers | Language | Target Contribution Date | Status |
ORAN Alliance WG 6 | AAL FEC | x86 Server | aal_fec/profile | Why WG6 is considering splitting its AAL FEC specification into two portions to be published together in the July 2021 train – a) a formal specification document published through the normal O-RAN FRAND process that covers stage 1 and stage 2 specifications, and b) a stage 3 API document that covers data structures and programming language level details specific to open source implementations such as DPDK that would be published in ORAN OSC repo under a BSD license and referenced from the formal AAL FEC specification. The purpose is to enable easier ingestion of the ORAN FEC gaps identified by the ORAN community in upstream communities such as DPDK. What To facilitate this split, WG6 co-chairs would like to request an OSC repo titled aal_fec/profile to be created for the above purpose. The purpose of this repository would be to store stage 3 specification documents and in the future, header files as well as test artifacts for the AAL FEC profile. Releases from this repository will be aligned with ORAN specification release trains as we intend to publish the stage 3 specification updates conjointly with the main spec. License BSD – we would prefer a BSD license to be compatible with the upstream community (DPDK) with which the spec is to be aligned. | Exception request: BSD | niall.power@intel.com (PTL) | C/C++ | ToC consideration (June/30/21) |
2020-2019
Company | Functions/Components implemented by contribution | Running Platform/ Environment | Source code repos | Target Contribution Date | Status | ||||
---|---|---|---|---|---|---|---|---|---|
repo name | Description | code license | committers | language | |||||
Lenovo | Abstraction Adaptation Layer | OpenStack Hypervisor | aal/lib | Apache2 | done | ||||
aal/logic | Apache2 | done | |||||||
aal/mgmt | Apache2 | done | |||||||
aal/virt | Apache2 | C/C++ | done | ||||||
China Mobile | Integrated eNB | x86 Server | |||||||
Inspur | Infrastructure monitoring | x86 Server | imp/metal | Host Configuration Management | Apache2 | gaosong.lc@inspur.com, liutao.lc01@inspur.com, qiaoxj@inspur.com | Python | requested 2019/06/11, LF Ticket #76725 | |
imp/metal-api | Host management interface | Apache2 | gaosong.lc@inspur.com, liutao.lc01@inspur.com, qiaoxj@inspur.com | Python | requested 2019/06/11, LF Ticket #76725 | ||||
imp/fm | Host Fault Monitoring, Detection and Recovery | Apache2 | gaosong.lc@inspur.com, liutao.lc01@inspur.com, qiaoxj@inspur.com | Python | requested 2019/06/11, LF Ticket #76725 | ||||
Intel | DU layer 1 | x86 Server | o-du/phy | O-RAN DU Layer 1 | Apache 2 | zhimin.yuan@intel.com, vitaliy.zakharchenko@intel.com, nicolas.chautru@intel.com, luis.farias@intel.com | C/C++ | requested 2019/06/11, LF Ticket #76725 | |
Radisys | DU layer 2 and layer 3 | x86 Server | o-du | O-RAN DU | Apache 2 | C | requested 2019/06/11, LF Ticket #76725 | ||
o-du/l2 | O-RAN DU Layer 2 | Apache 2 | balaji.shankaran@radisys.com, somshekar.ydlapur@radisys.com | C | requested 2019/06/11, LF Ticket #76725 |
Guidelines:
Seed code preparation:
################################################################################ # Copyright (c) [years] [company name] # # # # Licensed under the Apache License, Version 2.0 (the "License"); # # you may not use this file except in compliance with the License. # # You may obtain a copy of the License at # # # # http://www.apache.org/licenses/LICENSE-2.0 # # # # Unless required by applicable law or agreed to in writing, software # # distributed under the License is distributed on an "AS IS" BASIS, # # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # # See the License for the specific language governing permissions and # # limitations under the License. # ################################################################################
Repo creation:
IS / HAS | IS NOT / DOES NOT |
---|---|
|
|
Technology for the sake of technology won't cut it, neither will solutions in search of problems.
The TOC will always look more favorably on project proposals that address gaps in existing ORAN-SC functionality vs. replacing existing functionality with a new proposal. |
The TOC will always look more favorably on project proposals that address gaps in existing ORAN-SC functionality vs. replacing existing functionality with a new proposal. |
As you go through the proposal here are the things to keep in mind. Many of these are typical of the questions that you get asked over and over. A project proposal should answer six fundamental questions:
What is the problem?
Why can’t it be solved in existing projects?
How do you propose we solve it?
Thinking of or speaking of companies or individuals as “proposed contributors” to your project will almost always get you into trouble. It is probably best to consider it to be a binary; either they directly committed resources to work on the project to you first hand, or they did not. Comments such as, "Yes, that sounds like a good idea", "Yes, my company would like something like that", or even "Yes, I'd be very interested in your project!" are not the same as someone saying, "Yes, I can work on your project". |
Source: Credit to ONAP community for new Project Proposal page guidelines, which we have replicated.