rfc: updates to Ambassador program #90
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here's a document written for prospective Ambassadors.
After discussion both with this working group and elsewhere in the Foundation, this is taking a very nice shape now.
I've tightened up the Ambassador requirements, but these shouldn't be too onerous. It's inspired both by the AsyncAPI program and the CNCF program. Members of this group rather liked the idea that a prospective Ambassador is already doing Ambassador tasks, so I hope that is reflected.
We have an opportunity to present this at the next board meeting which I think is next week (26 June), after that it'll be time to put this on the website and take applications.
I have the beginnings of a spreadsheet of individuals to invite to apply - around 40 people. We will also be inviting member companies of the Foundation to nominate Ambassadors both within their organisation and outside. Bear in mind not all of these people will want to go through with applying! So if you have any ideas do reach out to me (privately) to add their name. I particularly need names of project maintainers.
I think that's all, thanks everyone! Looking forward to getting this off the ground and, yes, possibly announcing it at GraphQL Conf!