Hi Michael, On Wed, Oct 21, 2026 at 3:01 PM Michael Niedermayer via ffmpeg-devel < [email protected]> wrote:
> Hi Tomas > > On Wed, Oct 21, 2026 at 01:22:46PM +0200, Tomas Härdin via ffmpeg-devel > wrote: > > On Wed, 2026-10-21 at 00:09 +0200, Michael Niedermayer via ffmpeg-devel > > wrote: > > > Also fairy today gained the ability to close PRs and Issues > > > > > > First issue she has closed: > > > https://code.ffmpeg.org/FFmpeg/FFmpeg/issues/24564 > > > > > > ATM closing tickets still requires human approval, but i will likely > > > soon remove that latency as i expect her to be able to do that > > > reliably > > > > A fancy Markov chain is not a person > > > > If we're going to be automatically closing tickets, why are we > > delegating that to a statistical model, whose behavior is fundamentally > > random? > > We have >500 open tickets and not enough volunteers to review them all > manually. > That's why we're using Fairy to help with this. > I do not have the technical expertise to help with the review effort, but do wish to weigh in on this change of policy. I think it should be discussed and approved by a consortium of developers as it is a major change in contribution standards. "we're using" above should really be "I decided to use", unless i have missed a discussion. A related question, if some form of automatic AI moderation is agreed upon, are its limits. Can tickets only be closed (and only as not a bug), can PR's be rejected only, or also be merged? How far is the project willing to go? The situation with many open issues and PRs is no different from before the project moved to forgejo, and indeed not ideal, but this should be discussed before implemented. All the best, Dee _______________________________________________ ffmpeg-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
