Promote KubeVirt to a CNCF incubating project about community

[jberkus]

So our original DD is here: https://github.com/cncf/toc/blob/main/proposals/sandbox/kubevirt.adoc

We start with that, and update it for the current status of Kubevirt.

[mazzystr]

Sent introduction/petition email to Nutanix, Emporia State U, Nearby Computing, Canadian Centre for Cyber Security

[mazzystr]

https://docs.google.com/presentation/d/1eIyMHqr_ygktQwGz-U9MXEwmIQ8oa0dBRMWdPrEXWH0/edit#slide=id.ge3e23850b8_0_14

Adopters ... Reach out via mailing list, twitter, set heading in #virtualization. Check SUSE presentation from KubeVirt Summit for contact. Provide Diane with SUSE contact (Vasiliy Ulyanov)

• sahibinden.com, appneta.com, slb.com, ciena.com, stackpath.com, packet.com, arm, Ateme
• Add Platfom9. Ask them to ask their users to add themselves as adopters
• Kubermatic .... Ask them to ask their users to add themselves as adopters
• SAP ... Ask them to ask their users to add themselves as adopters

Monthly / Core maintainer meeting

• Review stats to find new maintainers

Weekly Meeting

• Encourage users to participate in meeting. Post notice to Slack

Reach out to Chinese mailing list

• Provide CNCF infrastructure

[mazzystr]

Due Diligence items now documented in the following doc per Alena ....

• https://docs.google.com/document/d/1L1JG9IVja7j5cV5c1mxutctGPpL3ihz5nW1S1w4zvS4/edit#

[mazzystr]

This is still in progress. Reopening the issue.

More progress on Alena's document ...

• Filled in community health

• Emailed Vasiliy / SuSe to get their opinion on community pro/cons

• Conversation with Howard Zhang with ARM about interview and website advertisement

• In progress of contacting Jeff Applewhite / STACKPATH regarding their opinion on community pro/con's and website advertisement

[mazzystr]

Added note from Vasiliy / SuSe

[mazzystr]

I spoke with someone I know at STACKPATH. They are reviewing their internal procedures for logo advertisement with Open Source projects as well as community participation. We are asked to stand by and wait for their review.

[kubevirt-bot]

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

[mazzystr]

/remove-lifecycle stale

…

On Tue, Feb 22, 2022 at 11:59 AM kubevirt-bot ***@***.***> wrote: 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 — Reply to this email directly, view it on GitHub <#96 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAS5KZ5KOKIL4ZNGGNLGSLDU4PTJLANCNFSM43I7VOFA> . 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>. You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[mazzystr]

@jberkus This issue can be closed complete, correct?

[jberkus]

Oh, yes.

/close

[kubevirt-bot]

@jberkus: Closing this issue.

In response to this:

Oh, yes.

/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/test-infra repository.