forked from nodejs/node
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
doc: add info on how project manages social media
Signed-off-by: Michael Dawson <[email protected]> PR-URL: nodejs#57318 Reviewed-By: Rafael Gonzaga <[email protected]> Reviewed-By: Joyee Cheung <[email protected]> Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
- Loading branch information
Showing
1 changed file
with
49 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
# Managing social media accounts | ||
|
||
The project obtains and manages social media accounts in order to help | ||
promote the project and to share content that benefits the ecosystem. | ||
|
||
Currently the project has the following social media accounts: | ||
|
||
* [bluesky](https://bsky.app/profile/nodejs.org) | ||
* [twitter](https://x.com/nodejs) | ||
* [Facebook](https://www.facebook.com/nodejsfoundation) | ||
* [LinkedIn](https://www.linkedin.com/company/node.js-foundation/) | ||
|
||
## bluesky | ||
|
||
Bluesky is managed directly by the project. Automation is used | ||
to request posts/reposts as outlined in | ||
[nodejs/bluesky](https://github.com/nodejs/bluesky). | ||
|
||
Login credentials are available to members of the Technical | ||
Steering Committee, but are not to be used directly except | ||
in exceptional circumstances. | ||
|
||
## Twitter/X | ||
|
||
Day to day management of the Twitter/X account has been | ||
delegated to the Foundation Staff. | ||
|
||
In addition, it has been agreed that Releasers may login | ||
and post when doing a release, and TSC members may post | ||
an announcement of a release if a releaser is not able to | ||
do it themselves. | ||
|
||
Login credentials are available to members of the Technical | ||
Steering Committee. Releasers may request access by | ||
opening an issue in the nodejs/admin repo asking for access. | ||
|
||
|
||
Day to day management of the Facebook account has been | ||
delegated to the Foundation Staff. | ||
|
||
No project members have access to the Facebook account. | ||
|
||
|
||
Day to day management of the LinkedIn account has been | ||
delegated to the Foundation Staff. | ||
|
||
No project members have access to the LinkedIn account. |