From: Vittorio Giovara <vittorio.giovara@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] VDD 2023, FFmpeg meeting notes, (23-11-2023, 4pm, Dublin)
Date: Tue, 3 Oct 2023 15:13:29 -0400
Message-ID: <CABLWnS-Rp8POW3ctyGsgbmG0CSqZaLpiLCUM2Qc+Gi7eNzxS2g@mail.gmail.com> (raw)
In-Reply-To: <ZRxicQzx6bmqyIi2@phare.normalesup.org>
On Tue, Oct 3, 2023 at 2:50 PM Nicolas George <george@nsup.org> wrote:
> Vittorio Giovara (12023-09-27):
> > This is basically saying that you don't trust the community to make the
> > best decisions for itself, or that the community is not mature enough to
> > stand on its own to support the project.
>
> You are twisting the words to make it sound bad, but it is roughly what
> I am saying, and I suspect also what Michael is saying.
>
YOU LITERALLY DO THIS TO EVERYONE WHO RESPONDS TO YOU
You do not intend to win an argument with reason, you mean to tire the
opposing side by tirelessly draining the energy of the counterparty with
essay long replies,
In other words, you're filibustering any reasonable change and improvement
in this community, it's a net negative help!
I am not willing to play your game, and I don't think this community should
either! You claim democracy is a bad model for ffmpeg stewardship, but it's
the only thing that is keeping certain members in the community, and
letting this kind of abuse happen at every discussion. Just please be
better and just stop sending overly long emails with skewed rehashing of
the past or with wrong interpretations of the concept of community,
democracy, and software maintenance.
--
Vittorio
_______________________________________________
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-10-03 19:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 8:37 Kyle Swanson
2023-09-24 9:21 ` Matthias Dressel
2023-09-24 10:09 ` Michael Niedermayer
2023-09-24 10:13 ` Jean-Baptiste Kempf
2023-09-24 22:14 ` Derek Buitenhuis
2023-09-24 15:31 ` Ronald S. Bultje
2023-09-24 17:12 ` Nicolas George
2023-09-27 18:03 ` Michael Niedermayer
2023-10-04 14:51 ` Anton Khirnov
2023-09-24 12:36 ` Marton Balint
2023-09-24 13:46 ` Michael Niedermayer
2023-09-24 15:10 ` Ronald S. Bultje
2023-09-24 16:45 ` Michael Niedermayer
[not found] ` <119D9DAB-2F0B-427B-A7D1-063C0AF7C3BD@cosmin.at>
2023-09-25 13:16 ` Cosmin Stejerean via ffmpeg-devel
2023-09-26 13:21 ` Ronald S. Bultje
2023-09-27 10:00 ` Michael Niedermayer
2023-09-27 13:29 ` Vittorio Giovara
2023-10-03 18:50 ` Nicolas George
2023-10-03 19:13 ` Vittorio Giovara [this message]
2023-10-03 19:29 ` Kieran Kunhya via ffmpeg-devel
2023-10-04 14:23 ` Michael Niedermayer
2023-10-04 15:06 ` Anton Khirnov
2023-10-05 12:55 ` Nicolas George
2023-10-05 17:32 ` Vittorio Giovara
2023-10-05 18:33 ` Michael Niedermayer
2023-10-05 19:45 ` Rémi Denis-Courmont
2023-10-05 19:54 ` Nicolas George
2023-10-05 19:00 ` Nicolas George
2023-10-04 15:11 ` Rémi Denis-Courmont
2023-10-03 19:29 ` Rémi Denis-Courmont
2023-10-03 19:36 ` Leo Izen
2023-09-26 19:26 ` Anton Khirnov
2023-09-26 18:44 ` Anton Khirnov
2023-09-27 13:15 ` Tomas Härdin
2023-10-02 9:55 ` Nicolas George
2023-10-03 18:41 ` Nicolas George
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=CABLWnS-Rp8POW3ctyGsgbmG0CSqZaLpiLCUM2Qc+Gi7eNzxS2g@mail.gmail.com \
--to=vittorio.giovara@gmail.com \
--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