add community meeting info and video archives.#806
Conversation
Signed-off-by: Tomoya Fujita <tomoya.fujita825@gmail.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
fujitatomoya
left a comment
There was a problem hiding this comment.
2 things.
- this is supposed to fail because of #804
- i intentionally exclude the Chinese doc to add those information.
There was a problem hiding this comment.
Code Review
This pull request introduces two new documentation files, meetings.md and talks.md, which provide comprehensive details on KubeEdge community meetings and recorded talks/videos respectively. It also updates a link in membership.md to point to the new meetings page. The review feedback focuses on improving clarity, correcting grammar and spelling (such as replacing "biweekly" with "every two weeks" to avoid ambiguity, and standardizing on American English spelling), and updating URLs to use cleaner or more modern domains.
| All meetings are public and anyone is welcome to join, listen in, or present a topic. | ||
|
|
||
| The single source of truth for meeting times, agendas, and recordings lives in the [kubeedge/community](https://github.com/kubeedge/community) repository. | ||
| The information below is a quick reference and may lag the upstream `README`; if anything here disagrees with the upstream repository, the upstream repository wins. |
There was a problem hiding this comment.
The phrase 'lag the upstream' is grammatically incomplete. It is more idiomatic to use 'lag behind the upstream'.
| The information below is a quick reference and may lag the upstream `README`; if anything here disagrees with the upstream repository, the upstream repository wins. | |
| The information below is a quick reference and may lag behind the upstream \`README\`; if anything here disagrees with the upstream repository, the upstream repository wins. |
| | **Technical Steering Committee (TSC) Meeting** | Wednesdays 10:00–11:00 Beijing Time (UTC+8) | Biweekly | | ||
| | **Regular Community Meeting** | Wednesdays 16:30–17:30 Beijing Time (UTC+8) | Biweekly | |
There was a problem hiding this comment.
The term 'Biweekly' is ambiguous as it can mean either twice a week or once every two weeks. To avoid confusion for community members, it is clearer to use 'Every two weeks'.
| | **Technical Steering Committee (TSC) Meeting** | Wednesdays 10:00–11:00 Beijing Time (UTC+8) | Biweekly | | |
| | **Regular Community Meeting** | Wednesdays 16:30–17:30 Beijing Time (UTC+8) | Biweekly | | |
| | **Technical Steering Committee (TSC) Meeting** | Wednesdays 10:00–11:00 Beijing Time (UTC+8) | Every two weeks | | |
| | **Regular Community Meeting** | Wednesdays 16:30–17:30 Beijing Time (UTC+8) | Every two weeks | |
| | **Technical Steering Committee (TSC) Meeting** | Wednesdays 10:00–11:00 Beijing Time (UTC+8) | Biweekly | | ||
| | **Regular Community Meeting** | Wednesdays 16:30–17:30 Beijing Time (UTC+8) | Biweekly | | ||
|
|
||
| Use [thetimezoneconverter.com](https://www.thetimezoneconverter.com/?t=10%3A00&tz=GMT%2B8&) to convert the Beijing time slot to your local time zone. |
There was a problem hiding this comment.
The timezone converter URL contains an unnecessary trailing ampersand (&). Removing it makes the URL cleaner.
| Use [thetimezoneconverter.com](https://www.thetimezoneconverter.com/?t=10%3A00&tz=GMT%2B8&) to convert the Beijing time slot to your local time zone. | |
| Use [thetimezoneconverter.com](https://www.thetimezoneconverter.com/?t=10%3A00&tz=GMT%2B8) to convert the Beijing time slot to your local time zone. |
| ## Code of conduct | ||
|
|
||
| All community meetings, just like every other KubeEdge interaction, are governed by the project [Code of Conduct](https://github.com/kubeedge/kubeedge/blob/master/CODE_OF_CONDUCT.md). | ||
| If you experience or witness behaviour that violates the Code of Conduct, please follow the reporting instructions in that document. |
There was a problem hiding this comment.
The word 'behaviour' uses British spelling. To maintain consistency with the rest of the documentation which uses American English (e.g., 'organization'), please use 'behavior'.
| If you experience or witness behaviour that violates the Code of Conduct, please follow the reporting instructions in that document. | |
| If you experience or witness behavior that violates the Code of Conduct, please follow the reporting instructions in that document. |
|
|
||
| - KubeEdge **blog** — long-form release announcements, design write-ups, and case studies are published at [kubeedge.io/blog](https://kubeedge.io/blog) and mirrored under the [blog/](https://github.com/kubeedge/website/tree/master/blog) directory of the website repository. Several blog posts pair directly with conference talks; the post usually links to the recording when one exists. | ||
| - [KubeEdge on the CNCF project page](https://www.cncf.io/projects/kubeedge/) — entry point with links to graduation announcement, devstats, and CNCF news. | ||
| - [KubeEdge on X / Twitter](https://twitter.com/KubeEdge) — announcements of upcoming talks and live coverage from KubeCon. |
There was a problem hiding this comment.
The URL for Twitter can be updated to use the modern x.com domain to keep the links current.
| - [KubeEdge on X / Twitter](https://twitter.com/KubeEdge) — announcements of upcoming talks and live coverage from KubeCon. | |
| - [KubeEdge on X / Twitter](https://x.com/KubeEdge) — announcements of upcoming talks and live coverage from KubeCon. |
| - **KubeCon + CloudNativeCon China** — typically the venue for the largest KubeEdge presence, including graduation announcements and case-study tracks from Chinese telco, energy, and industrial users. | ||
| - **KubeCon + CloudNativeCon Japan / India** — newer regional KubeCons that have featured KubeEdge talks since their inception. | ||
| - **Open Source Summit** (Linux Foundation) — KubeEdge has featured in edge-computing and IoT tracks. | ||
| - **CNCF on-line events** — webinars and "Project Journey" reports, including the KubeEdge graduation report and security audit summaries. |
There was a problem hiding this comment.
The word 'on-line' is typically written as 'online' without a hyphen.
| - **CNCF on-line events** — webinars and "Project Journey" reports, including the KubeEdge graduation report and security audit summaries. | |
| - **CNCF online events** — webinars and "Project Journey" reports, including the KubeEdge graduation report and security audit summaries. |
Which issue(s) this PR fixes:
Fixes #
Adding community meeting information and video archives.
None of them
community meeting information and video archives are available
No