From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Kieran Kunhya <kieran618@googlemail.com> Subject: Re: [FFmpeg-devel] FFmpeg at NAB 2024 Date: Sun, 19 Nov 2023 14:26:22 +0000 Message-ID: <CABGuwEnJ-rhMRsxkoCfjWBdruo8+zH6337vCGr-YEyQigoeDMw@mail.gmail.com> (raw) In-Reply-To: <1321993a-4601-4a7c-b230-f77f395219fe@gmail.com> On Sun, 19 Nov 2023, 14:05 Derek Buitenhuis, <derek.buitenhuis@gmail.com> wrote: > Hi, > > Followup question... > > On 11/1/2023 9:25 PM, Derek Buitenhuis wrote: > > This is certainly interesting considering we just had a giant thread > about not using > > or using SPI, with multiple people accused of having corporate interests. > > I noticed FFmpeg is on the NAB floor plan. > > This implies FFmpeg has signed a contract with NAB, as to my knowledge, > you are > not on the floor plan without doing that. > > There is one slight problem here... FFmpeg does not have a legal entity in > which > such a contract could have been signed. > > So who signed? The "anonymous" corproate entity, on behalf of FFmpeg, with > out > our consent? > > Pardon my French, but this is sketchy as all fuck. > In addition, the remaining costs of the booth, which in my experience total around twice as much as the floor space itself need to be paid by this corporate contributor. I would not find it acceptable for SPI to pay these costs. I do not feel donors would want their money spent on a corporate show in Las Vegas. Also no plan has been provided about who will actually be present on the booth. Ragards, Kieran Kunhya > _______________________________________________ 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-11-19 14:26 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-01 20:37 Thilo Borgmann via ffmpeg-devel 2023-11-01 21:25 ` Derek Buitenhuis 2023-11-19 14:05 ` Derek Buitenhuis 2023-11-19 14:19 ` Derek Buitenhuis 2023-11-19 14:20 ` Derek Buitenhuis 2023-11-19 14:26 ` Kieran Kunhya via ffmpeg-devel [this message] 2023-11-19 21:46 ` Michael Niedermayer 2023-11-19 23:49 ` Kieran Kunhya via ffmpeg-devel 2024-03-31 11:48 ` Derek Buitenhuis 2023-11-01 21:25 ` Kieran Kunhya 2023-11-02 7:58 ` Rémi Denis-Courmont
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=CABGuwEnJ-rhMRsxkoCfjWBdruo8+zH6337vCGr-YEyQigoeDMw@mail.gmail.com \ --to=ffmpeg-devel@ffmpeg.org \ --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