From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Kieran Kunhya <kieran618@googlemail.com> Subject: Re: [FFmpeg-devel] FFmpeg Community Committee – Updates & Next Steps Date: Tue, 4 Mar 2025 08:13:11 -0600 Message-ID: <CABGuwEmr_Kahkwo-xWafwvW+xmg7nAeVAxO8QeGCHUK7Uvsdkw@mail.gmail.com> (raw) In-Reply-To: <20250304023539.GK4991@pb2> On Mon, 3 Mar 2025, 20:35 Michael Niedermayer, <michael@niedermayer.cc> wrote: > 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. > Hi Michael, Was all the STF discussion around the first application done in public? Kieran > _______________________________________________ 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 14:13 UTC|newest] Thread overview: 19+ 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 2025-03-04 14:13 ` Kieran Kunhya via ffmpeg-devel [this message] 2025-03-04 17:17 ` Michael Niedermayer 2025-03-04 19:01 ` Kieran Kunhya via ffmpeg-devel 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=CABGuwEmr_Kahkwo-xWafwvW+xmg7nAeVAxO8QeGCHUK7Uvsdkw@mail.gmail.com \ --to=ffmpeg-devel@ffmpeg.org \ --cc=kieran618@googlemail.com \ /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