search

kubevirt / kubevirt.github.io

KubeVirt website repo, documentation at https://kubevirt.io/user-guide/
https://kubevirt.io
MIT License
30 stars 112 forks source link

Obtain permission to advertise Google on index page #783

Closed mazzystr closed 2 years ago

mazzystr commented 3 years ago

/kind enhancement

What happened: Let's find the Google representative and obtain explicit permission to advertise.

What you expected to happen:

Anything else we need to know?: Add logo here Add data here

mazzystr commented 3 years ago

@jberkus Do either Diane or you know who to contact at Google to start this process?

jberkus commented 3 years ago

I can ask, but how do we know that Google is a user?

mazzystr commented 3 years ago

They're among us. I've spoken to one regarding but was told not yet. The topic might be better approached from the OSPO level.

On Mon, Aug 30, 2021 at 8:27 AM Josh Berkus @.***> wrote:

I can ask, but how do we know that Google is a user?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/kubevirt/kubevirt.github.io/issues/783#issuecomment-908438540, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAS5KZZNGSHOGGSZZ5FFR73T7OPN3ANCNFSM5C3WX44Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

kubevirt-bot commented 2 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

kubevirt-bot commented 2 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

jberkus commented 2 years ago

Since we don't have a name of anyone at Google who definitely uses Kubevirt, I suggest closing this for now.

kubevirt-bot commented 2 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

kubevirt-bot commented 2 years ago

@kubevirt-bot: Closing this issue.

In response to [this](https://github.com/kubevirt/kubevirt.github.io/issues/783#issuecomment-1030439265): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.