Attendees
- @adam-fowler
- @FranzBusch
- @Joannis_Orlandos
- @tiborbodecs
- @finestructure
- @0xTim
- @taylorswift
- @Ben_Cohen
- @jbelkins
Goals
Concurrency & Structured Concurrency adoptions
@FranzBusch and @Joannis_Orlandos to collaborate and a rough outline for a structured concurrency server applications post
Swift 6
- Adoption of strict concurrency is in progress
Marketing
- @ktoso to address creating benchmarks from the SSWG perspective
- Build out integrated example project @FranzBusch @tiborbodecs
- Wait for Swift 6 before we build integrated example
- Announce third Swift Server Side meetup dates @Joannis_Orlandos & @sebsto
- Show-case two server side projects/success stories @0xTim @ktoso
- Tim has some examples for a blog post. Should be something available next meeting.
Tooling
- Investigate official Swift GH action @0xTim , @FranzBusch , @sebsto
- work in progress
HTTP server and middlewares
- Move forward with the reviews of the initial API drafts @FranzBusch
- carry over
Benchmarks
- @Joannis_Orlandos to share instruments trace
- Start off with a simple one and extend it from there
Previous Actions Items
- @FranzBusch add explanation for last-three-versions toolchain requirement for server apps to swift.org
- @sebsto @tiborbodecs review and update swift.org deployment guides (AWS & others).
- @tachyonics to review Refactor the Why Swift on Server section and add page on concurrency. by tachyonics · Pull Request #496 · swiftlang/swift-org-website · GitHub
- Installing the Swiftinit GitHub app to swiftlang org @Ben_Cohen to look at, and team to bring up at the next Core Team meeting
- @taylorswift to tag @Ben_Cohen on message
Agenda
Website discussion
- @federicobucchi joined us today to talk about the server parts of the website
- What's important to the workgroup
- @Joannis_Orlandos promote the reasons why Swift on Server should be picked
- @Joannis_Orlandos address the concerns of maturity of the language and the ecosystem
- @Joannis_Orlandos Find resources/Good packages
- @FranzBusch Information hierarchy and navigation
- @0xTim We have a server page but it's content needs improvement
- @Ben_Cohen Thinks server shouldn't be a top level item but maybe have a "use-cases" drop down
- What can we do?
- Review the organization of our content
- @FranzBusch to talk with @mishal_shah about GH actions on the website repo