Action items
-
Simon Pilkington: Publish in Slack the links to meeting notes that need to be reviewed; ensure the notes up to date and post the additional one for today. -
Everyone: Review the draft charter and provide feedback -
Everyone: Contributors interested in CodeQL should review the Hummingbird rules, propose additions/removals, and provide reviews to improve and maintain the rule set.
Codeql rules discussion and upstreaming
-
There is a CodeQL repo under Hummingbird; upstreaming to the main CodeQL repo was discussed but Joannis wants to avoid imposing opinionated server-specific rules on the entire Swift ecosystem.
-
Joannis prefers to maintain Swift server–specific CodeQL rules focused on server concerns (e.g., unstructured tasks, OpenTelemetry/metrics, avoiding denial of service) rather than broad opinionated Swift rules.
-
Adam noted some of Joannis' continuation-related rules would be good general Swift rules because they find bugs.
-
Simon suggested packaging extension rules for reuse; Joannis confirmed Hummingbird already provides such extension rules and recommended promoting and maintaining that package for server projects.
-
Action: Contributors interested in CodeQL should review the Hummingbird rules, propose additions/removals, and provide reviews to improve and maintain the rule set.
Charter update and incubation process
-
Simon has drafted an updated charter and posted the main version in the Swift Server WG repo and on the internal forums area for feedback; focus areas were proposed and need review.
-
Konrad suggested prioritizing library adoption and ecosystem growth as the most actionable focus, and noted the incubation/process guidance should reflect the WG's evolving role.
-
Adam raised whether the WG should continue hands-on management of the incubation process or shift responsibilities to automation; Konrad agreed some legwork is still needed to enable automation.
-
Simon will rework the charter text to reflect the WG's role in the revised process and incorporate feedback from the forum thread before the next meeting.
-
Action: Attendees should review the draft charter and provide comments so a more in-depth discussion can happen at the next meeting.