From: Stefano Sabatini <stefasab@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: "Jonatas L. Nogueira" <jesusalva@spi-inc.org> Subject: Re: [FFmpeg-devel] Sovereign Tech Fund Date: Thu, 1 Feb 2024 00:15:03 +0100 Message-ID: <ZbrUd3pNyFpMvTPa@mariano> (raw) In-Reply-To: <25474700.8Xr1rsAvgU@basile.remlab.net> On date Wednesday 2024-01-31 18:10:57 +0200, Rémi Denis-Courmont wrote: > Hi, [...] > Sarcasm aside, I take that to mean that SPI has been involved with those > discussions for months in a private and closed process. Michael asserted that > an open inclusive process is better than the usual closed approach whence the > funding goes through a company. > > It looks to me that those SPI discussions were just as opaque and closed, and > all the talk of openess is just pretense. It does not help that Michael, and > now you too, misrepresent any challenge to SPI proposed *process* as an > attempt to reject the idea of STF sponsorship, under the convenient pretext > that there is not enough time. > > This is further aggravated by the context that Michael brought forward the > idea of funding developers through SPI 3 months ago (in actual Earth units). > From your statement, I have to infer that Thilo, Michael and SPI already knew > of the STF plan and concealed that key piece of contextual information back > then. > José already provided and excellent summary from his side. On my side I can say I was involved in the discussion, and that this was mostly about the feasibility and the groundwork of approaching STF and later SPI. So in my opinion there was no need to involve the community at that early stage, especially given that until the past week there was still no evidence that STF was providing a grant (and BTW, still this needs to be substantiated with a SOW and then it will have to be reviewed and approved on the STF side). Also SPI was involved at a later stage, after the investigation about using the donors fund for active development (which also involves the handling of SOW from SPI to the individual contributor). The main result of that investigation was discussed in the open and can be found here: https://ffmpeg.org/pipermail/ffmpeg-devel/2023-October/315702.html If I undestand it correctly, it was never committed because there was a disagreement about where to put it (ffmpeg or ffmpeg-web) and about the general intent, then at some point the discussion died off before a conclusion was really reached. Note that the focus in that case was to make good use of the donations fund (keeping it in the account is not a good use for it). > In hindsight, it feels hypocritical to me that they were arguing for the SPI > path, and against the corporate path, on the basis of openess already then, to > be honest. > > I can only agree with Anton that this looks like an attempt to strongarm the > community. This is ostensibly being to ignore all the objections that were > already brought in October and are being brought again now, with the > complicity of SPI. I can't say that this looks well on SPI, but that's just my > personal opinion. SPI was involved at a later stage to act as fiscal sponsor for STF. Just to reiterate, SPI involvement was requested, and was not actively seeked by SPI itself. I cannot read any attempt to strongarm the community, nor I see why this should challenge the corporate path (which has a different focus and has its own merits). > With all that said, I don't think anybody will attempt to prevent this from > happening (if they even can?). But that will take place without the consent of > the GA, without any legitimacy on the claims of openess and inclusiveness, and > obviously without any form of preclearance from the technical appropriateness > of the resulting code contributions. It's unfortunate there is a tight deadline - one option would be to try to delay the deadline and ask General Assembly for a vote before the application is sent - we might probably want both things to avoid the feeling that this is done against the "community" and create a tense environment, but any of this might probably result in voiding the opportunity. Also, it should be assumed that this proposal was done in good faith, in view of the sustainability discussions done in the past months. _______________________________________________ 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:[~2024-01-31 23:15 UTC|newest] Thread overview: 123+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-28 3:25 Michael Niedermayer 2024-01-28 15:54 ` Kieran Kunhya 2024-01-28 17:12 ` Michael Niedermayer 2024-01-28 18:59 ` Kieran Kunhya 2024-01-28 19:20 ` Jonatas L. Nogueira via ffmpeg-devel 2024-01-28 19:30 ` Jonatas L. Nogueira via ffmpeg-devel 2024-01-28 19:34 ` Kieran Kunhya 2024-01-28 21:18 ` Jonatas L. Nogueira via ffmpeg-devel 2024-01-28 21:33 ` Kieran Kunhya 2024-01-29 21:27 ` Anton Khirnov 2024-01-28 20:06 ` Michael Niedermayer 2024-01-28 20:32 ` Kieran Kunhya 2024-01-28 20:34 ` Kieran Kunhya 2024-01-28 20:37 ` Kieran Kunhya 2024-01-28 20:42 ` Kieran Kunhya 2024-01-28 21:47 ` Michael Niedermayer 2024-01-29 18:31 ` Kieran Kunhya 2024-01-29 18:46 ` Jonatas L. Nogueira via ffmpeg-devel 2024-01-29 18:54 ` Michael Niedermayer 2024-01-29 19:02 ` Kieran Kunhya 2024-01-29 20:04 ` Michael Niedermayer 2024-01-29 22:54 ` Kieran Kunhya 2024-01-30 9:20 ` Tomas Härdin 2024-01-28 21:34 ` Michael Niedermayer 2024-01-28 21:39 ` Kieran Kunhya 2024-01-29 2:26 ` Jonatas L. Nogueira via ffmpeg-devel 2024-01-29 14:52 ` Derek Buitenhuis 2024-01-29 15:02 ` Kieran Kunhya 2024-01-29 15:05 ` Derek Buitenhuis 2024-01-29 16:40 ` Jonatas L. Nogueira via ffmpeg-devel 2024-01-29 17:05 ` Kieran Kunhya 2024-01-29 17:27 ` Michael Niedermayer 2024-01-29 17:36 ` Kieran Kunhya 2024-01-29 17:43 ` Rémi Denis-Courmont 2024-01-29 18:11 ` Michael Niedermayer 2024-01-29 21:01 ` Rémi Denis-Courmont 2024-01-29 22:43 ` Michael Niedermayer 2024-01-30 6:30 ` Rémi Denis-Courmont 2024-01-30 17:15 ` Michael Niedermayer 2024-01-30 18:00 ` Michael Niedermayer [not found] ` <A40E9FF7-EC74-458A-A195-26EE8062992E@cosmin.at> 2024-01-29 22:23 ` Cosmin Stejerean via ffmpeg-devel 2024-01-29 22:31 ` Kieran Kunhya 2024-01-30 10:12 ` Nicolas George 2024-01-30 10:19 ` Kieran Kunhya 2024-01-30 10:31 ` Nicolas George 2024-01-30 10:44 ` Kieran Kunhya 2024-01-30 10:46 ` Nicolas George 2024-01-30 10:53 ` Kieran Kunhya 2024-01-30 11:47 ` Anton Khirnov 2024-01-28 19:17 ` Rémi Denis-Courmont 2024-01-28 20:33 ` Michael Niedermayer 2024-01-29 14:38 ` Derek Buitenhuis 2024-01-29 18:25 ` Michael Niedermayer 2024-01-29 18:37 ` Derek Buitenhuis 2024-01-29 19:21 ` Michael Niedermayer 2024-01-29 20:09 ` Vittorio Giovara 2024-01-29 20:15 ` Derek Buitenhuis 2024-01-30 6:48 ` Rémi Denis-Courmont 2024-01-29 20:19 ` Anton Khirnov 2024-01-29 20:20 ` Derek Buitenhuis 2024-01-29 20:36 ` Vittorio Giovara 2024-01-29 21:27 ` Michael Niedermayer 2024-01-31 11:19 ` Anton Khirnov 2024-01-29 20:41 ` Diederick C. Niehorster 2024-01-29 21:19 ` Anton Khirnov 2024-01-29 21:11 ` Anton Khirnov 2024-01-29 23:41 ` Jonatas L. Nogueira via ffmpeg-devel 2024-01-29 23:53 ` Stefano Sabatini 2024-01-31 12:30 ` Anton Khirnov 2024-01-31 21:26 ` Stefano Sabatini 2024-01-30 0:15 ` Michael Niedermayer 2024-01-30 0:19 ` Michael Niedermayer 2024-01-31 12:59 ` Anton Khirnov 2024-01-31 14:10 ` Jonatas L. Nogueira via ffmpeg-devel 2024-01-31 15:17 ` Anton Khirnov 2024-01-31 15:17 ` Kieran Kunhya 2024-01-31 16:00 ` Jonatas L. Nogueira via ffmpeg-devel 2024-01-31 16:03 ` Jonatas L. Nogueira via ffmpeg-devel 2024-01-31 16:10 ` Rémi Denis-Courmont 2024-01-31 17:04 ` Jonatas L. Nogueira via ffmpeg-devel 2024-01-31 18:03 ` Michael Niedermayer 2024-01-31 18:22 ` Kieran Kunhya 2024-01-31 18:40 ` Jonatas L. Nogueira via ffmpeg-devel 2024-01-31 18:48 ` Kieran Kunhya 2024-01-31 19:07 ` Michael Niedermayer [not found] ` <A7F30D96-F8DB-45EA-9CDB-3545E3ECE0C9@cosmin.at> 2024-01-31 19:16 ` Cosmin Stejerean via ffmpeg-devel 2024-01-31 20:19 ` Kieran Kunhya 2024-01-31 21:43 ` Michael Niedermayer 2024-01-31 21:54 ` Kieran Kunhya 2024-01-31 22:40 ` Michael Niedermayer 2024-01-31 22:45 ` Kieran Kunhya 2024-02-02 13:52 ` Michael Niedermayer 2024-02-02 13:58 ` Kieran Kunhya 2024-01-31 19:20 ` Jonatas L. Nogueira via ffmpeg-devel 2024-01-31 17:58 ` Michael Niedermayer 2024-01-31 23:15 ` Stefano Sabatini [this message] 2024-02-01 0:16 ` Stefano Sabatini 2024-02-06 0:00 ` Jonatas L. Nogueira via ffmpeg-devel 2024-01-30 1:48 ` Michael Niedermayer 2024-01-30 9:32 ` Vittorio Giovara 2024-01-30 10:07 ` Nicolas George 2024-01-30 10:13 ` Vittorio Giovara 2024-01-30 10:15 ` Nicolas George 2024-01-30 10:56 ` Vittorio Giovara 2024-01-31 1:07 ` Michael Niedermayer 2024-01-31 21:44 ` Derek Buitenhuis 2024-01-31 21:55 ` Kieran Kunhya 2024-01-31 23:07 ` Michael Niedermayer 2024-02-01 17:59 ` Anton Khirnov 2024-02-01 18:14 ` Rémi Denis-Courmont 2024-02-01 22:55 ` Michael Niedermayer 2024-02-05 10:21 ` Michael Niedermayer 2024-02-05 11:53 ` Kieran Kunhya 2024-02-05 13:10 ` Zhao Zhili 2024-02-01 19:22 ` Derek Buitenhuis 2024-02-04 9:49 ` Rémi Denis-Courmont 2024-02-04 10:02 ` J. Dekker 2024-02-04 10:09 ` Paul B Mahol 2024-02-04 13:41 ` Michael Niedermayer 2024-02-04 14:38 ` Rémi Denis-Courmont 2024-02-04 19:28 ` Michael Niedermayer 2024-02-04 21:21 ` Rémi Denis-Courmont 2024-04-12 23:43 ` Thilo Borgmann via ffmpeg-devel
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=ZbrUd3pNyFpMvTPa@mariano \ --to=stefasab@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=jesusalva@spi-inc.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