Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel]  FFmpeg Community Committee – Updates & Next Steps
Date: Wed, 26 Feb 2025 20:51:49 -0300
Message-ID: <09d9dd01-ac00-482c-9391-1f4b6233148e@gmail.com> (raw)
In-Reply-To: <20250226015112.GC4991@pb2>


[-- Attachment #1.1.1: Type: text/plain, Size: 2989 bytes --]

On 2/25/2025 10:51 PM, Michael Niedermayer wrote:
> Hi Marth64
> 
> On Tue, Feb 25, 2025 at 05:04:00PM -0600, Marth64 wrote:
>> Dear FFmpeg Community,
>>
>> We’d like to share an update on the work of the Community Committee
>> (CC). Starting this week, we will hold a weekly internal panel to
>> discuss community matters and ensure more structured issue resolution.
>>
>> One of our key goals is to address some of the lingering discussions
>> from 2024 while laying a strong foundation for the future. We
>> recognize that progress will be gradual, but we are committed to
>> working as a team and presenting unified messaging to improve
>> communication and transparency. We expect to deliver communications
>> soon on some issues.
>>
>> We look forward to continuing to serve the FFmpeg community and
>> fostering a collaborative and productive environment. Thank you for
>> your ongoing support and engagement.
>>
>> On behalf of the CC,
> 
> There are 3+ parts here
> 
> 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.
> 
> 2. The CC is overstepping its authority.

How? What part of the above makes you think that? He only stated they 
are now discussing and going through the 2024 stuff.

> 
> 3. There is a huge growing backlog of increasing development issues

Yes, he said as much.

>     id like to work on without having to fight and argue over governance
>     Id like to backport security fixes, make new releases.
> 
> About "internal panel", There should not be a "internal panel" dominated
> by videolan developers discussing FFmpeg. If there is such a panel, it
> should be the main authors, the people who did spend a significant time
> of their life working on FFmpeg. (and you should be included as you seem
> good at this, and i should be in it because iam one of the main authors
> amongth other things)

If you wanted to be part of the CC and its deliberations, why didn't you 
volunteer for it during last vote? You were in the previous CC, and you 
would have surely been among the five voted if so.

For what is worth, you, even if not part of the CC but as the one that 
made several accusations (and the target of another bunch), could 
request to be part of the deliberations regarding those specific issues.
Is this codified anywhere? If not, it could be drafted and a vote be 
held for such addition.

> 
> Thank you
> 
> PS: this is just my initial thought/reply and i may have a better idea
> after sleeping over this
> 
> [...]
> 
> 
> _______________________________________________
> 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".


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 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".

      parent reply	other threads:[~2025-02-26 23:52 UTC|newest]

Thread overview: 6+ 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-26 23:51   ` James Almer [this message]

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=09d9dd01-ac00-482c-9391-1f4b6233148e@gmail.com \
    --to=jamrial@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