Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/nodejs/tweet
Guidelines for the Node.js Twitter and automation through PRs to tweet.
https://github.com/nodejs/tweet
node nodejs twitter
Last synced: 3 months ago
JSON representation
Guidelines for the Node.js Twitter and automation through PRs to tweet.
- Host: GitHub
- URL: https://github.com/nodejs/tweet
- Owner: nodejs
- License: mit
- Archived: true
- Created: 2020-07-09T18:32:36.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2023-04-27T09:04:47.000Z (over 1 year ago)
- Last Synced: 2024-04-14T00:38:25.678Z (9 months ago)
- Topics: node, nodejs, twitter
- Language: JavaScript
- Homepage:
- Size: 91.8 KB
- Stars: 21
- Watchers: 5
- Forks: 21
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# nodejs/tweet
The Node.js Social handles ([Twitter](https://twitter.com/nodejs), [LinkedIn](https://www.linkedin.com/company/node-js), [Facebook](https://www.facebook.com/nodejsfoundation/), and [Mastodon](https://social.lfx.dev/@nodejs)) are operated by the OpenJS Foundation.
* **For retweets, likes, and other simple requests**: Ping the [Node.js Social Team Slack Channel](https://openjs-foundation.slack.com/archives/C0142A39BNE). Tag the `@nodejs-social-team` handle for fastest response.
* **For planned announcements and longer form posts**: Please fill out the [Node.js Social Request Form](https://forms.gle/Y5Jo42tb1AMqn9Rj8).
If you have any questions, please review the [Node.js Social Guidelines](https://docs.google.com/document/d/1yrYZJ2twrbpUuScbo3rmN_v-Jfv6d2tO74nCT6PcpxI/edit?usp=share_link).
Previous instructions
## How we approach content for Twitter
Both Social Team members and Node.js project collaborators submitting PRs should approach creating content for Twitter in the same way:
- The language being written should be as precise and clear as possible.
- There should generally be no hashtags contained within, unless they are relevant to real-world events like conferences.
- Hashtags like #nodejs or #javascript are relatively unused outside of spam at this point, and add no additional semantic value on Twitter.
- We do not amplify or share content that could unduly promote or benefit one corporation that does work in the space of Node.js over another.
- We try to amplify the collaborators who are doing the work rather than anonymously taking credit for it as the project.
- For general releases, we try to amplify those on the Release Team who are cutting releases directly rather than tweeting release announcements directly from the project's account.
- For security releases, it is important that the tweet come directly from the Node.js Twitter account (the authoritative source) so that readers will immediately recognize the announcement. Additionally, if there is an announcement tweet from collaborators who put in the effort to make the security release happen, those tweets should also be amplified with a retweet from the Node.js account.
- In situations where a collaborator might become a target for harassment, post from the project account directly.
- We aim to support and amplify ecosystem members who are doing interesting and nice work.
This list should not be expected to be comprehensive nor exclusive, and may be clarified, ammended, or otherwise modified to ensure that the way the Social Team works in the context of our Twitter account is well represented here.
### Other tips for tweets:
- If you are driving folks to a link, place that link at the end of the tweet so that Twitter displays the content as a Twitter Card.
- Are you trying to get people to take some sort of action? (Read blog post, participate in an event, etc...) If so, then make that "call to action" text clear and use encouraging language.
## Request a tweet from the [@nodejs](https://twitter.com/nodejs) Twitter account
To request a tweet from the @nodejs account, follow the instructions here: [/tweets](./tweets/)
## Process for tweets regarding Node.js releases:
For all major and minor releases, the following process should be done:
1. Retweet canonical tweet from person leading the effort
1. Quote tweet the canonical tweet with the following language: (if possible wait 1-2hrs after step 1, the retweet above)
```
📣 Node.js vX.x.x now available
$ nvm install x.x.x
Thank you to all the people who helped make it happen 🙌
```
For security release tweets, the process is documented here: https://github.com/nodejs/node/blob/master/doc/contributing/security-release-process.md