search

kubernetes / steering

The Kubernetes Steering Committee
Apache License 2.0
86 stars 61 forks source link

Add SC liaisons for committees #170

Closed nikhita closed 2 years ago

nikhita commented 4 years ago

In #159 and #168, we added Steering Committee liaisons for SIGs, WGs and UGs but we left out committees because they don't need to submit annual reports.

@parispittman suggested that we should also add SC liaisons for committees so that we have good feedback loops with them (thanks, Paris!)

fyi @divya-mohan0209 this might affect the blog post :)

divya-mohan0209 commented 4 years ago

Yay, more content! Thank you for thinking of me @nikhita :)

fejta-bot commented 4 years ago

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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

nikhita commented 4 years ago

/remove-lifecycle stale

On Tue, Oct 6, 2020 at 4:46 PM fejta-bot notifications@github.com wrote:

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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta https://github.com/fejta. /lifecycle stale

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kubernetes/steering/issues/170#issuecomment-704200359, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD24BUDIB655ARZJFHPP77TSJL4B3ANCNFSM4OUMVR6A .

fejta-bot commented 3 years ago

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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

nikhita commented 3 years ago

/remove-lifecycle stale

On Mon, Jan 4, 2021 at 5:58 PM fejta-bot notifications@github.com wrote:

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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta https://github.com/fejta. /lifecycle stale

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kubernetes/steering/issues/170#issuecomment-753947656, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD24BUGWRFSCBTXHY4BI7YDSYGX5TANCNFSM4OUMVR6A .

fejta-bot commented 3 years ago

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.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

nikhita commented 3 years ago

/remove-lifecycle stale

On Sun, Apr 4, 2021 at 9:12 PM fejta-bot @.***> wrote:

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.

Send feedback to sig-contributor-experience at kubernetes/community https://github.com/kubernetes/community. /lifecycle stale

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kubernetes/steering/issues/170#issuecomment-813054427, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD24BUEEJZ4UPBJ2MIEVLLDTHCCFXANCNFSM4OUMVR6A .

fejta-bot commented 3 years ago

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.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

nikhita commented 3 years ago

/remove-lifecycle stale

On Sun, 4 Jul 2021 at 14:27, fejta-bot @.***> wrote:

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.

Send feedback to sig-contributor-experience at kubernetes/community https://github.com/kubernetes/community. /lifecycle stale

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kubernetes/steering/issues/170#issuecomment-873549617, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD24BUAUVQURNDLITUO6KQLTWAO5ZANCNFSM4OUMVR6A .

k8s-triage-robot commented 3 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

dims commented 3 years ago

/remove-lifecycle stale

celestehorgan commented 3 years ago

One comment: the purpose of the Committees is to do work that needs to be done in private. As such:

  1. What are the expectations for a liaison? Will that liaison attend committee meetings, be in the committee channel, etc.?
  2. What is Steering's expectation for these liaisons reporting back?
parispittman commented 3 years ago

@celestehorgan there are no reporting duties and liaisons will be part of public channels only; this is mainly a way for us to flow information better specifically governance changes and events. An example for cocc’s liaison would be to remind about elections (both cocc and steering) and then possibly help start it like I’ve done in the past.

justaugustus commented 3 years ago

Opened https://github.com/kubernetes/community/pull/6260 to continue the discussion. /assign

justaugustus commented 2 years ago

From @tpepper in Steering agenda doc:

an idea not from the meeting live: Can committees be asked to give a read-out in the Annual Reports? CoCC effectively has one already in the new Conduct Transparency Report. Similar from sec. response could be informative to track abstract workload and committee internal ops health.