You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Discuss initial cut at text for ambassador program #266
@nodejs/next-10 we discussed in the team meeting today, and made some edits. Plan is for me to open the issue in the Node.js/node repo on Monday unless there are concerns/objections raised before then.
If you can take a look before then and let me know if you have any comments or suggestions that would be great.
I would like to invite feedback from @anfibiacreativa and @whitep4nth3r, with whom I brainstormed a bit around the problem (and IMHO they would both make great ambassadors).
The project aims to support and encourage developer advocates
Do ambassadors need to be "developer advocates" specifically? What about developers building in public with Node?
that this content does not overly market their employer
I like this addition a lot. It may be worth also adding in something like "does not overly market their employer or product/business" if you choose to expand the pool of eligible ambassadors to not only developer advocates.
It also might be useful to stipulate that for communication purposes and collaboration opportunities, ambassadors should be a member of the OpenJS Slack.
Reacted by Matteo Collina, Michael Dawson and Stephen Belanger
Do ambassadors need to be "developer advocates" specifically? What about developers building in public with Node?
Thanks for the suggestion updated to say developers or developer advocates and the part about not promoting products too much. Also added at the bottom the need to be part of the OpenJS slack along with the invite link.
@mhdawson I had written draft in a private repo to brainstorm with @mcollina and @whitep4nth3r (keeping it there not to confuse anyone). I would like to share that with the rest. Should I post it here?
Activity
mhdawson commentedon May 1, 2024
@nodejs/next-10 we discussed in the team meeting today, and made some edits. Plan is for me to open the issue in the Node.js/node repo on Monday unless there are concerns/objections raised before then.
If you can take a look before then and let me know if you have any comments or suggestions that would be great.
mcollina commentedon May 2, 2024
I would like to invite feedback from @anfibiacreativa and @whitep4nth3r, with whom I brainstormed a bit around the problem (and IMHO they would both make great ambassadors).
whitep4nth3r commentedon May 2, 2024
Do ambassadors need to be "developer advocates" specifically? What about developers building in public with Node?
I like this addition a lot. It may be worth also adding in something like "does not overly market their employer or product/business" if you choose to expand the pool of eligible ambassadors to not only developer advocates.
It also might be useful to stipulate that for communication purposes and collaboration opportunities, ambassadors should be a member of the OpenJS Slack.
mhdawson commentedon May 2, 2024
@whitep4nth3r
Thanks for the suggestion updated to say developers or developer advocates and the part about not promoting products too much. Also added at the bottom the need to be part of the OpenJS slack along with the invite link.
mhdawson commentedon May 6, 2024
PR created here - nodejs/node#52857
anfibiacreativa commentedon May 9, 2024
@mhdawson I had written draft in a private repo to brainstorm with @mcollina and @whitep4nth3r (keeping it there not to confuse anyone). I would like to share that with the rest. Should I post it here?
mhdawson commentedon May 10, 2024
@anfibiacreativa is that draft an alternative to nodejs/node#52857 ? I so then commenting in that issue might make sense at this point.
mhdawson commentedon May 29, 2024
PR is opened so closing this one out.
trivikr commentedon Jun 6, 2024
@mhdawson did you miss closing this issue?
mhdawson commentedon Jun 26, 2024
Closing as PR landed in Node.js/node repo