On Thu, 11 Jul 2024 at 13:47, Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxx> wrote: > > On Thu, Jul 11, 2024 at 12:08 PM Stephen Smoogen <ssmoogen@xxxxxxxxxx> wrote: > > > > On Thu, 11 Jul 2024 at 11:34, Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxx> wrote: > > > > > > On Wed, Jul 10, 2024 at 12:46 PM Daniel P. Berrangé <berrange@xxxxxxxxxx> wrote: > > > > > > > > On Wed, Jul 10, 2024 at 09:36:35AM -0400, Stephen Gallagher wrote: > > > > > I'm guessing Josh's response was an attempt to use AI to generate a > > > > > summary. In the future, please label it as such, so people will read > > > > > it with a critical eye. It has some flaws which I will address inline: > > > > > > > > If content is labelled as written by AI I'd skip reading it entirely. > > > > Reading "with a critical eye" implies we have to either guess (or > > > > research) which parts are accurate and which are wrong, neither option > > > > being desirable. > > > > > > > > I'd ask for human written summaries, or none at all, in prefence to > > > > misleading AI summaries. > > > > > > Human in the loop is of course important. The intention would be to > > > have FESCo review any AI generated content for accuracy before sending > > > it out. From a consumer perspective, you get content that has been > > > validated by a human and you should be able to trust it like you would > > > any other email sent. > > > > > > If FESCo doesn't want to use AI at all, I don't care. I just want > > > better summaries than what zodbot is currently providing (which aren't > > > reviewed either afaics...) > > > > > > > The 'summaries' are just what the person running the meeting is > > collecting during the meeting while trying to also keep the meeting > > running AND be a participant of the meeting. The person doing this is > > a volunteer and generally has zero training in note taking, running > > meetings or a dozen other things which are expected. If better notes > > are expected, then better training or having an agreed upon > > professional whose sole job is this task is generally needed. > > I don't agree with this at all. I served on FESCo for years. I know > what the existing summaries represent, how they're generated, and what > the dynamics of the meetings are. You don't need training and > professional people to improve things as a project. > My apologies, I wasn't clear. I consider bringing a GPT into the mix the same as having a professional on it. It is a 'service' which is paid for in some way which is 'trained' to do a particular job well. The example you gave was better detailed (if flawed) than I think I have ever seen a FESCO or Council meeting annotated excluding ones by specific people who have either training or a knack on doing this well. That was the level of detail I was thinking was wanted and not something I expect someone who is volunteering to do this and trying to get information out before their day job takes over to do as well. Again my apologies for not being clear. > Honestly, I'm not finding fault with FESCo. I'm saying the thing they > are doing today is not really valuable for a consumer base that wasn't > in the meeting. If they want to make it better, AI is a tool that is > actually pretty simple to use to do that without a ton of effort. If > they don't want to make it better, then maybe just stop publishing the > summary emails entirely and save themselves and others time. The > meeting logs will still be there. > > josh > -- > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
