/
2019 Q4 (Oct, Nov, Dec)

2019 Q4 (Oct, Nov, Dec)

2019 12 18

Recording: toc-weekly-20191218.mp4

Agenda

  1. Call for Scribe (minutes owner) Lusheng Ji
  2. Roll Call & Quorum Check 

    Company

    Contact NameAttendanceAlternate ContactAttendance

    AT&T

    Jack Murray Co-Chair

    Y



    China Mobile

    Jinri Huang Co-Chair

    Y

    Deutsche Telekom 

    David Streibl




    NTT DOCOMO

    Masafumi Masuda




    Orange

    William Diego


    Vincent Danno

    Viswa Kumar

    Y

    *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 Meeting

    1. Moved by Jinri, Seconded by Viswa, passed 3/0/0.
  4. Review of Today's Agenda
    1. Jinri requested new agenda item for discussing community contributions too PoC at MWC Barcelona.
    2. Jun Song: procedure for individual company to contribute at MWC?
      1. Jack: open use of O-RAN SC software because it is open source, but nice to know who/how using; but if making claims regarding O-RAN such as compliance, then need permission from O-RAN Alliance.
      2. Jinri: concur with Jack.  also can be done by individual company, but we are collecting and coordinating for representing the community under WG1
        1. Jun: customer related, so need to discuss with them.
        2. Jinri: can proceed in parallel, discussing with customer and providing info to the collection table.
        3. Jack: AT&T has 3, 1 live demo and 2 videos
  5. Release Votes and Approval:
    1. Review Project Readiness for Amber Release
    2. Review Bronze 
  6. Marketing of the Amber release (WG, LF, PR)
    1. Jinri: regarding the MWC demos: Paul Smith and Jinri are collecting info on MWC demos; two gate points: 12/19 for entering info and preliminary approval, 01/20 for completing preparation and final approval for any PR.
    2. Jack:  LF Networking conference April 2020.  we will coordinate presentations there.  
    3. Jinri: Global plugfest events at NA, EU, Beijing.  PR under preparation, will be on wire today, covering O1/A1 PoC, as well as Beijing plugfest.  Active attendance: over 70 companies; 200+ attendees; 4 integration groups testing open front haul; WG6 in HW SW decoupling; 
  7. Status of Open Action Items (Old Business)
    • Action / TOC voting members: Provide an alternate contact on the TOC list above.
      • Jinri to send out email.
    • ActionTracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
      • Tracy: completed uploading video recording to O-RAN.  Need approval to upload to LF wiki.
        • Jinri will make request to EC tomorrow.
      • Martin: remove this action item.
    • ActionFormer user (Deleted) Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
      • Jack: Rittwik on vacation, action item deferred.
    • Actionhuangjinri@chinamobile.com provide an answer to Former user (Deleted) regarding support for O-CU, O-DU.  Without commitments from O-CU and O-DU the end to end use cases are in jeopardy.
      • Jack: will be high priority when we come back in Jan. End-to-end use cases require support from O-CU and O-DU.  Need PTL commitments.
        • O-CU PTL: support UE attachment first, challenge for e2e data collection, design in release B.
          • Work with RSAC to pull this together, to identify which items to complete in B, which to defer.
          • Same for O-DU's.
          • Every module to perform some basic self-test, reporting, and communication functions so dashboard reports them as part of the inventory.
          • From RSAC main ask for O-CU is E2 interface reporting which depends on progress by WG3.
            • Many software functions can move ahead of spec.
    • Action/ PTLs enter epics from Contributions into jira.
      • Will use JIRA more in Release B for reporting and tracking.  
      • Need more participation on cross-project/company activities/contributions. Will ask one ToC member to coordinate inter-project activities.
    • Action/ PTLs participate in the Bronze planning meetings held twice a week by the 3605446 committee.  PTLs who are planning to contribute to Bronze must attend.
  8. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Project Readiness for Amber Release
      2. Maintenance Release
      3. Project Bronze Release
    2. Former user (Deleted) Test & Integration Planning (INT)
    3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
      3. Former user (Deleted) O-RAN Centralized Unit (OCU)
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan (Deactivated) 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 Ni Documentation (DOC)
      10. John Keeney (Ericsson EST) Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
    4. Former user (Deleted) Requirements Software Architecture Committee
  9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
    1. By Jinri: possible contribution to MWC Barcelona
      1. Already covered at item 6 above (marketing)
    2. O-ARN Alliance Face to face meeting: 
      1. Jinri: on Monday TSC call, we discussed meeting arrangement but no conclusion yet.  F2F to be held Feb 17-21, Paris. 
  10. Planning for Next Meeting
  11. Any Other Business (AOB) 
  12. Meeting Summary (resolutions, new action items, etc.)

2019 12 11

Zoom meeting: 2019-12-11-toc.mp4

Agenda

  1. Call for Scribe (minutes owner) Farheen Cefalu
  2. Roll Call & Quorum Check 

    Company

    Contact NameAttendanceAlternate ContactAttendance

    AT&T

    Jack Murray Co-Chair

    x



    China Mobile

    Jinri Huang Co-Chair

    x

    Deutsche Telekom 

    David Streibl




    NTT DOCOMO

    Masafumi Masuda

    x

    Orange

    William Diego


    Vincent Danno

    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 Meeting

    1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Vote to approve minutes for  
      2. On motion made by huangjinri@chinamobile.com
      3. Seconded by MASAFUMI MASUDA
      4. VOTE: Vote taken, item passed
  4. Review of Today's Agenda
  5. Release Votes and Approval
  6. Marketing of the Amber release (WG, LF, PR)
    • Jinri - Making a video that will cover the software community.
    • Zbynek (PM O-RAN Alliance marketing and communications) wrote a newsletter for the EC meeting.  Jinri will attend and will include the Amber release in this newsletter.
  1. Status of Open Action Items (Old Business)
    1. ActionTracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
      • Jinri - 2 plugfest sessions last week organized by Tracy has been recorded.  Tracy reported this to EC this morning.  Tracy raised whether she can share the video with the SC.  Suggested to put it on the o-ran wiki first then decide whether to make it public on the software wiki.
      • North American and Asian session happening this week.
        • Preparation work has been done
        • Tomorrow there will an operator lab tour
        • Orange, Telecom Italia, Geo, and Sprint will be visiting the lab for the plugfest.
        • Tomorrow afternoon we arranged a slot to shoot a video for the MWC video.
        • In the Asian session we prepared 5 integration line.  You can understand it as 5 different sets of test and integration.  
        • 5 sets of demos integration and test.
        • We will demonstrate an online show that will be available to public to watch the demo live.
        • To accomodate time zones morning timeslot will be made convenient to US and afternoon for Europe.
        • Around 200 attendees.
        • Keynotes, test and integration results by the group data gates, and round tables.
        • We also prepared the live broadcast can join via Zoom bridge.
        • Although in Chinese we provide translation
        • Next week will be a deep dive sessions.
        • Anyone who is interested can join us.
        • A lot of attention is being given to the software community.  We need to work with the plugfest attendees how to utilize their feedback and use it.
    2. ActionFormer user (Deleted) Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
      • Started communicating.
  2. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Project Readiness for Amber Release
      2. Maintenance Release
      3. Project Bronze Release
    2. Former user (Deleted) Test & Integration Planning (INT)
      • We will not have TOC meetings the week of December 25 and January 1.  These are U.S. holidays.
      • Concern about PTL participation.  We have to grow the community and work towards and end to end system. 
      • The mission is to have the software work across the system.  T
      • Take this time to improve and accomplish the goals of the project.
      • We will ask each PTL to provide a brief discussion on what each PTL is working on each week.
    3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
      3. Former user (Deleted) O-RAN Centralized Unit (OCU)
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan (Deactivated) 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 Ni Documentation (DOC)
      10. John Keeney (Ericsson EST) Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
    4. Former user (Deleted) Requirements Software Architecture Committee
      • Epics are complete for the Bronze release.
      • Multiple discussions around two use cases.
        • Traffic sharing
        • Healthcheck
      • Rittwik asked about contributions for O-CU.
      • Actionhuangjinri@chinamobile.com provide an answer to Former user (Deleted) regarding support for O-CU, O-DU.  Without commitments from O-CU and O-DU the end to end use cases are in jeopardy.
      • Use Samsung as an E2 starter example.
      • Between now and end of year all PTLs must put the epics into Jira.
      • In January the TOC calls should refer Jira tickets.
      • We are ready to release the bronze release document.(Contributions)
      • Action/ PTLs enter epics from Contributions into jira.
      • Martin - suggestion to create one common link.
  3. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
    1. Jinri - 5 minutes to introduce the Asian Plugfest and 3 minutes for the O-RAN F2F 
      1. Next F2F is in Feb 17 - 22 in Paris.  One week after Barcelona meeting.
        1. Daily working sessions with only 3 hours for TOC.  Would like to see more time for TOC added to the agenda.
        2. All these sessions happen in parallel. They are across different working groups.  Before we used to invite our delegates from other WGs to join.  We also want to reach out to have different WGs meet.  Example would be Rittwik attending another working group meeting.
        3. Rittwik only drawback is when TOC is going on you miss the parallel sessions.  
    2. Rittwik - Raise a concern about the low attendance of PTLs for the Bronze release planning.
      1. It is the end of year holiday season so low attendance is expected this time of year.
  4. Planning for Next Meeting
  5. Any Other Business (AOB) 
  6. 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  
        2. On motion made by huangjinri@chinamobile.com
        3. Seconded by MASAFUMI MASUDA
        4. VOTE: Vote taken, item passed
    2. Actions
      1. Action / TOC voting members: Provide an alternate contact on the TOC when you can not attend the TOC meeting.
      2. ActionTracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
      3. ActionFormer user (Deleted) Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
      4. Actionhuangjinri@chinamobile.com provide an answer to Former user (Deleted) regarding support for O-CU, O-DU.  Without commitments from O-CU and O-DU the end to end use cases are in jeopardy.
      5. Action/ PTLs enter epics from Contributions into jira.

2019 12 04

Zoom meeting: 2019-12-04-toc-audio_only_1.m4a

Agenda

  1. Call for Scribe (minutes owner) Farheen Cefalu
  2. Roll Call & Quorum Check 

    Company

    Contact NameAttendanceAlternate ContactAttendance

    AT&T

    Jack Murray Co-Chair

    x



    China Mobile

    Jinri Huang Co-Chair

    x

    Deutsche Telekom 

    David Streibl

    x

    NTT DOCOMO

    Masafumi Masuda




    Orange

    William Diego


    Vincent Danno

    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 Meeting

    1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Vote to approve minutes for  
      2. On motion made by huangjinri@chinamobile.com
      3. Seconded by Former user (Deleted)
      4. VOTE: Vote taken, item passed
    2. The minutes of the prior meetings were reviewed, and there was a request to update the audio recording.  Recording updated  
      1. Vote to approve minutes for  
      2. On motion made by huangjinri@chinamobile.com
      3. Seconded by Former user (Deleted)
      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)
    2. Vote to accept the license scan and upstream licenses are approved for use. These have been reviewed with LF and are normal.
    3. Vote on the official release of Amber and  branches.  Vote to approve the branching and release of the Amber software.
    4. 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. 
  6. Marketing of the Amber release (WG, LF, PR)
  7. Status of Open Action Items (Old Business)
    1. Action/huangjinri@chinamobile.com  will create a framework  for the O-RAN SC marketing plan.
      • Contact Jinri for details around the marketing plan.
      • Jinri - On the web page I saw some videos.  We really need to take advantage of the videos at the events.
      • Plugfest Beijing will last two weeks and there is also Barcelona to activate the marketing plan.
      • Channels to promote our visibility
        • Press Release
        • Symposium. - Consisted of key notes and round table for the traditional symposium.  Will be in Barcelona this year.
        • Industry events - Invite key speakers to discuss the key features of O-RAN.
      • Possible additional channels
        • O-RAN newsletter internal base of 1200 wiki users, plus 285 subscriptions from web.
        • Twitter 
        • Promotional Videos
      • Zbynek Dalecky is the project organizer for the O-RAN Alliance press releases and site.
    2. ActionTracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
      • 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.
    3. Actionhuangjinri@chinamobile.com  will add the F2F meeting minutes to the events page. 
    4. ActionFormer user (Deleted) Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
      1. Rittwik - I still have to work on this.
    5. Action/PTLs update Releasing Amber Tasks  and create a short video like OTF by  
  8. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Project Readiness for Amber Release
        • 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.
      2. 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.
        • Each PTL must look this spreadsheet and review. 
        • Contributions 
        • OSC Use Case:Traffic Steering QoE Contributions 
        • 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.
    2. Former user (Deleted) Test & Integration Planning (INT)
    3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
      3. Former user (Deleted) O-RAN Centralized Unit (OCU)
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan (Deactivated) 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 Ni Documentation (DOC)
      10. John Keeney (Ericsson EST) Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
    4. Former user (Deleted) Requirements Software Architecture Committee
  9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
    1. Rittwik - Discuss the B release.
  10. Planning for Next Meeting
  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  
        2. On motion made by huangjinri@chinamobile.com
        3. Seconded by Former user (Deleted)
        4. VOTE: Vote taken, item passed
      2. The minutes of the prior meetings were reviewed, and there was a request to update the audio recording.  Recording updated  
        1. Vote to approve minutes for  
        2. On motion made by huangjinri@chinamobile.com
        3. Seconded by Former user (Deleted)
        4. VOTE: Vote taken, item passed
    2. Actions
      1. ActionTracy Van Brakle and Martin Skorupski Plugfest and demo video alignment update.
      2. ActionFormer user (Deleted) Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.

2019 11 27

Zoom Meeting2019-11-27_toc.mp4

Agenda

  1. Call for Scribe (minutes owner) Farheen Cefalu
  2. Roll Call & Quorum Check 

    Company

    Contact NameAttendanceAlternate ContactAttendance

    AT&T

    Jack Murray Co-Chair

    x



    China Mobile

    Jinri Huang Co-Chair




    Deutsche Telekom 

    David Streibl

    x

    NTT DOCOMO

    Masafumi Masuda




    Orange

    William Diego


    Vincent Danno

    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

  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)
    2. Vote to accept the license scan and upstream licenses are approved for use. These have been reviewed with LF and are normal.
    3. Vote on the official release of Amber and  branches.  Vote to approve the branching and release of the Amber software.
    4. 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. 
  6. Marketing of the Amber release (WG, LF, PR)
  7. Status of Open Action Items (Old Business)
    1. Action/huangjinri@chinamobile.com  will create a framework  for the O-RAN SC marketing plan.
      1. Rittwik: AT&T provided the input.  He was looking for other operators.
      2. 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.
      3. We are uploading the epics into the wiki.  By next Wednesday meeting I will go through the epics.
    2. ActionTracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
      1. 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.
    3. Actionhuangjinri@chinamobile.com  will add the F2F meeting minutes to the events page.  
    4. ActionFormer user (Deleted) Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
      1. Rittwik - No progress yet.  Chilin is working on slides to get the word out of the Amber release.
    5. ActionJack Murray closing the remaining the TOC slots.
      1. Reviewed analytics https://test.lfanalytics.io/projects/o-ran
      2. Action / Former user (Deleted) sent a note to Agnes and copy Trishan de Lanerolle regarding the documentation repo analytics on https://test.lfanalytics.io/projects/o-ran.
    6. ActionFormer user (Deleted) add record and date of the approved licenses on License Attribution Records wiki page.
  8. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Project Readiness for Amber Release
    2. Former user (Deleted) Test & Integration Planning (INT)
      1. 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
        1. Action/PTLs update Releasing Amber Tasks with all of your tasks and a short video like OTF by  
      2. After the TSC meeting we will start our integration and test meeting.
    3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
      3. Former user (Deleted) O-RAN Centralized Unit (OCU)
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan (Deactivated) 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 Ni Documentation (DOC)
      10. John Keeney (Ericsson EST) Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
    4. Former user (Deleted) 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
  11. Any Other Business (AOB) 
  12. Meeting Summary (resolutions, new action items, etc.)
    1. Votes - No quorum
    2. Actions
      1. Action/huangjinri@chinamobile.com  will create a framework  for the O-RAN SC marketing plan.
      2. ActionTracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
      3. Actionhuangjinri@chinamobile.com  will add the F2F meeting minutes to the events page. 
      4. ActionFormer user (Deleted) Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
      5. Action/PTLs update Releasing Amber Tasks  and create a short video like OTF by  

2019 11 20

Zoom meeting: 2019-11-20_toc_audio_only.m4a

Agenda

  1. Call for Scribe (minutes owner) Farheen Cefalu
  2. Roll Call & Quorum Check 

    Company

    Contact NameAttendanceAlternate ContactAttendance

    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

    xVincent Danno

    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  
      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 (Nov 2019) 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. 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 Former user (Deleted)
          3. Seconded by MASAFUMI MASUDA
          4. VOTE: Vote taken, item passed
        6. Action/ Former user (Deleted) add record and date of the approved licenses on License Attribution Records. (Former user (Deleted): completed 11/21)
    3. 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 Former user (Deleted)
            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 Jack Murray or huangjinri@chinamobile.com.  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.  
  7. Status of Open Action Items (Old Business)
    1. Action/huangjinri@chinamobile.com  will create a framework  for the O-RAN SC marketing plan.
    2. ActionTracy 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. Actionhuangjinri@chinamobile.com  will add the F2F meeting minutes to the events page.  
    4. ActionFormer user (Deleted) Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
    5. ActionJack Murray closing the remaining the TOC slots.
    6. ActionFormer user (Deleted) update the TOC with the status of branching Amber on  
    7. Action / Jack Murray We will vote on the licensing next week  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. Former user (Deleted) 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. Former user (Deleted) O-RAN Centralized Unit (OCU)
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan (Deactivated) 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 Ni Documentation (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 (Ericsson EST) Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
    4. Former user (Deleted) 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.
  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.)
    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  
        2. On motion made by William DIEGO
        3. Seconded by MASAFUMI MASUDA
        4. VOTE: Vote taken, item passed
      2. Vote to approve Request to Approve referencing and using the additional licenses for the open source software community from section of License Attribution Records.  
        1. On motion made by Former user (Deleted)
        2. Seconded by MASAFUMI MASUDA
        3. VOTE: Vote taken, item passed
      3. Vote to allow all the green repos to align with the process from this Project Readiness for Amber Release.
        1. On motion made by Former user (Deleted)
        2. Seconded by William DIEGO
        3. VOTE: Vote taken, item passed
    2. Actions
      1. Action/huangjinri@chinamobile.com  will create a framework  for the O-RAN SC marketing plan.
      2. ActionTracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
      3. Actionhuangjinri@chinamobile.com  will add the F2F meeting minutes to the events page.  
      4. ActionFormer user (Deleted) Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
      5. ActionJack Murray closing the remaining the TOC slots.
      6. ActionFormer user (Deleted) add record and date of the approved licenses on License Attribution Records. (Former user (Deleted): completed 11-21)

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 NameAttendanceAlternate ContactAttendance

    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

    xVincent Danno

    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  
    3. On motion made by Former user (Deleted)
    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 huangjinri@chinamobile.com and copy Jack Murray.
  6. Status of Open Action Items (Old Business)
    1. Action/huangjinri@chinamobile.com  will create a framework  for the O-RAN SC marketing plan.
    2. ActionTracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
    3. Actionhuangjinri@chinamobile.com  will add the F2F meeting minutes to the events page.  
    4. ActionFormer user (Deleted) Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
    5. ActionJack Murray closing the remaining the TOC slots.
    6. ActionFormer user (Deleted) update the TOC with the status of branching Amber on  
    7. Action / Jack Murray We will vote on the licensing next week  regarding the License Attribution Records
    8. Action/ TOC Docker hub prefix naming vote due  .  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. Former user (Deleted) 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  .  We need this done to branch the Amber code.  We need to complete the branching by next weeks meeting.  .  
        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 cha