Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marth64 <marth64@proxyid.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel]  FFmpeg Community Committee – Updates & Next Steps
Date: Thu, 27 Feb 2025 17:00:30 -0600
Message-ID: <CAAhd_PVhT12oJ6o4=Gxs3ye_A2jURVKbxOrmzoQPcGAdGC-RTw@mail.gmail.com> (raw)
In-Reply-To: <20250227181808.GG4991@pb2>

Hi Michael,

Thanks for the reply & thoughts.

To clarify on "internal panel" and "structured issue resolution", this
is with regards to unresolved complaints sent to CC, such as publicly
or privately reported interpersonal/CoC issues.
Some high ticket items directed to the CC from last year remain
unaddressed and we were elected to be accountable for this, so we have
to move forward in some way.
There are tough problem statements to unpack and it is not always simple.

The point I was trying to convey is we are going to approach, review,
and push to closure on reported issues in a methodical fashion.
We have set up a cadence to meet on items that our attention was
called to. Kind of like a standup meeting on the tasks we are assigned
to.
So the "panel" in that regard, is a check-in amongst ourselves. If we
feel other people or opinions need to be involved we will navigate
that bridge as we get there.

If CC is engaged for a task then we have to look into it and figure
out a plan or execution.
IIRC one main concern of the CC last year was there was limited
movement on problem solving.

"laying a strong foundation for the future" is with regards to us
putting a process in place and being a visibly effective CC.
The phrase is ambitious but focused on issues that are on our docket.
It's not a blanket statement for a revolution.

For example, laying a parallel hypothetical, this is as if the TC met
once a week to discuss "what's on our agenda this week? what actions
do we need to take? how do we clear roadblocks? what is our north star
for the future?"

Does this help?

Thank you,
Marth64
_______________________________________________
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-27 23:01 UTC|newest]

Thread overview: 15+ 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 [this message]
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-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='CAAhd_PVhT12oJ6o4=Gxs3ye_A2jURVKbxOrmzoQPcGAdGC-RTw@mail.gmail.com' \
    --to=marth64@proxyid.net \
    --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