Technical Charter for O-RAN Software Community

2020 06

24

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu

2. Roll Call & Quorum Check 

   John Keeney

   Company	Contact Name	Attendance	Alternate Contact	Attendance
   AT&T	Jack Murray Co-Chair		Lusheng Ji
   China Mobile	Jinri Huang Co-Chair		Weichen Ni
   Deutsche Telekom	David Streibl		Ondřej Hudousek
   Ericsson	John-Paul Lane		John Keeney
   NTT DOCOMO	Masafumi Masuda		Anil Umesh
   Nokia	Juha Oravainen		Thoralf Czichy
   Orange	William Diego		Vincent Danno	Verizon	Viswa Kumar	Kristen Young
   Nokia	Juha Oravainen	Thoralf Czichy	Radisys	Ganesh Shenbagaraman		Sachin Srivastava	Ericsson	John-Paul Lane
   Verizon	Viswa Kumar		Kristen Young

   *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 

4. Review of Today's Agenda

5. Release Votes and Approval

6. Copyright updates

7. Marketing of the current release (WG, LF, PR)

   1. Bronze Release PR

   2. Virtual Exhibition.

   3. OSC Logo status.

8. Status of Open Action Items (Old Business)

   1. Action/ William DIEGO update on the coordination with the O-RAN test group
   2. Action/ Farheen point to the F2F meeting from the Events page to O-RAN Alliance's latest spreadsheet Jinri Huang notify the EC that the Bronze release has been voted on and approved.
   3. Action/ Vishnu send Rittwik the slides for the ITU / AiML Challenge
   4. Action/ Rittwik: Post ITU / AiML Challenge slides on the wiki and pull together a team.  Include Thoralf.
   5. Action/ Rittwik: I will set up a meeting for ITU AI/ML and pull together a team.
   6. Action/ Trishan: clear all the legal items for the code and figure out what is needed for the O-CU repo creation so the team can continue.
   7. Action/ user-d3360 provide Trishan with the O-CU repo trouble ticket.
   8. Action/ Jinri Huang generate an email to inform Zybnek and EC regarding that we will be delaying the release 

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

   1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling

      1. Bronze Timeline

      2. Review Bronze Release Highlights

   2. user-59b16 Requirements Software Architecture Committee

   3. user-d3360  Integration and Test

   4. Report out from PTL: Stand-Up & Report Out on Blockers - next week we will start to cover this list.  Are there any major items that anyone would like to raise to the TOC this week? 

      1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)

      2. Matti Hiltunen RIC Applications (RICAPP) 

      3. Thoralf Czichy RIC Platform (RIC)

         1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)

      4. user-a934b O-RAN Centralized Unit (OCU) 

      5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)

      6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)

      7. Martin Skorupski Operations and Maintenance (OAM)

      8. Alex Stancu Simulations (SIM)

      9. Xiaohua Zhang Infrastructure (INF)

      10. weichen ni Documentation (DOC)

      11. (TBD) O-RAN Radio Unit (ORU)

10. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items. 

11. Planning for Next Meeting

12. Any Other Business (AOB) 

13. Meeting Summary (resolutions, new action items, etc.)

1. 1.  user-d3360 send Jinri your status slides.

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

   1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling

      1. Bronze Timeline

      2. Review Bronze Release Highlights

   2. user-59b16 Requirements Software Architecture Committee

   3. user-d3360  Integration and Test

   4. Report out from PTL: Stand-Up & Report Out on Blockers - next week we will start to cover this list.  Are there any major items that anyone would like to raise to the TOC this week? 

      1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)

      2. Matti Hiltunen RIC Applications (RICAPP) 

      3. Thoralf Czichy RIC Platform (RIC)

         1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)

      4. user-a934b O-RAN Centralized Unit (OCU) 

      5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)

      6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)

      7. Martin Skorupski Operations and Maintenance (OAM)

      8. Alex Stancu Simulations (SIM)

      9. Xiaohua Zhang Infrastructure (INF)

      10. weichen ni Documentation (DOC)

      11. (TBD) O-RAN Radio Unit (ORU)

3. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items. 

4. Planning for Next Meeting

5. Any Other Business (AOB) 

6. Meeting Summary (resolutions, new action items, etc.)

2020 06 17

Recording: 2020_06_17_O-RAN_SC_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

2020 06 10

Recording: 2020_06_10_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	Lusheng Ji
   China Mobile	Jinri Huang Co-Chair	x	Weichen Ni
   Deutsche Telekom	David Streibl	x	Ondřej Hudousek
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Orange	William Diego	x	Vincent Danno
   Verizon	Viswa Kumar		Kristen Young
   Nokia	Juha Oravainen	x	Thoralf Czichy
   Radisys	Ganesh Shenbagaramanx		Sachin Srivastava	x
   Ericsson	John-Paul Lane	x	John Keeney

   *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 no corrections.
      1. Vote to approve minutes for 03 10 Jun 2020 
      2. On motion made by Jinri Huangby John-Paul
      3. Seconded by Juha Oravainen
      4. VOTE: Vote taken, item passed

4. Review of Today's Agenda

   1. Jack: We will spend time today to vote and approve the Bronze release for 21 Jun 2020 
   2. Rittwik: What is the suggestion for the Viavi simulator on the lab.
   3. Any further updates for the ITU AI/ML Challenge.
      1. Rittwik: Sent it to John Paul.  Action/ Rittwik: I will set up a meeting and pull together a team.
      2. Jack: It is difficult to move quickly.  It takes time to ramp up.
      3. Rittwik: Where should I put the challenge?
      4. Jack: Events wiki and post to the reflector.
   4. Lusheng wants to post the status of the Integration and Test 

5. Release Votes and Approval

   1. Vote on the Bronze Release and Integration and Test Status
   2. Jack: The press releases are handled by the O-RAN Alliance.  Zbynek is the primary contact and he runs it through the O-RAN Alliance.  Jinri is our interface to Zbynek.  Zybnek has pulled together a draft.  It will be combined with the Virtual Demo and the board meeting that is coming up at the end of the month.  The direction is to release the press release at the end of the month like June 30th.  That gives us another week for the highlights.  That is the feedback from O-RAN Alliance and Zybnek is our contact.
   3. Jinri: Does not have the latest.
   4. Trishan: Do we need a quote for this release?
   5. Jack: Yes, we should.
   6. Trishan: Jinri please share.
   7. Jinri: I'm not sure we can share but we can pull out a portion and share with this community.
   8. Jack: It is a combined press release making it a little complicated.  I'm trying to work through how this work than through the traditional open source.
   9. Trishan: If it is a press release we keep it close.
   10. Jack: If you have input contact Zybnek and he will coordinate with Jinri for the PR Release.  That gives us a little window to discuss.  Let us go on to the report from the system integration group.
   11. Lusheng: Sharing screen.
   12. Jinri: OCU PTL informed Jinri they have code ready for quite some time.  They are waiting for the repo to be opened by the LF.  The request was submitted one month ago.  It has been ready for quite some time.  
   13. Lusheng: I was cc:d on the help desk ticket.  LF has added all the information needed for the automation job to create the repo.  7 - 8 hours ago there was a message from LF that the ticket is on hold.  Action/ user-d3360 will check the status of the O-CU demo.
   14. Lusheng: Scope: We have a number of use case flows.  Mainly the flows are RIC , O-1, A-1 healthcheck.  O-1 was descoped.  Traffic use case is a partial flow that verifies the traffic steering decision.  First is without KPIMon.  Second phase in the Bronze maint. release will deliver the full flow.  O-DU high and low will communicate over FAPI and exchange one MAC message.  This is also timed for B maint. release.  For integration this is what we deployed for testing. The color coding represents different code implemented for different projects.  There are some pieces that are grayed out and will be deoployed in Bronze maint release.  We deployed two k8 clusters in the lab.  We deployed SMO real time one towards edge.  Status: We have completed two of the four flows A1 RIC healthcheck.  Long with more than 60 calls.  The long chain will interact with non Real Time down to A1 mediator and distributor to the Hello World xApp.  To support xApp near Real Time RIC complex flow passed.  
   15. Proposals for 4 flows deliverables.
       1. Lusheng would like to recommend option 1
       2. Lusheng requesting a vote from the TOC. 
       3. Jack: Floor is open for questions.
          1. Jack: if we go with where we are right now.  What percentage of work that's been tested.  All flows have not been tested.  There are only certain things that we can test.  It is driven by end to end flows.  When you say for the overall testing plan what percentage would you put on the testing overall.  What percentage of testing of flows will one week give you?
          2. Lusheng: We are between 80 - 90% Blocker is the alarm flow that is blocking the two healthcheck.  We are not able to complete the test however the dev teams were successful.  That is why I think it is a configuration mismatch and not a feature missing.  There is a feature missing but will be provided.  The one week extension will help us to complete the alarm process and we will have the 4 flows.  The alarm processing flow involves O1 mediator and Prometheus and Prometheus manager.  Prometheus are external components of the upstream so configuration is tricky.
          3. Jinri: if we can address can we include O-CU with the one week extension?
          4. Lusheng: The code will not be a part of testing. 
          5. Jack: Has the license scan been completed and accepted?
          6. Lusheng: Yes, LF attorney conducted a scan and came back with questions.  I distributed to the PTLs.  I have to pull that report and return to legal.  The issues have been resolved but we don't have LF legal final approval to release the code.
          7. Lusheng: We are putting together a Getting Started guide.  It is a work in progress.  We will have the test documentation and a video tutorial.  The video will be on the tutorial.  After the Bronze release will be off. the landing page.  The quick start will be for end users of how to configure and run.  What are the commands to run.  We have the first part all the way up to deploying near completion.
          8. Jinri: Have you considered a two week extension for safety?
          9. Lusheng: No I did not.  
          10. Jack: We try to stick as close to our schedule as possible because people will start moving into. the maintenance release.  We try to focus to validate through testing.  That is what is most useful to the software community vs. diving into code that they are not familiar with and they don't have a lot of support.  It's progress for the community but not for downstream users.  You still have to clean things up.
              1. finishing completing testing
              2. getting through scans
              3. make the getting started guide for people to understand what the Bronze release is all about.
              4. Let the team take on a host of issues for the maintenance release rather than working the team week to week.
              5. user-2057e agrees with Jack to complete in a week and clean up in the maintenance release.
              6. Ganesh and Juha agree.
              7. Jinri: The reason i raised the comment because I think O-CU is critical for the release.  If we have a two week window extension we can get the O-CU part done.  The code is ready and waiting to be uploaded.  If we can do it in two weeks we can include the O-CU.
              8. Jack: We should get it scanned and address the legal issues in time I doubt two weeks... It will either pass or need more time to resolve that will push into maintenance release.
              9. Jack: Martin Skorupski provide the status for the TR-69 adaptor is included.
              10. Lusheng: The previous scan did not include.
              11. Jack: Those are two items we should put on the list for the maintenance release.
   16. Vote: On motion by user-d3360 to move the Bronze release from 14 Jun 2020  to 21 Jun 2020 add one week extension to the Bronze release.  Delay the release by one week.
       1. Seconded by user-2057e
       2. VOTE: Vote taken, item passed
   17. Jack: Action/ Trishan: clear all the legal items for the code and figure out what is needed for the O-CU repo creation so the team can continue.
   18. Action user-d3360 provide Trishan with the O-CU repo trouble ticket.
   19. Action/ Jinri Huang generate an email to inform Zybnek and EC regarding that we will be delaying the release 
   20. Zhimin: We decided to release next week.  I have questions for development on the branch.  What is the way for us to implement.
   21. Lusheng: I will send out a separate email for the release and action items.
   22. Jack: For pieces that are complete as far as Bronze is concerned they can branch their code and move on to maintenance.
   23. Lusheng: Yes, the release process, 1 you need to make sure as PTL that the artifacts exist in release repo registries and not in staging.  2.  xApp descriptors contain a link to the docker image.  After that you can make the branch.  We will use the bronze branch.  All lower case for the branch name.  bronze will be the bronze name.  The repo owners can make the branch.  Please make sure the release notes in the repo docs section is up to date and contains the bug fixes in the release notes.  This is the high level process.  
   24. Jack: Everyone should update their bronze release table for features and capabilities so that it is on the web site as well.
6. Copyright updates

7. Marketing of the current release (WG, LF, PR)

   1. Bronze Release PR

   2. Virtual Exhibition.

   3. OSC Logo status.

8. Status of Open Action Items (Old Business)

   1. Action/ William DIEGO update on the coordination with the O-RAN test group
9. 1. Last week we discussed delaying Bronze for one week.  We had the press release.  We voted and approved the delay by one week.
   2. Lusheng; With the extension we have completed all the flows for the use cases.  We have started preparing for the release.  A wiki page has been created for tracking the remaining tasks.
      1. Repo must address all finding with the LF legal scan.  There were 3 findings.  2 offending references have been removed.  1 for O-DU project has a resolution but it will take some time.  The resolution will be on Thursday or Friday. After scan seed code 2 GNR scans have to be addressed.  Lusheng will address after O-DU scan has passed.
      2. Binary artifacts will be perpetual.
      3. All the repos must update their release
      4. Bronze branch will be released for all the code.
      5. We are between 80 and 90% completion level for all the remaining tasks.
         1. See Releasing Bronze Tasks to see how we keep track of where everything is.
         2. John Keeney: Which comes first the code or the release?
         3. Lusheng: We have completed one round of passing Bronze release testing.  Previously for the non real time RIC there it was yellow.  The last round of testing passed.  We will do another round of testing after the tasks are complete.
         4. Remaining tasks for Integration and testing teams. 
         5. We are also creating a Getting Started wiki page to stand up their own near real time RIC and non real time RIC.  We will also provide a video of the flows.
         6. We will have a Bronze Release Page
         7. Deferred to Bronze Maintenance Release
            1. US O-DU Low and O-DU High Use Case
            2. Full Traffic Steering Use Case
            3. RICApp xApp raising alarms Use Case
            4. O-DU-LOW CICD
            5. O-CU CICD
         8. Rittwik: This is pending the emulator decision because the input to the KPIMon is dependent on the emulator or else it is not a full traffic steering use case.
         9. Jinri: Where can I get these slides?
            1. Action/ user-d3360 send Jinri your status slides.
            2. Jack: I wanted to elaborate on the getting started.  I asked a team of people to take a look at the process of starting the procedure.  We found from other projects that it is easier to have a getting started page for new people who are not familiar with the project.
            3. How do we see updates before release and after release?
            4. The deadline for the release is Sunday 21 Jun 2020 
            5. Lusheng: The tarball is the source code for getting the branch at that moment.  The images are self service releasing.  What does it really mean when people release.  We will provide recipe files in the Getting Started.  After a repo has been released and more changes are needed we will maintain the head of the Bronze branch as much as we could.
         10. Given the current status user-d3360made a motion for a go or no go for the Bronze release. 
             1. On motion made by user-d3360 to officially release the Bronze code on 21 Jun 2020 
             2. seconded by Jinri Huang
             3. VOTE: Vote taken, item passed
10. Copyright updates
    1. Jack: O-RAN copyrite usage for O-RAN specifications.  
       1. Jinri: I was late to the last EC.  I will follow up with Zybnek.
       2. Jack: We have not gotten official closure for the vote.  Next week we will get the exact clarification.  On a related topic ETSE approved the O-RAN Alliance use of copyright.  In process and making progress for the O-RAN SC to have copyrights.

11. Marketing of the current release (WG, LF, PR)

    1. Bronze Release PR

       1. We are working through establishing some guidelines for that PR release.  Some of the feedback is we're trying to keep the statements refined.  I was asked to go back and ask the companies to trim to make a crisp statement with a blog are for extended information.  We are working through that with the EC and PR teams.

    2. Virtual Exhibition.

       1. Jinri: I don't have the progress.  I have not seen any email exchange between Zybnek, Paul and me.  Zybnek is working on online.  I will update the progress next time.
       2. Jack: It will come out along with the board meeting.  The opportunity to the community is to show off progress we are making in the O-SC.  It is a good place to show the O-SC software.
       3. John Paul: I heard 19 Jun 2020 is the last day for the deadline communication.
       4. Jinri: Gate 1 is to review.  Gate 2 is PR which has already past.
       5. John Paul: The submission of the actual demo deadline is this Friday 19 Jun 2020 .
       6. Juha: I see the deadline is 19 Jun 2020 
       7. Zhimin: Intel has not given feedback for the PR.  Is it already tracked?
       8. Jinri: It is already tracked.  I forwarded it to Zybnek.
    3. OSC Logo status.

12. Status of Open Action Items (Old Business)

    1. Action/ William DIEGO update on the coordination with the O-RAN test group
       1. https://oranalliance.atlassian.net/wiki/spaces/TTIFG/pages/480542932/1.0+Draft.
       2. William: I will continue to attend the ETE meetings.
    2. Action/ Farheen point to the F2F meeting from the Events page to O-RAN Alliance's latest spreadsheet.
       1. We had some OSC meetings on this topic.  One was a F2F of all the WGs.  Well over 100 participants attended.  We had a second one on a more detailed discussion on the emulator activities.  We made a presentation and discussed the values.
    3. Action/ Vishnu send Rittwik the slides for the ITU / AiML Challenge
       1. Jack: We did not do too much 
    4. Action/ Rittwik: Post ITU / AiML Challenge slides on the wiki and pull together a team.  Include Thoralf.
       1. Rittwik: I would like to know where we are with Viavi simulator?
       2. Jack: It is at the EC level.  They have been very busy the last few weeks.  It is on the agenda but we have not come to a resolution or a vote at this time.
       3. Jinri: Several EC members had dropped the meeting and not enough time to discuss.  Tomorrows EC call this has been put at the top priority.  The EC members have reviewed the documentation late so they postponed it to tomorrows call.
       4. Jack: More complicated because of the Virtual F2F.  
    5. Action/ Rittwik: I will set up a meeting for ITU AI/ML and pull together a team.
    6. Action/ Trishan: clear all the legal items for the code and figure out what is needed for the O-CU repo creation so the team can continue.
    7. Action/ user-d3360 provide Trishan with the O-CU repo trouble ticket.
       1. The repo was created and since then O-CU has uploaded the code and merged.
       2. Jack: The key is to get that repo added to the analytics page.
       3. Trishan: It should be available after 6 hours of adding the 
    8. Action/ Jinri Huang generate an email to inform Zybnek and EC regarding that we will be delaying the release 
       1. Jack: Action/ Jinri Huang notify the EC that the Bronze release has been voted on and approved.
       2. Jack: We'll start planning for Cherry and Bronze Maintenance release.  We want to look at the end to end use cases that will align the community and O-RAN Alliance forward.  I need to ask for people to look at the requirements and test teams.  Those teams have done two releases and are small.  Typically on projects we rotate people.  We will need new people to step up for the Cherry release or else we won't be able to do all the testing.  It is imortant for all the oprators, vendors, and participants in the community and look to contribute and find a place where everybody an pitch in.  Requirements, Inetgration and Test and requirements will be pulling this all together.  These up front and back end teams need participation with the community ore las we will have do more testing.  I asked the other TOC members to take time to see if there is any where they can contribute.
       3. Jack: We are at the end of our meeting and thanked the team.  DU High and Low made significant progress to make the end to end flow.  We have new code coming in from two areas like TR69 and O-CU code that will bring functionality.  We are looking to Cherry to add more O1 and A1 support so it looks lie a system and not just stand alone parts.  I look forward to new projects such as the SMO work.  There is still a lot to do and participate.  I wanted to thank everybody for all the progress and look forward to watch Cherry

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

    1. Release

    Standing Agenda Items (Brief Status of Ongoing Activities)

    1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling

       1. Bronze Timeline

       2. Review Bronze Release Highlights

    2. user-59b16 Requirements Software Architecture Committee

    3. user-d3360  Integration and Test

    4. Report out from PTL: Stand-Up & Report Out on Blockers - next week we will start to cover this list.  Are there any major items that anyone would like to raise to the TOC this week? 

       1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)

       2. Matti Hiltunen RIC Applications (RICAPP) 

       3. Thoralf Czichy RIC Platform (RIC)

          1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)

       4. user-a934b O-RAN Centralized Unit (OCU) 

       5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)

       6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)

       7. Martin Skorupski Operations and Maintenance (OAM)

       8. Alex Stancu Simulations (SIM)

       9. Xiaohua Zhang Infrastructure (INF)

       10. weichen ni Documentation (DOC)

       11. (TBD) O-RAN Radio Unit (ORU)

14. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items. 

15. Planning for Next Meeting

16. Any Other Business (AOB) 

17. 1. 1. 1. -05-12" in Bronze Release (Jun 2020)

       2. user-a934b O-RAN Centralized Unit (OCU) 

       3. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)

       4. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)

       5. Martin Skorupski Operations and Maintenance (OAM)

       6. Alex Stancu Simulations (SIM)

       7. Xiaohua Zhang Infrastructure (INF)

       8. weichen ni Documentation (DOC)

       9. (TBD) O-RAN Radio Unit (ORU)

18. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items. 

19. Planning for Next Meeting

20. Any Other Business (AOB) 

21. Meeting Summary (resolutions, new action items, etc.)

    1. Votes:
       1. The minutes of the prior meetings were reviewed, and no corrections.
          1. Vote to approve minutes for 10 Jun 2020 
          2. On motion made by John-Paul
          3. Seconded by Juha Oravainen
          4. VOTE: Vote taken, item passed
       2. Given the current status user-d3360made a motion for a go or no go for the Bronze release. 
          1. On motion made by user-d3360 to officially release the Bronze code on 21 Jun 2020 
          2. seconded by Jinri Huang
          3. VOTE: Vote taken, item passed
    2. Actions:
       1. Action/ William DIEGO update on the coordination with the O-RAN test group
       2. Action/ Jinri Huang notify the EC that the Bronze release has been voted on and approved.
       3. Action/ user-d3360 send Jinri your status slides.

    Meeting Summary (resolutions, new action items, etc.)

    1. Votes
       1. The minutes of the prior meetings were reviewed, and no corrections.
          1. Vote to approve minutes for 03 Jun 2020 
          2. On motion made by Jinri Huang
          3. Seconded by Juha Oravainen
          4. VOTE: Vote taken, item passed
       2. On motion by user-d3360 to move the Bronze release from 14 Jun 2020  to 21 Jun 2020 add one week extension to the Bronze release.  Delay the release by one week.
          1. Seconded by user-2057e
          2. VOTE: Vote taken, item passed
    2. Actions
       1. Action/ William DIEGO update on the coordination with the O-RAN test group
       2. Action/ Farheen point to the F2F meeting from the Events page to O-RAN Alliance's latest spreadsheet.
       3. Action/ Vishnu send Rittwik the slides for the ITU / AiML Challenge
       4. Action/ Rittwik: Post ITU / AiML Challenge slides on the wiki and pull together a team.  Include Thoralf.
       5. Action/ Rittwik: I will set up a meeting for ITU AI/ML and pull together a team.
       6. Action/ Trishan: clear all the legal items for the code and figure out what is needed for the O-CU repo creation so the team can continue.
       7. Action/ user-d3360 provide Trishan with the O-CU repo trouble ticket.
       8. Action/ Jinri Huang generate an email to inform Zybnek and EC regarding that we will be delaying the release 

Archived Meetings