docs(community): publish the meeting archive and how the meeting runs - #47
docs(community): publish the meeting archive and how the meeting runs#47Timur Tukaev (tym83) wants to merge 1 commit into
Conversation
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
a39dec7 to
3a6b36f
Compare
The README promised meeting notes and community calls; nothing in the repo delivered them. Two years of meetings existed only as a Google Doc and a YouTube playlist that neither the repo nor the website pointed at, so from the outside the project looked like it holds no public calls at all. Add community_meeting.md (schedule, joining link, agenda format, how to put a topic on it) and meetings/README.md indexing all 72 meetings held since April 2024 with their topics and recordings. The index makes gaps visible too: ten meetings have notes but no published recording. Signed-off-by: Timur Tukaev <timur.tukaev@aenix.io>
3a6b36f to
83da23a
Compare
Summary
The README promised "Meeting notes and community calls" and the repo delivered
none. Two years of biweekly meetings existed only as a Google Doc and a YouTube
playlist that neither this repo nor the website linked to — so from the outside
the project looked like it holds no public calls at all.
What
community_meeting.md— the schedule, the joining link, the host, theagenda format, how to put a topic on the agenda, how to get edit access to the
notes document, and what the host does after the call.
meetings/README.md— an index of all 72 meetings held since 2024-04-04,each with its date, topics and recording. 62 recordings are linked; the ten
meetings with notes but no published recording are shown with an explicit dash
rather than omitted.
README.md— replaced "contains (or will contain soon)" with what the repoactually holds, and added a table of the four YouTube playlists (community
meetings, CozySummit 2026 on the CNCF channel, CozySummit'25, CNCF webinars).
The notes themselves stay in the shared document — it is edited live during the
call by attendees, and copying it into Git would create a second source of truth
that immediately drifts. This repo indexes and points at it, the way
kubernetes/community and kubevirt/community do.
Why
Anyone evaluating the project — a prospective contributor or a governance
reviewer — currently has no way to learn from this repository that community
meetings happen at all, let alone find a specific discussion. The index also
makes the gaps visible, which is the point: ten missing recordings are now a
list someone can work through rather than an invisible hole.
Notes for reviewers
YYYY-DD-MMfor most of2026,
YYYY-MM-DDearlier, dots instead of dashes for eight of them). Dates inthe table were resolved against the actual meeting list in the notes document,
not parsed blindly. Worth normalising the titles on the channel separately.
second Thursday. This file states biweekly, matching the actual cadence — the
document header should be corrected too.
github.com/aenix-io/cozystack, whichpredates the move to the
cozystackorg.