Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

REQUEST: Boost communication about Etcd Operator Survey #7897

Closed
jberkus opened this issue May 14, 2024 · 6 comments
Closed

REQUEST: Boost communication about Etcd Operator Survey #7897

jberkus opened this issue May 14, 2024 · 6 comments
Labels
area/contributor-comms Issues or PRs related to the upstream marketing team lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience.

Comments

@jberkus
Copy link
Contributor

jberkus commented May 14, 2024

What do you want send out?(Please include a link to a draft)

Please share out this survey with the Kubernetes community:

Sample text:

Kubernetes SIG-Etcd and SIG-Cluster-Lifecycle are planning to develop an official etcd operator. This operator is specifically for people who run etcd clusters in addition to the one embedded in Kubernetes. In the first step, we'd like to collect feedback from the community. Please kindly fill in the following survey when you get a couple of minutes. Thanks.

https://forms.gle/5gBpzaxYtuQPWdBo9

The survey has already been shared with etcd-dev, kubernetes-dev, and #sig-etcd and #surveys channels. Appropriate additional shares would include #announcements, social media, and LWKD.

@jberkus jberkus added area/contributor-comms Issues or PRs related to the upstream marketing team sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. labels May 14, 2024
@jberkus
Copy link
Contributor Author

jberkus commented May 14, 2024

Added to LWKD draft

@chris-short
Copy link
Contributor

So etcd has a Twitter account, it would make sense for us to boost that in addition to the Comms posting about the it directly.

@jberkus Do we want this going to LinkedIn? I think that's a more end user audience at the moment but, I'm not going to exclude it unless you want us too (which means we should probably have some kind of network selection mechanism in our template cc @mfahlandt).

@jberkus
Copy link
Contributor Author

jberkus commented May 21, 2024

Yes, we want it on Linkedin. We're trying to reach end users.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 20, 2024
@jberkus
Copy link
Contributor Author

jberkus commented Aug 22, 2024

This survey is over.

/close

@k8s-ci-robot
Copy link
Contributor

@jberkus: Closing this issue.

In response to this:

This survey is over.

/close

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-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/contributor-comms Issues or PRs related to the upstream marketing team lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience.
Projects
None yet
Development

No branches or pull requests

4 participants