Mailing list and #ricp

We use with hashtag "#ricp" in the subject of emails. Note that you might also want to subscribe to "", but this is not to be used for near-RT RIC discussions and rather used for discussion in the TOC (technical oversight commitee). The mailing list is for general announcements.

Please make sure that you add somewhere in the subject of your email "#ricp". 

Example subject: "#ricp Please help!"

More examples:

O-RAN-SC members who are not interested in OAM email conversations can mute the hashtag "#ricp": 

Contact the committer

You can see the committer of a particular component from this wiki page. The information in the wiki page is based on the committer information in the INFO.yaml file in the root directory of the master branch of each Gerrit repo. You find them by adapting this link to point to the repo in question (replacing the repo name "ric-plt/submgr"):;a=blob;f=INFO.yaml , or try to find the correct repo by name from this link.


JIRA entries follow the scheme: . See also this auto-filter: Jira development items (better use links from item 4 in §7 in wiki page named "Jira usage conventions")


You can find the bulk of the RIC Platform repositories under the ric-plt folder from here:,25 (you might have to click on next or previous page to find the right entries)

New feature request

Persons outside of the near-RT RIC project, please post new feature/enhancement requests to the mailing list (see above). People working with the near-RT RIC project, please raise these issues in the project meeting or send a e-mail to the PTL. For "external requests" we will create a JIRA entry with label "external-feature-request" link after discussion.


Please report bugs in JIRA using this "JIRA create" link. Make sure to select issue type "bug". If possible, select one of the existing RIC components in the JIRA field "Component/s" to indicate which one is likely the one containing the bug. Do not select more than one component as the component field is used to manage ownership based on components. We use this filter to see all open RIC bugs. In addition, you may also want to write an e-mail to the committers of the suspected component or to the mailing list.

Security bugs

We currently expect all security bugs to be reported publicly as JIRA issue of type "Security Bug". Other then classified as type "Security Bug", they are managed in the JIRA tool the same way as other bugs.You can use this filter (requires login) to view all security bugs: (same filter without login: link)

  • No labels