SSWG April 24
Attendees
- @0xTim
- @finestructure
- @FranzBusch
- @graskind
- @Joannis_Orlandos
- @jbelkins
- @sebsto
- @taylorswift
- @tiborbodecs
2024 goals
- Concurrency & Structured Concurrency adoptions @FranzBusch
- Guide for structured concurrency
- ongoing work
- Overview of where we are standing with our libraries and the remaining work
- Guide for structured concurrency
- Swift 6
- Compatibility testing the packages @finestructure
- we've run two passes of Swift 6 toolchains across all packages and collected error stats
- Swift 6 preview page coming soon
- NIO needs to finalise its Sendable annotations @FranzBusch
- Compatibility testing the packages @finestructure
- Marketing
- Think about two guides that either need to be overhauled or created from scratch
- Build out integrated example project
- User group meetings @Joannis_Orlandos & @sebsto
- first meet-up happened, cross off now
- Show-case two server side projects/success stories
- Tooling
- Find a solution going forward for swiftly
- HTTP server and middlewares @tachyonics @Joannis_Orlandos @adam-fowler @FranzBusch
Franz to invite Tibor to HTTP server & middleware repos, he'll help
- then we'll post announcement
Previous action items
Sven post-meeting note: these need review, I didn't catch if there were ones that are done
Integrated: @FranzBusch @tiborbodecs to sync on integrated example
Meet-up 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
Update SSWG security email membership @ktoso
@taylorswift to produce an example for a potential DocC problem in the swift-foundation migration
Task from within task group can crash
- @Joannis_Orlandos reports a crash around task locals when bringing up a Task from within a TaskGroup
@FranzBusch flagged this with concurrency group, needs chasing, will follow up
Meetup recap
- 110-120 viewers
- 2 hours
- went really well
- global audience
- a lot of interaction on the chat
- Q&A amongst viewers, very lively
@sebsto & @Joannis_Orlandos to post a recap to the forums
- next one: Hummingbird intro by @adam-fowler
NIO SSH
- @Joannis_Orlandos needs more crypto configurability
- has a fork that he'd rather not maintain anymore
- @FranzBusch : Corey busy, set reminder until mid June
Ubuntu 2024 support
- no docker images yet
- not released yet but imminent
@graskind to write message to platform steering group about it
New member announcements
@ktoso & @FranzBusch : next week we'll know if new members need to be approved
Doc review
- installation & setup page should move elsewhere
- building
- @0xTim should go to platform team
- @Joannis_Orlandos server heavy
- @FranzBusch needs to be reworked somewhere else or removed for the time being
- testing
- @FranzBusch a lot is outdated, needs updating/moving
- debugging
- should be on a higher level
- guides are useful
- @0xTim should be on swift.org (could be on swiftonserver.com in addition)
- same for allocations
- deployment
- @0xTim belongs to us
- @tiborbodecs guides are not up to date (at least the first two)
@sebsto @tiborbodecs will update AWS guide
@tiborbodecs will review guides
- let's set recurring reminder to update
- @0xTim will shepherd through PRs
- Packaging
- @graskind : will get more complex with Windows on the horizon
- should be under deployment
- @Joannis_Orlandos argument could be made that a lot of these should go to platform group
- log levels
Sven post-meeting note: didn't manage to follow discussion about this point
- main server page
- @FranzBusch @Joannis_Orlandos : should rewrite the server page as an elevator pitch about Swift on Server and then link out to guides living somewhere else
- reduce number of guides under Server as things move into language proper
- @Joannis_Orlandos server page not very attractive/welcoming
- page is very text heavy
- @taylorswift hard to make changes, should this live on the swiftonserver.com site?
- @0xTim needs to be on swift.org really
- @FranzBusch need owner for doc updates
- @graskind people aren't aware of latest Swift improvements. Anecdotally, many people still think Swift is bloated, slow from very early impressions. The page should counter those false impressions.
- @tiborbodecs and @Joannis_Orlandos will take ownership
- add it to yearly goals to overhaul server guides
@tiborbodecs and @Joannis_Orlandos summarise to WSWG and core team what pages we plan to update