Add official Nutanix CAPI Provider Slack Channel

[tuxtof]

This PR adds a slack channel for The Nutanix CAPI Provider (CAPX) - https://github.com/nutanix-cloud-native/cluster-api-provider-nutanix

Which issue(s) this PR fixes: NONE

[k8s-ci-robot]

Welcome @tuxtof!

It looks like this is your first PR to kubernetes/community 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/community has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. :smiley:

[k8s-ci-robot]

Hi @tuxtof. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[markjacksonfishing]

/ok-to-test

[jdumars]

I am not sure this particular projects meets expectations in terms of community engagement. I am going to defer to the judgment of other moderators, but I think this may be premature to separate from the regular CAPI discussion.

[tuxtof]

Hello @jdumars , nice to meet you, the goal here is to federate and drive the community as for all other CAPI provider who already have their own dedicated channel. Can you please help us to understand which expectations in terms of community engagement are missing in your opinion and how to solve them ?

Can you also invite the other moderators you are talking about, because i see only @markyjackson-taulia and he already approve the request.

Thanks for your response

[jdumars]

@tuxtof first, thanks for the response and follow-up questions. There are certain parts of the moderator job that are challenging - the biggest of which is balancing the introduction of new things and the importance of doing it at the right time for the right reasons. Slack, as a community tool is intended to facilitate discussion in ways that serve the community, and visibility is a key aspect of that. When we create new channels it should be with the intent of limiting unrelated conversations in another place, and in this case it would be away from core Cluster API conversations (or threads in that channel). From a philosophical angle, anyone requesting something new bears the burden of explaining why it serves the broader community to have it, versus asking the community why it shouldn't. My concern is fundamentally: does the current level of conversation and unique discussion on this topic merit its own separate channel, since a new channel is not intended to serve as a validation or promotion tool. That would not be in the interest of the community, but in the interest of the requestor(s).

All that said, the Cluster API provider communities pose a particular challenge for understanding activity/engagement. As a precedent, Oracle's provider is a similar scale and has already been approved. Based on that, I am willing to approve this request, but want to make the underlying motivations clear.

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jdumars, markyjackson-taulia, tuxtof

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:

• ~~communication/slack-config/OWNERS~~ [jdumars]

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

[jdumars]

If no other moderators are able to review tis by the end of the week, I will remove the hold.

[tuxtof]

hello @jdumars any news ? thanks

[markjacksonfishing]

/hold cancel