From 737f5465cbb58a80a4fab268d8279cb712fe0bd0 Mon Sep 17 00:00:00 2001 From: Piotr Monwid-Olechnowicz Date: Sat, 16 Aug 2025 03:09:51 +0200 Subject: [PATCH] Sync new data from Sched --- scripts/sync-sched/schedule-2025.json | 290 ++++++++++++++++++++------ scripts/sync-sched/speakers.json | 175 ++++++++-------- scripts/sync-sched/sync.ts | 2 +- 3 files changed, 316 insertions(+), 151 deletions(-) diff --git a/scripts/sync-sched/schedule-2025.json b/scripts/sync-sched/schedule-2025.json index 8b3b04055b..35ac508bec 100644 --- a/scripts/sync-sched/schedule-2025.json +++ b/scripts/sync-sched/schedule-2025.json @@ -1,4 +1,40 @@ [ + { + "event_key": "929642", + "active": "Y", + "pinned": "N", + "name": "Cloakroom", + "event_start": "2025-09-08 08:00", + "event_end": "2025-09-08 19:15", + "event_type": "Breaks / Networking / Special Events", + "description": "SECURITY NOTICE\nPlease keep all personal belongings in your possession during the conference. GraphQL, The Linux Foundation nor the Pakhuis de Zwijger are responsible for lost or stolen items. If something is misplaced, check in with an Event Staff member at the registration desk.", + "goers": "0", + "seats": "0", + "invite_only": "N", + "venue": "K Floor - Underground Floor", + "id": "1431b61d59a47bd0eb505916e30a5bfa", + "venue_id": "2191087", + "event_start_year": "2025", + "event_start_month": "September", + "event_start_month_short": "Sep", + "event_start_day": "8", + "event_start_weekday": "Monday", + "event_start_weekday_short": "Mon", + "event_start_time": "08:00", + "event_end_year": "2025", + "event_end_month": "September", + "event_end_month_short": "Sep", + "event_end_day": "8", + "event_end_weekday": "Monday", + "event_end_weekday_short": "Mon", + "event_end_time": "19:15", + "start_date": "2025-09-08", + "start_time": "08:00:00", + "start_time_ts": 1757311200, + "end_date": "2025-09-08", + "end_time": "19:15:00", + "event_subtype": "" + }, { "event_key": "1", "active": "Y", @@ -7,7 +43,7 @@ "event_start": "2025-09-08 08:00", "event_end": "2025-09-08 18:30", "event_type": "Registration + Badge Pick-up", - "goers": "2", + "goers": "3", "seats": "0", "invite_only": "N", "venue": "BG Foyer - Ground Floor", @@ -43,7 +79,7 @@ "event_start": "2025-09-08 09:00", "event_end": "2025-09-08 09:05", "event_type": "Keynote Sessions", - "goers": "1", + "goers": "3", "seats": "0", "invite_only": "N", "venue": "Grote Zaal - 2nd Floor", @@ -89,7 +125,7 @@ "event_start": "2025-09-08 09:05", "event_end": "2025-09-08 09:15", "event_type": "Keynote Sessions", - "goers": "2", + "goers": "4", "seats": "0", "invite_only": "N", "venue": "Grote Zaal - 2nd Floor", @@ -136,7 +172,7 @@ "event_end": "2025-09-08 09:30", "event_type": "Keynote Sessions", "description": "Even ten years in, GraphQL continues to evolve—not just in code, but in connection. This year the Foundation has doubled down on transparency, support, and shared leadership: board minutes are now public, Subject Matter Experts have helped shape the conference agenda, and we'll be launching a new program live on stage! There are also updates on our existing initiatives including community grants and GraphQL Locals.\n\nThis talk is a thank you to the people behind the progress and a celebration of our growing constellation of contributors. It's also an invitation to step forward and get involved—one of the best ways to do that is by joining our new Community Working Group, giving passionate community members a voice in shaping the Foundation's directions and initiatives for the next ten years of GraphQL.", - "goers": "3", + "goers": "5", "seats": "0", "invite_only": "N", "venue": "Grote Zaal - 2nd Floor", @@ -196,7 +232,7 @@ "event_end": "2025-09-08 09:45", "event_type": "Keynote Sessions", "description": "Meet the new developer journey: Ask AI → Generate code → Iterate → Ship. This fundamental shift in how developers work demands we rethink every touchpoint of our GraphQL APIs. This talk focuses on the developer experience layer—how to design schemas that are self-explanatory, structure documentation so AI gives accurate answers about your API, and build tools that feel like pair programming with a senior engineer.", - "goers": "1", + "goers": "3", "seats": "0", "invite_only": "N", "venue": "Grote Zaal - 2nd Floor", @@ -241,7 +277,7 @@ "event_end": "2025-09-08 10:00", "event_type": "Keynote Sessions", "description": "A peek behind the curtain revealing how GraphQL is used at Meta. We will explore how everything from culture, development process, client and server implementations, schema patterns and conventions, advanced tooling and more work together to allow GraphQL to enable great user and developer experiences at Meta.", - "goers": "2", + "goers": "4", "seats": "0", "invite_only": "N", "venue": "Grote Zaal - 2nd Floor", @@ -286,8 +322,8 @@ "event_start": "2025-09-08 10:05", "event_end": "2025-09-08 10:15", "event_type": "Keynote Sessions", - "description": "As developers build with AI agents, we face a challenge: how do we provide these agents with reliable, flexible access to our distributed data? GraphQL's graph-based approach makes it the ideal language for AI. Join Matt DeBergalis, CTO and Co-founder of Apollo GraphQL, to explore how \"thinking in graphs\" fundamentally transforms API orchestration from procedural code to declarative queries – creating the composable data layer that AI-driven applications require.", - "goers": "1", + "description": "As developers build with AI agents, we face a challenge: how do we provide these agents with reliable, flexible access to our distributed data? GraphQL's graph-based approach makes it the ideal language for AI. Join Matt DeBergalis, CEO and Co-founder of Apollo GraphQL, to explore how \"thinking in graphs\" fundamentally transforms API orchestration from procedural code to declarative queries – creating the composable data layer that AI-driven applications require.", + "goers": "3", "seats": "0", "invite_only": "N", "venue": "Grote Zaal - 2nd Floor", @@ -332,7 +368,7 @@ "event_start": "2025-09-08 10:15", "event_end": "2025-09-08 10:20", "event_type": "Keynote Sessions", - "goers": "2", + "goers": "4", "seats": "0", "invite_only": "N", "venue": "Grote Zaal - 2nd Floor", @@ -378,7 +414,7 @@ "event_start": "2025-09-08 10:20", "event_end": "2025-09-08 10:45", "event_type": "Breaks / Networking / Special Events", - "goers": "0", + "goers": "2", "seats": "0", "invite_only": "N", "venue": "Foyer Grote Zaal - 2nd Floor", @@ -414,7 +450,7 @@ "event_start": "2025-09-08 10:20", "event_end": "2025-09-08 18:45", "event_type": "Solutions Showcase", - "goers": "1", + "goers": "2", "seats": "0", "invite_only": "N", "venue": "Workspace - 2nd Floor", @@ -451,7 +487,7 @@ "event_end": "2025-09-08 11:15", "event_type": "Developer Experience", "description": "Even dedicated GraphQL developers face the reality of enterprise environments: multiple REST endpoints requiring complex orchestration and endless fetch requests. In this developer-focused session, we'll explore practical schema design patterns for effectively mapping common REST API shapes into your GraphQL schema.\n\nWe'll dive into real-world examples showing how to transform pagination, filtering, nested resources, and other REST patterns into intuitive GraphQL abstractions. You'll learn proven strategies for maintaining excellent developer experience while rapidly onboarding existing services to your graph.\n\nWhether working with OpenAPI specs or internal API documentation, we'll demonstrate tooling and techniques to accelerate this process dramatically – bringing your REST services into your graph in days, not months. Stop writing endless API orchestration code and start delivering value through GraphQL.", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "Grote Zaal - 2nd Floor", @@ -525,6 +561,52 @@ "end_time": "11:15:00", "event_subtype": "Scaling" }, + { + "event_key": "929641", + "active": "Y", + "pinned": "N", + "name": "What’s Missing in Your Graph? Using AI to Uncover and Close Gaps - Christian Ernst, Booking.com", + "event_start": "2025-09-08 10:45", + "event_end": "2025-09-08 11:15", + "event_type": "GraphQL in Production", + "description": "At Booking.com, we’re applying AI to uncover data blind spots in our GraphQL schema, specifically gaps between what’s exposed today and what still lives in our legacy Perl systems. As we continue modernizing our frontend architecture, one major challenge is identifying what data is already available, what’s duplicated, and what’s missing entirely from the graph. Using AI, we’ve begun introspecting legacy domains to map their data structures against the schema, surface PII fields for tagging and tracking, and inform where schema design can be improved. In this talk, we’ll share how we’re using AI to support schema modernization at scale, streamline developer experience, and bring more consistency to a graph that continues to grow and change across teams.", + "goers": "1", + "seats": "0", + "invite_only": "N", + "venue": "IJzaal - 5th Floor", + "audience": "Intermediate", + "id": "41cdd30e0b737298834f3a929e2fd241", + "venue_id": "2152806", + "speakers": [ + { + "username": "christian.ernst1", + "id": "21066804", + "name": "Christian Ernst", + "company": "Booking.com", + "custom_order": 0 + } + ], + "event_start_year": "2025", + "event_start_month": "September", + "event_start_month_short": "Sep", + "event_start_day": "8", + "event_start_weekday": "Monday", + "event_start_weekday_short": "Mon", + "event_start_time": "10:45", + "event_end_year": "2025", + "event_end_month": "September", + "event_end_month_short": "Sep", + "event_end_day": "8", + "event_end_weekday": "Monday", + "event_end_weekday_short": "Mon", + "event_end_time": "11:15", + "start_date": "2025-09-08", + "start_time": "10:45:00", + "start_time_ts": 1757321100, + "end_date": "2025-09-08", + "end_time": "11:15:00", + "event_subtype": "Schema evolution" + }, { "event_key": "929626", "active": "Y", @@ -609,7 +691,7 @@ "event_end": "2025-09-08 11:35", "event_type": "Developer Experience", "description": "What if you could keep traditional UI pagination concepts, but with the performance and reliability of cursor-based pagination? In this lightning talk, you’ll learn how relative cursors enable fast, consistent pagination while preserving familiar UX patterns like “jump to page.” It’s a smarter, more robust approach to navigating data—ideal for modern APIs and real-world apps.", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "IJzaal - 5th Floor", @@ -655,7 +737,7 @@ "event_end": "2025-09-08 11:55", "event_type": "GraphQL in Production", "description": "After maintaining GraphQL Java for 10 years we learned what aspects of GraphQL are critical for optimal performance. \n \nWe we look at what users of GraphQL should consider and which aspects of the spec are critical for optimal performance.\n \nWe will look also closer into the aspects of operating GraphQL at scale including and what it means when the schema and requests continue to grow.", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "Studio - 5th Floor", @@ -701,7 +783,7 @@ "event_end": "2025-09-08 11:55", "event_type": "Developer Experience", "description": "Despite having \"Graph\" in its name, GraphQL schemas are rarely visualized as actual graphs.\n\nThis lightning talk explores the untapped potential of graph visualization for GraphQL schemas based on lessons learned while working on graphql-voyager.\n\nWe'll explore the theory behind effective schema visualization, share key insights from my 9 years of experience in this field, and discuss current challenges in representing complex schemas.\n\nI'll also present experimental approaches that go beyond existing libraries, pushing the boundaries of how we understand and interact with GraphQL schemas.\n\nJoin me for a visual journey that reveals what makes the \"Graph\" in GraphQL truly powerful, potentially reshaping how we design and understand our APIs.", - "goers": "1", + "goers": "3", "seats": "0", "invite_only": "N", "venue": "IJzaal - 5th Floor", @@ -747,7 +829,7 @@ "event_end": "2025-09-08 12:35", "event_type": "Developer Experience", "description": "GraphQL error handling sucks. There, I said it.\n\nEver hunted through the errors list to figure out if a null was legit or caused by an error? If you're like me, you gave up and now treat nulls as \"maybe errored, maybe absent, maybe both.\"\n\nAnd nullability. Schema designers make anything that might fail nullable, producing partial responses when errors occur. But since anything can fail, now everything is nullable—\nand we're drowning in null checks. We recklessly cast to non-null or fall back to the empty string out of desperation. And we still don't know what's truly nullable.\n\nNo more.\n\nThis talk introduces a new, pragmatic approach, born from years of work by the Nullability WG. We propose a future where schemas reflect the true nullability of business entities, and error handling is where it belongs: in your code, not your data. Use your language's built-in tools to handle errors ergonomically; and drop the unnecessary null checks. When you read a null, it should mean one thing: the absence of data.\n\nThis isn't some distant ideal on the horizon of GraphQL's future; with just 512 bytes added to your GraphQL client, you can start adopting this today. Come see how.", - "goers": "2", + "goers": "3", "seats": "0", "invite_only": "N", "venue": "Grote Zaal - 2nd Floor", @@ -788,11 +870,11 @@ "event_key": "903215", "active": "Y", "pinned": "N", - "name": "Modernizing a Million Lines of Code: Jira's Journey To GraphQL and Relay - Sourav Shaw & Vivek Yadav, Atlassian", + "name": "Modernizing a Million Lines of Code: Jira's Journey To GraphQL and Relay - Vivek Yadav & Kritika Bahl, Atlassian", "event_start": "2025-09-08 12:05", "event_end": "2025-09-08 12:35", "event_type": "GraphQL in Production", - "description": "Abstract\nDiscover how we transformed Jira's issue view to GraphQL and Relay—handling billions of monthly interactions across 100+ field types while meeting enterprise compliance and reliability agreements. With hundreds of developers and teams modifying a decade-old codebase daily in a frontend monorepo, we faced unique challenges in technical design and execution.\nWe'll share:\n- GraphQL schema design for scale\n- Bridging Redux, Sweet State, and Relay in a multi-team environment\n- Incremental rollout strategies with feature flags for safe migration\n- Field-by-field adoption approaches maintaining workflow and compliance\n- Performance optimization under enterprise-scale load\n- Testing approaches at scale\n- Developer experience takeaways\n \nImpact & Takeaways\n- Performance metrics during incremental migration\n- Developer experience improvements\n- Cross-team collaboration\n- Production-proven strategies for state management in existing codebase\n \nThis isn't about building new—it's about modernizing Jira's critical interface while maintaining compliance for enterprise customers. Ideal for leaders coordinating teams and architects planning GraphQL adoption in regulated organizations.", + "description": "Abstract\nDiscover how we transformed Jira's issue view to GraphQL and Relay—handling billions of monthly interactions across 100+ field types while meeting enterprise compliance and reliability agreements. With hundreds of developers and teams modifying a decade-old codebase daily in a frontend monorepo, we faced unique challenges in technical design and execution.\nWe'll share:\n- GraphQL schema design for scale\n- Bridging Redux, Sweet State, and Relay in a multi-team environment\n- Incremental rollout strategies with feature flags for safe migration\n- Field-by-field adoption approaches maintaining workflow and compliance\n- Performance optimization under enterprise-scale load\n- Testing approaches at scale\n- Developer experience takeaways\n\nImpact & Takeaways\n- Performance metrics during incremental migration\n- Developer experience improvements\n- Cross-team collaboration\n- Production-proven strategies for state management in existing codebase\n\nThis isn't about building new—it's about modernizing Jira's critical interface while maintaining compliance for enterprise customers. Ideal for leaders coordinating teams and architects planning GraphQL adoption in regulated organizations.", "goers": "1", "seats": "0", "invite_only": "N", @@ -802,16 +884,16 @@ "venue_id": "2152806", "speakers": [ { - "username": "shawsourav91", - "id": "23098801", - "name": "Sourav Shaw", + "username": "vivekyadav.cse.2005", + "id": "23098813", + "name": "Vivek Yadav", "company": "Atlassian", "custom_order": 0 }, { - "username": "vivekyadav.cse.2005", - "id": "23098813", - "name": "Vivek Yadav", + "username": "kbahl", + "id": "23438695", + "name": "Kritika Bahl", "company": "Atlassian", "custom_order": 1 } @@ -891,7 +973,7 @@ "event_start": "2025-09-08 12:35", "event_end": "2025-09-08 13:45", "event_type": "Breaks / Networking / Special Events", - "goers": "1", + "goers": "2", "seats": "0", "invite_only": "N", "venue": "Foyer Grote Zaal - 2nd Floor", @@ -1027,7 +1109,7 @@ "event_end": "2025-09-08 14:55", "event_type": "Developer Experience", "description": "GraphQL federation has changed how we think about data and it's time to adopt that thinking to how we build UIs and component systems. In this talk, Gabe will share his deep experience from building design systems at Apple, Netflix and now StubHub to help you design yours.\n \nWhat are the advantages GraphQL brings to a traditional React component system? How can fragments optimize the composability of your components? How to reduce duplication while reducing the time you need to ship new features?\n \nWe will provide guidance on how to build and leverage a federated component system along-side your design system. \n \nFinally, we will cover how we've leveraged AI to speedup the creation of our design system and federated components at StuHub. Join to learn more!", - "goers": "1", + "goers": "2", "seats": "0", "invite_only": "N", "venue": "IJzaal - 5th Floor", @@ -1309,7 +1391,7 @@ "event_start": "2025-09-08 15:35", "event_end": "2025-09-08 15:55", "event_type": "Breaks / Networking / Special Events", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "Foyer Grote Zaal - 2nd Floor", @@ -1346,7 +1428,7 @@ "event_end": "2025-09-08 16:25", "event_type": "Developer Experience", "description": "Over the past few years, GraphQL has fallen out of favor for developers looking to build full-stack typescript applications. With projects like TRPC and NextJS, many people have started to pigeonhole GraphQL into an enterprise-shaped box. But this doesn't have to be the case! In this talk, Alec will give a practical introduction with live coding to Houdini, a GraphQL-first application framework and demonstrate how to rapidly move from idea to creation with a state-of-the-art developer experience that brings GraphQL back as a contender for the best choice for smaller applications.", - "goers": "1", + "goers": "2", "seats": "0", "invite_only": "N", "venue": "Studio - 5th Floor", @@ -1438,7 +1520,7 @@ "event_end": "2025-09-08 16:25", "event_type": "GraphQL in Production", "description": "Turning a private GraphQL API into a public one comes with unexpected challenges. We’ll share how we approached this transition—starting from an existing internal schema that wasn’t shaped for external consumers—and the steps we took to expose only what was ready. Using Apollo Federation Contracts, we filtered out unstable or sensitive parts of the graph. Along the way, we defined best practices for the public schema, like cursor-based pagination, using oneOf for inputs and results.\nWe’ll also touch on how we serve the schema through Hive Gateway with a supergraph setup, and the security measures we added, like depth limiting and complexity analysis. To keep things evolving safely, we rely on GraphQL Hive to track usage and guide deprecations.\n \nIf you’re thinking about exposing a GraphQL API—or just want ideas for keeping one clean and manageable—this talk will share what worked for us, what didn’t, and what we learned.", - "goers": "1", + "goers": "2", "seats": "0", "invite_only": "N", "venue": "Grote Zaal - 2nd Floor", @@ -1629,7 +1711,7 @@ "event_end": "2025-09-08 17:05", "event_type": "GraphQL in Production", "description": "alt title: Surviving Change Without Breaking Everything\n \nWhen we launched our new GraphQL API at Netflix, it felt perfect—destined to power hundreds of millions of devices. Yet, change is inevitable. Even if your schema seems flawless today (which it isn't), requirements will shift, new features will emerge, and regrets will follow.\n \nGraphQL promises evolvability, allowing us to move forward without multiple API versions. But how does this hold up in practice? We mark fields as @deprecated, but what happens next? How can we embrace experimentation without entombing technical debt in the API? Does federation complicate things? Evolving your schema without breaking clients is easy, right? Right??\n \nDrawing from experience with the Netflix API, this talk explores techniques for evolving your schema safely and painlessly. We'll cover the schema lifecycle—from experimentation to design, deprecation, and deletion.\n \nAttendees will leave with:\n- Schema design principles that facilitate change\n- Practical techniques for evolving GraphQL schemas\n- Strategies for managing a deprecation workflow\n \nJoin us as we learn to face the inevitability of change with confidence and serenity.", - "goers": "1", + "goers": "3", "seats": "0", "invite_only": "N", "venue": "Grote Zaal - 2nd Floor", @@ -1675,7 +1757,7 @@ "event_end": "2025-09-08 17:45", "event_type": "GraphQL in Production", "description": "Over the past six years, Viaduct has grown from Airbnb’s unified data access layer into a central platform for hosting business logic — now supporting over 1 million lines of code, 500+ monthly contributors, and 100+ teams.\n\nThat scale has brought a familiar risk: the slow creep toward monolith. Viaduct was never meant to be a microservices system, but we’ve had to make deliberate choices to preserve team autonomy, performance, and codebase sanity.\n\nThis talk shares the strategies we’re using — and actively evolving — to make that possible, including:\n\n* Tenant modules that define slices of the GraphQL schema alongside their implementation logic;\n* Relying on GraphQL fragments instead of service calls for inter-module communication;\n* Building ownership and attribution into the platform so teams can trace metrics and errors back to themselves.\n\nWe haven’t fully solved these challenges — but we’ve learned a lot about what works, what breaks, and what to watch for.", - "goers": "0", + "goers": "2", "seats": "0", "invite_only": "N", "venue": "Studio - 5th Floor", @@ -1812,7 +1894,7 @@ "event_start": "2025-09-08 17:45", "event_end": "2025-09-08 18:45", "event_type": "Breaks / Networking / Special Events", - "goers": "1", + "goers": "3", "seats": "0", "invite_only": "N", "venue": "Foyer Grote Zaal - 2nd Floor", @@ -1840,6 +1922,42 @@ "event_subtype": "", "description": "" }, + { + "event_key": "929643", + "active": "Y", + "pinned": "N", + "name": "Cloakroom", + "event_start": "2025-09-09 08:00", + "event_end": "2025-09-09 18:00", + "event_type": "Breaks / Networking / Special Events", + "description": "SECURITY NOTICE\nPlease keep all personal belongings in your possession during the conference. GraphQL, The Linux Foundation nor the Pakhuis de Zwijger are responsible for lost or stolen items. If something is misplaced, check in with an Event Staff member at the registration desk.", + "goers": "0", + "seats": "0", + "invite_only": "N", + "venue": "K Floor - Underground Floor", + "id": "c2fd359dcbd99712bc116a0139bb4d76", + "venue_id": "2191087", + "event_start_year": "2025", + "event_start_month": "September", + "event_start_month_short": "Sep", + "event_start_day": "9", + "event_start_weekday": "Tuesday", + "event_start_weekday_short": "Tue", + "event_start_time": "08:00", + "event_end_year": "2025", + "event_end_month": "September", + "event_end_month_short": "Sep", + "event_end_day": "9", + "event_end_weekday": "Tuesday", + "event_end_weekday_short": "Tue", + "event_end_time": "18:00", + "start_date": "2025-09-09", + "start_time": "08:00:00", + "start_time_ts": 1757397600, + "end_date": "2025-09-09", + "end_time": "18:00:00", + "event_subtype": "" + }, { "event_key": "2", "active": "Y", @@ -1880,12 +1998,12 @@ "event_key": "17", "active": "Y", "pinned": "N", - "name": "Open GraphQL Foundation Board Meeting", + "name": "GraphQL All Hands Meeting", "event_start": "2025-09-09 09:00", "event_end": "2025-09-09 10:30", "event_type": "Breaks / Networking / Special Events", - "description": "Join GraphQL Foundation Board Members and TSC Members for a public meeting and help provide input on what the Foundation's priorities for 2026 should be.", - "goers": "0", + "description": "Help shape the future of GraphQL! Join GraphQL Foundation Board Members, TSC Members, and other community leaders for a public meeting about goals and priorities for 2026, and help us celebrate 2025's wins.", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "IJzaal - 5th Floor", @@ -2048,7 +2166,7 @@ "event_start": "2025-09-09 10:30", "event_end": "2025-09-09 10:45", "event_type": "Breaks / Networking / Special Events", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "Foyer Grote Zaal - 2nd Floor", @@ -2085,7 +2203,7 @@ "event_end": "2025-09-09 11:25", "event_type": "GraphQL Working Group", "description": "Although the topic of namespacing has been brought up repeatedly in the GraphQL community over the last decade, there is an understandable worry that it would lead to anti-patterns in schema design. If namespacing is used as an excuse to avoid coordination between teams, this can result in a fragmented GraphQL schema that reflects current team boundaries as opposed to domain or client concerns.\n\nGraphQL Federation offers an alternative architecture: when coordination is enforced and consistency guaranteed, a large number of teams can contribute to a single, coherent GraphQL schema without the danger of stepping on each other's toes.\n\nEven with that architecture in place however, I believe there are still legitimate use cases for namespacing. In this talk, I will go over some of those use cases, and formulate a set of design principles that could guide the introduction of namespacing in GraphQL.", - "goers": "1", + "goers": "2", "seats": "0", "invite_only": "N", "venue": "IJzaal - 5th Floor", @@ -2130,6 +2248,7 @@ "event_start": "2025-09-09 10:45", "event_end": "2025-09-09 12:15", "event_type": "Unconference", + "description": "\"Unconference\" starts with U! Do you have a demo to share, an itch to scratch, lightning talk to workshop, or proposal you want to brainstorm? There's ample opportunity to bring your thoughts to the unconference table and seek or share feedback.\n\nThe unconference agenda will be created onsite - stay tuned for more info about how you can add your topics.", "goers": "0", "seats": "0", "invite_only": "N", @@ -2156,8 +2275,7 @@ "start_time_ts": 1757407500, "end_date": "2025-09-09", "end_time": "12:15:00", - "event_subtype": "", - "description": "" + "event_subtype": "" }, { "event_key": "21", @@ -2221,7 +2339,7 @@ "event_end": "2025-09-09 12:15", "event_type": "GraphQL Working Group", "description": "The GraphQL community has come together to standardize how people can build distributed systems with GraphQL as an orchestrator. In this talk I will explain the general idea that we have for GraphQL as an Orchestrator in this space and how the new specification is tackling this. We will look at the progress we have made since last GraphQL Conf in the GraphQL composite schema working group and also get some sneak peaks at our early RFCs and prototypes. I will outline how this new specification is taking the best ideas of existing solutions in the market to make the next big leap towards mainstream adoption. This will allow anyone to build tooling by implementing the spec or parts of the spec that seamlessly integrate with other vendors.", - "goers": "1", + "goers": "2", "seats": "0", "invite_only": "N", "venue": "IJzaal - 5th Floor", @@ -2274,7 +2392,7 @@ "event_end": "2025-09-09 14:15", "event_type": "Breaks / Networking / Special Events", "description": "Lunch will be on your own. Amsterdam offers a variety of dining options nearby to suit different tastes and preferences.", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "id": "c792d79fcbf90eafe5aeccec4e753e2a", @@ -2353,7 +2471,8 @@ "event_start": "2025-09-09 14:15", "event_end": "2025-09-09 15:45", "event_type": "Unconference", - "goers": "0", + "description": "\"Unconference\" starts with U! Do you have a demo to share, an itch to scratch, lightning talk to workshop, or proposal you want to brainstorm? There's ample opportunity to bring your thoughts to the unconference table and seek or share feedback.\n\nThe unconference agenda will be created onsite - stay tuned for more info about how you can add your topics.", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "Studio - 5th Floor", @@ -2379,8 +2498,7 @@ "start_time_ts": 1757420100, "end_date": "2025-09-09", "end_time": "15:45:00", - "event_subtype": "", - "description": "" + "event_subtype": "" }, { "event_key": "20", @@ -2444,7 +2562,7 @@ "event_end": "2025-09-09 15:45", "event_type": "GraphQL Working Group", "description": "Curious about how observability is evolving in the GraphQL ecosystem? This session explores the current state of OpenTelemetry and its integration with GraphQL. We'll cover the fundamentals of OpenTelemetry, introduce the OpenTelemetry working group (https://github.com/graphql/otel-wg), and dive into tracing, logging, and metrics - all essential pillars of observability. You'll also learn how OpenTelemetry is being applied in distributed GraphQL architectures to improve performance monitoring and troubleshooting across services. Whether you're new to observability or looking to level up your GraphQL stack, this talk will bring you up to speed on where the community is heading.", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "IJzaal - 5th Floor", @@ -2489,7 +2607,7 @@ "event_start": "2025-09-09 15:45", "event_end": "2025-09-09 16:00", "event_type": "Breaks / Networking / Special Events", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "Foyer Grote Zaal - 2nd Floor", @@ -2526,7 +2644,7 @@ "event_end": "2025-09-09 16:40", "event_type": "GraphQL Working Group", "description": "This discussion embarks on a thought experiment to redesign GraphQL from the ground up. We will explore the choices that might be made if we could start over, free from the constraints of existing implementations.\n\nThe session focuses on key areas where the current GraphQL specification has faced challenges and sparked debate within the community. Discussions will cover: Union Types: Exploring alternative approaches to improve flexibility and usability. Schema-Defined Nullability: Rethinking how nullability is handled to enhance clarity and consistency. Error Handling: Proposing new strategies for more robust and intuitive error management.\n\nThrough collaborative discussions and interactive exercises, participants will contribute insights and ideas, shaping a theoretical vision of what GraphQL 2.0 could look like. This thought exercise is designed to challenge assumptions and inspire innovative solutions.\n\nThe session will conclude with a focus on the practicalities of evolving GraphQL towards a 2.0 version in the real world, exploring how to address these design challenges while considering migration paths and maintaining backward compatibility.", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "IJzaal - 5th Floor", @@ -2592,6 +2710,7 @@ "event_start": "2025-09-09 16:00", "event_end": "2025-09-09 17:30", "event_type": "Unconference", + "description": "\"Unconference\" starts with U! Do you have a demo to share, an itch to scratch, lightning talk to workshop, or proposal you want to brainstorm? There's ample opportunity to bring your thoughts to the unconference table and seek or share feedback.\n\nThe unconference agenda will be created onsite - stay tuned for more info about how you can add your topics.", "goers": "0", "seats": "0", "invite_only": "N", @@ -2618,8 +2737,7 @@ "start_time_ts": 1757426400, "end_date": "2025-09-09", "end_time": "17:30:00", - "event_subtype": "", - "description": "" + "event_subtype": "" }, { "event_key": "24", @@ -2676,7 +2794,7 @@ "event_end": "2025-09-09 17:30", "event_type": "GraphQL Working Group", "description": "This session is an opportunity for working group members to discuss the topics raised in the working group talks earlier in the day, and brainstorm ideas for moving forward.", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "IJzaal - 5th Floor", @@ -2704,6 +2822,42 @@ "end_time": "17:30:00", "event_subtype": "" }, + { + "event_key": "929644", + "active": "Y", + "pinned": "N", + "name": "Cloakroom", + "event_start": "2025-09-10 08:00", + "event_end": "2025-09-10 17:30", + "event_type": "Breaks / Networking / Special Events", + "description": "SECURITY NOTICE\nPlease keep all personal belongings in your possession during the conference. GraphQL, The Linux Foundation nor the Pakhuis de Zwijger are responsible for lost or stolen items. If something is misplaced, check in with an Event Staff member at the registration desk.", + "goers": "0", + "seats": "0", + "invite_only": "N", + "venue": "K Floor - Underground Floor", + "id": "ec905b832dfbb9b0dc7445305f188cbc", + "venue_id": "2191087", + "event_start_year": "2025", + "event_start_month": "September", + "event_start_month_short": "Sep", + "event_start_day": "10", + "event_start_weekday": "Wednesday", + "event_start_weekday_short": "Wed", + "event_start_time": "08:00", + "event_end_year": "2025", + "event_end_month": "September", + "event_end_month_short": "Sep", + "event_end_day": "10", + "event_end_weekday": "Wednesday", + "event_end_weekday_short": "Wed", + "event_end_time": "17:30", + "start_date": "2025-09-10", + "start_time": "08:00:00", + "start_time_ts": 1757484000, + "end_date": "2025-09-10", + "end_time": "17:30:00", + "event_subtype": "" + }, { "event_key": "3", "active": "Y", @@ -2795,7 +2949,7 @@ "event_end": "2025-09-10 09:30", "event_type": "GraphQL in Production", "description": "What started as a single developer's passion project now powers mission-critical APIs for tech giants like Twitter/X, Netflix, Amazon, AirBnB, and Atlassian. As the engine behind Spring for GraphQL and with over 2.2 million monthly downloads, GraphQL Java has become the Java implementation of GraphQL.\n\nHow does a volunteer-driven open source project not just survive, but thrive for a decade? In this talk, we'll share the crucial technical decisions and community building strategies that transformed a hobby project into an industry standard. We'll share how we fostered contributions from over 250 volunteers while maintaining high code quality and project momentum. You'll walk away with actionable insights to help you lead any software project, whether it's open source or enterprise.\n\nAbout the speakers: we are the maintainers of GraphQL Java, who have guided the project from its first commit to becoming the industry standard.", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "Grote Zaal - 2nd Floor", @@ -2893,7 +3047,7 @@ "event_start": "2025-09-10 09:00", "event_end": "2025-09-10 16:00", "event_type": "Solutions Showcase", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "Workspace - 2nd Floor", @@ -3022,7 +3176,7 @@ "event_end": "2025-09-10 10:10", "event_type": "Developer Experience", "description": "Managing separate API definitions for REST and GraphQL APIs that serve the same underlying data can be inefficient and lead to duplicated efforts. At Pinterest, we are streamlining our API definitions and unifying our data models with TypeSpec. TypeSpec allows us to define our API shapes once and generate API schemas in multiple forms such as OpenAPI, Protobuf, and now GraphQL!\n \nWe’ve developed an open-source TypeSpec GraphQL Emitter which generates valid GraphQL schemas directly from TypeSpec definitions.\n \nJoin us for an overview of how TypeSpec and the GraphQL Emitter can streamline your API workflow. We'll explore:\n \n* How TypeSpec's unified definition approach accelerates development across multiple API specs\n* The inner workings of our open-source GraphQL Emitter\n* Our wins and lessons learned while building the GraphQL Emitter\n \nThis talk will be perfect for anyone interested in GraphQL schema generation, unified API definitions, and vague Lord of the Rings references! See you there!", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "IJzaal - 5th Floor", @@ -3160,7 +3314,7 @@ "event_end": "2025-09-10 10:30", "event_type": "Developer Experience", "description": "Effective caching is essential for building fast, resilient mobile apps especially when aiming for offline-first experiences. Apollo Kotlin and Apollo iOS offer a powerful Normalized Cache component tailored to GraphQL. In this lightning talk, we’ll showcase the latest advancements in both libraries, including support for pagination, cache expiration, and other new features designed to simplify and supercharge cache management on mobile.", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "Grote Zaal - 2nd Floor", @@ -3259,7 +3413,7 @@ "event_end": "2025-09-10 10:50", "event_type": "GraphQL in Production", "description": "GraphQL provides flexibility in fetching data but this can prove challenging for caching. In this talk I cover the basics of caching in GraphQL such as layers you can cache at a high level. Layers such as the CDN, client side, server side, and database are touched upon with solutions from the community. The talk will also cover when to use each layer and what statistics to look at for improvement. I talk about how caching at multiple layers provides the best experience for the end user. By the end of this talk beginners will have a path forward to how they can cache at different layers for better performance.", - "goers": "1", + "goers": "2", "seats": "0", "invite_only": "N", "venue": "Grote Zaal - 2nd Floor", @@ -3304,7 +3458,7 @@ "event_start": "2025-09-10 10:50", "event_end": "2025-09-10 11:15", "event_type": "Breaks / Networking / Special Events", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "Foyer Grote Zaal - 2nd Floor", @@ -3341,7 +3495,7 @@ "event_end": "2025-09-10 11:45", "event_type": "Developer Experience", "description": "There are many aspects to consider when building a GraphQL API: Authentication, authorization, performance, schema design, and team workflow to name a few. Each aspect encompasses considerations, practices, and tools (or lack thereof). One aspect, documentation, can be easily neglected. This year at The Guild I spent time exploring that domain and prototyping an open source tool we’re calling Polen.\n\nI will present our thoughts on what characteristics and features we’d like to have from GraphQL documentation tooling and finish with a demo of how Polen tackled some of those things. I hope this session stimulates your own thinking about what documentation tools should include and tangible technical steps we might take to get there.", - "goers": "1", + "goers": "2", "seats": "0", "invite_only": "N", "venue": "Grote Zaal - 2nd Floor", @@ -3525,7 +3679,7 @@ "event_end": "2025-09-10 12:25", "event_type": "GraphQL in Production", "description": "HotelPage Service (HPS) is one of the busiest, most business-critical systems at Booking.com — originally built as a REST API with Protobufs for speed and structure. It was fast but rigid. As product demands grew and clients needed more flexibility, cracks began to show: over-fetching, unclear ownership, and slow iteration cycles.\n \nThis talk shares our real-world journey of modernizing that stack with GraphQL — not just adopting it as a new interface, but transforming how teams design schemas, collaborate across domains, and scale under load. We’ll walk through how we evolved from a proto-backed monolith to a federated GraphQL architecture — improving performance, enabling resolver ownership, and making the schema reflect real product needs.\n \nWhether you're planning a GraphQL migration or scaling one across teams, this talk delivers actionable insights and hard-won lessons from operating at billions of requests per day.\n \nAttendees will gain:\n- Align schema design with client and product needs\n- Handle organisational complexity in federation\n- Avoid pitfalls like over-fetching and the N+1 trap\n- Drive resolver ownership and collaboration\n- Optimise execution paths under high traffic", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "Studio - 5th Floor", @@ -3616,7 +3770,7 @@ "event_start": "2025-09-10 12:25", "event_end": "2025-09-10 13:40", "event_type": "Breaks / Networking / Special Events", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "Foyer Grote Zaal - 2nd Floor", @@ -3759,7 +3913,7 @@ "event_end": "2025-09-10 14:10", "event_type": "GraphQL in Production", "description": "When adopting GraphQL, teams diligently follow \"best practices\" without realizing they're actually choosing between two fundamentally different approaches: designing schemas to serve UI components (frontend-first) or to represent domain models (structure-first). This distinction is rarely framed as an explicit choice in GraphQL literature, with most examples showcasing the structure-first approach by default.\n\nYet this initial decision shapes everything from your team structure to how you handle breaking changes—and if you start with a structure-first approach, it's especially difficult to unwind that decision later. In this session, we'll explore the critical differences between these philosophies, examine how they manifest in real schemas, and analyze the trade-offs each approach presents. You'll see how changes that feel natural in one approach become deeply problematic in the other, and learn to identify which patterns your team has already begun to follow.", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "IJzaal - 5th Floor", @@ -3807,12 +3961,12 @@ "event_key": "927072", "active": "Y", "pinned": "N", - "name": "The New GraphiQL - Dimitri Postolov, -", + "name": "The New GraphiQL - Dimitri Postolov, Independent", "event_start": "2025-09-10 14:20", "event_end": "2025-09-10 14:50", "event_type": "Developer Experience", "description": "In this talk, I will discuss recent developments in GraphiQL, including compiling source code with the React Compiler, support for React 19, migration to Zustand for state management, and the long-awaited transition to the Monaco Editor.", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "Studio - 5th Floor", @@ -3824,7 +3978,7 @@ "username": "en3m", "id": "18743843", "name": "Dimitri Postolov", - "company": "-", + "company": "Independent", "custom_order": 0 } ], @@ -4116,7 +4270,7 @@ "event_end": "2025-09-10 15:30", "event_type": "GraphQL in Production", "description": "\"There are only two hard things in Computer Science: cache invalidation and naming things\".\n\nGraphQL provides many benefits over other query languages. Federation builds on top of this foundation to provide even more flexibility and power. But even with all that GraphQL has to offer, the problem of naming remains.\n\nIn this talk, Jeff Dolle, from The Guild, will share what he's learned about schema design: proven design philosophies, designing for forward compatibility, exposing errors through types, and tips for how to avoid ambiguous or misleading type names.\n\nTogether, we will then go through an example product design meeting: taking user stories and building a complete GraphQL schema.", - "goers": "1", + "goers": "2", "seats": "0", "invite_only": "N", "venue": "IJzaal - 5th Floor", @@ -4161,7 +4315,7 @@ "event_start": "2025-09-10 15:30", "event_end": "2025-09-10 15:50", "event_type": "Breaks / Networking / Special Events", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "Foyer Grote Zaal - 2nd Floor", @@ -4251,7 +4405,7 @@ "event_end": "2025-09-10 16:20", "event_type": "GraphQL in Production", "description": "Pinterest is adopting GraphQL. Given our app's size, we can't simply rewrite everything in one fell swoop. So, we created the Relay Migration API (RMA) — a set of tools to incrementally migrate your React components to consume GraphQL-shaped data while making requests to REST endpoints.\n\nI'll share how we've significantly evolved the RMA after migrating four key surfaces, focusing on the advanced challenges we faced:\n\nRMA recreates objects on every render by default, breaking components expecting stable references. We implemented a caching layer, similar to Relay's, to return consistent objects between renders. RMA originally read from static source objects, creating stale data when Redux state changed. Our solution: a selective subscription system that re-computes GraphQL data only when source fields change, keeping data current while eliminating unnecessary renders. And in cases where Redux and GraphQL schemas fundamentally differ, we built bidirectional mapping with schema validation to ensure data consistency.\nJoin us to learn how the Relay migration API has evolved and how it helps you accelerate your GraphQL migrations without disrupting existing applications!", - "goers": "1", + "goers": "2", "seats": "0", "invite_only": "N", "venue": "Studio - 5th Floor", @@ -4297,7 +4451,7 @@ "event_end": "2025-09-10 16:45", "event_type": "Keynote Sessions", "description": "This talk will give attendees an overview of the structure of GraphQL's official organizations: The GraphQL Foundation and the GraphQL Specification Project. It will get specific about the governance and roadmaps of each organization and their specific priorities in 2025 and beyond.\n\nIn my time serving in these various institutions, I've noticed that even the most active GraphQL practitioners aren't fully aware of what they are and what they do. Attendees will learn about the GraphQL Working Group, the Technical Steering Committee, and the Foundation's Governing Board. We'll also touch upon the various technical working groups and the new Community Working Group. The talk culminates in a call to action for folks to get involved.", - "goers": "1", + "goers": "2", "seats": "0", "invite_only": "N", "venue": "Grote Zaal - 2nd Floor", @@ -4342,7 +4496,7 @@ "event_start": "2025-09-10 16:45", "event_end": "2025-09-10 17:00", "event_type": "Keynote Sessions", - "goers": "0", + "goers": "1", "seats": "0", "invite_only": "N", "venue": "Grote Zaal - 2nd Floor", diff --git a/scripts/sync-sched/speakers.json b/scripts/sync-sched/speakers.json index 3fbf3a5e43..33a352f124 100644 --- a/scripts/sync-sched/speakers.json +++ b/scripts/sync-sched/speakers.json @@ -82,7 +82,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1753974079549 + "~syncedDetailsAt": 1755306559287 }, { "username": "adam.sayah", @@ -136,7 +136,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1751472966787 + "~syncedDetailsAt": 1755306383054 }, { "username": "ajhingran", @@ -192,7 +192,7 @@ 2023, 2025 ], - "~syncedDetailsAt": 1753215856700 + "~syncedDetailsAt": 1755306547408 }, { "username": "alex_reilly.7ldur4l", @@ -255,7 +255,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1751472966787 + "~syncedDetailsAt": 1755306383054 }, { "username": "amy1908", @@ -330,7 +330,7 @@ 2024, 2025 ], - "~syncedDetailsAt": 1753215856700 + "~syncedDetailsAt": 1755306547408 }, { "username": "andrei.bocan", @@ -346,7 +346,7 @@ 2024, 2025 ], - "~syncedDetailsAt": 1753467946105 + "~syncedDetailsAt": 1755306559287 }, { "username": "andrew.doyle1", @@ -483,7 +483,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1753467946105 + "~syncedDetailsAt": 1755306559286 }, { "username": "ardatanrikulu", @@ -508,7 +508,7 @@ 2023, 2025 ], - "~syncedDetailsAt": 1751472966787 + "~syncedDetailsAt": 1755306383054 }, { "username": "arkenflame", @@ -570,7 +570,7 @@ 2024, 2025 ], - "~syncedDetailsAt": 1751472966787 + "~syncedDetailsAt": 1755306383054 }, { "username": "benjamin154", @@ -585,7 +585,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1753467946105 + "~syncedDetailsAt": 1755306559287 }, { "username": "benjie3", @@ -611,7 +611,7 @@ 2024, 2025 ], - "~syncedDetailsAt": 1753467946105 + "~syncedDetailsAt": 1755306559287 }, { "username": "BoD", @@ -626,7 +626,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1753467946105 + "~syncedDetailsAt": 1755306559287 }, { "username": "borisbesemer", @@ -641,7 +641,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1753215856699 + "~syncedDetailsAt": 1755306547407 }, { "username": "brandon.r.minnick", @@ -792,14 +792,15 @@ "position": "Senior Software Engineer", "name": "Christian Ernst", "about": "Christian is currently a Senior Software Engineer at Booking.com. For the last three years Christian has been working to drive the GraphQL initiative across the company by helping teams adopt build new features leveraging GraphQL.", - "location": "", + "location": "Amsterdam", "url": "", "avatar": "//avatars.sched.co/9/39/21066804/avatar.jpg.320x320px.jpg?fff", "socialurls": [], "_years": [ - 2024 + 2024, + 2025 ], - "~syncedDetailsAt": 1749505494947 + "~syncedDetailsAt": 1755306383053 }, { "username": "christian.stangier", @@ -829,7 +830,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1753467946105 + "~syncedDetailsAt": 1755306559287 }, { "username": "danadajian", @@ -864,7 +865,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1753974079549 + "~syncedDetailsAt": 1755306559287 }, { "username": "danielle.man", @@ -909,7 +910,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1751472966787 + "~syncedDetailsAt": 1755306383054 }, { "username": "dkuc", @@ -933,7 +934,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1751472966787 + "~syncedDetailsAt": 1755306383054 }, { "username": "donnasiqizhou", @@ -954,7 +955,7 @@ 2023, 2025 ], - "~syncedDetailsAt": 1753467946105 + "~syncedDetailsAt": 1755306559287 }, { "username": "dotan1", @@ -1037,7 +1038,7 @@ }, { "username": "en3m", - "company": "-", + "company": "Independent", "position": "dimaMachina.com", "name": "Dimitri Postolov", "about": "Open Source developer from Paris\nGraphQL-ESLint, Nextra and GraphiQL maintener", @@ -1062,7 +1063,7 @@ 2023, 2025 ], - "~syncedDetailsAt": 1753467946105 + "~syncedDetailsAt": 1755306559287 }, { "username": "erikwrede2", @@ -1087,7 +1088,7 @@ 2024, 2025 ], - "~syncedDetailsAt": 1752072949897 + "~syncedDetailsAt": 1755306383054 }, { "username": "ernie.turner1", @@ -1126,7 +1127,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1753974079550 + "~syncedDetailsAt": 1755306559287 }, { "username": "fbjork", @@ -1150,7 +1151,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1751472966787 + "~syncedDetailsAt": 1755306383054 }, { "username": "fionabronwen", @@ -1170,7 +1171,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1752072949897 + "~syncedDetailsAt": 1755306383054 }, { "username": "gabe210", @@ -1185,7 +1186,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1753974079550 + "~syncedDetailsAt": 1755306559287 }, { "username": "gabrielschulhof", @@ -1307,7 +1308,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1753974079550 + "~syncedDetailsAt": 1755306559287 }, { "username": "hello2358", @@ -1372,7 +1373,7 @@ 2024, 2025 ], - "~syncedDetailsAt": 1753467946105 + "~syncedDetailsAt": 1755306559287 }, { "username": "ivan.goncharov.ua", @@ -1387,7 +1388,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1753974079550 + "~syncedDetailsAt": 1755306559287 }, { "username": "jamie855", @@ -1441,7 +1442,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1753974079550 + "~syncedDetailsAt": 1755306559287 }, { "username": "jared_cheney.7rad60v", @@ -1481,7 +1482,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1752072949897 + "~syncedDetailsAt": 1755306383054 }, { "username": "jeff.auriemma", @@ -1507,7 +1508,7 @@ 2024, 2025 ], - "~syncedDetailsAt": 1753974079549 + "~syncedDetailsAt": 1755306559287 }, { "username": "jeff737", @@ -1538,11 +1539,16 @@ "location": "Chandlers Ford, UK", "url": "https://github.com/jemgillam", "avatar": "//avatars.sched.co/f/8a/23300543/avatar.jpg.320x320px.jpg?afe", - "socialurls": [], + "socialurls": [ + { + "service": "LinkedIn", + "url": "https://www.linkedin.com/in/jem-gillam-92063b14/" + } + ], "_years": [ 2025 ], - "~syncedDetailsAt": 1753215856699 + "~syncedDetailsAt": 1755306547407 }, { "username": "jens63", @@ -1601,7 +1607,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1752072949897 + "~syncedDetailsAt": 1755306383054 }, { "username": "jim.barton", @@ -1735,6 +1741,21 @@ ], "~syncedDetailsAt": 1754078014495 }, + { + "username": "kbahl", + "company": "Atlassian", + "position": "", + "name": "Kritika Bahl", + "about": "", + "location": "", + "url": "", + "avatar": "", + "socialurls": [], + "_years": [ + 2025 + ], + "~syncedDetailsAt": 1755306383053 + }, { "username": "keerthan.ekbote", "company": "solo.io", @@ -2065,7 +2086,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1751472966787 + "~syncedDetailsAt": 1755306383054 }, { "username": "marco.reni", @@ -2085,7 +2106,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1752072949897 + "~syncedDetailsAt": 1755306547407 }, { "username": "marion84", @@ -2160,7 +2181,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1752503797083 + "~syncedDetailsAt": 1755306547407 }, { "username": "marybriskin", @@ -2215,7 +2236,7 @@ 2024, 2025 ], - "~syncedDetailsAt": 1752503797083 + "~syncedDetailsAt": 1755306547407 }, { "username": "matteo.collina1", @@ -2235,7 +2256,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1752072949898 + "~syncedDetailsAt": 1755306547407 }, { "username": "mauricio.montalvo.guzman", @@ -2251,7 +2272,7 @@ 2024, 2025 ], - "~syncedDetailsAt": 1751472966787 + "~syncedDetailsAt": 1755306383054 }, { "username": "meenakshi.dhanani1", @@ -2341,7 +2362,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1752072949898 + "~syncedDetailsAt": 1755306547407 }, { "username": "michael.bleigh", @@ -2380,7 +2401,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1752503797083 + "~syncedDetailsAt": 1755306547407 }, { "username": "omribruchim", @@ -2519,7 +2540,7 @@ 2024, 2025 ], - "~syncedDetailsAt": 1753974079549 + "~syncedDetailsAt": 1755306559287 }, { "username": "rachit_sengupta", @@ -2593,7 +2614,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1752503797083 + "~syncedDetailsAt": 1755306547407 }, { "username": "rickbijkerk54", @@ -2608,7 +2629,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1752503797083 + "~syncedDetailsAt": 1755306547407 }, { "username": "robert.balicki", @@ -2672,7 +2693,7 @@ 2024, 2025 ], - "~syncedDetailsAt": 1751036945383 + "~syncedDetailsAt": 1755306383053 }, { "username": "saihaj", @@ -2687,7 +2708,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1753215856699 + "~syncedDetailsAt": 1755306547407 }, { "username": "saihajpreet.singh", @@ -2726,7 +2747,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1752503797083 + "~syncedDetailsAt": 1755306547407 }, { "username": "sanvertarmur", @@ -2741,7 +2762,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1751472966787 + "~syncedDetailsAt": 1755306383054 }, { "username": "sasanders26", @@ -2762,7 +2783,7 @@ 2024, 2025 ], - "~syncedDetailsAt": 1753215856699 + "~syncedDetailsAt": 1755306547407 }, { "username": "sasha177", @@ -2892,21 +2913,6 @@ ], "~syncedDetailsAt": 1749502079623 }, - { - "username": "shawsourav91", - "company": "Atlassian", - "position": "Principal Engineer", - "name": "Sourav Shaw", - "about": "Engineer with decade of experience in software. Worked across platform and product teams at Atlassian.\nCurrently working as an architect in Jira's Issue Domain at Atlassian.", - "location": "", - "url": "", - "avatar": "//avatars.sched.co/6/e0/23098801/avatar.jpg.320x320px.jpg?8c8", - "socialurls": [], - "_years": [ - 2025 - ], - "~syncedDetailsAt": 1752503797083 - }, { "username": "siva27", "company": "Intuit", @@ -2940,7 +2946,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1753974079549 + "~syncedDetailsAt": 1755306559287 }, { "username": "spencer211", @@ -2977,7 +2983,7 @@ 2024, 2025 ], - "~syncedDetailsAt": 1751036945383 + "~syncedDetailsAt": 1755306383053 }, { "username": "stefan239", @@ -3022,7 +3028,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1752503797083 + "~syncedDetailsAt": 1755306547407 }, { "username": "suresh_muthu", @@ -3129,7 +3135,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1752072949897 + "~syncedDetailsAt": 1755306383054 }, { "username": "tim.hall.engr", @@ -3168,7 +3174,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1752503797083 + "~syncedDetailsAt": 1755306547407 }, { "username": "tristan119", @@ -3263,7 +3269,7 @@ 2024, 2025 ], - "~syncedDetailsAt": 1751036945383 + "~syncedDetailsAt": 1755306383053 }, { "username": "vincent.desmares", @@ -3283,9 +3289,9 @@ { "username": "vivekyadav.cse.2005", "company": "Atlassian", - "position": "Modernizing a Million Lines of Code: Jira's Journey to GraphQL and Relay", + "position": "", "name": "Vivek Yadav", - "about": "Masters from IIT Roorkee. Engineer with decade of experience in software previously Worked in Amazon & Uber. \nIn Atlassian Using GraphQL to handle JIRA's scale and optimising for better observability, safe rollouts and making JIRA more responsive.", + "about": "Masters from IIT Roorkee. Engineer with decade of experience in software previously Worked in Amazon & Uber.\nIn Atlassian Using GraphQL to handle JIRA's scale and optimising for better observability, safe rollouts and making JIRA more responsive.", "location": "", "url": "", "avatar": "//avatars.sched.co/5/b1/23098813/avatar.jpg.320x320px.jpg?d11", @@ -3293,14 +3299,14 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1752503797083 + "~syncedDetailsAt": 1755306547407 }, { "username": "vmjohnson999", "company": "The New York Times", "position": "Android Engineer", "name": "Vanessa Johnson", - "about": "Vanessa Johnson is an Android Engineer at The New York Times working on the Games Android app. She loves building mobile apps and any technical topics she finds interesting. She is passionate about accessibility, is working on various side projects, and has a newsletter & a podcast. When she isn’t coding she is usually playing pickup basketball or watching a horror movie.", + "about": "Vanessa Johnson is an Android Engineer at The New York Times working on the Games Android app. She loves building mobile apps and any technical topics she finds interesting. She is passionate about accessibility, is working on various side projects, and has a newsletter & an upcoming podcast. When she isn’t coding she is usually playing pickup basketball or watching a horror movie.", "location": "New York City", "url": "https://vanessamj99.github.io", "avatar": "//avatars.sched.co/c/54/23098810/avatar.jpg.320x320px.jpg?394", @@ -3329,7 +3335,7 @@ 2024, 2025 ], - "~syncedDetailsAt": 1753467946105 + "~syncedDetailsAt": 1755306559287 }, { "username": "x65han", @@ -3344,7 +3350,7 @@ "_years": [ 2025 ], - "~syncedDetailsAt": 1753215856699 + "~syncedDetailsAt": 1755306547407 }, { "username": "yaacovcr", @@ -3419,11 +3425,16 @@ "location": "", "url": "", "avatar": "//avatars.sched.co/f/a8/23098819/avatar.jpg.320x320px.jpg?d3f", - "socialurls": [], + "socialurls": [ + { + "service": "LinkedIn", + "url": "https://www.linkedin.com/in/luli-rosenberg/" + } + ], "_years": [ 2025 ], - "~syncedDetailsAt": 1753215856699 + "~syncedDetailsAt": 1755306547407 } ] } \ No newline at end of file diff --git a/scripts/sync-sched/sync.ts b/scripts/sync-sched/sync.ts index 3598bcc039..6b92cf15c2 100644 --- a/scripts/sync-sched/sync.ts +++ b/scripts/sync-sched/sync.ts @@ -261,7 +261,7 @@ async function updateSpeakerDetails( } function help() { - return console.log("Usage: tsx sync.ts --year ") + return console.log("Usage: tsx sync.ts --year --quota ") } function partitionRemovedSpeakers(