GOVERNANCE: Update meeting details#1387
Closed
jmarrero wants to merge 1 commit into
Closed
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
|
|
||
| Time zones permitting, Maintainers are expected to participate in the public | ||
| developer meeting, which occurs at 3:30 PM ET on Thursdays via [Zoom](TODO). | ||
| developer meeting, which occurs at 11:30 AM ET on Fridays via [jit.si](https://meet.jit.si/YourOperatingSystemIsAContainer). |
Contributor
There was a problem hiding this comment.
The meeting link includes YourOperatingSystemIsAContainer which seems like a placeholder. Please ensure this is the correct and intended link for the meeting.
Suggested change
| developer meeting, which occurs at 11:30 AM ET on Fridays via [jit.si](https://meet.jit.si/YourOperatingSystemIsAContainer). | |
| developer meeting, which occurs at 11:30 AM ET on Fridays via [jit.si](https://meet.jit.si/). |
Signed-off-by: Joseph Marrero Corchado <jmarrero@redhat.com>
cgwalters
reviewed
Jun 27, 2025
|
|
||
| Time zones permitting, Maintainers are expected to participate in the public | ||
| developer meeting, which occurs at 3:30 PM ET on Thursdays via [Zoom](TODO). | ||
| developer meeting, which occurs at 11:30 AM ET on Fridays via [jit.si](https://meet.jit.si/YourOperatingSystemIsAContainer). |
Collaborator
There was a problem hiding this comment.
Suggested change
| developer meeting, which occurs at 11:30 AM ET on Fridays via [jit.si](https://meet.jit.si/YourOperatingSystemIsAContainer). | |
| developer meeting, which occurs at 11:30 AM EST on Fridays via [jit.si](https://meet.jit.si). The actual URL will be posted on the Slack channel a few minutes before the meeting. |
That said it'd be better to have the time be in UTC not EST to be a bit more timezone friendly and not have people need to remember when EST changes daylight savings etc.
That said also I think the best thing here is to have an ical entry or so? Surely there's some best practice here.
Collaborator
|
Wait this PR just duplicates #1368 right? |
Contributor
Author
|
Yeah, sorry when trying to socialize the meeting I was looking for where to point and did not see our meeting in the doc. Let's merge the other one and bikeshed later? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Make sure we link to the jit.si meeting we have been using.