Ambassador program

[mhdawson]

No description provided.

[nodejs-github-bot]

Review requested:

• @nodejs/tsc

[mhdawson]

Some related background

• Discuss initial cut at text for ambassador program next-10#266 - recent issue that discussed this PR
• Deep dive on advocacy where we disucussed seeting up an ambassador program - Deep Dive: Advocacy and promotion for the project next-10#247
• Some related discussion - Next steps from Advocacy Deep dive next-10#259

[benjamingr]

@goldbergyoni@lirantal

[mhdawson]

@kyliewd FYI as the current approach asks for retweets through slack.

[kyliewd]

thanks @mhdawson - this sounds fine to me. i would add though that as ambassadors for the project, they need to follow CoC guidelines (especially when promoting content)

i'm happy to help promote this as needed

[mhdawson]

@kyliewd thanks for reviewing/confirming.

[mhdawson]

@kyliewd and good point about the CoC, will add some words around that.

[Trott]

I won't block over this but: We seem to spin these things up from time to time (Evangelism, Social Media Delegates, Outreach, Node.js Collection, and more) and it seems that they never work out well. I don't see an indication of what is different this time around that makes a more successful initiative likely. Maybe a clear sentence explaining the goal (or mission or vision or whatever) in the document would help mitigate the "Haven't we seen this before?" sense I'm getting. Is this based on a successful initiative in another big project (like Python or Rust) or something like that?

[Trott]

TBD needs to be replaced, right?

[mhdawson]

@Trott since you've indicated you won't block, I assume no response to the comment of "this never works out well". Buy my 2 cents I think this is a much more specific/constrained proposal than some of the instances you pointed to which started as WIP and never went beyond that.

TBD replaced

[mhdawson]

@Trott, I can't find it right now but on the question of calendar year versus 12 months I think calendar year makes more sense. It will be easier to handle all together versus trying to track 12 months for each ambassador.

[Trott]

Michael let me know that there was a 2-hour discussion about this in February. I can't find any comprehensive notes (just a few bullet points, but also maybe I don't know where to look?--the siloing problem is real!), but there's a video at https://www.youtube.com/live/gTgHkyCyXP0.

So, you know, if anyone else wants a fuller background on where this is coming from, that might help.

[Trott]

Michael let me know that there was a 2-hour discussion about this in February. I can't find any comprehensive notes (just a few bullet points, but also maybe I don't know where to look?--the siloing problem is real!), but there's a video at https://www.youtube.com/live/gTgHkyCyXP0.

So, you know, if anyone else wants a fuller background on where this is coming from, that might help.

One surprise for me is that it seems that the goal here is to solve friction/pain points experienced by self-identified advocates for Node.js. That's a separate (but, obviously, related) population from Node.js core and Node.js users. It's a different lens than the one I was looking through.

[mhdawson]

@Trott thanks for adding the link to the video, thats probably something I should have included when I opended the PR as providing good context.

[avivkeller]

Tip

I'm not a core collaborator, and these are only suggestions

[mhdawson]

Squashed, rebased and forced pushed to see if that will fix the Windows failure as I think that job has been temporarily disabled.

[mhdawson]

Plan to land tomorrow assuming CI passes.

[mhdawson]

Landed in 756b397