kubernetes
add CAPG office hour
adding the CAPG office hours
I need to know how to create a zoom meeting and maybe have the host key?
/assign @dims @neolit123 @mrbobbytables
@cpanato it should be created by the sig leads for SCL and they can provide you with info / host key.
@cpanato we seem to have a problem with the SIG calendar and the event cannot be added there. but at least you can add the Zoom link here in the PR: https://zoom.us/j/96963829102?pwd=WjBZcmwvZFZsUU93aVZieUk1L3FnZz09
NVM: it was a temp issue and the meeting was added to the SIG calendar.
@neolit123 rebased PTAL
also i did not see the meeting show up in my calendar, there is anything to do?
also i did not see the meeting show up in my calendar, there is anything to do?
There is a meeting in the SIG CL calendar for today (same time as CAPI main meeting), but it did not appear in the k8s community calendar. #sig-contribex might be able to help.
When adding the meeting I was seeing some odd errors like "quota exceeded" but don't remember exactly. That might be related.
When adding the meeting I was seeing some odd errors like "quota exceeded" but don't remember exactly. That might be related.
That means too many calendar events have been made by a single individual in too short a time. The only options are to wait or have someone else create the event. This is the same issue that made us move off public google groups to a managed domain for kdev.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: cpanato, neolit123 To complete the pull request process, please ask for approval from dims after the PR has been reviewed.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@mrbobbytables have the host key and just missing the calendar entry which we are trying to get it, but i guess we can merge this PR
@mrbobbytables @cpanato @neolit123 It seems that there is a problem with the SIG SCL calendar, the same @neolit123 quoted above:
- we cannot include the SIG CL ML as a guest, because when doing this we got an error about reaching calendar limits.
- as a consequence, the event does not show up in the k8s calendar
As a temporary solution, people can follow the SCL calendar (https://calendar.google.com/calendar/u/0?cid=dTU4MjJscmw0cTY4aWMxaWFrdXZjcGU3YjRAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ), but in the long run 2e need guidance on how restore the operativity on the SCL calendar
However, this PR can merge IMO
@fabriziopandini - the only complete solution to that problem is to migrate off a public googlegroup. =/ This is why we did the kdev migration to a kubernetes.io managed domain. We could no longer send it calendar invites. Migrating users is a bit of a pain right now. Theres a hacky script that was used for kdev that is by no means ready for general use, we could bump the priority on getting that taken care of, but it'd definitely be post kubecon.
@cpanato: PR needs rebase.
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.
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:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Reopen this PR with
/reopen - Mark this PR as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closed this PR.
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closedYou can:
- Reopen this PR with
/reopen- Mark this PR as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/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.