From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Anual Committee Report
Date: Thu, 28 Sep 2023 20:46:36 +0300
Message-ID: <23887682.ouqheUzb2q@basile.remlab.net> (raw)
In-Reply-To: <20230928141918.GX3543730@pb2>
Le torstaina 28. syyskuuta 2023, 17.19.18 EEST Michael Niedermayer a écrit :
> Hi all
>
> I think the 2 commmittteees we have should produce an anual report
> so that the developers who vote for members know the perfomance and
> what the last comite did
> like # of cases, # of times people where contacted, % where committi
> intervention produced a noticable improvment ...
The commitees should post the result of their deliberations. This seems
evident for the TC. But the CC should also do it to avoid seeming like they
are not acting, that the CoC is only for show. And based on negative
experience in other projects, I would also emphasise that the CC also needs to
avoid making public statements about some cases or people and not others as
well.
That being said, I don't think annual reports are necessary or even useful on
top of per-case summaries. The number of cases _should_ be low enough that
year-on-year statistics should not be very meaningful. Also that seems like
useless paperwork added on top of what is already free and not particularly
fun community service.
--
Rémi Denis-Courmont
http://www.remlab.net/
_______________________________________________
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-09-28 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 14:19 Michael Niedermayer
2023-09-28 15:23 ` Nicolas George
2023-09-28 17:18 ` Thilo Borgmann via ffmpeg-devel
2023-09-28 17:46 ` Rémi Denis-Courmont [this message]
2023-09-28 20:36 ` Tomas Härdin
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=23887682.ouqheUzb2q@basile.remlab.net \
--to=remi@remlab.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