diff options
| -rw-r--r-- | communication/marketing-team/social-guidelines.md | 65 |
1 files changed, 42 insertions, 23 deletions
diff --git a/communication/marketing-team/social-guidelines.md b/communication/marketing-team/social-guidelines.md index e55194e2..38b905e9 100644 --- a/communication/marketing-team/social-guidelines.md +++ b/communication/marketing-team/social-guidelines.md @@ -1,23 +1,42 @@ -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 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. + +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, 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. + +Kubernetes Organization Members with access to account are: +- @parispittman +- @mrbobbytables +- @chris-short + +## Themes/Topics + +- Contributor/SIG blog posts +- Events +- 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.) + +### Frequently Asked Questions (FAQ) + +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). + +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) |