From: "Satter, Raphael \(Reuters\) via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org> To: Kieran Kunhya <kieran618@googlemail.com>, FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: "Satter, Raphael \(Reuters\)" <Raphael.Satter@thomsonreuters.com> Subject: Re: [FFmpeg-devel] [EXT] Re: Query from Reuters on XZ, open source, and Microsoft Date: Wed, 3 Apr 2024 19:26:00 +0000 Message-ID: <PH0PR03MB5752CC4227A444518077631FE33D2@PH0PR03MB5752.namprd03.prod.outlook.com> (raw) In-Reply-To: <CABGuwEnJ-q4q56UNbiaqhfMZU-bC3eXZzsq=A_zTcnTf=XxF7w@mail.gmail.com> Dear Kieran & co., Thank you I’ve had a chance to see the talk. It’s a marker of how invisible even critical open source projects can be that I wasn’t aware of FFmpeg’s role in powering the likes of YouTube and Netflix. A few questions I had: * How much did Microsoft end up paying for the one-time fix? * What’s the solution here? Your talk mentioned paying developers, getting an SLA, or hiring them as consultants … but why would companies bother when they can just free ride? I asked the same question to CISA’s Jack Cable when he told me that companies need to “contribute back and help build the sustainable open source ecosystem that we get so much value from.” Sure, they “need” to do it, but who will punish them if they don’t? * Any other thoughts you might have on this episode – or others you think I should speak to – would be greatly appreciated. Raphael From: Kieran Kunhya <kieran618@googlemail.com> Sent: Wednesday, April 3, 2024 12:39 PM To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Satter, Raphael (Reuters) <Raphael.Satter@thomsonreuters.com> Subject: [EXT] Re: [FFmpeg-devel] Query from Reuters on XZ, open source, and Microsoft External Email: Use caution with links and attachments. Hi Raphael, I was the author of the tweet and I gave a short talk about this topic at Demuxed at a video conference last year: https://m.youtube.com/watch?v=OIyOEuQQsCQ&t=930s<https://urldefense.com/v3/__https:/m.youtube.com/watch?v=OIyOEuQQsCQ&t=930s__;!!GFN0sa3rsbfR8OLyAw!fil3G3T7uUxCpJLVmYwgXrszOLckOVB2iMJMDO7QCKMoC7pWR9np5VcDBSAQwsXzhMcbBH9RL7tMr8KurldS9Ga_7Ai-q2U$> That said this is a community project and it would be best to continue the discussion on this mailing list unless agreed otherwise. Regards, Kieran Kunhya On Wed, 3 Apr 2024, 16:52 Satter, Raphael (Reuters) via ffmpeg-devel, <ffmpeg-devel@ffmpeg.org<mailto:ffmpeg-devel@ffmpeg.org>> wrote: Dear FFMPEG community, This is Raphael Satter, a journalist with Reuters. I saw your thread on X about your experience with Microsoft in the context of the XZ story and would love to follow up with a few questions. Is there a good person to talk to? I’m reachable using the details below or on Signal/WhatsApp at +1 202 430 9389. Raphael 💻 raphael.satter@tr.com<mailto:raphael.satter@tr.com> 🌎 raphaelsatter.com<https://urldefense.com/v3/__http:/raphaelsatter.com__;!!GFN0sa3rsbfR8OLyAw!fil3G3T7uUxCpJLVmYwgXrszOLckOVB2iMJMDO7QCKMoC7pWR9np5VcDBSAQwsXzhMcbBH9RL7tMr8KurldS9Ga_d7ggKWg$> 📰 reuters.com/authors/raphael-satter<http://reuters.com/authors/raphael-satter> Thomson Reuters 1333 H Street NW Washington, DC 20005 ☎️ +1 202 843-6302 _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org<mailto:ffmpeg-devel@ffmpeg.org> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel<https://urldefense.com/v3/__https:/ffmpeg.org/mailman/listinfo/ffmpeg-devel__;!!GFN0sa3rsbfR8OLyAw!fil3G3T7uUxCpJLVmYwgXrszOLckOVB2iMJMDO7QCKMoC7pWR9np5VcDBSAQwsXzhMcbBH9RL7tMr8KurldS9Ga_oyXmFKo$> To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org<mailto:ffmpeg-devel-request@ffmpeg.org> with subject "unsubscribe". _______________________________________________ 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-04-03 19:26 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-03 15:51 [FFmpeg-devel] " Satter, Raphael (Reuters) via ffmpeg-devel 2024-04-03 16:38 ` Kieran Kunhya via ffmpeg-devel 2024-04-03 16:42 ` [FFmpeg-devel] [EXT] " Satter, Raphael (Reuters) via ffmpeg-devel 2024-04-03 19:26 ` Satter, Raphael (Reuters) via ffmpeg-devel [this message] 2024-04-03 19:43 ` Kieran Kunhya via ffmpeg-devel 2024-04-08 11:02 ` Tomas Härdin 2024-04-08 14:40 ` Nicolas George 2024-04-08 17:56 ` Paul B Mahol 2024-04-09 19:08 ` Tomas Härdin 2024-04-17 19:05 ` [FFmpeg-devel] Mailinglist conduct (was: [EXT] Re: Query from Reuters on XZ, open source, and Microsoft) Ronald S. Bultje 2024-04-08 18:13 ` [FFmpeg-devel] Query from Reuters on XZ, open source, and Microsoft Romain Beauxis 2024-04-08 21:29 ` Vittorio Giovara 2024-04-09 3:09 ` Rémi Denis-Courmont 2024-04-09 8:36 ` Nicolas George 2024-04-10 9:27 ` Stefano Sabatini 2024-04-10 13:15 ` Gyan Doshi 2024-04-09 19:05 ` Tomas Härdin 2024-04-09 20:57 ` Romain Beauxis 2024-04-09 23:46 ` Paul B Mahol 2024-04-10 1:43 ` Romain Beauxis 2024-04-10 12:40 ` Ronald S. Bultje 2024-04-10 11:38 ` Tomas Härdin 2024-04-11 1:19 ` Michael Niedermayer 2024-04-11 3:59 ` Vittorio Giovara 2024-04-11 7:27 ` Paul B Mahol 2024-04-17 19:24 ` epirat07
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=PH0PR03MB5752CC4227A444518077631FE33D2@PH0PR03MB5752.namprd03.prod.outlook.com \ --to=ffmpeg-devel@ffmpeg.org \ --cc=Raphael.Satter@thomsonreuters.com \ --cc=kieran618@googlemail.com \ /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