Create Knative Social Media Guidelines : https://github.com/knative/community/issues/1444

[nainaz]

Fixes #1444

Changes

New markdown for social media guidelines

/kind

Fixes #

Release Note

Docs

[knative-prow[bot]]

@nainaz: The label(s) kind/<kind> cannot be applied, because the repository doesn't have them.

In response to this:

Changes

/kind

Fixes #

Release Note

Docs

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[aliok]

Another thing, could you please rename the file to something like SOCIAL_MEDIA_GUIDELINES.md? Other files have that kind of pattern.

One last thing, when the PR merges, can you delete the nainaz-patch-1 branch? I know it is a bit confusing, but generally:

• You work in your own fork
• Create a branch there
• Send a PR agains main branch of this repo

[aliok]

@nainaz now that we want to use social media more often, would you like me to take this PR over?

[nainaz]

Please go ahead

[nainaz]

Agree with weekly cadence and I created an issue to add Linkedin added to Follow us on website

Thank you, -N

On Tue, 23 Apr 2024 at 12:14, Evan Anderson @.***> wrote:

@.**** commented on this pull request.

In Knative Social Media Guidelines.md https://github.com/knative/community/pull/1445#discussion_r1398284983:

@@ -0,0 +1,62 @@ +# Knative Social Media Guidelines

+This document covers the social media guidelines for the use of the Knative Twitter/X channel.

+1

It would be nice to have a Mastodon and/or LinkedIn handle, since the changes at Twitter in the last year.

In Knative Social Media Guidelines.md https://github.com/knative/community/pull/1445#discussion_r1576530183:

+- Share information on how-tos, demos, etc. that are valuable to the community. +- Build awareness for the project. +- Drive engagement and participate in the project.

+## Strategy and Guidelines + +### Strategy + +- Keep messages positive and uplifting, consistent with the values and principles of CNCF. +- Communicate big picture ideas vs “announcements” or news. News will be positioned less like an announcement and more around what it means. +- Share content across social media channels that benefit the ecosystem as a whole. +- Maintain a balance of posting on CNCF activities/news and ecosystem-focused content. +- Share vendor-neutral, community-sourced posts that are informational, engaging, and ecosystem-focused. +- Engage with the community through retweets and sharing of community content. + +### General Guidelines

It feels like an ideal cadence might be weekly or twice-weekly, but I'm not sure we're up for producing content that fast yet.

— Reply to this email directly, view it on GitHub https://github.com/knative/community/pull/1445#discussion_r1398284983, or unsubscribe https://github.com/notifications/unsubscribe-auth/AISZCFA4ZVJCG4MVZXCZQCDY62CFLAVCNFSM6AAAAAA52SODY2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTOMZYGQ4TMMJWHE . You are receiving this because you were mentioned.Message ID: @.***>

[aliok]

@knative/steering-committee

I've updated the document. Can you review please?

[knative-prow[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: evankanderson, nainaz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• ~~OWNERS~~ [evankanderson,nainaz]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment