You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!)
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.
I still think it's a good idea (and makes maintainers' lives easier), just needs someone to work on it!
tekton-robot
added
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
Aug 12, 2020
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
The text was updated successfully, but these errors were encountered: