Face-to-Face Meeting: BAC + TAC
Dates: 2–3 October
We will bring both the Business Advisory Committee (BAC) and the Technical Advisory Committee (TAC) together for two full days. The goal is to align governance and next-year focus areas, and to prepare for the upcoming panel session and the conference.
What We Ask from You
✅ Top 5 priorities/issues for the next 12 months
From your perspective (business/community for BAC, technical for TAC).
One line per item + a short “why now”.
Please come prepared to share these at the face-to-face meeting.
Planned topics
Governance input: boundaries for decision-making (what belongs with TAC, with the BAC, and Board); consensus signals.
TAC focus: actionable technical priorities to move TAC to an “operational” state.
BAC focus: specific business-impact areas.
Examples, slides, and data points (from customers, community feedback).
-
On-site flow:
short simulation and simple timing signal before the panel;
time-boxed discussions, including uncomfortable issues;
Next Steps
Bring your Top 5 priorities to the face-to-face meeting.
Everything else will be handled on-site.
In no particular order:
Engine & deprecated function removal (should be in 4.0)
atexit() removal (should be in 4.0)
Removal of all global mutable data (use libctx instead)
DTLS 1.3
Extending EVP_SKEY
Distance-Preserving Encryption (DPE)
Reduce PR backlogs especially API changing ones (should be in 4.0)
And don’t wait until we’re in the room, if you already have priorities or thoughts in mind, drop them here. Even a quick note helps get the conversation rolling.