server/tickets

Collection of this group's data for a LLM-powered weekly report #263

New issue

Open

opened 2026-09-09 09:57:10 +00:00 by abompard · 1 comment

abompard commented

2026-09-09 09:57:10 +00:00

Hi folks,

I'm generating a weekly report of activity in the Fedora project centered on teams and SIGs, it's called This Week in Fedora. This generation uses an LLM. The goal is to make it easier to catch up with everything that's going on in the project, and to give visibility to each group's work and requests for help. I think that from a newcomer's point of view, having an insight on what a group is working on at a point in time is helpful to decide whether it's interesting and worth contributing to.
I'm collecting activity from:

the server mailing-list
discourse posts with the #server-wg tag
this tracker
meetings in the Matrix meeting rooms

In the latest version, I've added the possiblity to gather messages exchanged in Matrix channels. The #server channel is public and its history is available to anyone, but a quite a few people in mutiple Matrix channels were unhappy about the LLM collecting this info, for various reasons.
I would like to know whether this group is OK with my program collecting and submitting info to an LLM from the following sources:

mailing-lists and discourse posts
the tracker
the matrix channel

I would like to make the case for source 3 (the Matrix channel) because I think it's less obvious: knowing the "tone" of a conversation and the currently discussed subjects before joining is very important to help contribute to it. It's like when you're added to an empty group chat and you don't know how to start. That's why we show history to new channel members, and this would be the same idea at a higher level. Plus there's actual work going on in there for a lot of groups.
That said, I recognize that the form of the tool influences its use, chat messages are usually less thought-through than emails or forum posts, and members could be indimidated that something they write there and regret end up in a visible summary (the program respects message edits, but anyway).
Since my goal is to foster participation, the one thing I don't want to do is to hinder it in another way.

I know I've asked this in the chat yesterday but someone in another room noted that people can easily miss Matrix messages, which it true.

Please decide which collected sources, if any, you are OK with (and if you work in other places that you would like to have collected, of course (I can do RSS feeds!)). If the group is OK with Matrix channel collection but some individuals aren't, I can also exclude certain Matrix usernames from collection throughout the Matrix channels that are not meetings.

I'm happy to answer questions if you have any.

Hi folks, I'm generating a weekly report of activity in the Fedora project centered on teams and SIGs, it's called [This Week in Fedora](https://abompard.fedorapeople.org/twif/). This generation uses an LLM. The goal is to make it easier to catch up with everything that's going on in the project, and to give visibility to each group's work and requests for help. I think that from a newcomer's point of view, having an insight on what a group is working on at a point in time is helpful to decide whether it's interesting and worth contributing to. I'm collecting activity from: - the `server` mailing-list - discourse posts with the `#server-wg` tag - this tracker - meetings in the Matrix meeting rooms In the latest version, I've added the possiblity to gather messages exchanged in Matrix channels. The `#server` channel is public and its history is available to anyone, but a quite a few people in mutiple Matrix channels were unhappy about the LLM collecting this info, for various reasons. I would like to know whether this group is OK with my program collecting and submitting info to an LLM from the following sources: 1. mailing-lists and discourse posts 2. the tracker 3. the matrix channel I would like to make the case for source 3 (the Matrix channel) because I think it's less obvious: knowing the "tone" of a conversation and the currently discussed subjects before joining is very important to help contribute to it. It's like when you're added to an empty group chat and you don't know how to start. That's why we show history to new channel members, and this would be the same idea at a higher level. Plus there's actual work going on in there for a lot of groups. That said, I recognize that the form of the tool influences its use, chat messages are usually less thought-through than emails or forum posts, and members could be indimidated that something they write there and regret end up in a visible summary (the program respects message edits, but anyway). Since my goal is to foster participation, the one thing I don't want to do is to hinder it in another way. I know I've asked this in the chat yesterday but someone in another room noted that people can easily miss Matrix messages, which it true. Please decide which collected sources, if any, you are OK with (and if you work in other places that you would like to have collected, of course (I can do RSS feeds!)). If the group is OK with Matrix channel collection but some individuals aren't, I can also exclude certain Matrix usernames from collection throughout the Matrix channels that are not meetings. I'm happy to answer questions if you have any.

pboy commented

2026-09-09 18:17:31 +00:00

Owner

A summary of our discussion at meeting Sep 09, 2026:

Bot Aurélien noted:

LLM-Powered Weekly Reports:

The proposal to use an LLM to generate weekly summaries from the group's public chat channels was met with mixed feelings.
Concerns were raised about privacy, the feeling of being monitored, potential for misinterpretation, and the specifics of the LLM implementation.
A request was made for an opt-out mechanism for individuals' messages.
The group decided to postpone the decision and discuss the matter further in their Matrix room.

We agreed to use our more or less regular Fridays open gathering, starting at 17:00 UTC with open end.

A summary of our discussion at meeting Sep 09, 2026: Bot Aurélien noted: #### LLM-Powered Weekly Reports: - The proposal to use an LLM to generate weekly summaries from the group's public chat channels was met with mixed feelings. - Concerns were raised about privacy, the feeling of being monitored, potential for misinterpretation, and the specifics of the LLM implementation. - A request was made for an opt-out mechanism for individuals' messages. - The group decided to postpone the decision and discuss the matter further in their Matrix room. We agreed to use our more or less regular Fridays open gathering, starting at 17:00 UTC with open end.

pboy added the

Working Group Organization

label

2026-09-20 06:44:39 +00:00

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

server/tickets#263

No description provided.

Rows
Columns