2025-12-04 TSC Minutes
Representatives & Attendees
Quick Links: TSC Mailing List | Meeting Recordings
TSC Members | Company |
|---|---|
TSC Members may indicate their attendance by changing the cell background for their name to green. | |
@Sana Tariq (Chairperson) | TELUS, Canada |
@Ciaran Johnston (Ericsson) (Vice-Chairperson) | Ericsson |
@Avinash Bhat | Samsung Electronics Co Ltd |
@Timo Perala (Nokia) | Nokia |
@Sagar Arora | OpenAirInterface Software Alliance (OSA) |
@balaji varadaraju | Red Hat |
@Vishal Varvate | Capgemini India |
@Eric Debeau | Orange |
@Bernard Tsai | Deutsche Telekom |
@Kandan Kathirvel | Google Cloud |
@Hunor Demeter (Deactivated) | VMWare by Broadcom |
@Seshu Kumar Mudiganti | WindRiver |
@Phil Porras | SRI International |
@Raj Panchapakesan | AccuKnox Inc |
Iain Wilkinson | Vodafone |
Community members may @ tag themselves below to show their attendance.
You can add action items anywhere in the minutes by typing “/action” and pressing enter
Action Items:
LF Staff:
Agenda
The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF. |
Key Updates
GitHub Organization structure
Follow up on permissions. IT has been back and forth on using a tool to resolve the issue, but it seems that it will take too long to implement, so they’ve come back with questions for the community.
So, there are a few different ways to approach this, but there's one issue up front: GitHub doesn't allow non-owners to invite people to the org. Even using Organization Roles (which can be helpful for some of this), that part will continue to be owner-only.
In terms of managing teams with current org members, we have more options. The main one is that we can assign "team maintainers," who have the right to add and remove members of teams that they're on. Depending on what the permission structure looks like, it might make sense to create parent/child teams, e.g. have a top level team that has all chairs (TSC and SIG), and then a child team with just the TSC chair and co-chair (just a suggestion; if all members should have the same permissions, that won't be necessary). Permissions for child groups are inherited from their parents, and can only get more permissive, so you could, for example, have all TSC members with Maintainer permissions to all repos, and then have a child team for the Chairs that has admin permissions.
More info on team maintainers can be found here: https://docs.github.com/en/enterprise-cloud@latest/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member
If the inability to invite new org members isn't a deal-breaker, feel free to share more details on the permission structure they'd like to see, and I can provide more specific implementation details.
TSC Election
We are still looking for Nominees
Please get your nominations in by Dec 11, 2025
Zulip
New channels were added for the SIGs.
#lfn-nephio-wg-automation
#lfn-nephio-wg-release
#lfn-nephio-wg-network-architecture
#lfn-nephio-wg-security
R6 Release
Dates and content for feedback from TSC - @balaji varadaraju and @Liam Fallon
SIG Status
Network Architecture
.
Automation
.
Release
.
Security
.
Other Updates
.
Action Items Review
Minutes