Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Codify steering committee liasons for SIGs into sigs.yaml #64

Closed
spiffxp opened this Issue Jul 18, 2018 · 6 comments

Comments

Projects
4 participants
@spiffxp
Copy link
Member

spiffxp commented Jul 18, 2018

Discussed during 2018-07-18 meeting

We currently have two steering committee members assigned to review a given SIG's charter in a spreadsheet. Ideally one who is involved and familiar with the SIG, and one who is not.

We discussed turning this into an ongoing role to make sure we have clear points of contact going forward. Both for steering to reach out to sigs, and vice-versa.

I will implement this by adding fields to sigs.yaml and updating sig readmes to include this info. I will make sure verbiage about this ends up in the same document that describes other common sig roles.

/assign

@spiffxp spiffxp added this to Backlog in Steering via automation Jul 18, 2018

@spiffxp spiffxp moved this from Backlog to In Progress in Steering Jul 18, 2018

@spiffxp

This comment has been minimized.

Copy link
Member Author

spiffxp commented Jul 18, 2018

/committee steering
/sig contributor-experience

@spiffxp

This comment has been minimized.

Copy link
Member Author

spiffxp commented Aug 9, 2018

Will be sourcing from this spreadsheet

@spiffxp spiffxp moved this from In Progress to Backlog in Steering Nov 30, 2018

@fejta-bot

This comment has been minimized.

Copy link

fejta-bot commented Dec 20, 2018

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

@fejta-bot

This comment has been minimized.

Copy link

fejta-bot commented Jan 20, 2019

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

@fejta-bot

This comment has been minimized.

Copy link

fejta-bot commented Feb 19, 2019

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

k8s-ci-robot commented Feb 19, 2019

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

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/test-infra repository.

Steering automation moved this from Backlog to Done Feb 19, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.