Have a wiki link with all the release info in one place (in process)
Gather all items related to the Amber Release under Amber Release on this wiki.
Vote to accept the license scan and upstream licenses are approved for use. These have been reviewed with LF and are normal.
LF code scans, code licenses, and code clean up work status.
TSC will take a vote to approve upstream licenses that are compatible within our projects.
This will be repeated at every release.
Lusheng - LF sends us a spreadsheet that lists all the red and yellow items that have failed the scan.
binary issues have all been addressed.
non-binary have been scanned.
Attribution tab these are the files hosted in our repo and they are not Apache 2 license. Common practice is to copy from another open project into our project code. As long as the foreign code license is not copy left. As long as it is open source friendly it is legally safe to practice. Foreign code files should contain their own license claims and should be highlighted as non open source compatible.
We follow the LF practice about foreign code from the License Attribution Records page. You will find the best practices for license attribution friendliness.
Vote to approve Request to Approve referencing and using the additional licenses for the open source software community from section of License Attribution Records.
Not appropriate on gerrit. We will have to display videos on this wiki.
Under the Amber release tab we will have a table with all the projects and videos. That will be the release point to go to on the wiki for the Amber release.
Action / Farheen Cefalu work with Jack to update the Amber Release page.
The Release PR will go out Dec 3. The final day of the release is November 30. The guidance is to do it on a Tuesday. The first Tuesday in December the press release will go out. The vote today is the official designation and preparation of the Amber release. Clean up these last remaining items to support the release by the end of November. Once we branch we will move into the maintenance cycle to start fixing defects and moving to the maintenance release for Amber. We will go through a similar process for each release.
Approve the Amber Release and go ahead and branch all the code and related information supporting the release thereby closing the Amber release so that we can close all Amber activities by November 30 and do a press release on December 3rd for the O-RAN-SC Amber Release. Project Readiness for Amber Release.
The key is PR. We had an EC meeting on Monday. We discussed the PR statement. Jack and Jinri are working through the input from different entities. O-RAN Alliance gave guidance along with LF. Statement is not a lot of content. We open it for quotes from companies related to the release. Individual companies who want to add quotes to the statement reach out to John Murray or Jinri Huang. There is a deadline for to get your quotes in. We don't have a formal PR system but we are working through getting that sorted out through the assistance of O-RAN Alliance and LF.
Status of Open Action Items (Old Business)
Action/Jinri Huang will create a framework for the O-RAN SC marketing plan.
Tracy - It's moving forward and we will record the readout on December 5th. There are updated slides on O-RAN SC and the ONAP wiki.
Martin - For NJ there are new code artifacts based on the current repo available. First use case of O-RAN Alliance OAM is still available. I am confident that we will have a nice plugfest in New Jersey.
There is a simplified optimization. It will be an interesting event in both the POC and plugfest.
Action/ Jinri Huang will add the F2F meeting minutes to the events page.
Action/ felhasználó-59b16 Alignment and adjust OAI code to be compliant with O-RAN Alliance. This is an architectural review of fitting the code.
Action/ John Murray closing the remaining the TOC slots.
Action/ felhasználó-d3360 update the TOC with the status of branching Amber on
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)
Epics are in the spreadsheet. Most people have contributed to the epics. We have been going through the epics in the RSAC.
Request to have all the PTLs to be review the spreadsheet of epics.
Matti - we will share slides with Rittwik for xApps.
Rittwik - In the spreadsheet we have classified them into higher level topic names. These classifications are really our epics. Please review the spreadsheet. Next week we can briefly go over. The next meeting we will shift from PTLs to planning and requirements software. Development meetings will start in February.
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
Planning for Next Meeting
Next week Thursday is a holiday. There may be lighter attendance next Wednesday. We will recap Amber and start the discussion around Bronze.
Open Discussion
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)
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