Commit graph

12 commits

Author SHA1 Message Date
d4280d633b docs: clarify GPU instance wording and credit reference post
Rename 'RAG instance' to 'GPU instance' for accuracy, and add a References
section crediting the LinuxCapable Fedora NVIDIA guide that mentors shared and
the RPM Fusion Howto, per review.

Signed-off-by: gtfrans2re <francoisgonothitoure@gmail.com>
2026-08-06 08:41:01 +00:00
9a40a91afc docs: add GPU driver setup runbook
Document the RPM Fusion NVIDIA driver + CUDA install used on the GPU instance
(Fedora 44 Cloud, A10G), for reproducibility and to inform the containerized
workflow. Verified: driver 610.43.03, CUDA 13.3, 24GB.

Assisted-by: Claude Opus 4.8
Signed-off-by: gtfrans2re <francoisgonothitoure@gmail.com>
2026-08-06 08:41:01 +00:00
56b8174e8b Merge remote-tracking branch 'upstream/main' into feat/eval-and-interface
Signed-off-by: gtfrans2re <francoisgonothitoure@gmail.com>

# Conflicts:
#	.gitignore
#	tests/conftest.py
2026-08-05 10:52:13 -04:00
19f157748b feat: add data-prep staging script and annotated source list (#2)
Script-driven corpus staging for the packaging-guidelines RAG pipeline.
Sources declared in data/sources.yaml, fetched into data/source/ for
ramalama rag to ingest. Corpus is a gitignored build artifact.

Assisted-by: Claude Opus 4.8
Signed-off-by: gtfrans2re <francoisgonothitoure@gmail.com>

Reviewed-on: #2
Reviewed-by: dominik kawka <dominikkawka@noreply.forge.fedoraproject.org>
Reviewed-by: Justin Wheeler <jwheel@redhat.com>
2026-08-05 13:45:03 +00:00
9f6d18346b fix: address PR review feedback on templates and defaults
Remove duplicate top-level Forgejo issue templates, keeping the standard
issue_template/ layout. Change the default RAG image from the personal Quay
namespace to quay.io/fedora/packaging-guide-ramalama across the app, CLI, and
RAG config; the personal namespace remains available via the PGR_RAG_IMAGE
override. Increase the question text area height for larger displays.

Assisted-by: Claude Opus 4.8
Signed-off-by: gtfrans2re <francoisgonothitoure@gmail.com>
2026-08-03 18:31:01 -04:00
c134c9e0f9 chore: remove committed Python bytecode
Assisted-by: Claude Opus 4.8
Signed-off-by: gtfrans2re <francoisgonothitoure@gmail.com>
2026-07-14 17:36:35 -04:00
0063d76d9c feat: implement the spec review output type
Implement the output design discussed in issue #160: lead with a prioritized,
actionable summary of issues (blockers first, each naming the guideline it
violates and the fix), expandable into a full fedora-review style checklist.

The model returns structured JSON so both views render from a single set of
findings rather than needing two model calls that could disagree. The schema
forces the model to cite a guideline and propose a fix for every finding,
which is where a RAG assistant adds value over the mechanical checks that
fedora-review and rpmlint already cover.

Delivered via a CLI (scripts/review_spec.py, with --full and --json) and the
Streamlit app, sharing one output layer. The parser tolerates messy model
output, with 19 airgapped unit tests.

Assisted-by: Claude Opus 4.8
Signed-off-by: gtfrans2re <francoisgonothitoure@gmail.com>
2026-07-14 16:08:15 -04:00
72793afb51
feat: add eval harness, RAG config, Forgejo templates, app, and notebook
Add the RAGAS vs DeepEval evaluation harness (eval/) with a Fedora Packaging
Guidelines question set and a tool recommendation, the RamaLama RAG config with
a packaging system prompt, Forgejo issue/PR templates, a Streamlit spec-review
app, and an exploration notebook. Addresses the remaining issue #160 deliverables.

Assisted-by: Claude Opus 4.8
Signed-off-by: gtfrans2re <francoisgonothitoure@gmail.com>
2026-07-11 01:17:50 -04:00
c0fca9ebdf
🔥 chore: Remove committed Python bytecode files
These `.pyc` files were accidentally committed alongside the docs
changes. They are build artifacts that belong in `.gitignore` (which
already excludes `__pycache__/`), not in the repository.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-07-11 01:09:39 -04:00
2a0ce36d2b
📝 docs: Add project docs for contributors, users, and AI agents
The `ai-ml/packaging-guide-ramalama` repo had code and data but not any
documentation explaining how to run the pipeline, how to contribute, or
how AI agents should interact with the project. These three files fill
that gap.

`GUIDE.md` walks a user from a fresh clone through corpus staging to a
built RAG vector store and a live query — the full pipeline end to end.
It is written to eventually move to the AI/ML SIG docs site once the
project stabilizes. `CONTRIBUTING.md` codifies the PR workflow, DCO
sign-off expectations, and AI-assisted contribution disclosure per
Fedora policy. `AGENTS.md` gives coding agents the project layout,
RamaLama API constraints, and safety guardrails they need to contribute
without inventing flags or committing secrets.

All three docs reflect the current state of the data-prep pipeline and
encode review feedback: one-sentence-per-line convention, corpus
terminology defined on first use, Fedora Packaging Guidelines
acknowledged as the primary and heaviest-weight data source, and the AI
disclosure exemption scoped strictly to superficial language help.

Assisted-by: Claude Opus 4.8
Signed-off-by: gtfrans2re <francoisgonothitoure@gmail.com>
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-07-11 01:08:31 -04:00
020968650b Update README.md
Absolute path needed since the issues path is not relative to code
2026-05-15 01:28:58 +00:00
86eb419549 Add README.md
Initialize repo with prefatory info
2026-05-15 00:06:56 +00:00