|
| 1 | +# Managing social media accounts |
| 2 | + |
| 3 | +The project obtains and manages social media accounts in order to help |
| 4 | +promote the project and to share content that benefits the ecosystem. |
| 5 | + |
| 6 | +Currently the project has the following social media accounts: |
| 7 | + |
| 8 | +* [bluesky](https://bsky.app/profile/nodejs.org) |
| 9 | +* [twitter](https://x.com/nodejs) |
| 10 | +* [Facebook](https://www.facebook.com/nodejsfoundation) |
| 11 | +* [LinkedIn](https://www.linkedin.com/company/node.js-foundation/) |
| 12 | + |
| 13 | +## bluesky |
| 14 | + |
| 15 | +Bluesky is managed directly by the project. Automation is used |
| 16 | +to request posts/reposts as outlined in |
| 17 | +[nodejs/bluesky](https://github.com/nodejs/bluesky). |
| 18 | + |
| 19 | +Login credentials are available to members of the Technical |
| 20 | +Steering Committee, but are not to be used directly except |
| 21 | +in exceptional circumstances. |
| 22 | + |
| 23 | +## Twitter/X |
| 24 | + |
| 25 | +Day to day management of the Twitter/X account has been |
| 26 | +delegated to the Foundation Staff. |
| 27 | + |
| 28 | +In addition, it has been agreed that Releasers may login |
| 29 | +and post when doing a release, and TSC members may post |
| 30 | +an announcement of a release if a releaser is not able to |
| 31 | +do it themselves. |
| 32 | + |
| 33 | +Login credentials are available to members of the Technical |
| 34 | +Steering Committee. Releasers may request access by |
| 35 | +opening an issue in the nodejs/admin repo asking for access. |
| 36 | + |
| 37 | +## Facebook |
| 38 | + |
| 39 | +Day to day management of the Facebook account has been |
| 40 | +delegated to the Foundation Staff. |
| 41 | + |
| 42 | +No project members have access to the Facebook account. |
| 43 | + |
| 44 | +## Linkedin |
| 45 | + |
| 46 | +Day to day management of the LinkedIn account has been |
| 47 | +delegated to the Foundation Staff. |
| 48 | + |
| 49 | +No project members have access to the LinkedIn account. |