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 / Farheen Cefalu send out a note today of when we have to have our votes in by . Update the site
This was opened at the f2f and discussions going on with the EC. We got the presentation from last weeks meeting. Challenge is Jack needs a readout from legal team to understand what options and work needs to take place. No official move in O-RAN Alliance and what we are going to do in Open source. They have their own licensing.
Rittwik assigned but not sure.
Architectural alignment and where we are aligned and where are we mis-aligned with our architecture.
Christian Gallard - If OAI current requirements meet the O-RAN Alliance architecture?
Jack - recommendation from a technical review vs. the legal review.
Action/ user-59b16 Alignment and adjust OAI code to be compliant with O-RAN Alliance. This is an architectural review of fitting the code.
Who is taking care of the dashboard epics? Will it be OAM?
Jack - Right now that makes the most sense to put them in the OAM project. We want the team to decide what reports should be presented in the dashboard. OAM teams need to access and utilize dashboards without having to read a manual.
Tracy Van Brakle wants an offline conversation about traceability.This is for OA-Bronze. We need distinguish between OAM and dashboard.
We can add this topic to the architecture meetings or have a separate meeting. Tracy Van Brakle will set it up.
Action/ John Murray closing the remaining the TOC slots.
We are working with LF to close on the reporting for contributions and activities but we had a set back last week on gathering information. They were reporting that there would be an update early this week.
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. . Action/ user-d3360 update the TOC with the status of branching Amber on
Action / John Murray We will vote on the licensing next week
Report out from PTL: Stand-Up & Report Out on Blockers
Action/Jinri Huang will create a framework for the marketing plan.
A message from the call this Monday is this will be a joined release with the Linux Foundation. We can have one quote from O-RAN leadership.
user-59b16 send Jinri information about the overall targeted use case and functionality as targeted working material. Announce the first release about the features we are delivering. What is the main functionality and how we pull this together as a community as a milestone.
The tone is important in the first press release. We don't want to oversell. We want to depict it as a milestone.
The LF leans towards talking about the current release and not the next release. Hopefully we can pull together the voting for the B release and the time frame. Trishan de Lanerolle volunteered to help.
No updates . We are in the process of setting up the VPN to the process. Up and running.
Tracy - Thinks the time is right to include the names of the participating written vendors. Does anyone have an opinion or should I include their names in our documentation.
How many participants?
For the OSC POC there are additional vendors (open front haul) 5 committed members. I have confirmation from Conscope Ericsson NEC and Nokia. OSC O1 related use cases from slides on wiki. Others are captured from Beijing captured on their slides.
From OSC perspective I think it is OK to put their names.
They confirmed in writing. I will put their names.
We have to avoid words like compliance because they're participating.
Agree this is a demo proof of concept un-certified non-compliant.
Action/ Jinri Huang will add the F2F meeting minutes to the events page.
EC discussed this. Orange proposed dividing this corporation into two stages. Short and long term targets. First term have a joint proof of concept. Bad news is they don't have details of code distribution tools, integration. One of the requests from Hank is to require Orange to come up with detailed mechanics of POC. Long term is to have a third license from OAI. Desire is to put this under O-RAN SC so that it will encourage O-AI community to contribute to O-RAN SC. For this long term cooperation is not very clear. Uncertainty whether O-AI give up their work in their own community and assign their resources to O-RAN SC. My understanding is if we want to cooperate we should concentrate on the short term solution.
The question on the short term. Were they targeting that cooperation with O-RAN Alliance test group? O-SC test?
OSC. The software development work is mainly under our community. Their corporation will cover our software community.
We need to gather people of interest to work on this. user-59b16 set up an architecture team. We need to sit down and see how to use it as a target to see how to make it work. We should create a plan. Action/ user-59b16 Alignment and adjust their code to be compliant with O-RAN Alliance. The time frame is as part of B release what can we achieve as interoperability. Can we id a task with some level of interoperability with OAI.
Rittwik - My expectation is E2 adaptors.
Jack - These need to be listed out and agreed upon so everyone is on the same page. We need a some statement out so we can
Jinri - Maybe we should wait for Orange.
Jack - They will need some support from us.
Jinri - OK
Details
There is a spreadsheet that ids the B Epics. Action/user-59b16 send the epics to user-bc668 . December 4 or 6 the TOC will take a vote to approve the spreadsheet. We have this month to clean up all the epics and end to end use cases.
Viswa - Will there be a vote for seed code in the repo?
We got original seed code. We formed the individual projects with the PTLs. The community decided what they will pull in. We deleted some seed code. We left that to each of the working teams. The epics are pre- O-RAN Allliance specification. We are working towards. As we bring in code compliance with spec, some code may be depricated or changed to meet the specifications.
What is there is questionable code? Are we going to getting all the code or lifecycle only?
All the integration and test drives the package.
Lusheng's team is packaging up different projects that will be included in the release. Though some projects have not contributed enough code for detailed functionality.
Lusheng - we are asking each repo for a binary image or LF package for this release. For next release we will run those binary artifacts and end to end stories.
Viswa - If someone wants to check out the Amber release do they have to download from each repo?
Yes they will have to download from each repo and we can offer the Amber branch.
Now that we have pieces we will start to build the "B" release. The E2E use cases will drive the build.
If needed we can create automated script to grab the Amber release branch and put it into a big tar ball. However for A release not everything is integrated.
Earlier we had a word document that detailed the scope of A release. Now that we heard there is a project will there be one for B release.
The release architecture team should pull together and close software development and write detailed release notes. These are a part of the documenation for the release.
Action/ John Murray closing the remaining the TOC slots.
Jack sharing tes.lfanalytics.io/projects/o-ran.
We are not releasing it yet because the data that is presented is not accurate. This is progress. When clicked on we get metrics. The site is not fully released yet. We are continuing to work it. Trishan de Lanerolle there needs to be an overview. I wanted to show the progress. Lusheng is working with them on the first level. Getting the public release of metrics is important to show because we want to fill in the TOC slots.
Chris Lott has written a very good page and I still have to create a link to it.
Action/ weichen ni will provide PTLs with the steps that they need to view their converted docs on the documentation wiki. He will add the link to the top of the Project Readiness for Amber Release.
Action/ Each PTL write up a small clear statement about their license attribution that they can post to the email list.
This is from the license scan that the LF provided. There is code with DSD or MIT licenses.
These licenses can be used in upstream projects.
BSD-3-Clause need to be clearly marked of which directory from the external source. This was the assignment for PTLs to provide so TOC can approve.
Standing Agenda Items (Brief Status of Ongoing Activities)
At this point they should put the code in and it will be a part of the maintenance release if we choose to have one. At this point freeze the code and document. That repo won't be a part of this release. It will be a part of maintenance release if they are green.
Action/ PTLs must update their release notes in their documentation by . We will review the red rows on Project Readiness for Amber Release. If you haven't completed give us a percentage complete. We need a good faith demonstration.
As we are preparing for releasing docker images to docker hub prefix the organization with the docker name. TOC Co chairs have been asked for how to name this. ORAN is NYSE for Orange. Use o-ran. Jack - We should use o-ran-sc or scp. This makes it clear which license gets what. They both begin with O-RAN.
Concern about confusion around sc and scp. I would call it o-ran-sc. Once in binary the licensing is not important.