Skip to content

📖docs: updated community meetings link in README#929

Open
Janhvibabani wants to merge 2 commits intokubestellar:mainfrom
Janhvibabani:chore/update-community-meetings-link
Open

📖docs: updated community meetings link in README#929
Janhvibabani wants to merge 2 commits intokubestellar:mainfrom
Janhvibabani:chore/update-community-meetings-link

Conversation

@Janhvibabani
Copy link
Contributor

📌 Fixes

Fixes #866


📝 Summary of Changes

The previous link used to point to https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=MWM4a2loZDZrOWwzZWQzZ29xanZwa3NuMWdfMjAyMzA1MThUMTQwMDAwWiBiM2Q2NWM5MmJlZDdhOTg4NGVmN2ZlOWUzZjZjOGZlZDE2ZjZmYjJmODExZjU3NTBmNTQ3NTY3YTVkZDU4ZmVkQGc&tmsrc=b3d65c92bed7a9884ef7fe9e3f6c8fed16f6fb2f811f5750f547567a5dd58fed%40group.calendar.google.com&scp=ALL which was a wrong link as it used to point the meeting from 2023

Changes Made


Checklist

Please ensure the following before submitting your PR:

  • I have reviewed the project's contribution guidelines.
  • I have written unit tests for the changes (if applicable).
  • I have updated the documentation (if applicable).
  • I have tested the changes locally and ensured they work as expected.
  • My code follows the project's coding standards.

Screenshots or Logs (if applicable)


👀 Reviewer Notes

Add any special notes for the reviewer here

Copilot AI review requested due to automatic review settings January 30, 2026 07:21
@kubestellar-prow kubestellar-prow bot added the dco-signoff: yes Indicates the PR's author has signed the DCO. label Jan 30, 2026
@kubestellar-prow
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign sagar2366 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:

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

@github-actions
Copy link
Contributor

Welcome to KubeStellar! 🚀 Thank you for submitting this Pull Request.

Before your PR can be merged, please ensure:

DCO Sign-off - All commits must be signed off with git commit -s to certify the Developer Certificate of Origin

PR Title - Must start with an emoji: ✨ (feature), 🐛 (bug fix), 📖 (docs), 🌱 (infra/tests), ⚠️ (breaking change)

Getting Started with KubeStellar:

Contributor Resources:


🌟 Help KubeStellar Grow - We Need Adopters!

Our roadmap is driven entirely by adopter feedback. Whether you're using KubeStellar yourself or know someone who could benefit from multi-cluster Kubernetes:

📋 Take our Multi-Cluster Survey - Share your use cases and help shape our direction!


A maintainer will review your PR soon. Feel free to ask questions in the comments or on Slack!

@github-actions github-actions bot added the documentation Improvements or additions to documentation label Jan 30, 2026
@kubestellar-prow kubestellar-prow bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 30, 2026
@kubestellar-prow
Copy link

Hi @Janhvibabani. Thanks for your PR.

I'm waiting for a kubestellar 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.

@netlify
Copy link

netlify bot commented Jan 30, 2026

Deploy Preview for kubestellar-docs ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit d8e242c
🔍 Latest deploy log https://app.netlify.com/projects/kubestellar-docs/deploys/697e1cd19fc2a7000884957b
😎 Deploy Preview https://deploy-preview-929--kubestellar-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the README’s “Community Meetings” link to avoid directing users to an outdated (2023) Google Calendar event.

Changes:

  • Replaced the “community calendar” hyperlink under Community Meetings in README.md.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

README.md Outdated
- [kubestellar-dev](https://groups.google.com/g/kubestellar-dev) — Development discussions
- [kubestellar-users](https://groups.google.com/g/kubestellar-users) — User community discussions
- **Community Meetings**: Subscribe to our [community calendar](https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=MWM4a2loZDZrOWwzZWQzZ29xanZwa3NuMWdfMjAyMzA1MThUMTQwMDAwWiBiM2Q2NWM5MmJlZDdhOTg4NGVmN2ZlOWUzZjZjOGZlZDE2ZjZmYjJmODExZjU3NTBmNTQ3NTY3YTVkZDU4ZmVkQGc&tmsrc=b3d65c92bed7a9884ef7fe9e3f6c8fed16f6fb2f811f5750f547567a5dd58fed%40group.calendar.google.com&scp=ALL)
- **Community Meetings**: Subscribe to our [community calendar](https://docs.google.com/document/d/1XppfxSOD7AOX1lVVVIPWjpFkrxakfBfVzcybRg17-PM/edit?tab=t.0#heading=h.x7eowycdcihh)
Copy link

Copilot AI Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The link text says “Subscribe to our community calendar”, but the new URL points to a Google Doc (meeting agenda) rather than a calendar subscription/view link. This doesn’t match the stated goal of replacing the date-specific calendar event link with a non–date-specific calendar link, and it may also be inaccessible to users without doc permissions. Consider updating the URL to the project’s non–date-specific calendar subscription/view link (e.g., the public .ics or embed link used in docs/content/Community/_index.md) or adjust the link text to reflect that it’s an agenda document instead of a calendar.

Copilot uses AI. Check for mistakes.
@oksaumya
Copy link
Member

@Janhvibabani ,the Copilot suggestions look good. Please go ahead and implement them.

Signed-off-by: JANHVI BABANI <114232474+Janhvibabani@users.noreply.github.com>
…of a calendar.

Signed-off-by: JANHVI BABANI <114232474+Janhvibabani@users.noreply.github.com>
@Janhvibabani Janhvibabani force-pushed the chore/update-community-meetings-link branch from 40d2577 to d8e242c Compare January 31, 2026 15:16
@Janhvibabani
Copy link
Contributor Author

@oksaumya updated it, check!

@oksaumya
Copy link
Member

oksaumya commented Feb 1, 2026

still asking permission

Copy link
Contributor

@KPRoche KPRoche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe the agenda is only accessible via that link after one has successfully joined the mailing list. I think it would be wise to move its position in the list and note that fact.
That is also how you get the meeting notifications.

@Janhvibabani
Copy link
Contributor Author

hey, @KPRoche are you taking it over? i was actually unaware that we couldn't see the link unless we are part of the mailing list thanks for making it clear, i will add a note and make the changes if you haven't started working on it yet.

@KPRoche
Copy link
Contributor

KPRoche commented Feb 3, 2026

hey, @KPRoche are you taking it over? i was actually unaware that we couldn't see the link unless we are part of the mailing list thanks for making it clear, i will add a note and make the changes if you haven't started working on it yet.

Technically I never left :-)
I've been overseeing the KubeStellar site as part of the core team almost since it went live with mkdocs.
I try to keep an eye on all the docs PRs, and keep its semantic structure logically consistent.

I double-checked, and the meeting link is sent out to all members of the mailing list (and slack channel), so those are the best route to ensuring people get the most current link.

@Janhvibabani
Copy link
Contributor Author

@KPRoche Wow I didn't know this,just want to confirm I’ve got this right, Would adding an instruction to join the mailing list for the latest meeting updates be enough, and remove the link which leads to 2023 calendar event?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dco-signoff: yes Indicates the PR's author has signed the DCO. documentation Improvements or additions to documentation needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: Outdated Google Calendar link under “Subscribe to our community calendar” in README

3 participants