A reminder to the extra line Nokia wanted in source files for near-RT RIC to add this sentence: "This source code is part of the near-RT RIC (Radio Intelligent Controller) platform project (RICP)." (see also Scope of the near-RT RIC platform and its components (summary)). This is to clearly define the scope of the project to near-RT RIC. This was discussed earlier and Jack was supposed to come back with solution to this.
Ask reviewing for documentation at https://docs.o-ran-sc.org/en/latest/, whether all Amber release repos docs are shown well on the documentation page. (ODUHIGH and ric-app-admin are finished, but the link has some delay, so not shown on the page so far. There also a couple of repos are still working on docs, almost finish.)
John KeeneyNon-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
Jack saw the initial draft of the framework for the O-RAN SC marketing plan and needs to review. Comments from participating companies is encouraged. We are entering the window of time to get approvals to get a quote. Those interested reach out to Jinri Huang and copy John Murray.
Status of Open Action Items (Old Business)
Action/Jinri Huang will create a framework for the O-RAN SC marketing plan.
Action/ TOC Docker hub prefix naming vote due. Suggestion was made to call the prefix o-ran-sc
Jack: Use oransc and oranscp. This makes it evident that there is a difference and when people investigate that difference they see that it is associated with licensing
Standing Agenda Items (Brief Status of Ongoing Activities)
we are in week 44. At this point we should be preparing to branch the code.
Yes, branching now vs. later. Now there will be significant changes made on both branches vs. later less items to change.
No prepare for branching. Not actually branching. We are fixing and freezing that has to be wrapped up by the end of next week so we have one week to address any issues in the package.
The teams have made good progress in turning the cells in the link above to green.
What areas should we focus on to close.
Producing the documentation and the minimum requirement for documentation are the release notes.
Licensing License Attribution Records. LF has a scanning process for code licenses. They will be scanning licenses that we are pulling from an upstream source are being generated by a tool. The community should take the time to review License Attribution Records.
What is the next milestone to hit by this Friday from the TOC?
Was hoping to have all the cells green by today but will wait until Friday . We need this done to branch the Amber code. We need to complete the branching by next weeks meeting. .
Report out from PTL: Stand-Up & Report Out on Blockers