SSWG - July 17th 2024

[0xTim (Tim)]

Attendance:

• @tiborbodecs
• @taylorswift
• @Joannis_Orlandos
• @tachyonics
• @sebsto
• @0xTim
• @adam-fowler
• @finestructure

Previous Meetings:

Concurrency & Structured Concurrency adoptions

• Franz and Joannis to collaborate and a rough outline for a structured concurrency server applications post - carry over

Marketing

• @ktoso to address creating benchmarks from the SSWG perspective - carry over
• Build out integrated example project @FranzBusch @tiborbodecs - started on a gRPC demo but still need to decide on an actual example project.
  • Joannis mentioned we could expand SwiftOnServer.com to add comments or similar to add some application examples
  • Potential integration for Swiftinit
  • Sven mentioned it could be a bit niche, previous discussions revolved around a regular TODO list which adds some more ‘components’ etc
  • Sebastian mentioned that we need to be careful to ensure we don’t go too far and overcomplicate the tutorials
  • Need to use CI to ensure it stays up to date
• Announce third Swift Server Side meetup dates @Joannis_Orlandos & @sebsto - 17th September Morning UTC time
  • @ktoso to chase up second speaker and liaise with Sebastian
• Show-case two server side projects/success stories @0xTim @ktoso - carry over

Tooling

• Investigate official Swift GH action @0xTim, @FranzBusch, @sebsto - carry over but some progress

HTTP server and middlewares

• Move forward with the reviews of the initial API drafts
  • @FranzBusch to review to the PRs

Benchmarks

• @Joannis_Orlandos to share instruments trace - carry over
• @Joannis_Orlandos check if we can get a techempower based instrument trace - carry over

Action items

• @Ben_Cohen to verify the CI permissions so that @adam-fowler can trigger Swiftly CI - carry over
• Next meeting: New Incubation Maturity Review - will do offline
  • @0xTim to create voting thread on forums
• @ktoso @FranzBusch announce new SSWG members - carry over
  • @FranzBusch has draft
• @FranzBusch add explanation for last-three-versions toolchain requirement for server apps to swift.org - carry over
• @sebsto @tiborbodecs review and update swift.org deployment guides (AWS & others). - carry over

Agenda Items

• Refactor the Why Swift on Server section and add page on concurrency. by tachyonics · Pull Request #496 · swiftlang/swift-org-website · GitHub
  • @tachyonics to review
• https://github.com/swiftlang/swift-org-website/pull/447
  • @FranzBusch to look at when back
• @taylorswift asked about installing the Swiftinit GitHub app on the - carry over for @Ben_Cohen and bring up at the next Core Team meeting
  • @Ben_Cohen to look and, and team to bring up at the next Core Team meeting
• We need to discuss where to move repos like NIO, Metrics etc and where they are going to live like swiftlang
  • Mixed consensus whether we should move projects currently under the Apple to Swiftlang
  • Against - potential for packages to get lost in the masses, should swiftlang only be focused on language packages
  • For - easier to contribute, fundamental packages are ‘blessed’
  • @tiborbodecs to post list of repos to forums for us to track
  • To discuss with Core Team
• everyone to check their packages on Swift 6 nightlies to make sure we can fix issues before 6.0