Attendees & Representation

TAC Members and Project representatives should mark their attendance below

Agenda

• Check Action Items & Topic Requests (Backlog)

• AI Observability Updates @ravi sharma @Fatih Nar

• F2F Developer Meeting

• Any Other Topics

Face-to-Face Developer Meetings

• The TAC discussed whether there is community desire for a face-to-face developer event, either at the Open Networking and Edge Summit in Japan this December or sometime in 2027.

• The consensus is that a whole-community developer event is not achievable this year. Travel budgets remain tight across the industry, and Japan will be difficult for many LFN developers to reach. The cellular cluster of projects is already self-organizing activity around ONE Summit Japan, but that is taking shape as a CFP-driven conference track rather than a developer meetup.

• For 2027, the TAC favors a co-located or regional approach. Developer-only events are hard to justify to management, while co-locating with a major LF event or a regional event (the Board has discussed a North American regional event in early 2027) reduces cost and improves the travel case. Past LFN developer events in Porto and Budapest produced strong cross-project collaboration, but employers will generally not fund travel to standalone developer gatherings.

• Planning should start well in advance, with a date and location set six months or more out and firm yes or no commitments collected before anything is booked, so the community knows whether it is planning for 50 people or 200.

• The strongest path to travel approval is a compelling agenda. Topics with a strong AI focus attract funding and participation quickly, so the TAC will explore an agentic AI centric theme that bridges LFN's traditional work with autonomous networking, framed as an education and learning event with clear cross-project value.

• FD.io has held ad hoc in-person developer meetings at FOSDEM for the past two years and has asked whether LFN could fund a dedicated room for FOSDEM 2027.

AI Observability Follow-Up

• The data collection template is in progress. Supporting documents (PDFs and presentation) have been uploaded to the Applied Observability for AI page on the wiki, linked from the main page under Other Committees and Work Groups.

• The template will get a first pass review from a telco perspective, after which Verizon will verify the format before data collection begins.

• The GitHub repository and a use case page will be set up under the 5G Super Blueprint. The project has been renamed LFN Super Blueprint; renaming the GitHub org is planned but currently on the back burner.

LFN GitHub Repository Cleanup (Any Other Topics)

• Several repositories in the lfnetworking GitHub org are stale, with open issues and PRs from 7 or more years ago. The member landscape repo remains in active use and will be kept.

• Lazy consensus to archive the stale repositories, including the process and marketing repos. There is no interest in standing up a new marketing repository; repos can be unarchived later if a genuine need appears.

• A private repository has been created to draft a revised project onboarding process. It will be made public for community review and comment once a draft is ready.

Action Items