move meeting notes from hackmd.io to bootc-dev.github.io/news#37
move meeting notes from hackmd.io to bootc-dev.github.io/news#37wescpy wants to merge 3 commits into
Conversation
…to bootc-dev.github.io/news
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request standardizes the format of community meeting notes by removing Zola front matter and adding Markdown headers. It also adds a comprehensive set of new meeting notes from July 2025 to March 2026, documenting the project's evolution, technical milestones like composefs and chunkah, and community coordination. I have no feedback to provide.
jeckersb
left a comment
jeckersb
left a comment
There was a problem hiding this comment.
Looks like this fails to build:
$ zola build
Building site...
ERROR Failed to build the site
ERROR Couldn't find front matter in `/var/home/jeckersb/git/bootc-dev.github.io/content/news/2025-07-11-community-meeting.md`. Did you forget to add `+++` or `---`?
|
Whoops, didn't realize the Zola headers were required... fixed (I think)! |
|
Hm I think the CI failure is something goofy with the way github generates anchors via |
This is mildly goofy, but it appears that when you have a header inside of a markdown document, the anchor links are partially handled via scripts. As an example, on the raw page, the anchor for the code of conduct has `id=user-content-code-of-conduct` and `href=#code-of-conduct`. There's client-side javascript that handles finding the `user-content-code-of-conduct` anchor when you click on the `#code-of-conduct` link. Zola doesn't follow this, so it gets linkcheck errors. This points everything directly at the `#user-conduct-xxx` anchors which bypasses the clientside javascript shenanigans and makes the zola link checker happy. Signed-off-by: John Eckersberg <jeckersb@redhat.com>
|
Ok I added a commit to rewrite the links so it skips the javascript shenanigans. I think this is good to go now except it's missing the DCO sign-off on your two commits, let me know if you need assistance with that. |
|
One thing I did related to this is #48 |
|
I was thinking about this more and I'm not totally sure that the community meeting summaries should be "News" - what I'd bikeshed here is we have an "Events" feed which is mostly automated, and includes things like project releases and meeting summaries. It's kind of tricky because some of the meetings (actually often) are procedural about the project itself, which is not what I'd expect to see as a user mostly to see off the site? |
|
Perhaps actually we just need a procedure where we have https://github.com/bootc-dev/community/tree/meetings/$year/$month.md or so? |
3 participants
KubeCon EU
bootccontribfest contribution: split & move meeting notes fromhackmd.io/@cgwalters/HJk3Aj0ree/edittobootc-dev.github.io/news. Also did additional cleanup & making all the meeting notes consistent. CC: @nimbinatus nimbinatus