docs: words around important/negative messages #43
Conversation
|
I think I agree on the "negative communication case" but I'm not sure I agree with it in general. I don't see announcing security releases as a "negative" that we need to protect people from. If the argument is that a tweet directly from the Node.js account is more effective than a retweet that is a different discussion. If we think security release are a specific case I'd prefer they be called out specifically versus indirectly through "impactful". Anyway just one opinion. @nodejs/tsc FYI for your thoughts. |
|
Semi-related I wonder if we should ask people to hold off from tweeting about the security releases until the security announcement (versus the individual release blog posts) is published and even possibly once the tweet from the project as per the release process goes out (based on whatever we agree being the way we tweet security releases)? |
|
@bnb generally ok with the updated version, but would still prefer if we both tweeted directly and retweeted the releaser's post as a nod to the effort they put in. |
|
Yeah. I agree with Michael's last comment. We really should give credit to the work that is being done by amplifying the contributor doing the work. Both (retweet from account and new tweet from account) makes sense to me. |
|
I think the text as it stands (and also with my last suggestion) is consistent with "Definitely tweet security releases directly from the nodejs account, but also retweet the releasers about it too." (I don't oppose calling it out more specifically anyway, though.) |
|
With all the updates looks good to me now :) |
adds some wording around tweets for impactful or negative communication.
specifically, an example of where this would be applicable is something like a security release where there's the potential for harm to end-users. it's preferable that we use the account's voice directly rather than amplifying individuals to reduce the potential for individuals to be targeted and for the message to have a higher signal to noise ratio.
on the signal to noise ratio, effectively what I'm saying is that a tweet from @nodejs will be more obvious and engaged than that of an individual. readers don't need to wonder who they're looking at or why they're an authority - the account disambiguates a lot, making the message land more strongly.