Attendees
- @tiborbodecs
- @Joannis_Orlandos
- @ktoso
- @taylorswift
- @ben-cohen
- @sebsto
- @adam-fowler
- @graskind
- @FranzBusch
- @jbelkins
2024 goals
- Concurrency & Structured Concurrency adoptions @FranzBusch
- Guide for structured concurrency
- Overview of where we are standing with our libraries and the remaining work
- Swift 6
- Compatibility testing the packages @finestructure
- NIO needs to finalise it
Sendableannotations @FranzBusch
- Marketing
- Think about two guides that either need to be overhauled or created from scratch
- Build out integrated example project
- User group meetings @joannis & @sebsto
- Show-case two server side projects/success stories
- Tooling
- Find a solution going forward for
swiftly
- Find a solution going forward for
- HTTP server and middlewares @tachyonics @Joannis_Orlandos @adam-fowler @FranzBusch
Previous Action Items
Integrated: @FranzBusch @tiborbodecs to sync on integrated example- Meetup Planning: @sebsto To add a section for a SSWG community Q&A section
- Swiftly ownership: @FranzBusch to figure out the ownership
- @FranzBusch review HTTP server PR from @adam-fowler
- Potential Sendable over-annotation in SwiftNIO: Carry over with @FranzBusch
New action items
- Update SSWG security email membership @ktoso
- Everyone read through guides on Swift on Server | Swift.org and discuss what needs to be updated, moved or removed
- @taylorswift to produce an example for a potential DocC problem in the
swift-foundationmigration
Discussion
- @Tony_Parker joined us today to talk about the plan for
swift-foundation- Moving everything to be a package based dependency
- Requires work in Swift PM to make this transition as smooth as possible
- Goal is to have no API breaking changes
- @taylorswift Brought up some potential problems with DocC
- We can all help by testing out the
swift-corelibs-foundationandswift-corelibs-xctestbranchpackagein our packages
- Potential 2025 goal
- Make Swift plugins for the various soundness scripts