Skip to content

doc: doc that proj has access to linked in #57401

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 8 commits into
base: main
Choose a base branch
from
+10 −1
Open

doc: doc that proj has access to linked in #57401

Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
97a40b8
doc: doc that proj has access to linked in
mhdawson Mar 10, 2025
ec970bf
address comments/suggestions
mhdawson Mar 11, 2025
a52cddb
fixup
mhdawson Mar 11, 2025
b7c18c5
address comments
mhdawson Mar 11, 2025
a73cecc
fixup to make linter happy
mhdawson Mar 11, 2025
4a9ceed
fixup
mhdawson Mar 12, 2025
95ef4f3
squash: make linter happy
mhdawson Mar 12, 2025
475f8c0
Update doc/contributing/managing-social-media-acounts.md
mhdawson Mar 17, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion doc/contributing/managing-social-media-acounts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,4 +46,13 @@ 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.
In addition, it has been agreed that Releasers may login
and re-post their release announcement when doing a release,
and TSC members may re-post an announcement of a release if a
releaser is not able to do it themselves. All other content should
be managed by the Foundation staff.
Comment on lines +49 to +53
Copy link
Member

@Trott Trott Apr 14, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
In addition, it has been agreed that Releasers may login
and re-post their release announcement when doing a release,
and TSC members may re-post an announcement of a release if a
releaser is not able to do it themselves. All other content should
be managed by the Foundation staff.
Releasers may re-post their release announcements to the LinkedIn account.
TSC members may re-post an announcement if a Releaser is unable to do it.
All other content should be handled by the Foundation staff.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Trott was there some discussion while I was away. Unless there was discussion that new posts about the release annoucement was ok versus just reposting announcements I think the suggested text changes the intended scope of what is allowed.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't think there was a difference between a "re-post" and a "post" in this context, but I guess I'm wrong. I'll edit the suggestion accordingly.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've edited the suggestion to retain the term re-post.


LinkedIn allows the addition of content admins. Releasers may
request access by opening an issue in the nodejs/admin repo
asking for access. Once approved they should ask @bensternthal
to add them.
Loading