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: Thu, 5 Oct 2023 13:32:11 -0400
Message-ID: <CABLWnS8JNH-sYnrFibNLEPAt18L_bcbRNFeiLv573rn_hbBztQ@mail.gmail.com> (raw)
In-Reply-To: <ZR6yNRA6KngPjFQF@phare.normalesup.org>
On Thu, Oct 5, 2023 at 8:55 AM Nicolas George <george@nsup.org> wrote:
> Anton Khirnov (12023-10-04):
> > It is IMO perfectly reasonable to wonder why does someone who does not
> > agree with the basic rules participate in the project.
>
> Or you could have given the issue just two more seconds of thought and
> realized that FFmpeg is a software project rather than a Nomic game, and
> therefore where the code goes matters more than how it is decided.
Code never matters more than people. It's people who make the community and
it's the community who writes the code or who decides what belongs to the
project -- never a single individual.
There is a lot of content on the web that exemplifies that in professional
environments:
-
https://hackernoon.com/thoughts-on-software-development-heroes-5ec656c2e31a
How To Prevent Coding "Heroes" From Destroying The Team
-
https://leaddev.com/culture-engagement-motivation/eliminating-hero-culture-software-engineering-teams
Eliminating hero culture in software engineering teams
-
https://medium.com/@LuiscaGuerrero/the-myth-of-the-hero-developer-70870e76c00b
The myth of the Hero developer
I am as puzzled as you are why we let this kind of abuse happen in this
community, so claiming a CoC violation for a legitimate question seems a
bit ridiculous in my opinion.
Just my 2 cents
--
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-05 17:32 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
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 [this message]
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=CABLWnS8JNH-sYnrFibNLEPAt18L_bcbRNFeiLv573rn_hbBztQ@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