Skip to content

Latest commit

 

History

History
131 lines (100 loc) · 7.29 KB

File metadata and controls

131 lines (100 loc) · 7.29 KB
This is an open meeting: To attend, read JoiningAMeeting.md then edit and PR this file. (Edit ✎ 🡕)

GraphQL WG – January 2023 (Secondary, APAC)

The GraphQL Working Group meets regularly to discuss changes to the GraphQL Specification and other core GraphQL projects. This is an open meeting in which anyone in the GraphQL community may attend.

This is a secondary meeting, timed to be acceptable for those in Asia Pacific timezones, which typically meets on the second Wednesday of the month. The primary meeting is preferred for new agenda, where this meeting is for overflow agenda items, follow ups from the primary meeting, or agenda introduced by those who could not make the primary meeting time.

Attendees

Name GitHub Organization Location
Lee Byron (Host) @leebyron GraphQL Foundation San Francisco, CA, US
Donna Zhou @dondonz graphql-java / Atlassian Sydney, AU
Matt Mahoney @mjmahone Meta New York, NY, US
Roman Ivantsov @rivantsov Individual Seattle, WA, US
Anthony Miller @AnthonyMDev Apollo GraphQL Las Vegas, NV, US
Andi Marek @andimarek GraphQL Java Brisbane, AU

Agenda

  1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Lee)
  2. Introduction of attendees (5m, Lee)
  3. Determine volunteers for note taking (1m, Lee)
  4. Review agenda (2m, Lee)
  5. Review prior primary meeting (5m, Lee)
  6. Review previous meeting's action items (5m, Lee)
  7. Licensing & final legal sign-off for GraphQL Scalars project (5m, Donna)
  8. Fragment Arguments: Identify Open Concerns to Address (known concerns below) (10m, Matt)
    • Do we allow shadowing global variables?
    • PR with Variable Definitions instead of Fragment Argument Definitions.
    • Do we need PR Reviews to know if there are other concerns?
    • Maybe: additional graphql-js PR to use local scope, aka graphql-spec algorithm, rather than visit replacement?