doc: doc that proj has access to linked in

[mhdawson]

• suggested by a releaser as release posts are also promoted on linkedin

NOTE: Seems like we don't have agreement from the Foundation to proceed with this, so more discussion will be necessary to see if the request is possible.

[nodejs-github-bot]

Review requested:

• @nodejs/tsc

[mhdawson]

@bensternthal @rginn I don't think we discussed linked in so want to check with you if this is ok, and if so a heads up that I'll need your help to share the credentials like was done for twitter.

[RafaelGSS]

We could have the user/pass in the 1Pass for now, but I believe the ideal solution would be a nodejs/linkedin (similar to nodejs/bluesky) and automate this process using a secret key.

It seems linkedin API doesn't incur in costs: https://learn.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/share-on-linkedin

[bensternthal]

Linked in allows us to add existing linkedin users as "linkedin admins" to the node account. So there is no need to share credentials, we just add accounts to the page.

[RafaelGSS]

Linked in allows us to add existing linkedin users as "linkedin admins" to the node account. So there is no need to share credentials, we just add accounts to the page.

That's great. I wasn't aware of it. Could you include mine meanwhile? Is there an official process for that?

[bensternthal]

@RafaelGSS no official process as we rarely if ever adjust this. I just added you as a content admin. Note if you are posting anything editorial I would coordinate with Sally. It's important for this channel to always use the same "voice" and we want to ensure that you two do not duplicate any content.

[rginn]

Please note that our LinkedIn channels have a more business audience focus. I would like to wait for Kylie @kyliewd to return from family leave at the end of this month to manage and guide postings for the Node.js project because she's done a fantastic job launching and growing this important communications channel. In the meantime, Sally and I have admin access.

[mhdawson]

@rginn I think the suggestion was just for releasers to create a post which announces release just like what was agreed for twitter.

I don't think that falls into something editorial and documenting that access is only for announcing releases and that for anything else people should co-ordinate with Sally as @bensternthal would be consistent with the approach for twitter.

I'll update the PR to be in line with the apporach to adding access that Ben mentioned versus sharing the credential.

[marco-ippolito]

LGTM
I would note that this does only allow releasers to REPOST release announcements.
This removes the need to ping on the slack channel and wait for someone to repost it

[mhdawson]

@rginn does the change to clarify that it only allows a repost of the releaser's post change your objection to the project having access to the LinkedIn acocunt?

[RaisinTen]

What is the downside of giving access to the releasers for reposting release posts if it makes things easier for them? I don't think it's a good idea for repost requests from releasers to get blocked because one Foundation staff member is out of office.