On Fri, Nov 22, 2024 at 03:20:44PM +0100, Anton Khirnov wrote: > Quoting Derek Buitenhuis (2024-11-22 13:38:01) > > I do not accept this warning, and I do not agree with your reasoning. > > > > The entire point of that thread was paid work, and cost matters. I worded > > in an entirelty legitimate way. > > > > The fact that all the BS that has happened on this list since and *this* > > is the result is, for lack of a better work, complete bullshit. > > > > The CC is a lame duck. > > +1 > > I naively thought it doesn't get much worse than the previous CC that > might as well have not existed, but you're plumbing new depths here, > what with arbitrary selective enforcement and private warnings. Real > good secret police stuff, congratulations. > > > -------- Forwarded Message -------- > > Subject: Re: [FFmpeg-devel] [RFC] libpostproc splitout > > Date: Thu, 21 Nov 2024 15:18:04 -0500 > > From: Ronald S. Bultje <rsbul...@gmail.com> > > To: Derek Buitenhuis <derek.buitenh...@gmail.com> > > CC: c...@ffmpeg.org > > > > > > > > Hi Derek, > > > > On Thu, Nov 7, 2024 at 11:04 AM Derek Buitenhuis > > <derek.buitenh...@gmail.com <mailto:derek.buitenh...@gmail.com>> wrote: > > > > This work was very easy and not worth even remotely close to 5K euro. > > I had the exact same thought when looking at that thread, and the only > reason I did not send it to ML was my being on vacation. So let me > correct that now: > > Splitting out libpostproc is easy and not worth even remotely close to > 5K euro.
How much do you charge to split out libpostproc ? Note you _have to_ maintain the code afterwards, not just treat it as if split out means deleting it from ffmpeg. It must in the end include a bugtracker, wiki, packages in distributions, documentation, self tests and so on and probably alot more needs would come up also git history must be bisectable, and future changes from ffmpeg buildsystem must be merged also look at libpostproc, this code is not upto todays standards. Iam sure you agree ? To have libpostproc move forward as an independant (split out) and usefull project. Its not just copy and pasting code. This thing needs a new API, it needs a clean internal filter interface Theres no way or sense in copy and pasting this and then "maintaining" it I intended to do all the above and likely more for 15k euro. And i have yet to see someone offer to do this for less. Its easy to say "its worth less", iam still waiting for the one who actually does it for less. again, all the above, for 7k euro, ill pay you from my own money. wheres the person who does that ? (and yes that includes passing review and get into git and again maintaining it for the next few years, maintaining build system, reviewing patches that get submited, fixing security issues, awnsering developer questions, ...) I was considering to add some AI based filters into this after all the above is done. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB If one takes all money from those who grow wealth and gives it to those who do not grow wealth, 10 years later, almost the same people who where wealthy will be wealthy again, the same people who where poor will be poor again.
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
