You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Agenda

  1. Call for Scribe (minutes owner) 
  2. Roll Call & Quorum Check 
  3. Review and Agree to Minutes of Previous Meetings
  4. Review of Today's Agenda
  5. Status of Open Action Items (Old Business)
  6. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager/Release Planning: Weekly TOC Scheduling
    2. Report out from PTL: Stand-Up & Report Out on Blockers

    3. Test & Integration Planning

    4. Report Out of Sub-Committees

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

  8. Planning for Next Meeting
  9. Open Discussion
  10. Any Other Business (AOB)
  11. Meeting Summary (resolutions, new action items, etc.)

Status of Open Action Items (Old Business)

  • Will update wiki page for detailed meeting info: when and Zoom info Farheen Cefalu  
  • Encouraging participation
  • Avoid confusion about the two domain names:  oran-osc.org and o-ran-sc.org.  
    • Phil we go ahead and make the change for the o-ran-sc.org and move away from oran-osc.org
    • Action Phil will provide feedback from IT team in two days
    • Urgent request.  
  • Move all resources to o-ran-sc.org.  The sooner the better. Jack and Lusheng will work with Phil later today.
  • Follow up: Jinri to note onto O-RAN Alliance wiki
  • Get ToC members onto the mailing list, get mailing list info to prospective members Farheen Cefalu 
  • Review to-do list items (Jack's email on 04/15)
    • O-RAN Specification Code Project charter – Yes we need to align a few remaining comments. I hope we can finalize this this week. (Jinri)
    • O-RAN Specification code License – We need to set a goal, timeline, and communicate it. I am concerned we have communicated to a few companies but not had broader reviews.
    • Fill TOC membership slots 6-12 (O-RAN Alliance TSC)
  • On the TOC side, here are the next items to get accomplished

    • Set time for the weekly TOC meeting (David working it)

    • LF has assigned Phil Robb probb@linuxfoundation.org as our program manager initially. He will eventually assign this to someone else once established. I will send an email shortly.
    • Clarify the email list and domain names (Phil Robb)
    • Organize the TOC and establish a community best practices documentation including use of both licensing
    • Recruit a release manager and Establish a timeline I will share a target
      • What are goals for M0?
        • We have to find a release manager, integration and test, documentation lead, create projects 
    • Establish sub-committees then recruit PTL and participants
      • For the A release I was looking for one of the TOC members to help and gather requirements and talk to W8 and others and come up with a proposed list of sub committees and recruit the people needed for Software Architecture, Product Committees, 
      • Do we need sub committee first or do we need a project first?
        • In this case you need both but because we have a template for the project I am going to propose we work on that template for now.  We try to recruit the sub-committees first.  Pulling together people is much more work than putting together the project plan.  There is a lot of work in the requirements.  There are several roles in sub committees.  Is a security sub committee needed? 
        • I am asking for someone to come up with a proposal of sub-committees and a PTL for each committee they propose.
        • Vincent Danno - We can have a bottom up approach as you are proposing however I'm afraid by following that approach we may end up with many sub-committees while resources are limited?  Don't we want to find a common committee and then break it down after that.  
          • Yes, I am asking somebody on the TOC to think about and come up with a recommendation for the TOC to vote and approve.
          • Action Vincent will lead TOC based effort to identify and recommend what sub committees we want for the A release cycle.
        • Could you clarify the timeline?
          • Right now we go back to release page and click on release this is the proposed timeline until we finalize.  We want them identified by M0. 
        • Sprints are 3 weeks long.  At the end of each sprint we will set up a demo for what that sprint accomplished and test.  Aiming to have 80% of user stories completed because it's an open community.
        • Who is the appropriate person to take care of Security?
          • First decide a sub-committee then find a principal technical lead (PTL).  There are committers and code contributors.
            • First have a clear set of requirements for the release.    
    • Establish sub-Projects then recruit PTL, Committers, and contributors
      • We need a volunteer to put together a proposed list of project.  Work with subcommittees.  Focus on whether we are going to do on real time RIC non real time RIC.  You don't have to do that on you own.  Will someone take the lead to get that organized?
        • Jinri will take it as an initiative.
    • Continue to work with LF on infrastructure needs (Lusheng Ji current contact)
      • If no one has concerns I propose that we continue to have Lusheng in that role. 
    • O-RAN WG coordination and communications must be an on-going activity
      • Volunteer to work with O-RAN WG.  I wrangle the TOC that then wrangles the committees and projects.
      • The O-RAN TSC handles filling in the position O-RAN OFG.
  • Charter and License for Spec Code Project: To close with legal and Stefan.
  • ToC membership slot filling.
  • During O-RAN Alliance TSC meeting last Wed regarding approvals for Lenovo and Nokia, we were asked to provide clarification on criteria and guideline on ToC member recommendation on O-RAN Alliance wiki.  Jinri proposed text.
      • Whether to discuss Intel and Radisys and put in the same proposal with Lenovo and Nokia to TOC.
        • Next Tuesday is another meeting opportunity to talk about this before the Wed TOC meeting.

Standing Agenda Items (Brief Status of Ongoing Activities)

Release Manager/Release Planning: Weekly TOC Scheduling

Report out from PTL: Stand-Up & Report Out on Blockers

Test & Integration Planning

Report Out of Sub-Committees

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

Planning for Next Meeting

Open Discussion

Any Other Business (AOB)

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

This meeting is open to everyone.  Please invites people to the meeting and encourage them.  This meeting will spawn sub-committee meetings.  Next week is May 1 which is a day off in most countries.  Typically you would not hold the meeting if there is no attendance.  It is more work to move around.  Vincent Danno can make it.  Jinri can also make it.  We continue on and take who comes.  We are stuck between getting people signed up for a mail list and naming the mail lists.  The goal is to grow the community.  

Toshiro This Friday we will have a meeting. 

Jack: Finish the license, charter, and naming the TOC members.  After that we should focus on what our target is for June release.  Pick out a naming convention for releases.  If people can think about what naming conventions we want to follow.  


We have a timeline for A

We have a naming convention

vincent subcommittee

jinri project 

jack recommended best practices.  committee licences software agreement  What license in code  

Remove change of domain name  

I didnt get someone to lead the communications to the working groups  

add ORAN working group Liason


  • No labels