Community: Setup biweekly meeting for licensing subproject

[nikhita]

Licensing is a subproject under SIG Release: https://github.com/kubernetes/sig-release/tree/master/licensing

To keep the ball rolling on this, it would be helpful to setup a public biweekly meeting for it. This issue is for tracking setting up the meeting - creating a doodle, finalizing on a time, adding it to sigs.yaml and notifying the sig-release mailing list.

/sig release
/area licensing
/cc @swinslow @dims @justaugustus @tpepper @calebamiles

/assign @justaugustus
since you mentioned you'll create the doodle. let me know if you shouldn't be assigned here, I'll assign myself then :)

/cc @kubernetes/dep-approvers
since you might be interested in it

[justaugustus]

@nikhita @dims @swinslow -- Doodle is up here: https://doodle.com/poll/ch62xafdbgqmyrtp

[justaugustus]

@nikhita @dims @swinslow -- My apologies, KubeCon prep has gotten the best of me.
Can we plan to meet the week of 5/27? If that works, I'll send another Doodle.

[nikhita]

KubeCon prep has gotten the best of me.

Np, can relate to that :)

Can we plan to meet the week of 5/27?

Sounds good!

[swinslow]

Yes, works for me! Thanks @justaugustus :)

[justaugustus]

@nikhita @dims @swinslow -- New Doodle for the Licensing subproject meeting: https://doodle.com/poll/bg9g5pcfw3v66g7r

[justaugustus]

@dims -- just a heads up to vote on this Doodle when you have a chance.

[justaugustus]

@nikhita @dims @swinslow -- Invite sent for Thursday, May 30th, 2pm ET!
We may move this meeting as it is in the same timeslot as SIG Arch, but let's try it out for now and adjust if we need to later. :)

/close

[k8s-ci-robot]

@justaugustus: Closing this issue.

In response to this:

@nikhita @dims @swinslow -- Invite sent for Thursday, May 30th, 2pm ET!
We may move this meeting as it is in the same timeslot as SIG Arch, but let's try it out for now and adjust if we need to later. :)

/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.

[justaugustus]

Notified SIG Release on the mailing list: https://groups.google.com/d/topic/kubernetes-sig-release/boaGhSZwd54/discussion

[nikhita]

We may move this meeting as it is in the same timeslot as SIG Arch, but let's try it out for now and adjust if we need to later. :)

I'm cool with this timeslot for this week, but would prefer if we can move it later so that it won't conflict with the SIG Arch (code organization) meeting. :)

I think I filled out the doodle before the code organization meeting was setup (sorry!) :see_no_evil:

[justaugustus]

@nikhita -- For sure, that can be one of our discussion topics!

[justaugustus]

/reopen

[k8s-ci-robot]

@justaugustus: Reopened this issue.

In response to this:

/reopen

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.

[justaugustus]

@nikhita is going to be taking point on Licensing moving forward so that I can direct my attention to the Release Engineering work. I'll let her handle the scheduling and provide support where needed.

/unassign
/assign @nikhita

[fejta-bot]

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]

/remove-lifecycle stale

[fejta-bot]

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]

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

[swinslow]

/remove-lifecycle rotten

[swinslow]

Hi @nikhita, I've made a note to reach out to you shortly so that we can reconnect and move this forward. Thanks!

[dims]

@swinslow ping!

[fejta-bot]

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]

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]

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]

@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.