From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg Development <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg at IBC
Date: Tue, 16 Jul 2024 18:15:52 +0300
Message-ID: <2343646.4mYINpa0Oa@basile.remlab.net> (raw)
In-Reply-To: <768d90bd-9a76-43e0-b22d-eedb1fd3dc8f@mail.de>
Le sunnuntaina 14. heinäkuuta 2024, 10.45.43 EEST Thilo Borgmann via ffmpeg-
devel a écrit :
> Share with us your broken workflows, unfulfilled requirements, ideas for
> enhancements and after show drinks at W8.A23g!
I think that we need to keep in mind who typically attends IBC.
1) The majority are not sufficiently technically versed to know what problem
their employer has with FFmpeg. The message makes it sound like FFmpeg is
broken and not fullfilling requirements, and just sucks. Regardless of whether
we want to talk to those people or not, the message should really be more
positive.
2) Many there do not understand how open-source operates. It sounds like you
are offering to solve their problems for free.
IBC attendees are much more likely to be looking for consultants to hire than
wanting to report bugs.
--
雷米‧德尼-库尔蒙
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:[~2024-07-16 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-14 7:45 Thilo Borgmann via ffmpeg-devel
2024-07-16 15:15 ` Rémi Denis-Courmont [this message]
2024-07-16 15:24 ` Vittorio Giovara
2024-07-16 16:57 ` Michael Niedermayer
2024-07-16 18:19 ` Rémi Denis-Courmont
2024-07-16 18:47 ` Vittorio Giovara
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=2343646.4mYINpa0Oa@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