From: "Rémi Denis-Courmont" <remi@remlab.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] SWS cleanup / SPI Funding Suggestion Date: Tue, 17 Oct 2023 21:50:41 +0300 Message-ID: <2399184.TVbLC8jhAB@basile.remlab.net> (raw) In-Reply-To: <20231013191934.GQ3543730@pb2> Le perjantaina 13. lokakuuta 2023, 22.19.34 EEST Michael Niedermayer a écrit : > 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) It sounds very nice. But it also sounds very fuzzy and subjective. Unless you can put this in more objective terms such as would be expected of a statement of work, all the while not compromising the intent of the sponsorship, I would advise against using foundation funds. But first... > Proper payment (50k$ maybe) would be too much in relation to what SPI has > ATM (150k$) In my opinion, not "paying properly" is morally wrong, and sets a very bad example that it is acceptable not to pay developers properly. Also it is really not that much money. I suppose that the yearly revenues are even only a fraction of that balance. If so, I would argue that it is not financially reasonable, doubly so when the overall world economy is in a rather iffy situation. If it were up to me, I would keep that money for infrastructure and other fees, purposeful hardware donations and travel. Lastly using foundation funds to sponsor specific project may open a pandora box. What happens if more than one credible developer wants to take up the project? Or if other developers demand that their other reasonable clean-up projects be funded too? If the revenue and balance were much higher, you could hire all of them. But you can't, and then the simplest and safest way to avoid moral hazards is to hire nobody. N.B.: I am not part of the GA, and I have neither the expertise and credibility nor the time and motivation to take up this project, so that's just my free advice. -- Rémi Denis-Courmont http://www.remlab.net/ _______________________________________________ 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-17 18:50 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 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 [this message] 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=2399184.TVbLC8jhAB@basile.remlab.net \ --to=remi@remlab.net \ --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