Tracy - Plugfest in Beijing and a complimentary meeting in Europe. There is a readout December 5th. I am a member of Paul Smith's team. The EC put on their timeline some blog or press release for the blog and the plugfest the week of December 15.
Martin - Setting up infrastructure and will document our findings. The preparations of such an event makes us exercise.
POCs and plugfests are ongoing. We will be able to do a lot more with the bronze release.
When will the readout be ready?
It's been a challenge. Thursday 9:30 ET USA. We will put the recording on the O-SC wiki as well as the O-RAN wiki.
The North American plugfest should be on everyone's calendar.
Tracy thanked the vendors for their support.
What is relationship between the POC and the Plugfest?
POC in NA and Europe POC is the software management plane. In Beijing it is more the hardware side. They are complimentary.
We will collect all of the screenshots and videos and you and Paul can craft the message.
Action/ Jinri Huang will add the F2F meeting minutes to the events page.
Action/ user-59b16 Alignment and adjust OAI code to be compliant with O-RAN Alliance. This is an architectural review of fitting the code.
We are now in the maintenance release. We are collecting user feedback and entering Jira tickets. Typically in the maintenance window we don't do new development work. We typically try to address the technical debt. This is an opportunity to refine your code.
Project Bronze Release
Epics spreadsheet is on the wiki. Epics have been outlined into high level topics. They are into termination, platform hardening, database related, xApp chaining. Each PTL has to go through the list and put it in jira.
Action/ PTLs bring your objectives and interest to the Bronze release calls and get involved. We need an integrated system so talk to your developers communities, friends, and participants from your companies to get involved to be successful.
Action/Jinri Huang will create a framework for the O-RAN SC marketing plan.
Rittwik: AT&T provided the input. He was looking for other operators.
Jack - We have a draft we are working through the press release on Tuesday. We got feedback from EC, LF and a few participants offered some quotes for the press release. We moved this to the O-RAN Alliance to review and final approval. They will release the code on Tuesday. Major item remaining is that the marketing team would like us to improve the feature descriptions that are coming out in this release. They feel it is too technical. Outsiders won't understand as much. We are rounding out the descriptions that will have broader appeal. We want to get the facts in there to communicate the details.
We are uploading the epics into the wiki. By next Wednesday meeting I will go through the epics.
Tracy - POC plugfest North America is next Thursday. We are on track. Most is working in the lab. Video of overall demo and each equipment vendor will be demonstrating their use cases. Not all will be demonstrating. The video will be stored and available on the wiki.
Action/ Jinri Huang will add the F2F meeting minutes to the events page.
Action/ user-59b16 Alignment and adjust OAI code to be compliant with O-RAN Alliance. This is an architectural review of fitting the code.
Rittwik - No progress yet. Chilin is working on slides to get the word out of the Amber release.
Action/ John Murray closing the remaining the TOC slots.
We have a table for tracking our progress for releasing the remaining tasks that have to be completed to ready our release. Reviewed Releasing Amber Tasks.
Action/PTLs update Releasing Amber Tasks with all of your tasks and a short video like OTF by
After the TSC meeting we will start our integration and test meeting.
Report out from PTL: Stand-Up & Report Out on Blockers
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/ user-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/ user-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.)
Votes
The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
Vote to approve Request to Approve referencing and using the additional licenses for the open source software community from section of License Attribution Records.