remove obsolete social-team.md

[Trott]

I might be mistaken, but I think the social-team.md doc is obsolete and does not reflect either the current set of social media properties for the project or how those properties are managed. /ping @joesepi @nodejs/social for confirmation

[Trott]

To clarify: If I'm not mistaken, all of social media management for Node.js is now in the hands of the Foundation and it is up to them to indicate what process should be used to requrest a post, etc.

If I'm wrong and the document still accurately reflects things broadly, then I'll close this and open a different PR to update it so it is not linking to archived repositories and lists our current set of social media properties etc.

[joyeecheung]

I think the more accurate document is currently https://github.com/nodejs/node/blob/main/doc/contributing/managing-social-media-acounts.md

[mcollina]

lgtm

[mhdawson]

I agree with @joyeecheung that managing-social-media-acounts.md is the more update to date document.

The right answer might be to update the admin Repo to point to that, but happy to have the reference to the social team removed as a first step.

[mhdawson]

LGTM

[kyliewd]

that link above is not the correct process right now. please refer to this document: Node.js Social Media Governance + Guidelines

we'll work on getting all the different documentation on GitHub updated soon. CC - @rginn

[rginn]

The document posted by @kyliewd is the most current. All day-to-day Node.js social media is managed by Foundation staff. This includes Bluesky, X, LinkedIn, Facebook, Mastodon, and any other official social media platform that we may support. The link posted by @mhdawson is inaccurate and will be updated to align with Kylie's document.

[joesepi]

Hey gang.

The document referenced above was added three months ago:
https://github.com/nodejs/node/blob/main/doc/contributing/managing-social-media-acounts.md

And this document was created three years ago:
https://github.com/nodejs/node/blob/main/doc/contributing/suggesting-social-media-posts.md

The pre-existing doc clearly states "Node.js social media is managed by OpenJS Foundation staff."

The very recent doc is in direct conflict by stating "The project obtains and manages social media accounts [...]." Additionally, this new document says "Login credentials are available to members of the Technical Steering Committee, but are not to be used directly except in exceptional circumstances." but there are all sorts of non-exceptional posts on Bluesky, diminishing the value of subscribing to the Node.js social media feed.

It is common practice to have the foundation manage its projects social media, brand and marketing. And the OpenJS marketing team are very responsive and accommodating. Its not clear to me why this has become controversial.

[joyeecheung]

but there are all sorts of non-exceptional posts on Bluesky

The login credentials are not used to manage the posts on Bluesky. The content are posted using a github workflow, with the content itself being proposed and reviewed on GitHub, as documented in the same document:

Automation is used to request posts/reposts as outlined in nodejs/bluesky.

diminishing the value of subscribing to the Node.js social media feed.

Note that part of the reason Bluesky content curation is designed the way it is was motivated by the several incidents last year where incorrect content with technical errors were posted by the official Twitter account and led to questions by Twitter followers, and repeated delays or silence to the request of reposting release announcement.

As far as I know, the Bluesky content curation has not yielded any technical errors in the content from GitHub. The most notable incident came from the time when someone from the foundation posted an incorrect birthday of JavaScript using the login credential directly without going through reviews on GitHub, leading to questions in the comments by Bluesky followers.

We are also planning to conduct a survey among Bluesky followers about what they like to see more/less nodejs/bluesky#128