Add channels for Flannel project

[pgonin]

Add #flannel & #flannel-dev Slack channels

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: pgonin / name: Paul Gonin (15d3388)

[k8s-ci-robot]

Welcome @pgonin!

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. 😃

[k8s-ci-robot]

Hi @pgonin. 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.

Details

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.

[aojea]

flannel IIRC is not a kubernetes project https://github.com/flannel-io/flannel?tab=readme-ov-file#contact

[pgonin]

That's right
Working on changing this

[aojea]

That's right Working on changing this

are there any conversations happening somehwere? has this been shared with steering or sig netwokr or some related group in kubernetes?

[pgonin]

Our current efforts are to make the project ready by improving how it is organized and reviewing the various criteria https://github.com/cncf/toc/blob/main/.github/ISSUE_TEMPLATE/template-incubation-application.md

and one of the criteria is to have clear public communications channels
"Project must have, and document, at least one public communications channel for users and/or contributors."
current channels are not in Slack workspace for the Kubernetes community https://github.com/flannel-io/flannel?tab=readme-ov-file#contact

[aojea]

I think that you are mixing two things, CNCF and Kubernetes org, and if your intention is to donate to CNCF you should be opening those channels on the CNCF slack, cc @mrbobbytables for guidance

As SIG Network lead for kubernetes and part of steering I have doubts we should adopt flannel under the kubernetes org, but you are free to open that discussion and this is just my personal opinion,

[pgonin]

I'm not mixing up, but I'm certainly equally confused as many in the cloud native / kubernetes community... 2 separate slack environments do not really help.

We took a pragmatic approach and looked for the Slack where we are already engaging significantly... for example with the kube-router project which is also on kubernetes slack

Then I read Should you have a channel on the Kubernetes Slack?
in particular "The channel MUST be Kubernetes related in some way." and "External projects (ones not owned by a Kubernetes SIG) may have a maximum of two channels, usually #project or #project-users, and #project-dev."

[aojea]

I'm not mixing up, but I'm certainly equally confused as many in the cloud native / kubernetes community... 2 separate slack environments do not really help.

cncf != kubernetes basically, kubernetes is its own project with its own organization and policies

Then I read Should you have a channel on the Kubernetes Slack?
in particular "The channel MUST be Kubernetes related in some way." and "External projects (ones not owned by a Kubernetes SIG) may have a maximum of two channels, usually #project or #project-users, and #project-dev."

fair point, I was not aware that we had those policies, my apologies, but after the past drama with the slack license changes I find this policy confusing.
IIUIC the kubernetes project now assumes a responsibility with these third party projects and probably it also cost money to the project, tagging @kubernetes/steering-committee to fully understand the implication of this policy and @mfahlandt that handles most of the internal,
what SIG owns this policy?
what are the implications (cost, responsabilities, ...) of providing these resources to third party projects?

[pgonin]

and I also checked what (projects) channels were added recently, like #aicr or #kubetail

[aojea]

and I also checked what (projects) channels were added recently, like #aicr or #kubetail

ok, on fairness then whoever is approving those channels will decide, and I will open a new issue to discuss this policy in steering that is independent of this issue, and tries to understand better current policy

Sorry for the noise

[mrbobbytables]

We do have plenty of other projects that are in CNCF slack, they usually get 2 - the project and project-dev

[jberkus]

So, yes, adding a channel for Flannel would be within policy for Kubernetes Slack. However, if you are planning to contribute Flannel to the CNCF, then it would make sense to have a channel on CNCF slack instead.

As for our slack: we would not add both channels at once. Per our policy:

A second channel for a specific project will not be approved until the first channel demonstrates significant traffic.

So, if you still want a channel on Kubernetes slack, pick the one you want.

/hold

[jberkus]

per policy, you do not get two channels to start. Please pick the one you want.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: pgonin
Once this PR has been reviewed and has the lgtm label, please assign jeefy for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• communication/slack-config/OWNERS

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

[jberkus]

/remove-hold

[pgonin]

Channels were created on CNCF Slack

It would make sense for the Kubernetes / CNCF Community to have one location but that would certainly take too much energy to fix that

[jberkus]

@pgonin no, it really wouldn't.

We have good reasons for having two separate slacks.

[jberkus]

/close

per OP

[k8s-ci-robot]

@jberkus: Closed this PR.

Details

In response to this:

/close

per OP

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.