From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Anual Committee Report
Date: Thu, 28 Sep 2023 22:36:40 +0200
Message-ID: <dd5804fc6ba92cceadbe1542b0dec9c5acc01cfd.camel@haerdin.se> (raw)
In-Reply-To: <20230928141918.GX3543730@pb2>
tor 2023-09-28 klockan 16:19 +0200 skrev Michael Niedermayer:
> 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 ...
>
> # of cases where both parties where happy with the outcome, # of
> cases
> where one party only was happy, # of cases where neither party was
> happy
>
> Of course in some years there may be nothing at all, which then would
> be a rather simple report
Sounds like a step in the right direction. As a Swede we have a strong
voluntary association culture (föreningskultur) where most of this
stuff is routine. You hold regular meetings, elect a board, define
membership criteria, reasons for expulsion etc.
/Tomas
_______________________________________________
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".
prev parent reply other threads:[~2023-09-28 20:36 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
2023-09-28 20:36 ` Tomas Härdin [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=dd5804fc6ba92cceadbe1542b0dec9c5acc01cfd.camel@haerdin.se \
--to=git@haerdin.se \
--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