kubernetesio x guidelines #8066
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k8s-ci-robot
added
the
cncf-cla: yes
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mfahlandt The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
size/M
ArvindParekh
reviewed
Sep 7, 2024
| * Request for communication (social media, surveys, etc.) can be made via a GitHub Issue in the Community Repository or via a communication request in #sig-contribex-comms. The GitHub issue request is the preferred method. | ||
| * It is not possible to request communication via kubernetesio X account directly. We recommend that requesters define a targeted recipient group, rather than a target channel or account. The current recipient groups are: \ | ||
| Kubernetes Contributors \ | ||
| Kubernetes End User |
There was a problem hiding this comment.
Suggested change
| Kubernetes End User | |
| Kubernetes End User \ |
|
|
||
| ## The following policy will describe the usage policy of the kubernetesio X account. | ||
|
|
||
| * The kubernetesio account is reaching hundreds of thousands people. As such, we need to make sure we link to things that are owned by the community itself (mailing lists, GitHub, surveys, etc.). |
There was a problem hiding this comment.
Suggested change
| * The kubernetesio account is reaching hundreds of thousands people. As such, we need to make sure we link to things that are owned by the community itself (mailing lists, GitHub, surveys, etc.). | |
| * The kubernetesio account is reaching hundreds of thousands of people. As such, we need to make sure we link to things that are owned by the community itself (mailing lists, GitHub, surveys, etc.). |
| * The preferred way for managing tweets is handled via Buffer. | ||
| * Active members recognized in the [SIG ContribEx Comms readme](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md) can propose tweets via Buffer | ||
| * [SIG ContribEx Comms Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) and SIG ContribEx Comms Social Media Leads can approve tweets | ||
| * [SIG ContribEx Comms Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) and SIGContribEx Comms Social Media Leads must not approve their own proposed tweets - this can be overruled by emergency posts to be defined in sensitive communication |
There was a problem hiding this comment.
Reframing to make it clearer - as I did not understand it the first time until I remembered about the sensitive comms guidelines from our meetings.
Suggested change
| * [SIG ContribEx Comms Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) and SIGContribEx Comms Social Media Leads must not approve their own proposed tweets - this can be overruled by emergency posts to be defined in sensitive communication | |
| * [SIG ContribEx Comms Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) and SIGContribEx Comms Social Media Leads must not approve their own proposed tweets - except in emergencies, which will be defined under sensitive communication guidelines. |
| @@ -0,0 +1,43 @@ | |||
| # @kubernetesio X Account guidelines | |||
There was a problem hiding this comment.
Suggested change
| # @kubernetesio X Account guidelines | |
| # @kubernetesio X Account Guidelines |
| @@ -0,0 +1,43 @@ | |||
| # @kubernetesio X Account guidelines | |||
|
|
|||
| SIG ContribEx Comms has multiple communication channels, not limited to the kubernetesio account. The main difference is the targeted audience. | |||
There was a problem hiding this comment.
Suggested change
| SIG ContribEx Comms has multiple communication channels, not limited to the kubernetesio account. The main difference is the targeted audience. | |
| SIG ContribEx Comms manages multiple communication channels, each tailored to specific audiences, including but not limited to the kubernetesio X account.. |
|
|
||
| SIG ContribEx Comms has multiple communication channels, not limited to the kubernetesio account. The main difference is the targeted audience. | ||
|
|
||
| ### Kubernetes Contributors can be targeted by the following channels: |
There was a problem hiding this comment.
Suggested change
| ### Kubernetes Contributors can be targeted by the following channels: | |
| ### Kubernetes Contributors are engaged through the following channels: |
|
|
||
| * [[email protected]](mailto:[email protected]) mailing list | ||
| * Kubernetes Slack Announcement Bot | ||
| * Mastadon: [k8sContributors@hachiderm](https://hachyderm.io/@K8sContributors) |
There was a problem hiding this comment.
Suggested change
| * Mastadon: [k8sContributors@hachiderm](https://hachyderm.io/@K8sContributors) | |
| * Mastodon: [k8sContributors@hachiderm](https://hachyderm.io/@K8sContributors) |
| * [[email protected]](mailto:[email protected]) mailing list | ||
| * Kubernetes Slack Announcement Bot | ||
| * Mastadon: [k8sContributors@hachiderm](https://hachyderm.io/@K8sContributors) | ||
| * X: [k8sContributors](https://x.com/k8sContributors) |
There was a problem hiding this comment.
Suggested change
| * X: [k8sContributors](https://x.com/k8sContributors) | |
| * X (formerly Twitter): [k8sContributors](https://x.com/k8sContributors) |
|
|
||
| ### Mixed Channels: | ||
|
|
||
| * [Lwkd Newsletter](https://lwkd.info/) |
There was a problem hiding this comment.
Suggested change
| * [Lwkd Newsletter](https://lwkd.info/) | |
| * [Lwkd (Last Week in Kubernetes Development) Newsletter](https://lwkd.info/) |
| Kubernetes End User | ||
| Both of the above | ||
| * The ultimate decision regarding which channels fit the request best lies with SIG ContribEx Comms | ||
| * For time sensitive requests, please raise the attention additionally to the [SIG ContribEx Comms Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) |
There was a problem hiding this comment.
Suggested change
| * For time sensitive requests, please raise the attention additionally to the [SIG ContribEx Comms Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) | |
| * For time-sensitive requests, please escalate the issue to the [SIG ContribEx Comms Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles). |
| Both of the above | ||
| * The ultimate decision regarding which channels fit the request best lies with SIG ContribEx Comms | ||
| * For time sensitive requests, please raise the attention additionally to the [SIG ContribEx Comms Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) | ||
| * Moderation of the Kubernetesio account resides with [SIG ContribEx Comms Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) and [SIG ContribEx-Comms Social Media Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) |
There was a problem hiding this comment.
Suggested change
| * Moderation of the Kubernetesio account resides with [SIG ContribEx Comms Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) and [SIG ContribEx-Comms Social Media Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) | |
| * Moderation of the Kubernetesio account resides with [SIG ContribEx Comms Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) and [SIG ContribEx-Comms Social Media Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles). |
| * The ultimate decision regarding which channels fit the request best lies with SIG ContribEx Comms | ||
| * For time sensitive requests, please raise the attention additionally to the [SIG ContribEx Comms Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) | ||
| * Moderation of the Kubernetesio account resides with [SIG ContribEx Comms Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) and [SIG ContribEx-Comms Social Media Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) | ||
| * The kubernetesio account will not interact with any comments or reply to any accounts |
There was a problem hiding this comment.
Suggested change
| * The kubernetesio account will not interact with any comments or reply to any accounts | |
| * The kubernetesio account will not interact with any comments or reply to any accounts. |
| * For time sensitive requests, please raise the attention additionally to the [SIG ContribEx Comms Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) | ||
| * Moderation of the Kubernetesio account resides with [SIG ContribEx Comms Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) and [SIG ContribEx-Comms Social Media Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) | ||
| * The kubernetesio account will not interact with any comments or reply to any accounts | ||
| * X TOS |
There was a problem hiding this comment.
Suggested change
| * X TOS | |
| * X Terms of Service (TOS): |
| * Moderation of the Kubernetesio account resides with [SIG ContribEx Comms Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) and [SIG ContribEx-Comms Social Media Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) | ||
| * The kubernetesio account will not interact with any comments or reply to any accounts | ||
| * X TOS | ||
| * It is the responsibility of the [SIG ContribEx Comms Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) & [SIG ContribEx-Comms Social Media Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) to be familiar with the [terms of service (TOS) of X](https://x.com/en/tos), and to ensure the kubernetesio account maintains compliance with the X TOS. This includes understanding and adhering to rules around things like account age (birthday), language usage, etc. |
There was a problem hiding this comment.
Suggested change
| * It is the responsibility of the [SIG ContribEx Comms Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) & [SIG ContribEx-Comms Social Media Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) to be familiar with the [terms of service (TOS) of X](https://x.com/en/tos), and to ensure the kubernetesio account maintains compliance with the X TOS. This includes understanding and adhering to rules around things like account age (birthday), language usage, etc. | |
| * It is the responsibility of the [SIG ContribEx Comms Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) & [SIG ContribEx-Comms Social Media Leads](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md#roles) to be familiar with the [terms of service (TOS) of X](https://x.com/en/tos), and to ensure the kubernetesio account maintains compliance with the X TOS. This includes understanding and adhering to rules around things like account age (birthday), language usage, and other relevant guidelines. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A Guideline for the usage of the Kubernetes X account.
Which issue(s) this PR fixes:
Fixes #8059