Free and Open Source Software

20629 readers

1 users here now

If it's free and open source and it's also software, it can be discussed here. Subcommunity of Technology.

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 3 years ago

MODERATORS

Gaywallet@beehaw.org

alyaza@beehaw.org

223

FFmpeg to Google: Fund Us or Stop Sending Bugs (thenewstack.io)

submitted 6 days ago by als@lemmy.blahaj.zone to c/foss@beehaw.org

52 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] TehPers@beehaw.org 49 points 6 days ago (1 children)

I think the last thing ffmpeg devs want is AI generated bugfixes to their assembly-heavy codebase. What they should do is dedicate time for experienced devs to fix the bugs instead.

[–] veniasilente@lemmy.dbzer0.com 1 points 5 days ago (1 children)

ffmpeg devs can refuse the AI generated bugfixes for all we care. What I'm heading at is if Google is going to spend AI on posting a problem, then they should also post the solution. At their own expense.

[–] TehPers@beehaw.org 4 points 5 days ago (1 children)

ffmpeg devs can refuse the AI generated bugfixes for all we care.

This is a separate problem, but it's still a problem. Many projects have seen a rise in slop PRs. curl is notorious for complaining about AI slop vulnerabilities and patch requests.

But I think we both agree that Google needs to be doing something more rather than putting the workload entirely on the ffmpeg devs.

[–] veniasilente@lemmy.dbzer0.com 1 points 5 days ago

Agree! I hereby propose that Google forwards US$1000 to the developers each time the AI signals a bug. Don't even need to write it off as expense, it's just "investment on QA".