FFmpeg should be able to pull multiple $M per year easily from all the major corporations that use it. For comparison, $1M is the total yearly cost of ~3 average engineers at FAANGs. And most, if not all of them, use FFmpeg quite seriously.
FFmpeg should be able to pull multiple $M per year easily from all the major corporations that use it. For comparison, $1M is the total yearly cost of ~3 average engineers at FAANGs. And most, if not all of them, use FFmpeg quite seriously.
That's the point, they don't pay, and they don't get support. But they still complain when there is a major CVE.
> For comparison, $1M is the total yearly cost of ~3 average engineers at FAANGs.
I wish we got that...
2) When funding is low, big scary exclamation marks all over the place
3) Include a bulleted list of doomsday scenarios showing what could happen to YOU if a bug/vulnerability is found
4) Add a picture of a sad kitten or crying baby for good measure
Now just subscribe all of the non-tech business people at organizations that use FFMPEG, and wait for them to panic. (Make sure that they need to call you to unsubscribe from the newsletter, especially if they work at the New York Times)
Don't do that bit unless you're sure it's not illegal in your (and their) jurisdiction.
Spam being a thing, and there being laws against it.
> By using this software, you agree to subscribe to our monthly newsletter
(I was joking btw, in case that wasn't clear)
Ah, if only one could "just" get a mass of people's attention and send the message
[1]: From what I've seen this ~50% number seems to be pretty close to the mark across virtually all industries and jobs. I.e. it's pretty safe to assume that the total cost to your employer to retain you is around double your take home pay.
[1] https://en.wikipedia.org/wiki/Payroll_tax#/media/File:Effect...
You've put your finger on the core of the issue with FiloSottile's suggestion. The problem is that to sell something to a big corporation, you need to have something tangible you can sell. What you have are enormous pieces of widely used software, being given away for free. Many companies are going to take that and run with it, and forgo a support contract entirely. You may argue that they want support when there's an issue, but the truth is they're happy enough with the status quo and just complaining a lot.
In FiloSottile's model, a corporation needs to use your software for something specific, but also expects to need changes to it or prioritized issue support and approaches you; you send them an invoice with five zeroes on it as a bill for your services and they are heavily incentivized to pay for it.
Unfortunately that's not the reality for 99.9% of open source maintainers, a figure that includes most creators of popular software like VLC. I've personally contributed to a bunch of projects and maintain some of my own, but it's a hobby. As far as I know no corporations are even using any of them. Figuring out some software niche that no one yet has a product it, building it, and waiting for a corporation to swoop in and drop me a six figure yearly check cannot be a career strategy.
Sure, someone else may start a competing project…
If you want it fixed now submit a PR that I can accept. That’s what I do anyway.