[Docs] Auto Sync: meeting-notes/kubeedge-community-meeting-notes.md

[github-actions]

This PR was automatically generated by GitHub Actions to sync Google Docs.

• Source Doc ID: 1Sr5QS_Z04uPfRbA7PrXr3aPwCRpx7EtsyHq7mp6CnHs
• File: meeting-notes/kubeedge-community-meeting-notes.md

[kubeedge-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign hongbingzhang after the PR has been reviewed.
You can assign the PR to them by writing /assign @hongbingzhang in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[fujitatomoya]

does this really make sense? why do we not just keep the link to the google doc instead? or probably just make it merge automatically all the time, so that maintainers do not take this into account to merge every time?

[kevin-wangzefeng]

does this really make sense? why do we not just keep the link to the google doc instead? or probably just make it merge automatically all the time, so that maintainers do not take this into account to merge every time?

Thanks @fujitatomoya for raising the question.
Our meeting notes is stored in the google drive with the bot account and it happened a few times that the bot account was blocked by some reason, and we weren't able to retrieve them until we get to account back to live.

This gh action to auto-sync meeting notes to github is a starting point to verify if we can backup all the community assests to github.

We didn't make the PR accepted by automatically is based on the consideration that we need always verify whatever going to be checked into the repository. To improve the experience, probably we can move all the assests and backup automations to a separate repo, WDYT?

[fujitatomoya]

yeah that makes sense!