You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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 AreaNeed(s)
Integration and TestingOpen 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.7 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) and in xapp-frame-cpp 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.



  • No labels