Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg table at NAB
Date: Sun, 21 Apr 2024 16:47:05 +0800
Message-ID: <885A9246-BC02-454F-A1E2-98CF474F74EC@remlab.net> (raw)
In-Reply-To: <CAHGibzEMGFLqzid6sXi6n+MBmJe5f5D_sYOyQh8Fj+L7Uzxo7w@mail.gmail.com>

Hi,

I have been dragged privately into this issue so for the sake of transparency, I will just sum up my side here.


Le 17 avril 2024 07:21:18 GMT+08:00, Devin Heitmueller <devin.heitmueller@ltnglobal.com> a écrit :
>Hello all,
>
>I wasn't looking to start trouble, but I didn't see any discussion of
>this on the mailing list so wanted to bring it to the developer
>community's attention.
>
>I attended the NAB conference and went by the "ffmpeg" booth on
>Sunday.  What I found was a single table with the official ffmpeg
>banner hanging right next to a banner for the GPAC project, and two
>salespeople from GPAC handing out marketing literature and trying to
>educate me on why I should use their framework for my next project.

Thilo did announce that some unidentified party would be payind for FFmpeg to hold a booth (this should be visible in the archives). Kieran raised legitimate if not concerning questions based on his prior experience at NAB. Thilo did not answer, which is inexcusable, especially considering that there were several times that the questions were reiterated.

Thilo privately called Kieran a "troll" as the lame pretext for not answering the question (I can copy the CC privately if proof of this is needed).

In light of this, it seemed obvious that the FFmpeg booth would be a disaster, pretty much how Kieran had predicted.

So there you have it. On the bright side, FFmpeg was not footing the bill.

I think everybody can make their own conclusions without me speculating or opiniating further, so I will leave it at that.

>I'm not saying that GPAC shouldn't be able to have a table at the
>conference, but it feels pretty misleading to have an "ffmpeg" booth
>listed in the conference materials, with a table prominently
>displaying the ffmpeg logo, with zero people from ffmpeg and people
>pushing users to use an alternative framework that some might actually
>considered to be a competitor to ffmpeg.

Agreed. Thanks for your testimony.
_______________________________________________
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".

  parent reply	other threads:[~2024-04-21  8:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16 23:21 Devin Heitmueller
2024-04-17  8:03 ` Paul B Mahol
2024-04-17 13:49 ` Derek Buitenhuis
2024-04-17 13:54   ` James Almer
2024-04-17 13:55     ` Derek Buitenhuis
2024-04-17 19:00   ` [FFmpeg-devel] Mailinglist conduct (was: FFmpeg table at NAB) Ronald S. Bultje
2024-04-17 19:30     ` [FFmpeg-devel] Mailinglist conduct Derek Buitenhuis
2024-04-17 19:33       ` James Almer
2024-04-17 19:43         ` Derek Buitenhuis
2024-04-17 20:17           ` James Almer
2024-04-17 22:13 ` [FFmpeg-devel] FFmpeg table at NAB Thilo Borgmann via ffmpeg-devel
2024-04-21  8:47 ` Rémi Denis-Courmont [this message]
2024-04-21 20:25   ` Thilo Borgmann via ffmpeg-devel
2024-04-22  2:02     ` Rémi Denis-Courmont
2024-04-24  6:07       ` Thilo Borgmann via ffmpeg-devel
2024-04-24  6:36         ` [FFmpeg-devel] Cease and desist 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=885A9246-BC02-454F-A1E2-98CF474F74EC@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