REQUEST: New Slack <[channel]> < SRE-Learning-Platform >
ViktorUJ opened this issue · comments
GitHub Username
Slack Username
What Type of Request is it (Channel, User Group, Bot, Token, or Webhook)?
Channel
Name of Requested Resource
SRE-Learning-Platform
Description of Request
Dear Kubernetes Slack Administrators,
Good day! My name is Viktor. I have developed an open-source platform dedicated to learning Kubernetes and preparing for certification exams. The platform is designed to support individuals in their journey to understand and master Kubernetes, providing resources and materials beneficial for beginners and advanced users alike.
Considering the potential value it could bring to the community, I am reaching out to inquire if it would be possible to create a dedicated channel within the official Kubernetes Slack for this platform. This channel would serve as a hub for discussions, Q&A, sharing of resources, and support related to the learning platform and Kubernetes education in general.
I believe that such a channel could significantly contribute to the community, fostering a space for learning, collaboration, and growth among Kubernetes enthusiasts and professionals.
Thank you for considering my request. I am looking forward to your positive response and am more than willing to provide any further information or details required.
Best regards,
Viktor
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
The Kubernetes project currently lacks enough active 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 rotten
- Close this issue with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
is there any chance of doing that?