Add AI meeting summaries

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

@@ -0,0 +1,52 @@
+# Meeting Summary for OTel WG
+
+**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-02-26T18:01:12Z
+- Meeting end: 2026-02-26T18:35:36Z
+- Summary start: 2026-02-26T18:01:12Z
+- Summary end: 2026-02-26T18:35:34Z
+
+Pascal and Raymie discussed the development of GraphQL telemetry specifications for OpenTelemetry, focusing on span definitions and attributes. They reviewed the current state of pull requests and discussed how Viaduct's implementation of GraphQL tracing differs from other systems, particularly in how it handles resolver dependencies and field execution. Raymie expressed interest in contributing to the specification process, noting that while direct benefits to Airbnb might be limited, participating in the open source community would help Viaduct's adoption. Pascal explained that the goal is to create a standardized way for GraphQL servers to integrate with telemetry systems, making it easier for tools like Datadoc and Elastic to support GraphQL tracing. They agreed to continue working on the specification, with Pascal planning to create a pull request in the semantic conventions repository and add documentation to make the project more discoverable.
+
+## Next Steps
+
+- Pascal: Create a pull request to the OpenTelemetry Semantic Conventions repository this week, including the updated specification files and a new README file.
+- Pascal: Link the new pull request in both the working group spec folder and at the top of the repository for visibility.
+- Pascal: Add information to the main README in the working group repository to clarify goals, participation, and where the specification work is happening.
+- Raymie: Relay Pascal's email address (Pascal@chilicream.com) to Vicki for asynchronous discussion and future participation.
+- Raymie: Study the current specification and consider providing feedback or questions based on Airbnb/Viaduct's experiences.
+- Pascal: Consider adding optional guidance in the specification about using links for resolver dependencies, based on the discussion with Raymie.
+
+## Summary
+
+### Version 1 Discussion and Introductions
+
+Pascal and Raymie discussed Raymie's recent trip to India for a wedding, noting the cultural differences in wedding celebrations. They then formally introduced themselves and reviewed the meeting agenda, which included a discussion about the road to version 1. Pascal informed Raymie that the meeting would be published on YouTube and might use AI summary tools, offering options for those who preferred not to be AI summarized.
+
+### OpenTelemetry Metrics Update
+
+Pascal provided an update on the OpenTelemetry (OTel) metrics work, noting that he had merged several pull requests into the spec folder and simplified span naming conventions. He mentioned that while tracing is the primary focus, they have also defined attributes for logs and errors. Pascal expressed interest in connecting with Vicki, who specializes in OTel metrics and tracing, and requested that her contact information be shared. He also noted that the OTel working groups have been meeting less frequently due to scheduling conflicts and a smaller attendance.
+
+### GraphQL Pipeline Implementation Comparison
+
+Pascal and Raymie discussed the GraphQL processing pipeline, including parsing, validation, variable coercion, and operation planning. They compared their respective implementations, noting similarities and differences in how they handle parsing, validation, and coercion. Raymie explained how their system uses fragments and a dependency graph between resolvers, which creates a more complex graph structure rather than a simple span tree. They also discussed the challenges of tracing field executions and optimizing telemetry data.
+
+### Complex Resolver Parent-Child Relationships
+
+Pascal and Raymie discussed the use of links in specifications and data loaders to handle complex parent-child relationships in resolvers. Pascal explained that links are necessary when a resolver can have multiple parents, such as when using data loaders or when creating dependencies between resolvers. They also touched on how a dependency tree can be created to manage resolver dependencies and enable backtracing. Raymie mentioned that there was limited background information available in the working group's GitHub repo.
+
+### GraphQL Documentation Enhancement Discussion
+
+Raymie and Pascal discussed the need for clearer documentation and participation guidelines for work groups. Pascal explained that the goal is to develop semantic conventions for GraphQL, as the current system lacks typing capabilities. They agreed that more information should be added to the main README to better explain the specification and goals.
+
+### GraphQL Semantic Conventions Discussion
+
+Pascal explained the process of improving semantic conventions for GraphQL by referencing GenAI's conversation ID structure and outlined plans to submit a pull request to the semantic Conventions GitHub repository. Raymie discussed the benefits of conforming to a standard for telemetry in Viaduct, an open source project, and how it could be beneficial to Airbnb beyond its open source value.
+
+### GraphQL Telemetry Standardization Discussion
+
+Pascal and Raymie discussed a GraphQL telemetry standardization effort, where Pascal explained the goal is to enable telemetry systems like Datadoc and Elastic to better handle GraphQL APIs by defining a standard for how GraphQL operations should be traced. Raymie acknowledged that while Airbnb already has a mature telemetry setup, they would be willing to contribute to the specification to help with Viaduct's adoption. Pascal mentioned that a pull request would be opened in the semantic Conventions repository this week, with the goal of completing the specification before GraphQLConf.