Technical Charter for O-RAN Software Community

Heads Up! Different International Timings for Daylight Savings (Fall back one hour)

2019 11 20

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu

2. Roll Call & Quorum Check 

   Company	Contact Name	Attendance	Alternate Contact	Attendance
   AT&T	Jack Murray Co-Chair	x
   China Mobile	Jinri Huang Co-Chair
   Deutsche Telekom	David Streibl
   NTT DOCOMO	Masafumi Masuda	x
   Orange	William Diego	x	Vincent Danno
   Verizon	Viswa Kumar

   *Quorum: 50% or more of total TSC voting members unless excluded due to attendance.  We have a quorum and can vote on activities.

3. Review and Agree to Minutes of Previous Meetings

   1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Vote to approve minutes for 13 Nov 2019 
      2. On motion made by William DIEGO
      3. Seconded by MASAFUMI MASUDA
      4. VOTE: Vote taken, item passed
4. Review of Today's Agenda
5. Release Votes and Approval
   1. Have a wiki link with all the release info in one place (in process)
      1. Gather all items related to the Amber Release under Amber Release on this wiki.
   2. Vote to accept the license scan and upstream licenses are approved for use. These have been reviewed with LF and are normal.
      1. Vote on the official release of Amber and  branches
   3. Marketing of the Amber release (WG, LF, PR)
   4. Status of Open Action Items (Old Business)
      1. Action/Jinri Huang  will create a framework  for the O-RAN SC marketing plan.
      2. Action / Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
      3. Action/ Jinri Huang  will add the F2F meeting minutes to the events page. 27 Nov 2019 
      4. Action/ user-59b16 Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
      5. Action/ John Murray closing the remaining the TOC slots.
      6. Action/ user-d3360 update the TOC with the status of branching Amber on 20 Nov 2019 
      7. Action / John Murray We will vote on the licensing next week 20 Nov 2019 regarding the License Attribution Records
   5. 1. 1. LF code scans, code licenses, and code clean up work status. 
         2. TSC will take a vote to approve upstream licenses that are compatible within our projects. 
         3. This will be repeated at every release.
         4. Lusheng - LF sends us a spreadsheet that lists all the red and yellow items that have failed the scan.  
            1. binary issues have all been addressed.
            2. non-binary have been scanned. 
            3. 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.
            4. We follow the LF practice about foreign code from the License Attribution Records page.  You will find the best practices for license attribution friendliness.  
            5. We want TOC approval for the Request to Approve section of License Attribution Records
               1. Vote to approve Request to Approve referencing and using the additional licenses for the open source software community from section of License Attribution Records.  
               2. On motion made by user-d3360
               3. Seconded by MASAFUMI MASUDA
               4. VOTE: Vote taken, item passed
            6. Action/ user-d3360 add record and date of the approved licenses on License Attribution Records
      2. Vote on the official release of Amber and  branches.  Vote to approve the branching and release of the Amber software. 
         1. Project Readiness for Amber Release.  Lusheng asking to accept all the repos on the Project Readiness for Amber Release for the branching of the Amber release. 
         2. Where do we put the video demos?
            1. Not appropriate on gerrit.  We will have to display videos on this wiki.
               1. 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.
               2. Action / Farheen Cefalu work with Jack to update the Amber Release page.
               3. 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.
               4. 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.
                  1. Is the vote only for green?  
                     1. It is for green not red.
               5. Lusheng - Allow all the green repos to align with the process from this Project Readiness for Amber Release.
                  1. On motion made by user-d3360
                  2. Seconded by William DIEGO
                  3. VOTE: Vote taken, item passed
   6. Marketing of the Amber release (WG, LF, PR)
      1. 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 27 Nov 2019  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.  
   7. Status of Open Action Items (Old Business)
      1. Action/Jinri Huang  will create a framework  for the O-RAN SC marketing plan.
      2. Action / Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
         1. 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.  
         2. 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.
         3. There is a simplified optimization.  It will be an interesting event in both the POC and plugfest.
      3. Action/ Jinri Huang  will add the F2F meeting minutes to the events page. 27 Nov 2019 
      4. Action/ user-59b16 Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
      5. Action/ John Murray closing the remaining the TOC slots.
      6. Action/ user-d3360 update the TOC with the status of branching Amber on 20 Nov 2019 
      7. Action / John Murray We will vote on the licensing next week 20 Nov 2019 regarding the License Attribution Records
   8. Standing Agenda Items (Brief Status of Ongoing Activities)
      1. Release Manager/Release Planning: Weekly TOC Scheduling
         1. Project Readiness for Amber Release
      2. user-d3360 Test & Integration Planning (INT)
         1. We will be doing a demonstration of the branching process after this call.
      3. Report out from PTL: Stand-Up & Report Out on Blockers
         1. Matti Hiltunen RIC Applications (RICAPP) 
         2. Thoralf Czichy RIC Platform (RIC) 
            1. 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.
               1. Add it under the license
         3. user-a934b O-RAN Centralized Unit (OCU)
         4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
         5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
         6. Martin Skorupski Operations and Maintenance (OAM)
         7. Alex Stancu Simulations (SIM)
         8. Xiaohua Zhang Infrastructure (INF)
         9. weichen niDocumentation (DOC)
            1. 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.)
         10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
         11. (TBD) O-RAN Radio Unit (ORU)
      4. user-59b16 Requirements Software Architecture Committee
         1. Epics are in the spreadsheet.  Most people have contributed to the epics.  We have been going through the epics in the RSAC.
         2. Request to have all the PTLs to be review the spreadsheet of epics.
         3. Matti - we will share slides with Rittwik for xApps.
         4. 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.
      Standing Agenda Items (Brief Status of Ongoing Activities)
      1. Release Manager/Release Planning: Weekly TOC Scheduling
         1. Project Readiness for Amber Release
      2. user-d3360 Test & Integration Planning (INT)
      3. Report out from PTL: Stand-Up & Report Out on Blockers
      4. Matti Hiltunen RIC Applications (RICAPP) 
      5. Thoralf Czichy RIC Platform (RIC) 
         1. 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.
      6. user-a934b O-RAN Centralized Unit (OCU)
      7. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      8. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      9. Martin Skorupski Operations and Maintenance (OAM)
      10. Alex Stancu Simulations (SIM)
      11. Xiaohua Zhang Infrastructure (INF)
      weichen niDocumentation (DOC)
      1. 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.)
      12. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      13. (TBD) O-RAN Radio Unit (ORU)
      user-59b16 Requirements Software Architecture Committee
   9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
   10. Planning for Next Meeting
       1. Next week Thursday is a holiday.  There may be lighter attendance next Wednesday.  We will recap Amber and start the discussion around Bronze.
   11. Open Discussion
   12. Any Other Business (AOB) 
   13. Meeting Summary (resolutions, new action items, etc.)

   
   

2019 11 13

Zoom meeting: 2019-11-13_toc.mp4

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu

2. Roll Call & Quorum Check 

   Company	Contact Name	Attendance	Alternate Contact	Attendance
   AT&T	Jack Murray Co-Chair	x
   China Mobile	Jinri Huang Co-Chair
   Deutsche Telekom	David Streibl	x
   NTT DOCOMO	Masafumi Masuda	x
   Orange	William Diego	x	Vincent Danno
   Verizon	Viswa Kumar

   *Quorum: 50% or more of total TSC voting members unless excluded due to attendance.  We have a quorum and can vote on activities.

3. Review and Agree to Minutes of Previous Meetings

   1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
   2. Vote to approve minutes for 06 Nov 2019 
   3. On motion made by user-2057e
   4. Seconded by MASAFUMI MASUDA
   5. VOTE: Vote taken, item passed
4. Review of Today's Agenda
5. Marketing of the Amber release (WG, LF, PR)
   1. 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.
6. Status of Open Action Items (Old Business)
   1. Action/Jinri Huang  will create a framework  for the O-RAN SC marketing plan.
   2. Action / Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
   3. Action/ Jinri Huang  will add the F2F meeting minutes to the events page. 27 Nov 2019 
   4. Action/ user-59b16 Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
   5. Action/ John Murray closing the remaining the TOC slots.
   6. Action/ user-d3360 update the TOC with the status of branching Amber on 20 Nov 2019 
   7. Action / John Murray We will vote on the licensing next week 20 Nov 2019 regarding the License Attribution Records
   8. Action/ TOC Docker hub prefix naming vote due 13 Nov 2019 .  Suggestion was made to call the prefix o-ran-sc
      1. 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
7. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Project Readiness for Amber Release
         1. we are in week 44. At this point we should be preparing to branch the code.
            1. Yes, branching now vs. later.  Now there will be significant changes made on both branches vs. later less items to change.
               1. 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.
   2. user-d3360 Test & Integration Planning (INT)
      1. Project Readiness for Amber Release 
      2. The teams have made good progress in turning the cells in the link above to green.
      3. What areas should we focus on to close.
         1. Producing the documentation and the minimum requirement for documentation are the release notes.
      4. 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.
      5. What is the next milestone to hit by this Friday from the TOC?
         1. Was hoping to have all the cells green by today but will wait until Friday 15 Nov 2019 .  We need this done to branch the Amber code.  We need to complete the branching by next weeks meeting. 20 Nov 2019 .  
         2.  
   3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC)
         
         1. request to approve one new repo and committer changes for two existing repos as per this e-mail
            1. When we request changes from LF Aric Gardner has info.yml files for committer management.  This will be done through gerrit.  Need TOC and LF approval. 
               1. This will be handled in Bronze.
      3. user-a934b O-RAN Centralized Unit (OCU)
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      6. Martin Skorupski Operations and Maintenance (OAM)
      7. Alex Stancu Simulations (SIM)
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen niDocumentation (DOC)
         1. Thoralf: need to discuss how we know when a repo/subproject is done. So far not all is visible in readthedocs it seems.
            
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
          1. Henrik Andersson as a committer for the Non-RealTime RIC . 
          2. Motion made by John Keeney 
          3. Seconded by user-2057e
          4. VOTE: Vote taken, item passed
      11. (TBD) O-RAN Radio Unit (ORU)
   4. user-59b16 Requirements Software Architecture Committee
8. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
9. Planning for Next Meeting
10. Open Discussion
11. Any Other Business (AOB) 
12. Meeting Summary (resolutions, new action items, etc.)
    1. Votes

       1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.

          1. Vote to approve minutes for 06 Nov 2019 

          2. On motion made by user-2057e

          3. Seconded by MASAFUMI MASUDA

          4. VOTE: Vote taken, item passed

       2. Add Henrik Andersson as a committer for the Non-RealTime RIC . 
          1. Motion made by John Keeney 
          2. Seconded by user-2057e
          3. VOTE: Vote taken, item passed
    2. Actions
       1. Action/Jinri Huang  will create a framework  for the O-RAN SC marketing plan.
       2. Action / Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
       3. Action/ Jinri Huang  will add the F2F meeting minutes to the events page. 27 Nov 2019 
       4. Action/ user-59b16 Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
       5. Action/ John Murray closing the remaining the TOC slots.
       6. Action/ user-d3360 update the TOC with the status of branching Amber on 20 Nov 2019 
       7. Action / John Murray We will vote on the licensing next week 20 Nov 2019 regarding the License Attribution Records

Return to Todays Agenda ^

Archived Meetings