community
community copied to clipboard
Add automation for interacting with Tekton calendar via gitops
We have a shared Tekton calendar at https://github.com/tektoncd/community/blob/master/contact.md#calendar but at the moment only a couple of people can edit it, so when folks want to reschedule meetings (like @hrishin for the observability working group!), they have to find someone with access to the calendar.
What would be really great is if we could have the expected state of the Tekton calendar committed to this repo, and updates to it would be reflected in the Google calendar.
(And even better, it could be implemented with Tekton itself!)
p.s. this was actually @dlorenc 's idea
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Send feedback to tektoncd/plumbing.
/lifecycle frozen
I still think it's a good idea (and makes maintainers' lives easier), just needs someone to work on it!