Recording

Meeting Recording: https://zoom.us/rec/share/XJ0wGqP2nI_4b1HBRHNatF25LuMYjQUjoQDhQt6AKcDWanmgXlXE3Lo6wD_IigsE.xrY3c_dDw1cubYhJ

Agenda

• Roll Call & Quorum Check

• Review of last week's minutes

• G Release Vote

• Motion for New Repo for an xAPP for Anomaly Detection (AD)

• Ericsson will Scribe for January, except for the first week of January, where Viavi will be scribe.

Recording

Meeting Recording: https://zoom.us/rec/share/YCmMs7rNd1U4P_Iop_242Jn7r1oZ-oinBen9oTOxeLceviMzBy92OXDhVwF8D5YH.vGX0HExIs9puOclu

Agenda

• Call for Scribe (minutes owner):  Viavi is scrive for December 2022

• Roll Call & Quorum Check

• Release vote:   Outstanding repo request from RICAPP from last week - PTL, Sunil not present, moving to next week

• Copyright update:

• O-RAN related business:
  F2F June mtg, will be held in Osaka, Japan.
  F2F Oct mtg has not been decided yet.
  Call for Demo MWC Barcelona, Dec 6 has passed

• G release status
  License scanning: Reports have been shared to all PTLs. System idenified only 1 issue. GPL license issue for NS3. Good to go according to scans. All reports are fine.
  Sridhar to send scan reports to Ankit. Send it to TOC list.
  
  SMO: On track for completion. Missing highlights and source code image link
  Non-RT RIC, John K: Almost ready to release. Few clean up items. On track to finish by next week.
  Near-RT RICPLT, Thoralf: Need 1 more week.  
  RICAPP - Sunil: Report status by email
  O-DU High, Ankit: Working on documentation. Will complete by Dec 15.
  OAM, Martin: Reachout offline
  SIM, Alex: Reachout offline
  INF, Jackie: Completed all release images. Created a branch for G release. Some documentation to be updated.
  INT, James: Jinri to touch base with James for release certification by the 15th. Xtesting still in progress.
  AI/ML, Joseph: On track. Src code committed. Images are getting built and end-to-end testing is ongoing. Reach out to DOC PLT to include AI/ML docs.

Recording

Meeting Recording: https://zoom.us/rec/share/9BoINTXYAAnMlWqta6uLpO8QNrLrc5f8nNhu1uWC7OnJRnRruWdIzc9_gTHarEaW.zgaPmCC6htNJCcxq

Agenda

1. Call for Scribe (minutes owner):  

2. Roll Call & Quorum Check 

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.  

1. Review and Agree to Minutes of Previous Meeting

   1. Decision: Minutes for TOC meeting (2022-11-17) approval: Motion to be proposed by X second by X and the Motion was Accepted/Declined.

2. Review of Today's Agenda

3. Release Votes and Approval

4. Copyright update

   1. Is SCCL discussion progressing in O-RAN Alliance? Does the Alliance have plans to publish code-like specifications under SCCL anytime soon? Need to follow up with O-RAN legal team and O-RAN EC to determine current status of SCCL.

      1. 2022-10-06: @John Paul Lane request revised Technical Charter and CCLA before to be submitted to the validation by the board. 

      2. 2022-10-13:  @huangjinri@chinamobile.com request from Hank: how many codes under O-RAN software license? How many code of that have being donwloaded from our website? how many os those code have being integrated in our main gerrit? @Thoralf Czichy can check it from our gerrit. There are currently 4 projects coming up, and none of them are active (no contribution, or the contribuition was probably replaced by another). Action @Sridhar Rao will provide a report to Jinri https://gerrit.o-ran-sc.org/r/admin/repos/q/filter:scp (number of repos, description, how many times was downloaded, etc.). Action @Martin Skorupski: will provide a description of yang model repo to Jinri.

      3. 2022-10-20: Jack - there are meetings ongoing with the legal team in meeting, they are trying to work out some details on the charter, an e-mail vote will be set up.

      4. 2022-10-20: @huangjinri@chinamobile.com the charter is the main issue, there are 2 options: (1) to have 2 license O-RAN and SCCL depending on the project or (2) to have only one license for all the projects (the future ones). It does not impact the Apache v2.0 in the OSC.

      5. 2022-10-27: @huangjinri@chinamobile.com one slide on the topic was presented at the board meeting, Jinri will continue follwing this topic. 

      6. 2022-10-27: @Martin Skorupski https://lists.o-ran-sc.org/g/toc/message/812 → Licensing Headers. Jinri will update on that as soon as legal aspect will clarified.

      7. 2022-11-17: @huangjinri@chinamobile.com: No update, but there is a call about it happening right now.

5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. Plugfest

      1. 2022-07-21 : O-RAN Alliance will initiate the Call for Host on July 24th

      2. 2022-08-11: @huangjinri@chinamobile.com: Call for host for the fall Plugfest has been issued, and there are quite a few applications for host.

      3. 2022-09-08: @huangjinri@chinamobile.com : CFH is closed, with about 80 participants.

      4. 2022-10-27: @huangjinri@chinamobile.com the process is ongoing. summary session will be held at the end of Nov.

   2. Challenges for the OSC community (as report to EC)

      1. 2022-07-14 : There is no update this week

      2. 2022-11-03: @huangjinri@chinamobile.com: We need a place where to record the relationship between our activities and ORAN specifications. Right now we have one page with projects describing the release highlights. We can add a table to identify which specification the project covers and what specification it targets. @Jack Murray: Architecture team can discuss it during their meeting to see what makes sense.

   3. Budget:

      1. 2022-10-06: Jack  - budget plan will be reviewed during the next board meeting. OSC stayed under the budget, it covers cost relative to the repos, support for the community. OSC founds 100% of the community fees.

      2. 2022-10-13: @Sridhar Rao: two types of scanning: (1) license scanning of release code, twice a year, and (2) dependecy scanning (nexus). There is an increase in the license scanning part by ~30%, there is a discussion on going with team with is responsable. Action Sridhra: will provide a short presentation on the existing years budgets where the major line items spends. Two options: (1) accept the increase, (2) look for a new provider (and (3) cut budget from somewhere else).

      3. 2022-10-20: @Sridhar Rao  he is finalising the slides, it should be ready for next week. The previus AP should be adress next meeting.

      4. 2022-10-20: @huangjinri@chinamobile.com some budget alocation from EC could be possible, some contributors are planning to buy some equipments in particular vendor members, you will be contacted.

      5. 2022-10-27: @huangjinri@chinamobile.com OSC budget was validated by the board, Junri is working with James and David to the allocation. 

      6. 2022-11-03: @huangjinri@chinamobile.com : Board meeting approved budget to buy simulation tools. There will be a call with @David Kinsey [AT&T] and @James Li to discuss the details. Besides that the budget stays flat.

   4. F2F

      1. 2022-11-17: @huangjinri@chinamobile.com : There will be three F2F meetings in 2023: first in February in Prague, second in June in Japan, and one during October (location unknown).

6. Old business and Status of Open Actions

   1. OSC Lab

      1. 2022-10-06: Jack - New Jersey OSC lab will experiment a small window of the disruption mid next year (one week at the most).

   2. 5G Super Blueprint status - to be considered for H release.

      1. 2022-07-21 : David  mentioned that there hasnt been any progress on this. Decided to move to H release. (Updated the title header from G to H to reflect the same)

      2. 2022-09-29: @bwick  : will discuss offline with @David Kinsey [AT&T]  to brainstorm ideas.

      3. 2022-10-06:  @David Kinsey [AT&T] meeting with people from the 5G super blueprint organization, the slice SLA has been identified as a use case of interest, so we will work on that (H release). Connection from OSC lab to their lab is expected as part of H release.

7. Standing Agenda Items (Brief Status of Ongoing Activities)

   1. Release Manager  @Sridhar Rao  /Release Planning: Weekly TOC Scheduling

      1. 2022-09-22 @Sridhar Rao will setup a meeting for interacting for PTLs and LF teams.

      2. 2022-10-20: @Sridhar Rao have being working with James on the use of xTesting, and also updating wiki page with the use of xtesting.

      3. 2022-10-20:  @Avinash Bhat AI/ML project is doing well afetr some issues with the creation of repos,the seed cide is completely committed, they have a basic version of the C code available, they will presnet a demo during F2F meeting.

      4. 2022-10-20: Jack - the scan of new code has to be planned in advance in order to avoir last minute issues. @Sridhar Rao is planning to scan all the current release in the midle of the release schedule. Jack - November the 10th should be a good Time. AP @Sridhar Rao launch a code scan on November 10th.

      5. 2022-10-27: @Avinash Bhat AI/ML project has been started in the group, work is ongoing and cross-project coordination is also ongoing, a presentation on topic can be expected by December.

      6. 2022-11-10: @Jack Murray: AP @huangjinri@chinamobile.com and @David Kinsey [AT&T] - to check with @Sridhar Rao about the security tests. 

      7. @John Keeney (Ericsson EST): AP @Sridhar Rao - to look into the insight portal. It looks it is not up-to-date, it would be better to take it down until it is working properly.

   2. Requirements Software Architecture Committee (RSAC, link incl. meeting details)

      1. "G" Release

         1. 2022-11-10: @Jack Murray: request to share the notes for the press release over the next 2 weeks - send them individually to  with some evidence of contribution as a justification.