REQUEST: New private Slack channel external-secrets-maintainers

[Skarlso]

GitHub Username

@Skarlso

Slack Username

skarlso

What Type of Request is it (Channel, User Group, Bot, Token, or Webhook)?

channel

Name of Requested Resource

external-secrets-maintainers

Is this request supported by an existing Kubernetes group (SIG, WG, Team, Subproject)? If so, please name them here, and tag a SIG lead who can verify the request.

external-secrets

Description of Request

Hello.

We would like to request a private channel

Justification for Request

Hello!

The external secrets operator project would like to request a private channel for just maintainers.

I'm one of the maintainers or the project.

[Priyankasaggu11929]

cc: @jberkus @mrbobbytables (Slack Admins)

---

Also, JFYI - https://www.kubernetes.dev/docs/comms/slack/#private-channels

We offer private channels on the Kubernetes Slack extremely sparingly. The only private channels we currently support involve community-owned software security or community moderation in some way. Unless supported by a Kubernetes SIG or the Steering Committee, requests for a private channel will be treated with skepticism.

Most private channels will be required to include a member of the Slack Admins team.

[Skarlso]

Ah, I understand. Thank you very much for the link there. I didn't know that. If we still get that channel I'll be happy. Otherwise, we'll stick to DM groups.

[Priyankasaggu11929]

Ah, I understand. Thank you very much for the link there. I didn't know that. If we still get that channel I'll be happy. Otherwise, we'll stick to DM groups.

yes, please. Let's wait for the Slack Admins to review the request. I was just sharing the link for reference. 🙂

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale