Technical Charter for O-RAN Software Community

2020 04

07

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		Lusheng Ji
   China Mobile	Jinri Huang Co-Chair		Weichen Ni
   Deutsche Telekom	David Streibl		Ondřej Hudousek
   NTT DOCOMO	Masafumi Masuda		Anil Umesh
   Orange	William Diego		Vincent Danno
   Verizon	Viswa Kumar		Skand PriyaKristen Young
   Nokia	Juha Oravainen
   Radisys	Ganesh Shenbagaraman
   Ericsson	John-Paul Lane

   *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. Email from OAI
Lusheng: I would like to request a time slot during the 04/01 ToC weekly meeting to present the current plan for integration and testing Bronze release.
It will take about 5 minutes.
6. Release Votes and Approval
7. Marketing of the current release (WG, LF, PR)
   1. ONES = LF Networking Conference tentatively August/ September (Los Angeles).  Open Networking & Edge Summit Event
 
8. Status of Open Action Items (Old Business)Jack - How does the OSC evolve from where we're at.  Every piece is under construction.  O-DU Emulation will help with that.
   1. Action/ new TOC members provide an alternate contact for TOC calls when they are unable to attend. 
   2. Action / ENGWEI KOO  - will add  / ENGWEI KOO  - will add a deck to RSAC wiki.
   3. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
   4. Action / Tracy Van Brakle clarify Open Testing and Integration (OTIC) North America 
   5. Action/ Farheen Cefalu work with Tracy Van Brakle to update the events page with plugfests. 
   6. Action/ user-59b16 upload the UE emulator short/long term slide deck to the RSAC page.
   7. Action/ TOC provide feedback to Jack regarding the Cherry and D Release calendars on the Releases page
   8. Action/ Jinri Huang will point Thoralf Czichy to the appropriate WG specification times.  There are 3 trains for the specifications.  
   9. Action/ user-2057e update Vote Release Name page with the D release name options.

      1. you can now vote on name for release D here: https://wiki.o-ran-sc.org/display/REL/Vote+Release+Name

   10. Action/ Jinri Huang provide the TOC with the new O-RAN Alliance timeline.
   11. Action/ Trishan de Lanerolle let us know the outcome of the ticket that John Keeney  opened regarding the Calendar synchronization.
   12. Action/ PTLs update your project summaries with your sprint 2 status updates.  Be prepared to review your sprint 2 deliverables with the TOC.
   13. Action/ Jack will review Thoralf's How to request committer changes
   14. Action/ user-d3360 add the wiki link for SONAR to the Integration and Test wiki where people can easily find.
   15. Action/ user-59b16 set up a meeting with Viavi, O-RAN Alliance test committee (whoever is leading the test committee (David Orloff)), and the TOC.  
   16. Action/ William DIEGO  we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups 
   17. Action/ user-d3360 add the link in the Integration and Test wiki to the SONAR instructions that you discussed on 25 Mar 2020 TOC meeting.
   18. Action/ PTLs provide user-d3360  with your sprint 2 demos. 
9. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
      1. Project Bronze Release
   2. 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. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
         1. note I updated the committer change process as per discussion last week: How to request committer changes.
      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 ni Documentation (DOC)
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
   3. user-59b16 Requirements Software Architecture Committee
   4. user-d3360  Integration and Test
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.)

2020

04 01

Audio Recording: 0202020-0304-25-toc-audio_only.m4a01_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		Skand Priya

   Nokia	Juha Oravainen	x
   Radisys	Ganesh Shenbagaraman	x
   Ericsson	John-Paul Lane	x

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

   1. TOC Membership has increased.  It has been one year of the O-RAN-SC.  
   2. Action/ new TOC members provide an alternate contact for TOC calls when they are unable to attend.

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. Jinri found typos and will discuss with Farheen offline. 
      2. Vote Vote to approve minutes for 18 25 Mar 2020 
      3. On motion made by Jinri Huang
      4. Seconded by user-2057eWilliam DIEGO
      5. VOTE: Vote taken, item passed
4. Review of Today's Agenda
   1. Email from OAI
      Jack - Next week will be our first meeting of April. We will cross over completion of our first year as our open source community.  Thank you to everyone who supported the projects and contributed.  We will be transitioning to add 3 additional members to the TOC.  We will move to a 9 members of the TOC.  They will be introduced next week
      1. Jack needs to share that Jinri and Jack received an email from Open Air Interface with concerns with this project.  Jack forwarded the email to the legal team to review.  Jack will be able to address when he has clarification from legal.
      1. Lusheng: I would like to request a time slot during the 04/01 ToC weekly meeting to present the current plan for integration and testing Bronze release.
         It will take about 5 minutes.
   2. Release Votes and Approval
   3. Marketing of the current release (WG, LF, PR)
      1. Jinri - Nothing to report for marketing.
         1. Jack - We have to talk about  how to broaden our communication to the broader community.  We have to educate and communicate progress and activities.  We will have to get back to this at some point.
      2. ONES = LF Networking Conference tentatively August/ September (Los Angeles).  Open Networking & Edge Summit Event
 
      3. Virtual O-RAN demo was about to be activated.  The site has been constructed and is being reviewed by EC.  Will notify Farheen when the site is public.  There are around 20 demos.ONES = LF Networking Conference tentatively August/ September (Los Angeles).  Open Networking & Edge Summit Event
 
   4. Status of Open Action Items (Old Business)Jack - How does the OSC evolve from where we're at.  Every piece is under construction.  O-DU Emulation will help with that.
      1. Action / ENGWEI KOO  - will set up a meeting with  Tracy Van Brakle , Martin Skorupski John Keeney , and Alex Stanc to discuss O-1 interface options with Viavi.
         1. Rittwik - 7a and 7e relate to work with Viavi.  
         2. Jack - 7a was to discuss O-1 functionality and how there work will impact.
         3. Engwei - John, Martin, and High Street met on how O-1 testing is required here.  We concluded that there will be further dicussions for use cases. requirements for simulators.  What measurements and pm counters over to RIC for dynamic traffic steering.  We discussed E-1.  From Viavi we will make sure we are tracking the team.  John mentioned the need is for the Cherry release and anything for the Bronze.  Thanked the team for bringing Viavi up to speed.
         4. Action / ENGWEI KOO  - will add a deck.  Looking at the swim lane tables to track how Viavi will 
      2. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
      3. Action / Tracy Van Brakle clarify Open Testing and Integration (OTIC) North America 
      4. Action/ Farheen Cefalu work with Tracy Van Brakle to update the events page with plugfests. 
      5. Action/ user-59b16 update TSC with the short/long term UE emulator support.  
         1. Rittwik - sharing slide of what is needed for the short term.
         2. Action/ user-59b16 upload the slide to the RSAC page.
      6. Action/ Jack will update the O-RAN SC release timeline with Cherry and D release.
         1. Jack - Reviewed Releases page.  Action/ TOC provide feedback to Jack regarding the Cherry and D Release calendars on the Releases page
         2. Rittwik - WG input requirements from 14 - 20th of June.  Not sure that WG3 requirements will be done by then.
            1. Then we won't use them.  We can't be constantly changing so developers don't know what to build.  If we don't have then we will rework the use cases.  We can shift things a little.  The timelines are aggressive enough without changes.
            2. Rittwik - Please bring this chart up on this point to the TSC.  
            3. Jack - If it's not in the Cherry Release then it will get into the plan for D but won't happen until a year later.
            4. David - What do you mean by working group input freeze?
               1. Jack - We've been asked to coordinate with the O-RAN WGs.  We have Bronze release touchpoints.  The goal was to look for WG input.  When we complete our planning we will do a review with them.  We have a touch base twice.  Dev Sprint 4 ends 4-26.  We will give a demo of the functionality we plan to release.  In this case it's Bronze.  For Cherry I added the comment that we'd be freezing what specifications we'll be working with. 
               2. Thoralf - There is a difference between specifications.  
               3. Jinri - The freeze is not the freeze of specs.  We recognize at this time the latest spec we have from WG.
               4. In week 21 we will use version spec 2.1 that O-RAN Alliance is expecting to release in week 23.
               5. Jack - we agree on which specs we are working.  I'll be happy to use a different word than "freeze".
               6. Action/ Jinri Huang will point Thoralf Czichy to the appropriate WG specification times.  There are 3 trains for the specifications.  
               7. Jack - We need to figure out how to align.  I expect they will be in the same release window.
                  1. Rittwik - We will face challenges with the current situation.
                  2. Jack - Each release has it's own set of decisions.  We can stretch out a little bit.  If we stretch out in ETE testing then we have stretch.  The community can review if we provide it to the TOC.
      7. Action/ user-2057e update Vote Release Name page with the D release name options.
         1. David - There are very few colors with the word D in it.  It will be a fairly short list to avoid the "dark"  and "deep" colors.
      8. Action/ Jinri Huang will provide Jack with the WG2 and WG3 adjusted timeline for Cherry and D release.
      9. Action/ Jinri Huang provide the TOC with the new O-RAN Alliance timeline.
      10. Action/ Thoralf Czichy share the OSC Alignment Aspects slides with Jack.  We have means to align with WG3.  Rittwik - We need a timeline chart for C and D.  We need to know our timelines of what is at stake.  We need this for all WGs.
      11. Action/ Tracy Van Brakle  Trishan de Lanerolle set up a call with Jack and David because the Community asked for a release manager.
          1. Jack - will continue the discussion to see how we can improve.  We're a young community.  Some of our needs are different than other communities.  As a community if people find better ideas, or ways to do things bring them to the PTL or the TOC.  There may be things we can learn and get better at.
      12. Action/ John Keeney open a trouble ticket with LF for the Confluence calendar issue.
          1. Action/ Trishan de Lanerolle let us know the outcome of the ticket that John Keeney  opened regarding the Calendar synchronization.
   5. Standing Agenda Items (Brief Status of Ongoing Activities)
      1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
         1. Project Bronze Release
         2. We are in the sprint 3.  
         3. Action/ PTLs update your project summaries with your sprint 2 status updates.  Be prepared to review your sprint 2 deliverables with the TOC.
         4. Next week we will spend more time with each PTL.  Be prepared to inform us on what the projects have completed in sprint 2.
      2. 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. Matti Hiltunen RIC Applications (RICAPP) 
         2. Thoralf Czichy RIC Platform (RIC) 
            1. note I updated the committer change process as per discussion last week: How to request committer changes.
            2. Action/ Jack Review Thoralf's How to request committer changes
            3. Committers don't require a TOC votel.  
         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 ni Documentation (DOC)
         10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
         11. (TBD) O-RAN Radio Unit (ORU)
      3. user-59b16 Requirements Software Architecture Committee
         1. We will be starting Cherry.
         2. We need the Viavi simulator.
         3. Jack - Pulling together the overall stack it is important to show pieces evolving and their progress.
         4. Lusheng - we have one and a half development sprints left before the testing cycle starts and the simulator plays a very important role.  We would like to have the simulator sooner than later is preferred.
            1. Jack- As people know we have a plan and we have decisions with the broader TOC.
         5. Jack - David - Was there any update with the test focus group?
            1. David - William was working on that task.
            2. William - We are working on test and integration specification.  Work is ongoing. Orange will provide input next week.  We have made good progress.  The aspects from Open source simulations could be interesting.
               1. Jack - Has that group provided a plan for simulation?
                  1. William - Yes, Viavi is leading the test and integration focus group.  They have great suggestions.  We are trying to work with them to organize interfaces it will be a key aspect.  We are trying to get more input from other WGs to understand their specifications and we are taking their needs into account.
                  2. Jack - Action/ William DIEGO work with user-59b16 and set up a meeting with whoever the leadership is in the test committee so we are synchronized with the other TOC members.  The key is to get some of the decision makers from the test group so we can have their input.
                  3. Action/ user-59b16 set up a meeting with Viavi, O-RAN Alliance test committee (whoever is leading the test committee (David Orloff)), and the TOC.  
      4. user-d3360  Integration and Test
         1. In terms of code quality.  LF is using SONAR Cloud to report unit test coverage.  The integration team is providing  the sample repo set up to set up your code and publish to SONAR cloud.  Captured in the wiki page.  If you are a PTL you can work with your committers to add SONAR to the projects.
            1. Where can people find examples?
            2. Action/ user-d3360 add the wiki link in the Integration and Test.
            3. Post it on the integration and test wiki.
         2. Sprint demos: We have simulation and OAM have completed their demos.  The non Real Time did not have significant things to demonstrate.  Near real time will demo next Thursdays. 
            1. Action/ PTLs provide user-d3360  with your sprint 2 demos. 
            2. Demo activities are important and required to keep the overall project and stakeholders in synch. 
   6. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items. 
      1. Jinri Huang  - I saw an O-CU approval with two votes has that been closed?
         1. The PTL will raise it if it is an issue.  
      2. weichen ni  - There is a new request by documentation to create an API document.  Suggest each PTL to use an API document.  Be sure it generates a weblink to create a page in the docs.
         1. Where will the html be hosted?
            1. https://docs.o-ran-sc.org/en/latest/
            2. Weichen - you can put your api documentation in your repos docs directory and I will generate the html.
            3. Standardize the tools we use so we have a common set of tools.
   7. Planning for Next Meeting
   8. Any Other Business (AOB) 
   9. 1. add a deck to RSAC wiki.
      2. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
      3. Action / Tracy Van Brakle clarify Open Testing and Integration (OTIC) North America 
      4. Action/ Farheen Cefalu work with Tracy Van Brakle to update the events page with plugfests. 
      5. Action/ user-59b16 upload the UE emulator short/long term slide deck to the RSAC page.
      6. Action/ TOC provide feedback to Jack regarding the Cherry and D Release calendars on the Releases page
      7. Action/ Jinri Huang will point Thoralf Czichy to the appropriate WG specification times.  There are 3 trains for the specifications.  
      8. Action/ user-2057e update Vote Release Name page with the D release name options.

         1. you can now vote on name for release D here: https://wiki.o-ran-sc.org/display/REL/Vote+Release+Name

      9. Action/ Jinri Huang provide the TOC with the new O-RAN Alliance timeline.
      10. Action/ Trishan de Lanerolle let us know the outcome of the ticket that John Keeney  opened regarding the Calendar synchronization.
          1. Should we set a single to a common time zone?
             1. projects use UTC.
                1. Find the best solution to the problem.
      11. Action/ PTLs update your project summaries with your sprint 2 status updates.  Be prepared to review your sprint 2 deliverables with the TOC.
      12. Action/ Jack will review Thoralf's How to request committer changes
      13. Action/ user-d3360 add the wiki link for SONAR to the Integration and Test wiki where people can easily find.
      14. Action/ user-59b16 set up a meeting with Viavi, O-RAN Alliance test committee (whoever is leading the test committee (David Orloff)), and the TOC.  
      15. Action/ William DIEGO  we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups 
      16. Action/ user-d3360 add the link in the Integration and Test wiki to the SONAR instructions that you discussed on 25 Mar 2020 TOC meeting.
      17. Action/ PTLs provide user-d3360  with your sprint 2 demos. 
   10. Standing Agenda Items (Brief Status of Ongoing Activities)
       1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
          1. Project Bronze Release
             1. Rittwik - In the virtual F2F most of the projects met with their working group reviews.
             2. Jinri - Sees a gap in Cherry.  Overlap of WG.
                1. Jack - We have our ETE use cases that drive what we focus on in a release.  Right now we have two.  Traffic and self-test.  Think of it as something that is driving RAM functionality and OAM functionality.  Consider those and other tracks that are meaningful at pushing our community agenda.  The RSAC committee can provide the specifications that are changing in the window.  People that are interested please engage and help drive what are the important functionality.  C and D are important releases in delivering and driving value.  It is important that everyone get involved and the use cases in the C and D releases drive value to the O-RAN community participants and service providers otherwise we have to question whether we are going down the right path.  Please get involved and help us get there.  Let us see what we can do with the RSAC committee and see if our specs are frozen to make recommendations.
       2. 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. Matti Hiltunen RIC Applications (RICAPP)
             1. We are working on 6 xapps.  4 are traffic steering, 1 demo, 1 measurement campaign xapp.
                1. Is there a simulator requirement?
                   1. Even if we decide to go with Viavi I don't think they committed to the E2 interface.
                      1. The strategy was to get offline data.  If that is available we can replay the E2 simulator.
                         1. Are there committed resources?
                            1. Alex - This is an open issue no one has volunteered.
                         2. How can we help?  Who can step up and work with Alex to get this critical part done?  Is Viavi incremental to this need?  Is it available in this time frame? 
                            1. Not E2, we want the metric that the EU and DU can provide.  
                            2. RAN simulation data is critical.  We can work the E2 delivery in parallel.  
                            3. Is the simulator critically needed or not?
                               1. If we are using the RIC platform and we use the KPI.  We say we are using e2 then we need the simulator.  If we by pass e2 and kpi mon then we can populate the SDL layer.
                            4. Jack - yes it's needed.  Is there anyone on the call who can step up and help in this space?
          2. Thoralf Czichy RIC Platform (RIC) 
             1. note I updated the committer change process as per discussion last week: How to request committer changes.
          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 ni Documentation (DOC)
          10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
          11. (TBD) O-RAN Radio Unit (ORU)
       3. user-59b16 Requirements Software Architecture Committee
          1. David Kinsey, Rittwiki, RSAC team discussed one Dynamic (performance mgt.)  data collection set agenda pushed to ONAP.  It is the responsibility in SMO.  There is no SMO project. We are submitting. 
             1. Action user-59b16 add Martin Skorupski to conversations around dynamic data collection.
             2. Is there a cutoff point this week for your requirements because the ONAP G release gate is closing.
                1. Rittwik - Yes, we are working on the requirements.
                2. Action/ user-59b16 send @John Paul Lane from Ericsson the RSAC requirements.
          2. WLF files?  Zhimin Yuan we are in the process. 
          3. Will that happen once we do the integration
             1. We are preparing for the Bronze relase.
       4. user-d3360  Integration and Test
          1. Plan for Integration and Test 
             1. We have one development sprint left.  First we will do integration in two separate groups.  
             2. ODU Low and ODU high and
             3. OTF, OAM, NONRT RIC, Near RT RIC APP, SIM (Cloud), INF, O-DU LOW, O-DU High, SIM (Bare metal deployment)
             4. Integrated testing is lead by each PTL.  Every project is delivering multi-containers.  They are expected to do their own integration testing.
             5. Pairwise testing requires a need to interact.  Next level is our use case testing.  We will have a working session call and try to run the integrated testing together.
          2. How we will execute (be mindful of automated cleaning process) 
             1. We have a Nexus Staging Docker Registry (images on this registry only live for 30 days) after that an automated cleaner will remove.  There are ways to regenerate but keep the 30 day limit in mind.  
             2. merge jobs are automatically run weekly, which keeps images fresh in the staging registry :)
             3. There is a container tag.
             4. Nexus Release Docker Registry.  Images on release repo live "forever".  Images on release registry CANNOT be overwritten.
          3. Lusheng proposing to formally adopt semantic versioning for tagging released O-RAN docker containers.  After passing the component communicate through wiki, lists, and jira.
   11. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items. 
   12. Planning for Next Meeting
   13. Any Other Business (AOB) 
   14. Meeting Summary (resolutions, new action items, etc.)Meeting Summary (resolutions, new action items, etc.)
   15. Votes: 
       1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
          1. Jinri found typos and will discuss with Farheen offline. 
          2. Vote to approve minutes for 18 Mar 2020 
          3. On motion made by Jinri Huang
          4. Seconded by user-2057e
          5. VOTE: Vote taken, item passed
   Actions:
   16. Action / ENGWEI KOO  - will add a deck to RSAC wiki.
   17. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
   18. Action / Tracy Van Brakle clarify Open Testing and Integration (OTIC) North America 
   19. Action/ Farheen Cefalu work with Tracy Van Brakle to update the events page with plugfests. 
   20. Action/ user-59b16 upload the UE emulator short/long term slide deck to the RSAC page.
   21. Action/ TOC provide feedback to Jack regarding the Cherry and D Release calendars on the Releases page
   22. Action/ Jinri Huang will point Thoralf Czichy to the appropriate WG specification times.  There are 3 trains for the specifications.  
   23. Action/ user-2057e update Vote Release Name page with the D release name options.
   24. Action/ Jinri Huang provide the TOC with the new O-RAN Alliance timeline.
   25. Action/ Trishan de Lanerolle let us know the outcome of the ticket that John Keeney  opened regarding the Calendar synchronization.
   26. Action/ PTLs update your project summaries with your sprint 2 status updates.  Be prepared to review your sprint 2 deliverables with the TOC.
   27. Action/ Jack Review Thoralf's How to request committer changes
   28. Action/ user-d3360 add the wiki link for SONAR to the Integration and Test wiki where people can easily find.
   29. Action/ user-59b16 set up a meeting with Viavi, O-RAN Alliance test committee (whoever is leading the test committee (David Orloff)), and the TOC.  
   30. Action/ William DIEGO  we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.
   31. Action/ user-d3360 add the link in the Integration and Test wiki to the SONAR instructions that you discussed on 25 Mar 2020 TOC meeting.
   Action/ PTLs provide user-d3360  with your sprint 2 demos. 

   Return to Todays Agenda ^

   Archived Meetings