Participate/Engage in the O-RAN Software Community

Have you signed up for the mailing list, completed your Contributor License agreement and are ready to contribute to the O-RAN Software community?

Get started with project documentation and pages in the "Software" section.
Latest releases are available to download under "Releases"
Looking to dive into a project, start with the current open issues available on Jira.o-ran-sc.org

Below are a list of project high priority needs.(to be updated by PTLs)

Project Area	Need(s)
Non-RealTime RIC	If you want to get involved, check out our wiki pages, have a look at our code and documentation, then join our weekly meeting.
Integration and Testing	Open for Project Technical Lead to drive a key area for the community. The integration and test effort will focus on testing the requirements documented in each release, including end to end test and use case testing.
near-RT RIC project	If you want to contribute or get involved, please contact the PTL (project technical lead), participate in the fortnightly project meetings, or contact one of the sub-component owners/committers (see column committers in link). You can use JIRA to get an idea what are items that are worth working on. There are lots of links in Jira usage conventions, but for current work we have the links in §7.6 in Jira usage conventions. §7.5 contains the list of epics that are still open. For example, in O1 + vespamgr, in the pseudo Jira components ric-dep, ric-test, ricp-integration (related to continuous integration and testing) we have some level of open items without anybody readily picking them up. Documentation and step-by-step instructions could also be improved. In E2+E2mgr, sdl/DBaaS, xapp-frame-py and xapp-frame-go, A1 we have people working on these. But I think additional man-power is also helpful in these areas as standards evolved and we need to keep up with them. We don’t have a tracing solution as opentracing and successors of it are still waiting for someone to analyze them for their performance overhead. The RMR (RIC message routing) library is also lacking an expert to work on it. An analysis of its performance and robustness (all failure cases) is needed. We also have an issue in CI in that all code coverage reports currently fail. We know that the underlying Jenkins job definitions need to be investigated and updated (see also IT-22326). The deployment scripts used to deploy the near-RT RIC (in repo ric-dep and it/dep) also became quite dated and deserve some redesign and or improvements. E2Sim could also require some cleanup.
RICAPP	Looking for contributions on new xApp ideas (as well as improvements on existing ones). The RICAPP project already has contributions from companies as well as academia and are welcoming more contributors. Please reach out to the PTL for initial guidance on how your contribution idea fits with the project. Specific needs: Looking for a maintainer (or two) for the demo HelloWorld C++ xApp.