From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] SWS cleanup / SPI Funding Suggestion Date: Sat, 14 Oct 2023 00:02:34 +0200 Message-ID: <20231013220234.GR3543730@pb2> (raw) In-Reply-To: <CABLWnS8TWsnvyVuRdD37V8ejLZMiFjFNuD1uzoa3RBb=W9FA1Q@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 2372 bytes --] On Fri, Oct 13, 2023 at 04:30:56PM -0400, Vittorio Giovara wrote: > On Fri, Oct 13, 2023 at 3:19 PM Michael Niedermayer <michael@niedermayer.cc> > wrote: > > > Hi everyone > > > > I propose using 15k$ from SPI for funding sws cleanup work. > > this is substantially less than what people belive this needs (see IRC > > logs from yesterday or so) > > So it really is more a small price for a good deed and not proper payment. > > This of course is only available to competent developers. (exact rules or > > how thats determined > > would still need to be decided unless its a clear case) > > Also the exact outcome and goal would need to be discussed by the > > community and whoever > > does the work. > > But some goals would probably be to make sws > > * pleasent to work with > > * similar speed or faster > > * proper multithreading > > * proper full colorspace convertion not ignoring gamma, primaries, ... > > * clean / understandable modular design (maybe everything can be a > > "Filter" inside sws > > that get build into a chain) > > > > Proper payment (50k$ maybe) would be too much in relation to what SPI has > > ATM (150k$) > > > > Above all, this is just my oppinion, the actual SPI funding also would > > need to > > be approved by the community. This can happen after a specific volunteer > > comes forth > > or before, whichever way the community prefers. > > > > Hi Michael, Hi Vittorio [...] > if we absolutely > need no external deps, Yes, you are correct > then write an entirely new library, The path and the end result are 2 different things The end result that this funding is for is a clean libswscale aka a clean "image convertion lib inside FFmpeg". I think the path should be decided by the developer doing the work, if she wants to extend libplacebo and import that, sure ok too with me Only the contents of the C, H and asm files affects the people using the code And i expeted some reused code, so i call it cleanup. Things called "rewrites" also often failed. So its IMHO a sligtly cursed term, but they are just terms, what the rsult is matters thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB I know you won't believe me, but the highest form of Human Excellence is to question oneself and others. -- Socrates [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-10-13 22:02 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-13 19:19 Michael Niedermayer 2023-10-13 20:30 ` Vittorio Giovara 2023-10-13 21:23 ` Lynne 2023-10-13 22:02 ` Michael Niedermayer [this message] 2023-10-13 22:34 ` Niklas Haas 2023-10-13 22:42 ` James Almer 2023-10-13 22:54 ` Niklas Haas 2023-10-13 23:00 ` Vittorio Giovara [not found] ` <8A960BE2-8364-4AF8-A9B5-E0551C19F9DF@cosmin.at> 2023-10-13 23:16 ` Cosmin Stejerean via ffmpeg-devel 2023-10-14 14:19 ` Kieran Kunhya 2023-10-14 17:00 ` Michael Niedermayer 2023-10-14 17:24 ` Niklas Haas 2023-10-15 14:36 ` Michael Niedermayer 2023-10-14 17:41 ` Kieran Kunhya 2023-10-14 19:38 ` Vittorio Giovara 2023-10-14 17:26 ` Anton Khirnov 2023-10-14 15:45 ` Michael Niedermayer 2023-10-14 17:53 ` Stefano Sabatini 2023-10-17 14:36 ` Michael Niedermayer [not found] ` <430D0C5B-53A8-4920-B99A-D8BAD816D715@cosmin.at> 2023-10-17 16:58 ` Cosmin Stejerean via ffmpeg-devel 2023-10-18 21:53 ` Stefano Sabatini 2023-10-17 18:33 ` James Almer 2023-10-17 18:50 ` Rémi Denis-Courmont 2023-10-17 21:57 ` Michael Niedermayer 2023-10-17 22:10 ` Michael Niedermayer 2023-10-18 16:30 ` Rémi Denis-Courmont 2023-10-18 22:12 ` Stefano Sabatini
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20231013220234.GR3543730@pb2 \ --to=michael@niedermayer.cc \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git