Update 11-golden-path-wg-june-2026.md

[gmale]

Added my name to the attendees.

[linux-foundation-easycla]

• ❌ - login: @gmale / name: Kevin Gorham. The commit (7375c54, 8c9de59) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

[gmale]

Tried clicking the links and following the steps. That ended on a page asking me for the name/email of a CLA contact at Facebook for the golden-path-wg repo (does that role even exist?).

So I tried to fix this with internal tooling and failed my first attempt. I'll keep poking around... cc @benjie @mjmahone

[gmale]

Following up here: @benjie do you know the next steps to move CLA forward? I went through the form again, twice. The first time, it suggested filing a support ticket, if I don't know who the CLA Manager for Meta would be–I did that and apparently someone will email me about it soon. The second time, I entered Matt's name and email as the CLA Manager and it said, "An email has been sent to Matt Mahoney to request that they start the CLA signature process."

I also tried @mjmahone 's suggestion of making a PR against graphql-wg (graphql/graphql-wg#2003). The theory was that "the golden-path WG repo was created after we setup our CLA approvals." But the graphql-wg PR failed in the same way.

[benjie]

Hi @gmale - it was great to see you again at the WG! Your contact within Meta is @mjmahone I think, he'll need to ensure you're authorized. The test repo is http://github.com/graphql/easycla but it shouldn't be necessary to open another PR there - all of the repos should work the same.

You can use:

git log --format='Author: %an <%ae> Committer: %cn <%ce>'

to see the committer/author details for the commit. You're using an @gmail.com address; you must make sure this is the one that Meta have authorized for you.