Agenda
- Call for Scribe (minutes owner)
- Roll Call & Quorum Check
- Review and Agree to Minutes of Previous Meetings
- Review of Today's Agenda
- Status of Open Action Items (Old Business)
- 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.)
Status of Open Action Items (Old Business)
...
Minutes: (taken by Lusheng)
- Call opened at 8:05 EST 2019/04/17
- Roll call: ToC members Jack, Jinri, David,
- 50% ToC quorum reached
- Old business
- None
- New business
- Review of standard meeting agenda: https://wiki.oran-osc.org/display/TOC
- Noting the importance of sharing of info on wiki page
- Weekly ToC meeting schedule confirmed (based on David's opinion pull).
- Will update wiki page for detailed meeting info: when and Zoom info
...
...
- Encouraging participation
...
- Avoid confusion about the two domain names:
...
...
- and
...
...
- 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
- 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
...
...
- 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
...
- We have to find a release manager, integration and test, documentation lead, create projects
...
- Establish sub-committees then recruit PTL and participants
...
- 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.
...
- 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.
...
...
- Establish sub-Projects then recruit PTL, Committers, and contributors
...
...
- Continue to work with LF on infrastructure needs (Lusheng Ji current contact)
...
...
- O-RAN WG coordination and communications must be an on-going activity
...
...
...
- 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
...
- Closed at 9:58 EST