FYI...
-------- Forwarded Message --------
Subject: [govpp-dev] Action Required by August 18: Two items from the
LFN TAC for your TSC agenda
Resent-Date: Thu, 06 Aug 2026 08:28:21 -0700
Resent-From: [email protected]
Date: Thu, 6 Aug 2026 08:27:42 -0700
From: Casey Cain via lists.fd.io <[email protected]>
Reply-To: [email protected]
To: [email protected], [email protected]
Hi all,
The LFN TAC has two requests for each project community. Both are time
sensitive, and both need a TSC discussion rather than a single person's
answer.
*Action Required: Please put both items on your next TSC agenda and reply
by Monday, August 18.*
*1. Ideas for the next developer face-to-face event*
Companies begin 2027 budget planning within the next one to two months, and
most budgets are finalized between September and November. For the TAC to
bring a proposal to the Governing Board early enough for board members to
take it back to their own budget teams, we need ideas from the communities
now.
Travel budgets are tight, and "it would be good to attend" is no longer
enough to get people approved. We would like each community to identify a
concrete outcome that requires being in the same room. Starting points from
the TAC discussion:
- Structured contributor training for upstream work
- Hands-on labs with a defined deliverable at the end
- On-site certification
- Architecture or design working sessions on problems that are slow to
resolve over email and video calls
Worth covering in your discussion: what your community would produce during
the event, who needs to be there for that to work, and where it lands
relative to your release cycle.
*2. A named contact for AI discoverability and agentic consumption*
Roughly 60 percent of traffic to LFN web properties now comes from LLM
scrapers. Developers increasingly hand an abstract task to a coding agent
and let the agent choose the technology, which means coding agents are now
part of the audience for our projects. Most LFN projects are components
inside a larger system, so the practical risk is that agents assemble
solutions without selecting our projects at all.
The TAC is asking each project to name a contact person to lead this work
for your community. The TSC chair is the default if the community does not
nominate someone else. This is ongoing work rather than a one-time task, so
pick someone who can stay with it.
The mechanisms already exist, including AGENTS.md, MCP servers, A2A, and
answer engine optimization on project sites. There is no single approach
that fits every project, so each community will need to decide what suits
its technology and do the work to apply it.
Two tests you can run on your own project in the meantime:
- Ask an LLM for an overview of your project and see how much depth
comes back beyond a few surface bullets.
- Describe a generic problem in your domain without naming LFN or your
project, ask for a detailed system design, and see whether your project
gets selected.
Please reply to [email protected] by August 18 with your
community's ideas on the event and the name of your AI contact. Both will
be on the agenda at the next TAC meeting.
Happy to answer questions or join your TSC meeting if it would help to talk
it through.
Best,
Casey Cain
Sr. Technical Community Architect
Linux Foundation
_________________
Mobile: +1.503.779.4519
Book a Meeting w/ Casey <https://meetings.hubspot.com/casey324>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#27138): https://lists.fd.io/g/vpp-dev/message/27138
Mute This Topic: https://lists.fd.io/mt/120832088/21656
Group Owner: [email protected]
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/14379924/21656/631435203/xyzzy
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
