[Gonothi]: RAG Mini-Project - enhance a model with Fedora Magazine Blog Article Guidelines #146
Labels
No labels
state
ready for review
function
analytics
function
communications
function
docs
function
events
function
onboarding
function
operations
good first issue
help wanted
needs
changes
needs
reporter feedback
needs
team vote
needs
triage
scope
bug
scope
improvement
scope
new
state
approved
state
blocked
state
duplicate
state
invalid
state
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
Depends on
#145 [Gonothi]: Identify and scope a RAG mini-project candidate
commops/interns
Reference
commops/interns#146
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Enhance a model using RamaLama RAG on Fedora Magazine/Community Blog writing guidelines and past published articles to assist reviewers in evaluating draft submissions.
Background
The primary Outreachy internship project involves enhancing a model using RamaLama RAG with Fedora RPM Packaging Guidelines. As a warm-up mini-project, this task focuses on a smaller, well-scoped corpus: the Fedora Magazine blog article guidelines and past published articles. This was directly suggested by the mentors as a strong starting candidate due to its manageable size and real editorial utility.
Deliverables
Outcome
A working RAG prototype with Fedora Magazine/Community Blog guidelines is produced, validating the pipeline before tackling the full RPM documentation.
[Gonothi]: RAG Mini-Project - Train RamaLama on Fedora Magazine Blog Article Guidelinesto [Gonothi]: RAG Mini-Project - enhance a model with Fedora Magazine Blog Article Guidelines@gtfrans2re wrote in #146 (comment):
The best place to start is to make a pitch to the Fedora Magazine editors with the idea. They will give feedback and give a go-ahead to start drafting an article. Then, they will also be aware of the incoming content and can prepare the publishing schedule accordingly.
Updated the deliverables based on Justin's comment.
Hello, @jflory7! This is done and here it is:
@cybette, thanks for the update. I will have them all addressed.
Hello, @cybette!
As I still await the response of the Fedora Magazine Editorial team to my proposal here: https://discussion.fedoraproject.org/t/building-an-ai-editorial-assistant-for-fedora-publications-using-ramalama-rag/192396, and because I am unsure how to talk to them by Monday, June 8, which is the deadline, should I check off the two remaining items in the deliverables checklist? Or should I wait until I talk to them, even if the due date is exceeded?
Please let me know!
Hello, @cybette! Since today is the deadline to complete this task and the FP Magazine team has not yet gotten back to me, what should I do for the remaining two items on the checklist here?
I followed up and tagged you in here since it's been about 12 days: https://discussion.fedoraproject.org/t/building-an-ai-editorial-assistant-for-fedora-publications-using-ramalama-rag/192396/4 to see if you can help speed this up.
Also, about the blog post, I did draft one in the mini-project's git repo here that we can adapt later: https://github.com/gtfrans2re/fedora-commblog-rag/blob/main/docs/blog_draft.md.
@jflory7 and @dominikkawka, what are your thoughts on this?
Please let me know how I should proceed to complete this task today. Thank you in advance!
We can punt the remaining tasks to a later sprint, they are not a blocker for this part of the internship.
That's right, @cybette! Thank you so much for updating the issue as complete. We will get back to it in a later sprint, just as you said.