-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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.
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
doc: add link to doc with social processes #45584
Conversation
Signed-off-by: Michael Dawson <mdawson@devrus.com>
Review requested:
|
Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
@@ -0,0 +1,6 @@ | |||
# Interacting with social |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Interacting with social" is jargony. Most people don't translate "social" to "social media" much less "the social media team".
How about "Requesting social media posts" or something like that? (Same for the name of the file.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ooh, even better might be "Suggesting social media posts". @nodejs/social
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Happy to change the any to any of those, or whatever based on any more feedback fom social team.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe "Requesting social media posts or amplification" ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think "amplification" is still pretty jargony and makes it needlessly verbose, but I wouldn't block that. It's certainly more clear, I think, than "Interacting with social".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The title of the link that we got from the Foundation staff was Node.js Social Amplication Request Guidelines
I could just use that minus the Node.js part which I think would be redundant.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be specific social-amplification-request-guidelines.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The title of the link that we got from the Foundation staff was
Node.js Social Amplication Request Guidelines
I could just use that minus the Node.js part which I think would be redundant.
You could, and I'm not going to block on this, but it's jargon. Jargon is OK for an internal document or a draft, but if we're publishing it widely, "social amplification" is a term likely to be unfamiliar to most readers. We should use terms that most people are likely to understand and that they might be searching for so they can find the right doc. If I were trying to find out how to get the nodejs Twitter account to retweet something, I might search for "social media" or "Twitter" or "posts" or "tweet", but I would be unlikely to search for "amplification" or "interacting with social".
I'm not going to block on this, though, because having a link to the process is vastly better than not having a link to the process, even if the document containing the link has a title that I think could be improved. So better that this land than I get things hung up on a word or two in the title.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Trott , I really don't feel strong about it just thought leveraging language that the social team had used could make sense. I'll change to suggesting-social-media-posts.md
Co-authored-by: Rich Trott <rtrott@gmail.com>
Co-authored-by: Rich Trott <rtrott@gmail.com>
Co-authored-by: Rich Trott <rtrott@gmail.com>
Co-authored-by: Rich Trott <rtrott@gmail.com>
Signed-off-by: Michael Dawson <mdawson@devrus.com>
@Trott updated. |
Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: #45584 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Landed in 9bc00fd |
Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: nodejs#45584 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: #45584 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: #45584 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: #45584 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: #45584 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: #45584 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: #45584 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Signed-off-by: Michael Dawson mdawson@devrus.com