search

kubernetes / community

Kubernetes community content
Apache License 2.0
11.92k stars 5.16k forks source link

mailing lists and calendar invites #5981

Closed parispittman closed 2 years ago

parispittman commented 3 years ago

@thockin raised this in sig-contribex

Problem: subscribed to multiple mailing lists and those mailing lists send multiple calendar invites per group (ie big sigs with lots of subproject meetings). the amount of meetings on calendars is a burden for folks.

Knowns: calendars are terrible (hard to manage, timezones, ical, etc) we have too many meetings (45+ a week) permissions to change calendar invites has lots of layers (whoever establishes the invite is the owner) calendar guidelines leave comment below for others

Proposals:

parispittman commented 3 years ago

/sig contributor-experience

thockin commented 3 years ago

Or one meetings-calendar per SIG?

On Mon, Aug 30, 2021 at 11:35 AM Paris @.***> wrote:

/sig contributor-experience

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kubernetes/community/issues/5981#issuecomment-908587563, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABKWAVA57MZHCA5LPNDX3WLT7PFQNANCNFSM5DCODW7A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

justaugustus commented 3 years ago

have chairs create a mailing list for meetings only, example: sig-network-mtgs@

+1 to per-SIG meeting calendar + list. Most of us should already have associated calendars as part of SIG creation steps.

Voting for this one because I'm primarily interested in joining a list to get a fresh calendar invite because it blocks my availability. Depending on the email system, calendar configuration, or organizational restrictions, there's no guarantee that a separate calendar subscription will do the same.

cc: @kubernetes/sig-release for thoughts as well

sandipanpanda commented 2 years ago

/area community-management

salaxander commented 2 years ago

+1 to having a per SIG calendar that can be subscribed to. However it currently works being tied to the group is kind of a pain, especially if you lose one of the calendar invites. Having a dedicated calendar you can subscribe to would fix that for sure!

mrbobbytables commented 2 years ago

I am +1 for separate ML for calendar invites, but I would hold off on doing anything like that right now and make it a standard pattern when sigs start to migrate to kubernetes.io managed groups.

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/close

k8s-ci-robot commented 2 years ago

@k8s-triage-robot: Closing this issue.

In response to [this](https://github.com/kubernetes/community/issues/5981#issuecomment-1114256432): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues and PRs 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: >- Reopen this issue or PR with `/reopen` >- Mark this issue or PR as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.