From a7b361752790fdb1edc1add14a81bf9e70efa5f3 Mon Sep 17 00:00:00 2001 From: Chris Short Date: Fri, 3 Apr 2020 16:03:49 -0400 Subject: Updating Social Media Guidelines Less notey More wordy Signed-off-by: Chris Short --- communication/marketing-team/social-guidelines.md | 57 ++++++++++++++--------- 1 file changed, 34 insertions(+), 23 deletions(-) (limited to 'communication') diff --git a/communication/marketing-team/social-guidelines.md b/communication/marketing-team/social-guidelines.md index e55194e2..2fa4813a 100644 --- a/communication/marketing-team/social-guidelines.md +++ b/communication/marketing-team/social-guidelines.md @@ -1,23 +1,34 @@ -Future home of social media guidelines - -**Twitter:** K8sContributor - -Examples: -1. Try and tweet at least twice a week -2. No more than two original tweets a day, unlimited retweets; responding to others does not count in this -3. should respond within 48 hours -4. Contributor information/news/stories is the target; forward others to social@cncf.io for @kubernetesio main twitter account -5. Bio should mention that this is powered by sig-contribex, link to the kubernetes/community repo -6. Never include someones photo, twitter handle, or other personal identifiable info without their explicit permission -7. try not to abbreviate as much as possible -8. all event tweets should have an action and/or thumbnail image - -Themes: -- contributor/sig blog posts -- events -- keps -- process changes -- release info, code freeze, et al - -### open-ended questions: -who do we follow / does it matter +# Social media guidelines + +**Twitter:** [K8sContributor](https://twitter.com/k8scontributors) + +## General guidelines + +All messaging must be consistent with the values and principles of the project and the [ethos/vision of the team](https://github.com/kubernetes/community/blob/master/communication/marketing-team/CHARTER.md#ethosvision). Messaging should be positive and uplifting. Be aware that sarcasm and/or jokes are generally hard to read over a medium such as social media. + +Original messages should come out of this teams' accounts at least twice a week (if not more). However, there should be no more than three original messages per day. Retweets, likes, and responses are unlimited but, they should be thoughtful. All event messages should have an action and/or thumbnail image (click link for details, register today, etc. are example actions). Never include photos, user handles, or other personally identifiable information without explicit permission. + +Attempt to keep abbreviations to a minimum. Things like `k/k`, for example, might be known in the community, but for new contributors, this is something that is learned with time. Minimizing abbreviations and using plain language is strongly encouraged. + +Responses should include helpful links, validation, and/or additional information. Responses should occur within 48 hours. At the very least, like things as an acknowledgment. Sources of information should include Kubernetes contributor related web properties and documentation. TODO: CLEARLY DEFINE THOSE WEB PROPERTIES + +Ideally, no individuals outside of the contributor community with the possible exception that they are talking about contributors should be an considered a topic of messaging. Example: Bill Gates isn't part of the Kubernetes community, it wouldn't be prudent to message him. + +Other CNCF projects, unless there is a common contributor cause, are out of scope for coverage by this team's social media accounts. + +## Themes/Topics + +- Contributor/SIG blog posts +- Events +- KEPs +- Process changes +- Release info, code freeze, et al +- Significant historical events as related to the project (Kubernetes birthday, previous events, etc.) + +### Open-ended questions + +This team's social media accounts need to be incredibly mindful of who it follows. As it is an information dissemination channel some might think that following no one is a better choice but, that could end up limiting exposure. Attempt to keep follower count low to make it easier to manage. + +Trolls: Don't feed them, mute them. Block them as a last resort and only after discussing with team members. Reasons to block include verbal abuse, violating the platform's terms, or violating the [Code of Conduct](https://github.com/kubernetes/community/blob/master/code-of-conduct.md). The community is open and its accounts should be too but, there are limits. + +Credit: [Fedora Community](https://fedoraproject.org/wiki/Marketing) -- cgit v1.2.3 From a61c119e9489b396ef8dcfa90072029fccaed3aa Mon Sep 17 00:00:00 2001 From: Chris Short Date: Fri, 3 Apr 2020 16:16:26 -0400 Subject: Adding account controllers Signed-off-by: Chris Short --- communication/marketing-team/social-guidelines.md | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'communication') diff --git a/communication/marketing-team/social-guidelines.md b/communication/marketing-team/social-guidelines.md index 2fa4813a..5999b88e 100644 --- a/communication/marketing-team/social-guidelines.md +++ b/communication/marketing-team/social-guidelines.md @@ -16,6 +16,11 @@ Ideally, no individuals outside of the contributor community with the possible e Other CNCF projects, unless there is a common contributor cause, are out of scope for coverage by this team's social media accounts. +Kubernetes Organization Members with access to account are: +- @parispittman +- @mrbobbytables +- @chris-short + ## Themes/Topics - Contributor/SIG blog posts -- cgit v1.2.3 From 233762f8d1852cdd6c499a19be3fb207370c9ae2 Mon Sep 17 00:00:00 2001 From: Chris Short Date: Fri, 10 Apr 2020 15:41:32 -0400 Subject: Update communication/marketing-team/social-guidelines.md Co-Authored-By: Matt Broberg <1744971+mbbroberg@users.noreply.github.com> --- communication/marketing-team/social-guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'communication') diff --git a/communication/marketing-team/social-guidelines.md b/communication/marketing-team/social-guidelines.md index 5999b88e..70633851 100644 --- a/communication/marketing-team/social-guidelines.md +++ b/communication/marketing-team/social-guidelines.md @@ -6,7 +6,7 @@ All messaging must be consistent with the values and principles of the project and the [ethos/vision of the team](https://github.com/kubernetes/community/blob/master/communication/marketing-team/CHARTER.md#ethosvision). Messaging should be positive and uplifting. Be aware that sarcasm and/or jokes are generally hard to read over a medium such as social media. -Original messages should come out of this teams' accounts at least twice a week (if not more). However, there should be no more than three original messages per day. Retweets, likes, and responses are unlimited but, they should be thoughtful. All event messages should have an action and/or thumbnail image (click link for details, register today, etc. are example actions). Never include photos, user handles, or other personally identifiable information without explicit permission. +Original messages should come out of this teams' accounts at least twice a week (if not more). However, there should be no more than three tweets per hour (including retweets). Retweets, likes, and responses are unlimited, but they should be used thoughtfully to encourage inclusive and kind participation. Use scheduling software as needed to space out messages. All messages should serve a purpose: have an action and/or thumbnail image ("click link for details," "register today," etc. are example actions). Never include photos, user handles, or other personally identifiable information without explicit permission. Attempt to keep abbreviations to a minimum. Things like `k/k`, for example, might be known in the community, but for new contributors, this is something that is learned with time. Minimizing abbreviations and using plain language is strongly encouraged. -- cgit v1.2.3 From 96af3074c8a50f8a3cc3a74090067bc2dbf7effe Mon Sep 17 00:00:00 2001 From: Chris Short Date: Fri, 10 Apr 2020 15:41:52 -0400 Subject: Update communication/marketing-team/social-guidelines.md Co-Authored-By: Matt Broberg <1744971+mbbroberg@users.noreply.github.com> --- communication/marketing-team/social-guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'communication') diff --git a/communication/marketing-team/social-guidelines.md b/communication/marketing-team/social-guidelines.md index 70633851..2b14fb16 100644 --- a/communication/marketing-team/social-guidelines.md +++ b/communication/marketing-team/social-guidelines.md @@ -12,7 +12,7 @@ Attempt to keep abbreviations to a minimum. Things like `k/k`, for example, migh Responses should include helpful links, validation, and/or additional information. Responses should occur within 48 hours. At the very least, like things as an acknowledgment. Sources of information should include Kubernetes contributor related web properties and documentation. TODO: CLEARLY DEFINE THOSE WEB PROPERTIES -Ideally, no individuals outside of the contributor community with the possible exception that they are talking about contributors should be an considered a topic of messaging. Example: Bill Gates isn't part of the Kubernetes community, it wouldn't be prudent to message him. +Ideally, no individuals outside of the contributor community with the possible exception that they are talking about contributors should be an considered a topic of messaging. Example: Bill Gates isn't part of the Kubernetes community, so tweets with @BillGates will not be published. Other CNCF projects, unless there is a common contributor cause, are out of scope for coverage by this team's social media accounts. -- cgit v1.2.3 From 80482e26325206d416f79d4b40df9c9338f297c4 Mon Sep 17 00:00:00 2001 From: Chris Short Date: Fri, 10 Apr 2020 15:43:10 -0400 Subject: Update communication/marketing-team/social-guidelines.md Co-Authored-By: Matt Broberg <1744971+mbbroberg@users.noreply.github.com> --- communication/marketing-team/social-guidelines.md | 1 + 1 file changed, 1 insertion(+) (limited to 'communication') diff --git a/communication/marketing-team/social-guidelines.md b/communication/marketing-team/social-guidelines.md index 2b14fb16..1a10742c 100644 --- a/communication/marketing-team/social-guidelines.md +++ b/communication/marketing-team/social-guidelines.md @@ -28,6 +28,7 @@ Kubernetes Organization Members with access to account are: - KEPs - Process changes - Release info, code freeze, et al +- Accomplishments (reaching 100,000 GitHub stars for example) - Significant historical events as related to the project (Kubernetes birthday, previous events, etc.) ### Open-ended questions -- cgit v1.2.3 From 425d784b981afa3464e80432b8aae0b6286eadf9 Mon Sep 17 00:00:00 2001 From: Chris Short Date: Fri, 10 Apr 2020 15:43:21 -0400 Subject: Update communication/marketing-team/social-guidelines.md Co-Authored-By: Matt Broberg <1744971+mbbroberg@users.noreply.github.com> --- communication/marketing-team/social-guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'communication') diff --git a/communication/marketing-team/social-guidelines.md b/communication/marketing-team/social-guidelines.md index 1a10742c..cab80b72 100644 --- a/communication/marketing-team/social-guidelines.md +++ b/communication/marketing-team/social-guidelines.md @@ -31,7 +31,7 @@ Kubernetes Organization Members with access to account are: - Accomplishments (reaching 100,000 GitHub stars for example) - Significant historical events as related to the project (Kubernetes birthday, previous events, etc.) -### Open-ended questions +### Frequently Asked Questions (FAQ) This team's social media accounts need to be incredibly mindful of who it follows. As it is an information dissemination channel some might think that following no one is a better choice but, that could end up limiting exposure. Attempt to keep follower count low to make it easier to manage. -- cgit v1.2.3 From 2f889e4aafb685c36076b8283f616828d7ab0c41 Mon Sep 17 00:00:00 2001 From: Chris Short Date: Fri, 10 Apr 2020 15:43:36 -0400 Subject: Update communication/marketing-team/social-guidelines.md Co-Authored-By: Matt Broberg <1744971+mbbroberg@users.noreply.github.com> --- communication/marketing-team/social-guidelines.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'communication') diff --git a/communication/marketing-team/social-guidelines.md b/communication/marketing-team/social-guidelines.md index cab80b72..002b9d39 100644 --- a/communication/marketing-team/social-guidelines.md +++ b/communication/marketing-team/social-guidelines.md @@ -33,7 +33,8 @@ Kubernetes Organization Members with access to account are: ### Frequently Asked Questions (FAQ) -This team's social media accounts need to be incredibly mindful of who it follows. As it is an information dissemination channel some might think that following no one is a better choice but, that could end up limiting exposure. Attempt to keep follower count low to make it easier to manage. +Q: Will the account follow other accounts? +A: TODO (Y/N). The account is designed for information dissemination, so we will focus on that by (following no one and focusing on sharing || following everyone to extend our reach). Trolls: Don't feed them, mute them. Block them as a last resort and only after discussing with team members. Reasons to block include verbal abuse, violating the platform's terms, or violating the [Code of Conduct](https://github.com/kubernetes/community/blob/master/code-of-conduct.md). The community is open and its accounts should be too but, there are limits. -- cgit v1.2.3 From 6c1c6942a49db3dcf5529e14d1ccfa84181c2d31 Mon Sep 17 00:00:00 2001 From: Chris Short Date: Fri, 10 Apr 2020 15:43:57 -0400 Subject: Update communication/marketing-team/social-guidelines.md Co-Authored-By: Matt Broberg <1744971+mbbroberg@users.noreply.github.com> --- communication/marketing-team/social-guidelines.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'communication') diff --git a/communication/marketing-team/social-guidelines.md b/communication/marketing-team/social-guidelines.md index 002b9d39..38b905e9 100644 --- a/communication/marketing-team/social-guidelines.md +++ b/communication/marketing-team/social-guidelines.md @@ -36,6 +36,7 @@ Kubernetes Organization Members with access to account are: Q: Will the account follow other accounts? A: TODO (Y/N). The account is designed for information dissemination, so we will focus on that by (following no one and focusing on sharing || following everyone to extend our reach). -Trolls: Don't feed them, mute them. Block them as a last resort and only after discussing with team members. Reasons to block include verbal abuse, violating the platform's terms, or violating the [Code of Conduct](https://github.com/kubernetes/community/blob/master/code-of-conduct.md). The community is open and its accounts should be too but, there are limits. +Q: Do we engage with hostile messages? +A: No. Don't feed the trolls. Mute them is the correct response. Block them as a last resort and only after discussing with team members. Reasons to block include verbal abuse, violating the platform's terms, or violating the [Code of Conduct](https://github.com/kubernetes/community/blob/master/code-of-conduct.md). The community is focused on openness and our accounts should be too, but there are times when we should reduce harmful people's visibility through blocking. Credit: [Fedora Community](https://fedoraproject.org/wiki/Marketing) -- cgit v1.2.3