Programming

17394 readers

152 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

1056

Microsoft opens a "high priority" bug ticket in ffmpeg, attempting to leech the free labour of the maintainers (trac.ffmpeg.org)

submitted 7 months ago* (last edited 7 months ago) by Sibbo@sopuli.xyz to c/programming@programming.dev

226 comments fedilink hide all child comments

Microsoft employee:

Hi, This is a high priority ticket and the FFmpeg version is currently used in a highly visible product in Microsoft. We have customers experience issues with Caption during Teams Live Event. Please help

Maintainer's comment on twitter:

After politely requesting a support contract from Microsoft for long term maintenance, they offered a one-time payment of a few thousand dollars instead.

This is unacceptable.

And further:

The lesson from the xz fiasco is that investments in maintenance and sustainability are unsexy and probably won't get a middle manager their promotion but pay off a thousandfold over many years.

But try selling that to a bean counter

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

[–] TheMightyHUG@sh.itjust.works 71 points 7 months ago (74 children)

Can someone enlighten me why a one-time payment of a few thousand for a bugfix is unacceptable? I feel like I'm missing something.

[–] protozoan_ninja@sh.itjust.works 44 points 7 months ago* (last edited 7 months ago) (3 children)

There was no bug to fix, the PM didn't keep up with developments in an (apparently) core dependency and was passing outdated arguments to ffmpeg. The fix was for the project to update how it was passing flags to ffmpeg. They'd rather spend the time opening a ticket on ffmpeg's bugtracker and spend thousands of company money begging ffmpeg to help them, when MS is a massive corporation, is apparently relying on ffmpeg, yet has hitherto established no support relationship and also has developed no internal expertise on ffmpeg

They easily could have opened up the code and looked around to find the problem, or checked the changelog since an update broke it, or just rolled back to the last-known working version until they had time to figure it out, instead they just dumped it on ffmpeg's doorstep like their hair was on fire. FFMPEG's development model is explicitly that they iterate quickly and there are very likely to be poorly documented breaking changes between versions. It's not one you pull a new version of casually.

[–] duviobaz@lemmy.blahaj.zone 1 points 7 months ago

Thanks was too lazy to read the actual issue - exactly what i expected

load more comments (2 replies)

load more comments (72 replies)