nodejs
Ambassador program
Some related background
- https://github.com/nodejs/next-10/issues/266 - recent issue that discussed this PR
- Deep dive on advocacy where we disucussed seeting up an ambassador program - https://github.com/nodejs/next-10/issues/247
- Some related discussion - https://github.com/nodejs/next-10/issues/259
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
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 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.
@mhdawson For the ambassadors, what is the big incentive? Is the incentive here, basically that ambassadors get their content promoted by the official Node.js social media accounts?
@mhdawson For the ambassadors, what is the big incentive? Is the incentive here, basically that ambassadors get their content promoted by the official Node.js social media accounts?
That is the primary benefit, along with the ability to get some feedback on their content from mainainters and some direction on whathe the maintainers believe are important/priority messages to share.
@mhdawson For the ambassadors, what is the big incentive? Is the incentive here, basically that ambassadors get their content promoted by the official Node.js social media accounts?
That is the primary benefit,
What will prevent this from attracting people primarily interested in increasing their social media following?
along with the ability to get some feedback on their content from mainainters
Can't anyone ask for maintainer feedback?
and some direction on whathe the maintainers believe are important/priority messages to share.
Wouldn't this information be publicly available to anyone?
What will prevent this from attracting people primarily interested in increasing their social media following?
Nothing but the TSC should select/approve people with care
Can't anyone ask for maintainer feedback?
This program provides a specific way they can ask for feedback, and we should prioritize it for the ambassadors, we could even close issues asking for feedback from non-ambassadors in the ambassadors repo.
Wouldn't this information be publicly available to anyone?
Yes
@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.
Can't anyone ask for maintainer feedback?
This program provides a specific way they can ask for feedback, and we should prioritize it for the ambassadors, we could even close issues asking for feedback from non-ambassadors in the ambassadors repo.
We can't even get people to put news items in a designated place. Given that, is it reasonable to expect that maintainers are going to prioritize looking in a siloed ambassadors repo to provide helpful feedback? Won't most maintainers ignore that repo the same way they did all the other examples I provided earlier?
I don't think you're going to persuade me that this is likely to work, and I don't I'm likely to persuade you either. So feel free to proceed unless someone else objects. If you're right and I'm wrong, then great!
I still don't understand what problem we're trying to solve. Like, what's an example of something where Node.js just couldn't get their message out on social media and this will fix that?
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.
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.
@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.
Squashed, rebased and forced pushed to see if that will fix the Windows failure as I think that job has been temporarily disabled.