Clarify requirements for GraphQL Ambassadors - #2502
Conversation
Added clarification about the requirements for GraphQL Ambassadors.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
||
| Ambassadors are trusted go-to community leaders driven by a passion for GraphQL projects and strive to nurture the growing GraphQL community through collaboration, education and outreach. | ||
|
|
||
| GraphQL Ambassadors are not necessarily required to be deep GraphQL experts (although it's definitely appreciated), but they need to share a passion for helping others and spreading the GraphQL word and recognized best practices. |
There was a problem hiding this comment.
I don't agree with the "recognized best practices" part - if someone wants to say "I don't think the Global Object Identification Specification, the current GraphQL best practice, is what people should be building into their schemas - instead they should be using @lookup" then I think that should absolutely be allowed and encouraged. Best practices are just generally agreed upon broad opinions, rules of thumb, but they aren't universally applicable or universally correct, and someone who is passionately opposed to one of them should not necessarily be prevented from becoming an ambassador.
There was a problem hiding this comment.
Fair enough.
This was written on the spot and can definitely be improved. What I wanted to express is that low expertise is fine as long as the information is correct. It's okay to say "I don't know". It's not okay to improvise an answer.
There was a problem hiding this comment.
@benjie 100%. We ask that Ambassadors conduct themselves in a professional manner. But when it comes to things developers often hold strong opinions on and will discuss at length, we don't need our Ambassadors to completely "toe the party line" as it were.
There was a problem hiding this comment.
@martinbonnin if that's your intent I don't think it even needs to go on graphql.org. It should be in a guidance section of the Ambassador handbook. Where you've added it at the moment is for anyone to read to find out what an Ambassador is, not an instruction on Ambassador behaviour.
There was a problem hiding this comment.
@jemgillam I've removed the "best practices" part.
I'd prefer this to be in the main ambassadors page though.
The aim here is for everyone (including the community at large) to acknowledge that the program favors energy and passion over expertise, if this the direction we're taking.
There was a problem hiding this comment.
I'm not entirely comfortable with the second sentence about the program on the entire website stating that an Ambassador is not necessarily an expert.
You have to remember we do have some deep technical experts and project maintainers in their midst, plus a project maintainer may never do any other kind of community outreach and so doesn't fit under "spreading the word". It is hard to describe them all in one succinct way.
| Ambassadors are trusted go-to community leaders driven by a passion for GraphQL projects and strive to nurture the growing GraphQL community through collaboration, education and outreach. | ||
|
|
||
| GraphQL Ambassadors are not necessarily required to be deep GraphQL experts (although it's definitely appreciated), but they need to share a passion for helping others and spreading the GraphQL word. |
There was a problem hiding this comment.
Maybe this addresses your concern whilst maintaining positive wording?
| Ambassadors are trusted go-to community leaders driven by a passion for GraphQL projects and strive to nurture the growing GraphQL community through collaboration, education and outreach. | |
| GraphQL Ambassadors are not necessarily required to be deep GraphQL experts (although it's definitely appreciated), but they need to share a passion for helping others and spreading the GraphQL word. | |
| GraphQL's Ambassadors are a group of trusted educators, speakers, event organizers, maintainers, experts, enthusiasts and community leaders driven by a passion for GraphQL and for helping people. Ambassadors strive to nurture the growing GraphQL community through collaboration, education and outreach. |
There was a problem hiding this comment.
Talking with @jem, I didn't realize maintenance of GraphQL projects was such a big part of the program (vs outreach). I personnally was expecting a more prominent "outreach" component in the ambassador role.
Put it otherwise, I'd expect from a maintainer to also actively engage with the community, through social networks, conferences, locals, videos, etc... Not just shipping code.
I believe it's not an uncommon expectation to have from an ambassador. An ambassador is someone that represent the interests of a country (GraphQL) in foreign land (the community at large). But I'm happy to let it go, I was mainly opening this for discussion. I'm fine either way.
3 participants
This is a first shot, brainstorming during the primary working session meeting.