Community agenda items and open discussion (10 min)
Wrap-up and action items (5 min)
Propose an agenda item
We’d love the agenda to reflect what the community wants to discuss. Please reply to this thread with topics you’d like to cover, ideally with a sentence or two of context and roughly how much time you think it needs. To keep the meeting focused, we’ll include some agenda topics from the replies received for discussion as time permits and include anything else in the list of potential topics for future meetings.
A few notes so the meeting stays productive with a larger group:
Most decisions happen asynchronously on the forums, Slack, and GitHub. The meeting is for discussion and alignment, so you can participate fully asynchronously if you wish or if you cannot attend a particular timeslot.
We’ll use a raised-hand queue and chat for questions and discussions. Please take note of your position in the queue and try to avoid collisions with others when speaking.
We’ll post the notes from the meeting here on the forums afterwards. Note that we’re piloting AI note-taking tools but won’t be recording the meeting, and you can ask us to turn them off at any time.
We follow the Swift Code of Conduct. This is a public meeting, so please keep discussion to public, non-confidential topics.
Hello everyone, I’m really looking forward to the meeting as always!
I’d like to propose an agenda item on WebTransport. Over the last two months, I’ve been on a university internship during which I worked on implementing a WebTransport client and server in Swift, using swift-nio-http3 and swift-http-server.
If there's time, I would like to present the work I have done so far and get some feedback from the meeting participants, particularly on the design of the API I have implemented for the client and server. It won’t take me more than 5 minutes.
The group agreed on CI and pull request review guidelines for the swift-networking-types repository. CI will require Swift 6.4 on all supported platforms, and pull requests will need at least one approval from a code owner, with a two-day soak period and a goal of resolving each one within a week. The initial IP address and port types will merge first, followed by benchmarking and testing infrastructure. The HTTP client discussion weighed starting with an abstract protocol over existing clients against building a native client first, and covered configuration that spans layers, such as TLS, certificates, and transport path selection. The group agreed that the layering of the broader Swift networking stack should be scoped and documented before committing to higher-level HTTP client interfaces.
Notes
Repository CI
Swift 6.4 will be the required baseline for CI on all supported platforms. Nightly toolchain builds will also run but won’t block merging, so compiler regressions don’t hold up development.
CI coverage is planned for Windows, Linux, macOS and other Apple platforms, the Static Linux SDK, FreeBSD, Android, and Embedded Swift.
Pull Request Reviews
Pull requests will need at least one approval from a group of three code owners.
Pull requests will have a two-day soak period with a Slack notification, and a goal of resolving each pull request within a week.
The group agreed to enable automatic rebasing on main in the repository settings, and to look into Slack webhooks that alert reviewers to stale pull requests.
Currency Types
The group agreed to merge the initial IP address and port types first, followed by the benchmarking and testing infrastructure.
HTTP Client Strategy
The group discussed whether to start with an abstract protocol across the existing clients, which would be useful right away, or with a fully native Swift client, which could establish currency types optimized for Swift.
Configuration options that cross layers are difficult to abstract. Transport preferences like path selection can fall back gracefully, but security options such as TLS, mutual TLS, and certificate trust roots don’t map cleanly between platforms.
System frameworks on Apple platforms need strict binary and source compatibility, which rules out exposing their internal layers, while open source stacks have more flexibility.
The group agreed that the layering of the broader Swift networking stack should be scoped and documented before committing to higher-level HTTP client interfaces.
Next Steps & Action Items
Franz will enable CI across the supported platforms, with Swift 6.4 as the required baseline.
Franz will update the repository settings to require CI checks and enable automatic rebasing on main.
Franz and Tommy will look into setting up Slack notifications for pull requests that need review.
Jon will start a new thread in the Networking forums category to propose layering boundaries across the Swift networking stack and gather requirements for the underlying engines on each platform.
Mahdi and Keely will rebase the open Port and IP address types pull requests on main once the CI changes merge.