Skip to content

move meeting notes from hackmd.io to bootc-dev.github.io/news#37

Open
wescpy wants to merge 3 commits intobootc-dev:mainfrom
wescpy:main
Open

move meeting notes from hackmd.io to bootc-dev.github.io/news#37
wescpy wants to merge 3 commits intobootc-dev:mainfrom
wescpy:main

Conversation

@wescpy
Copy link
Copy Markdown

@wescpy wescpy commented Mar 30, 2026

KubeCon EU bootc contribfest contribution: split & move meeting notes from hackmd.io/@cgwalters/HJk3Aj0ree/edit to bootc-dev.github.io/news. Also did additional cleanup & making all the meeting notes consistent. CC: @nimbinatus nimbinatus

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Collaborator

@jeckersb jeckersb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 `---`?

@wescpy
Copy link
Copy Markdown
Author

wescpy commented Mar 31, 2026

Whoops, didn't realize the Zola headers were required... fixed (I think)!

@wescpy wescpy requested a review from jeckersb March 31, 2026 15:57
@jeckersb
Copy link
Copy Markdown
Collaborator

Hm I think the CI failure is something goofy with the way github generates anchors via <script> tags or something. Let me see if I can figure out what that's all about.

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>
@jeckersb
Copy link
Copy Markdown
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants