Document official Google calendar #46
Draft
Conversation
This file contains 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
|
Please feel free to remove me |
|
@rbvermaa Thanks, I've removed you. @infinisil Can you update the PR? |
edolstra
approved these changes
Dec 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Let's document the permissions for the official Google calendar explicitly, so that people can make PRs to request changes to it. I asked @edolstra for the current permissions, which this PR is based on.
@edolstra @grahamc
@rbvermaa@garbas @tomberek As the only people with access to manage permissions, you're being added as a code owner. The expectations are:This effectively makes this documentation the source of truth for calendar permissions. If you're okay with doing this, please approve this PR.
I'd say that those who don't react to this PR until 2024-12-23 (next Monday) can be assumed to not need access to manage permissions anymore, and would ask the others to remove them before we merge this PR. This ensures that everybody is willing to actively help maintain it.