Moderator - Uri Goldshtein
Panelists:
Lee Byron
Sasha Solomon
Benjie
Brielle Harrison
The GraphQL Working Group is a virtual space where developers and stakeholders discuss the development of GraphQL. It meets monthly to address and solve problems collaboratively, and these discussions often lead to enhancements in the GraphQL specification. The group plays a vital role in ensuring the GraphQL technology evolves in a way that benefits all users and aligns with the broader community's needs.
Key members include Brielle Harrison from PayPal, Benji who maintains PostGraphQL, Lee Byron, a co-creator of GraphQL and engineering manager at Robinhood, and Sasha Salmon, a staff software engineer at Twitter. All contribute significantly to the direction and development of GraphQL.
The GraphQL Working Group is a broader group that includes anyone interested in the development of GraphQL and meets to discuss ongoing issues and development. The Technical Steering Committee, on the other hand, is a smaller group with formal voting rights on technical decisions and plays a key role in steering the project's technical direction.
GraphQL began inside Facebook in 2012 as a 'crazy idea' aimed at improving data fetching and server-client interactions. It was initially developed through internal reviews and code contributions. By 2015, Facebook decided to open-source GraphQL, which included significant changes to its syntax and proposals, thus broadening its development and adoption.
Individuals interested in participating can add themselves to the agenda of the upcoming GraphQL Working Group meeting by contributing a pull request or joining the discussion in the group's GitHub repository. The community encourages active participation and engagement in discussions.
Recent topics of interest include client-controlled nullability, which allows clients more control over data requirements, and GraphQL fragment arguments, which enhance the flexibility of data requirement specifications within queries. These developments aim to refine and extend GraphQL's capabilities to better meet user needs.
We constantly think of articles and videos that might spark Git people interest / skill us up or help building a stellar career
Comments