Source drift is now tracked, straight from your point: gknowledge notices when an original file changed after ingestion. It flags the source, can update and re-ingest it, and exposes a stale_sources tool over MCP
(github.com/openapi/gknowledge/pull/42).
We took your runtime advice too: make start-flatpak runs the dev loop inside the GNOME runtime, so UI work is tested against the GTK/libadwaita that Flatpak users actually get. It already caught a real bug (SQLite WAL vs. the
document portal) before release.
We've only tested on Ubuntu so far. If you give it a spin on Fedora, I'd love to hear what breaks, and reviews or issues are very welcome. Also: would you mind if we linked your GNOME SDK write-up from our contributor docs?
Data & AI architect by day, open source developer by night. Ex-founder, Linux convert, and firm believer that the human is still the most important part of the loop.
Thanks Justin! Linked: CONTRIBUTING now points to your Part 1 right after the make start-flatpak section, for anyone setting up the GNOME SDK for the first time: github.com/openapi/gknowledge/blob...
Great to have a Fedora 44 test. That's the one combination I haven't been able to check myself. No issue is too small, and I'll get to yours first.
Data & AI architect by day, open source developer by night. Ex-founder, Linux convert, and firm believer that the human is still the most important part of the loop.
Gave it a spin on Fedora 44 and it works fine. No issue from me yet. Thanks for linking Part 1 in CONTRIBUTING. Part 2 is already out if anyone wants to keep going.
Thanks Justin, a clean run on Fedora 44 is exactly the report I was hoping for! I just saw the series is already at Part 6, so I'll point CONTRIBUTING to the series page instead of Part 1 alone.
One idea: would you be OK if I used Building GNOME Apps with Rust as a demo knowledge base for gknowledge? Feed the posts in as sources, compile the wiki, and show agents asking cited questions like "how does the bind/unbind
rhythm work in GtkListView?". It would link back to every post. Happy to share the result with you before publishing anything.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks again, Justin — your comment shaped the last release.
Flatpak is out (v0.3.0, GNOME 51 runtime, PDF support included):
flatpak install --user --from openapi.github.io/gknowledge/io.gi...
Source drift is now tracked, straight from your point: gknowledge notices when an original file changed after ingestion. It flags the source, can update and re-ingest it, and exposes a stale_sources tool over MCP
(github.com/openapi/gknowledge/pull/42).
We took your runtime advice too: make start-flatpak runs the dev loop inside the GNOME runtime, so UI work is tested against the GTK/libadwaita that Flatpak users actually get. It already caught a real bug (SQLite WAL vs. the
document portal) before release.
We've only tested on Ubuntu so far. If you give it a spin on Fedora, I'd love to hear what breaks, and reviews or issues are very welcome. Also: would you mind if we linked your GNOME SDK write-up from our contributor docs?
That was fast, and a stale_sources tool over MCP is a really nice touch. Good catch on the WAL and document portal bug.
Of course, link away. Part 1 is the one: fromthearchitect.dev/posts/gnome-r...
I'm on Fedora 44, so I'll install the Flatpak this week and open issues for anything that breaks.
Thanks Justin! Linked: CONTRIBUTING now points to your Part 1 right after the make start-flatpak section, for anyone setting up the GNOME SDK for the first time: github.com/openapi/gknowledge/blob...
Great to have a Fedora 44 test. That's the one combination I haven't been able to check myself. No issue is too small, and I'll get to yours first.
Looking forward to Part 2 of your series!
Gave it a spin on Fedora 44 and it works fine. No issue from me yet. Thanks for linking Part 1 in CONTRIBUTING. Part 2 is already out if anyone wants to keep going.
Thanks Justin, a clean run on Fedora 44 is exactly the report I was hoping for! I just saw the series is already at Part 6, so I'll point CONTRIBUTING to the series page instead of Part 1 alone.
One idea: would you be OK if I used Building GNOME Apps with Rust as a demo knowledge base for gknowledge? Feed the posts in as sources, compile the wiki, and show agents asking cited questions like "how does the bind/unbind
rhythm work in GtkListView?". It would link back to every post. Happy to share the result with you before publishing anything.