From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg Community Committee – Updates & Next Steps
Date: Tue, 4 Mar 2025 03:35:39 +0100
Message-ID: <20250304023539.GK4991@pb2> (raw)
In-Reply-To: <8c1d1b3f-8a76-42c2-9a18-9cc0cef5253d@betaapp.fastmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1214 bytes --]
Hi jb
On Thu, Feb 27, 2025 at 12:11:39AM +0100, Jean-Baptiste Kempf wrote:
> On Wed, 26 Feb 2025, at 02:51, Michael Niedermayer wrote:
> > 1. I agree we need discussions, transparency and maybe IRC or some other
> > audio/video form of commuication can be tried. Such discussion should be
> > public and open. And they must include admins and main authors.
>
> Great, the mailing list is here for that. It is public and open.
communication is important.
If all project related communication is on the ML, then the ML alone
would be ok. But if significant discussions about the project happens
elsewhere, like in a meeting or in a cafe or pub after the meeting.
Then that should be accessable for everyone remotely. And especially
for the main authors and active developers.
This is not just about technical things. Its about knowing what
people care about, what they want changed, what they agree with.
If half the team doesnt know what the other half wants, thats
a seed for a conflict that could be avoided.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Observe your enemies, for they first find out your faults. -- Antisthenes
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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:[~2025-03-04 2:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 23:04 Marth64
2025-02-26 1:51 ` Michael Niedermayer
2025-02-26 14:22 ` Vittorio Giovara
2025-02-26 22:33 ` Kieran Kunhya via ffmpeg-devel
2025-02-26 23:11 ` Jean-Baptiste Kempf
2025-02-27 18:18 ` Michael Niedermayer
2025-02-27 22:41 ` Vittorio Giovara
2025-02-28 7:13 ` compn
2025-02-28 13:48 ` Vittorio Giovara
2025-02-27 23:00 ` Marth64
2025-02-28 19:27 ` Michael Niedermayer
2025-02-28 20:35 ` Vittorio Giovara
2025-02-28 19:29 ` Michael Niedermayer
2025-03-02 10:16 ` Rémi Denis-Courmont
2025-03-04 2:35 ` Michael Niedermayer [this message]
2025-02-26 23:51 ` James Almer
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=20250304023539.GK4991@pb2 \
--to=michael@niedermayer.cc \
--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