Technical Charter for O-RAN Software Community

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

VOTE for the B Release!

2019 11 06

Agenda

1. Call for Scribe (minutes owner)

2. Roll Call & Quorum Check 

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

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

3. Review and Agree to Minutes of Previous Meetings
4. Review of Today's Agenda
5. Marketing of the Amber release (WG, LF, PR)
6. Status of Open Action Items (Old Business)
   1. Action/ Community Vote for a "B" Release Name
   2. Action / Farheen Cefalu send out a note of when we have to have our votes in by.
   3. Action / Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
   4. Action/ Jinri Huang  will add the F2F meeting minutes to the events page.
   5. Action/ John Murray to work with OAI interface.
   6. Action/ John Murray closing the remaining the TOC slots. 
   7. Action/ user-d3360 add the link of the Jenkins instructions from the the Jenkins status page to the top of the Project Readiness for Amber Release wiki page.
   8. Action/ weichen ni  will provide PTLs with the steps that they need to view their converted docs on the docunmentation wiki.  He will add the link to the top of the Project Readiness for Amber Release .
   9. Action/ Each PTL write up a small clear statement about their license attribution that they can post to the email list. 
7. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager/Release Planning: Weekly TOC Scheduling
   2. user-d3360 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)
         
         1. request to approve one new repo and committer changes for two existing repos as per this e-mail
      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)
   4. user-59b16 Requirements Software Architecture Committee
8. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
9. Planning for Next Meeting
10. Open Discussion
11. Any Other Business (AOB) 
12. Meeting Summary (resolutions, new action items, etc.)

2019 10 30

Zoom meeting: 2019-10-30-toc_audio.m4a

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu

2. Roll Call & Quorum Check 

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

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

3. Review and Agree to Minutes of Previous Meetings
   • The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
   • Vote to approve minutes for 23 Oct 2019 
   • On motion made by Jinri Huang
   • Seconded by MASAFUMI MASUDA
   • VOTE: Vote taken, item passed
4. Review of Today's Agenda
   1. What is the status of the F2F?
5. Marketing of the Amber release (WG, LF, PR)
   1. We need a TOC lead for getting the PR in place for approval for both the O-RAN Alliance and Linux foundation.
      1. Jinri will take the lead and will need support from others.
      2. LF does not want to give away what is on the next release.  They don't want to lose the momentum if discussed ahead of time.  
      3. Particpate in the opportunity to volunteer your company from a technical stand point.  Contact Jinri Huang if you are interested.
6. Status of Open Action Items (Old Business)
   • Status of Naming releases "B" and "C"
     • Action/ Community Vote for a "B" Release Name
     • Action / Farheen Cefalu send out a note of when we have to have our votes in by.
   • Amber Release PR
   • Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video. 
     • Nothing new everything is a  in progress.  We set up a few VMs.
   • Tracy Van Brakle will send out an email to TOC mail list.  We are not going to keep score or pass fail.
   • Jinri Huang will upload presentations and minutes under Events page on the wiki of the face to face meeting. 
     • Jinri set up a new file list under the events page and set up a new Costa Rica.
   • user-59b16  reach out to Jinri Huang for slides.
   • Action/ Farheen Cefalu remind Jack about how we want to arrange the events page with O-RAN Alliance slides.
   • Action/ Trishan de Lanerolle provide a report to John Murray of the analytics around contributions of the Amber release.
     • Tristan talked to the team in the LF and there is a system they will have online by November 1 this Friday.  They moved us up in the que.
       • Trishan - we will have something by next week.
         • There will be a tool on the wiki for people to generate reports to see the contributions being made.  Not biturgia but this is a tool that LF has brought online that will be supporting our project.
           • Similar to a beta version of bitergia.
             • When we say we will provide the analytics around the Amber release how up to date will it be?
               • It will be real time and you can time box it.
                 • Our goal is to have this available by next week.
   • Call to Action/ PTLs give a status report for release preparation.  Action/ user-d3360 post the request through mail list.
     • Lusheng - PTLs are providing the reports it is in progress.  We will review in the standing agenda today.
   • Summarize Face to Face meeting.
     • Presentation is online. 
     • Jinri Huang  will add the F2F meeting minutes to the events page.
     • Action to work with OAI interface.
     • Action Closing the remaining the TOC slots.  It is an interaction with the O-RAN Alliance.
7. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Last week of code sprint.  We have extended the code release that is coming to a close at the end of this week.  That will cap our contributions for the Amber release at the end of November.  There will be a window to branch the code and work to have the repos that build to a working project.  We have a code freeze which will become our primary branch.
         1. Peter from Samsung asked for the status.  We asked Thralf for code clean up.  This week is the last week if that kind of functionality is not in the repo the is the E2 interface feature included in the Amber release?
            1. Thoralf - You were concerned about the E2 manager.  They have been filled.  They should be there.  Source code is in the repo in the Amber release.
               1. Have any repos been withdrawn?
                  1. Anything that has to be brought back were brought back.  Lusheng will you talk about the projects?  We will see the status for that.
   2. user-d3360 Test & Integration Planning (INT)
      1. Lusheng and PTLs created Project Readiness for Amber Release to track the release.
         1. Near Realtime RIC Platform - first there is the legal part of the requirement.  No proprietary contributions. 
         2. LF provided the initial license scanning for our repos.   
         3. Next column is for code status.  We want to have buildable code into binary artifacts.
            1. Can you check the CI Integration?
               1. Yes there is a jenkins status page.
                  1. Action/ user-d3360 add the link to the instructions for the Jenkins status page at the top of the Project Readiness for Amber Release wiki page.
         4. Documentation column is for developer to developer documentation contributions.  Ideally if we follow the structure of the documentation project there are jenkins jobs that will scan the repos and convert to html readthedocs site.  
            1. As a PTL how do we know that our docs have been built.
               1. weichen ni  we have a test project.  Action/ weichen ni  will provide PTLs with the step that they need to view their converted docs.  Add the link to the top of the Project Readiness for Amber Release.
         5. It is up to the PTL if they want to do a video demo.
            1. The project should decide how they want to do that.  This is guidance.  Make sure it is understandable, clean and simple.  Don't turn it into a grueling activity.  Make it clean and understandable and usable.
            2. Record a terminal session explaining in your voice.  The written docs will be there for the devleoper community.  This can become your marketing or presentation materials.
         6. Questions?
            1. Zhimin Yuan  who will do the jenkins job definitions?
               1. Jenkins jobs are assigned per repo.  Anybody can define the job.  The job will be accepted by the LF engineers and added to the jenkins server.  Anybody can write the job definitions.  There is a repo called ci-management in the gerrit.  That is the repo for hosting all the jenkins job definitions.  The integration and test following this meeting I did not put down agenda.  We can make that into a tutorial. 
               2. Action/ user-d3360 record the tutorial. 
            2. Chris Lott  can support the CI process.
            3. weichen ni  doc follows another license not apache or O-RAN.
         7. During next weeks call we will plan for the repos that do not reach all the checkmarks on the Readiness wiki page. 
      2. Linux foundation scan results Lusheng sharing a spreadsheet from LF of the scanning of the code marked in red and yellow that need to be addressed.  There are also some action items and issues to review.  Our projects original source code is Apache 2.  Those that are not need further discussion.  The ones in red are binary files.  gerrit or git is not a tool for binary files.  LF requirement is not to have binary files in their gerrit repos.  Copyleft are unfriendly open source licenses.  We have to remove the copyleft items.  Lusheng will reach out to the PTLs.  Attribution needs TOC action because our charter says Apache 2 CC4, or O-RAN license.  We can fork other open source licenses.  FS, FAP, ETF, X11, MIT.  We need TOC decision if we can use these licenses.  Do not mix these licenses with the O-RAN SC.
         1. Jack - I want structure because it's an exception.  Action/ Each PTL write up a small clear statement that they can post to the email list.  We will get them on the agenda Farheen Cefalu at the next meeting.  We want to support the right answer but don't want to leave the door open.  It should be done consciously and documented by each PTL so it is clear.  Farheen Cefalu include this in Best Practices.
            1. Peter - Is there guidance from O-RAN SC for license?  I see there are some issues may be raised by other corporations developed on top of O-RAN.
               1. Jack - We may have to hold a special meeting to go through this.  There are friendly and un-friendly licenses.  Let us follow up and have that discussion.  It is a concern when you're using certain licenses.  This is a very high priority for the LF and TOC.  We need to address these items for the project to reach release status.  Please work with user-d3360. 
               2. Does this have effect on CLA?  That was signed for the Apache license.  We need instructions how you are supposed to handle these files and license.  
               3. Jack - get this on top of our list of things to address.  Let's work through the process.
               4. user-d3360  forward the license scan spreadsheet to the PTLs.
         2. No license found.  If it is a file that is inside the project then it should be marked with a license.  If it's an external file then put it in an external folder.
   3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Action/ Jack will move the order of the agenda by moving Test to the top during the release process. 
      2. Matti Hiltunen RIC Applications (RICAPP) 
      3. Thoralf Czichy RIC Platform (RIC)
         1. there was this vote (on moving the code freeze to Nov-4) in the Oct-09 ToC meeting: "There is a formal request. In the Amber release this schedule was ambitious process. One of the goals is to get people to get familiar and start contributing. Code freeze is supposed to occur at the end of this week. The developers enter a maintenance cycle. To get a release out we add a maintenance release. So the developers can continue to fix defects while everyone plans on what the new features are in the B release. This next window October 14 - November 2 is time to work on fixing bugs on the software only for this release. We should allow this extension because there is not enough code to do end to end testing." I am not sure how to interpret this. But is my understanding correct that after Nov-4 (the code freeze date) we will have a two week cycle in which only bug fixes go to the master branch and only after this two week cycle we branch of an Amber release maintenance branch? New code development cannot be committed to master during this 2 week cycle? Do we already have a plan on how we do and who does this branch off?
            1. The week of Nov 18 - 23 is the worse case window.
            2. Do we have instructions of how to create this branch?
               1. We need to define the CI from the release branch.  Lusheng will work with Chris for that.
      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. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      12. (TBD) O-RAN Radio Unit (ORU)
   4. user-59b16 Requirements Software Architecture Committee
      1. We took care of Jack's requirements for the second use case.  They are on the spreadsheet and it was uploaded last night.
      2. We added a word doc with a sequence diagram of how they run end to end.
      3. We can add a simple version on the Requirements and Software Architecture Committee Home 
      4. Second use case is a "hello world" heartbeat and health checks and functional test cases.  It's a self check 
   5. Project Metrics Plan for Nov 1st
8. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
   1. What is the status of the F2F and the interaction with OAI.
      1. You can find it in the slides on the events page.
      2. We need some guidance from the O-RAN legal team to understand what the issues are from the licensing stand point.  Primary contact is Stephan.  It takes time to get feedback.
         1. Do they seek input?
            1. Typically the alliance has their group and then Jack pulls in the LF experts when we are at a point to get their guidelines into the process.  Scott Nicolas and legal reps are there.  
               1. Who from the legal team?
                  1. Stefan Engel-Flechsig <stefan@o-ran.org>
                  2. You can attend the executive committee meeting 
9. Planning for Next Meeting
10. Open Discussion
11. Any Other Business (AOB) 
12. Meeting Summary (resolutions, new action items, etc.)
    1. Votes
       1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
          1. Vote to approve minutes for 23 Oct 2019 
          2. On motion made by Jinri Huang
          3. Seconded by MASAFUMI MASUDA
          4. VOTE: Vote taken, item passed
    2. Actions
       1. Action/ Community Vote Release Name
       2. Action/ Jinri Huang  will add the F2F meeting minutes to the events page.
       3. Action/ John Murray to work with OAI interface.
       4. Action/ John Murray closing the remaining the TOC slots. 
       5. Action/ user-d3360 add the link of the Jenkins instructions from the the Jenkins status page to the top of the Project Readiness for Amber Release wiki page.
       6. Action/ weichen ni  will provide PTLs with the steps that they need to view their converted docs on the docunmentation wiki.  He will add the link to the top of the Project Readiness for Amber Release .
       7. Action/ Each PTL write up a small clear statement about their license attribution that they can post to the email list. 

Return to Todays Agenda ^

Archived Meetings