|
| 1 | +# Advocacy Ambassador program |
| 2 | + |
| 3 | +Node.js aims to support and encourage developers and developer |
| 4 | +advocates to promote Node.js as a project and to help communicate |
| 5 | +key messages to their constituencies. |
| 6 | + |
| 7 | +The ambassador program does that by: |
| 8 | + |
| 9 | +* Maintaining an up-to-date set of messages that the Node.js maintainers would like ambassadors |
| 10 | + to promote. These will be documented in the nodejs/ambassadors repository. |
| 11 | +* Maintaining an up-to-date set of topics on which additional content |
| 12 | + would benefit the community. These will be documented in the |
| 13 | + nodejs/ambassadors repository. |
| 14 | +* Providing a space for collaborators to share new topics/features they |
| 15 | + are working on when they would be happy for ambassadors to help share and get |
| 16 | + early feedback. |
| 17 | +* Helping ambassadors promote content that aligns with the |
| 18 | + messages and topics defined. |
| 19 | +* Advocating for ambassadors to be part of the OpenJS speakers bureau, even if the |
| 20 | + ambassador is not otherwise an active member of the project itself. |
| 21 | + |
| 22 | +## Ambassadors nominations |
| 23 | + |
| 24 | +Any member of the Node.js organization may nominate an ambassador. |
| 25 | +The Technical Steering Committee (TSC) will review/approve ambassadors. |
| 26 | + |
| 27 | +In the initial phase of the program: |
| 28 | + |
| 29 | +* There will be a maximum of 4 ambassadors. |
| 30 | +* The term will be for the calendar year. After a year, ambassadors automatically |
| 31 | + drop out of the ambassador list and must be re-nominated. |
| 32 | +* Ambassadors will be documented on the nodejs/ambassadors `README.md`. |
| 33 | + |
| 34 | +The TSC may remove an ambassador for any reason, |
| 35 | +including promoting content misaligned with the project. |
| 36 | + |
| 37 | +Members of the Node.js organization can nominate ambassadors by opening |
| 38 | +a discussion issue with the nomination in |
| 39 | +[nodejs/collaborators](https://github.com/nodejs/collaborators/) |
| 40 | +titled `Nomination X to be an Ambassador`, where X is the name of the person |
| 41 | +being nominated. |
| 42 | + |
| 43 | +## Reviewing content |
| 44 | + |
| 45 | +Ambassadors are asked to share links to new content before asking |
| 46 | +for the content to be promoted. The goal is to provide the opportunity |
| 47 | +for collaborators to help improve content as opposed to a detailed |
| 48 | +nitpick review. |
| 49 | + |
| 50 | +This is done by opening an issue in the nodejs/ambassadors |
| 51 | +repository, which limits access to members of the Node.js |
| 52 | +organization. The issue may include the link to existing published |
| 53 | +content or a draft of the content itself. |
| 54 | + |
| 55 | +Interested members of the Node.js organization may comment |
| 56 | +in the issue and the ambassadors are expected to |
| 57 | +consider those suggestions and update the content when they feel it |
| 58 | +is appropriate. |
| 59 | + |
| 60 | +Explicit approval is not required in the issue (i.e. if there is no |
| 61 | +input, that's OK), but review comments should be addressed before |
| 62 | +requesting promotion. |
| 63 | + |
| 64 | +## Expectations on Ambassadors |
| 65 | + |
| 66 | +Ambassadors are expected to engage both within the project and externally |
| 67 | +in a manner that is consistent with the project's |
| 68 | +[Code of Conduct](https://github.com/nodejs/admin/blob/main/CODE_OF_CONDUCT.md) |
| 69 | +as well as the additional expectations outlined in |
| 70 | +[Member Expectations](https://github.com/nodejs/admin/blob/main/MemberExpectations.md). |
| 71 | + |
| 72 | +## Promoting content |
| 73 | + |
| 74 | +We trust ambassadors to only request promotion of content that lines |
| 75 | +up with the messages and topics outlined, that this content does not overly |
| 76 | +market their employer or product/business, and that they have followed the review |
| 77 | +process. An ambassador can request promotion of content in the following ways: |
| 78 | + |
| 79 | +* Requesting that a post be reposted by the Node.js account on a social media platform. |
| 80 | +* @-mentioning the nodejs/ambassadors team to ask other ambassadors to repost. |
| 81 | +* Posting a link to the content in the "what's new" issue in nodejs/ambassadors |
| 82 | + so that it goes out on the news feed. |
| 83 | + |
| 84 | +Foundation staff will repost the social media post |
| 85 | +without any need for validation based on the request coming from |
| 86 | +an ambassador. These requests can be made through the existing social channel |
| 87 | +in the OpenJS Slack. For that reason and for communication purposes and |
| 88 | +collaboration opportunities, ambassadors should be members of the |
| 89 | +[OpenJS Slack](https://slack-invite.openjsf.org/). |
0 commit comments