slack config: add jenkins-operator channel

[brokenpip3]

Hi, I'd like to propose a Slack channel for the jenkins kubernetes operator

Like the name is already explain the Jenkins Operator is a k8s operator which manages operations for Jenkins on Kubernetes. It has been built with Immutability and declarative Configuration as Code in mind.

Our previous slack channel (in a separated slack instance) will be not available anymore because the company that initially developed the operator stepped down and we are moving to a community model to continue to support and develop the operator, that's why we need a new chat home and the kubernetes slack seems the perfect match :)

Thanks in advance!

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: brokenpip3 / name: Luigi Operoso (9b1dca8)

[k8s-ci-robot]

Welcome @brokenpip3!

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 @brokenpip3. 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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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

[markjacksonfishing]

@brokenpip3 have you reached out to the CDF in their slack for a channel? I feel that would be more appropriate for this type of channel.
/hold

[markjacksonfishing]

/hold

[brokenpip3]

Hi @markyjackson-taulia thanks for the reply!
can you clarify what you mean with CDF?

[markjacksonfishing]

Hi @markyjackson-taulia thanks for the reply!

can you clarify what you mean with CDF?

@brokenpip3 my apologies. The CDF continuous delivery foundation and the Jenkins project have their own slack instance.

[brokenpip3]

No need to apologize at all :)
Yep make sense, let me ask there. Can you take this on old without closing it until I get back from them?
thanks!

[markjacksonfishing]

Let's leave it open for now, there is a hold. Take your time

[brokenpip3]

Hi @markyjackson-taulia I asked in the CDF community and they said that they think a matrix channel or the kubernetes slack should be a better home for the project: (here if you want to take a look). They also suggested to use the already present in k8s space jenkins-ci channel but I believe that channel is more about general jenkins questions and pipeline support/discussion (looking on the historical discussions there)

I still believe that since this is the kind-official kubernetes operator for jenkins having the jenkins-operator slack channel in the kubernetes slack space will be the best fit for the community, what do you think? :)
Thanks!

[markjacksonfishing]

@brokenpip3

Hey there,

Thank you for providing that information.
I still do feel that the CDF Slack would be a better fit for this channel rather then the Kubernetes Slack for a couple of reasons.

Firstly, there is some history with this operator that the Jenkins project is aware of and should handle accordingly. I also noted this in the CDF thread, and I think it's important for the Jenkins project to take the lead on any related issues.

Secondly, I believe that the main driver for this operator is Jenkins, and Kubernetes plays a supporting role. As a CDF foundational project, it would make sense to keep all communication within this Slack or Gitter to ensure transparency and that everyone stays up-to-date.

I understand that open-source projects rely on collaboration and communication, and I think it's important for us to have a friendly and empathetic environment where everyone's voice is heard. I hope you'll consider my perspective, and thank you.

[brokenpip3]

Hi Marky, thanks for you kind reply, really appreciate your way of discussing and also the reply in the CDF slack.
Make sense to me, will create a channel there or will use gitter.

Thanks for your support, have a nice weekend
Luigi