Add AI meeting summaries (#1966)

Author: benjie

notes/2026/summary-2026-04-02.md

@@ -0,0 +1,51 @@
+# Meeting Summary for Working Group Meeting
+
+**NOTICE**: This summary was auto-generated by Zoom's "AI". AI-generated
+content may be inaccurate or misleading. Always check for accuracy. If in
+doubt, please consult the meeting recording at
+https://youtube.com/@GraphQLFoundation/playlists
+
+- Meeting start: 2026-04-02T17:30:32Z
+- Meeting end: 2026-04-02T18:47:27Z
+- Summary start: 2026-04-02T17:30:33Z
+- Summary end: 2026-04-02T18:47:24Z
+
+The GraphQL Technical Specification Committee (TSC) meeting focused on reviewing several specification updates and proposals. The team discussed and approved a change to leaf field definitions in the specification, with Martin leading the discussion on formatting improvements. Benoit presented updates on directives on directives, which is currently at RFC1 stage, and the group agreed on the syntax approach despite some concerns about readability. Pascal provided an update on the OpenTelemetry working group, presenting a new specification for GraphQL semantic conventions that has been submitted for review. The team then extensively discussed the GraphQL over HTTP specification, with Benjie explaining the new 294 status code for partial success and the decision to move application/json media type details to an appendix before the first release. The conversation ended with Benjie presenting service capabilities as a new RFC1 item, discussing potential implementation approaches and future considerations for handling deprecation in the schema.
+
+## Next Steps
+
+- All TSC members: Review the OpenTelemetry GraphQL semantic conventions pull request and provide feedback/approval before it is merged
+- Benjie: Update GraphQLJS pull request for directives on directives to make "include deprecated" argument non-nullable before merging
+- Lee/Benoit: Merge the GraphQLJS pull request for directives on directives after the "include deprecated" fix
+- All TSC members: Review the GraphQL over HTTP spec before it goes to RFC3
+- Martin: Lead effort to restructure/move legacy parts of GraphQL over HTTP spec to Appendix A
+- All team members: Review the Service Capabilities PR (now at RFC1)
+- Team: Move to weekly meetings in April to focus on releasing the GraphQL over HTTP spec
+- Benjie: Create GraphQLJS implementation of Service Capabilities (separate from on-error handling)
+- Team: Use Discord channel to check progress on spec work and coordinate meetings/cancellations
+
+## Summary
+
+### Meeting Introduction and Planning Discussion
+
+The meeting began with casual conversation about weather across different locations, including cold conditions in France and warm weather in Singapore. Martin discussed plans for an upcoming biking event and mentioned that Akshat was motivated to attend an event, though assistance with travel was needed. The group briefly discussed Leonardo Losovis, the founder of Gatograph for WordPress, who might attend. Lee then opened the formal meeting, welcoming attendees and reminding the group about key links including the SPEC membership agreement and participation guidelines. The conversation ended with Lee introducing himself to the group for the benefit of recording.
+
+### Leaf Fields Editorial Updates Review
+
+The team reviewed the agenda and discussed editorial updates for leaf fields. Martin presented a pull request that clarified the definition of leaf fields to include enums and added a definition block. Lee explained the SpecMD syntax used for defining terms. The team then moved on to discuss updates on directives, with Benoit set to present on that topic next.
+
+### Directive Feature Migration Discussion
+
+The team discussed moving a directive-on-directive feature from RFC1 to RFC2. They agreed on the syntax approach and decided to make the `includeDeprecated` argument non-nullable before merging. The feature will be implemented with an experimental feature flag in GraphQL 16, with plans to forward-port to GraphQL 17 later. Lee offered to merge the changes directly after making the type adjustment, as the implementation appeared straightforward and safely gated behind a feature flag.
+
+### GraphQL Specification Updates Review
+
+Pascal presented a new GraphQL semantic conventions specification for OpenTelemetry that removes previous conventions and introduces new ones, including low cardinality span names and event definitions for errors. The specification is currently in review as a pull request in the semantic conventions repository, and Pascal requested that the TSC review it before merging. Benjie reported that the GraphQL over HTTP specification is complete and ready for publication, including the addition of a new 294 status code for partial success responses, though it requires careful review before implementation.
+
+### Application JSON Specification Updates
+
+The team discussed moving the Application JSON media type to an appendix before the first release to simplify the specification and provide a cleaner message about the new features. Pascal and Benjie debated the use of HTTP status codes for GraphQL mutations, with Benjie cautioning that it could be misleading and not align with best practices. The group ultimately agreed to release the current version of the spec without the status code changes, moving those details to an appendix for a future update.
+
+### GraphQL Specification and Service Capabilities
+
+The team discussed two main topics: GraphQL over HTTP specification and service capabilities. For GraphQL over HTTP, they agreed to make one final pass through the TSC for approval before moving to RFC3, with Martin suggesting a weekly meeting cadence in April to focus on completion. Benjie presented service capabilities as a new RFC1 item, which the team approved. The discussion included considerations about handling deprecation in the schema and potential future service capabilities, with Lee suggesting adding deprecation handling to the __schema field rather than __service.