[FFmpeg-devel] [RFC] Anual Committee Report

[FFmpeg-devel] [RFC] Anual Committee Report

[Michael Niedermayer]

[-- Attachment #1.1: Type: text/plain, Size: 907 bytes --]

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

thx

PS: no i dont remember how to spell committee, if i got one corrrect that
is unintentional.

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Many things microsoft did are stupid, but not doing something just because
microsoft did it is even more stupid. If everything ms did were stupid they
would be bankrupt already.

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

Re: [FFmpeg-devel] [RFC] Anual Committee Report

[Nicolas George]

[-- Attachment #1.1: Type: text/plain, Size: 191 bytes --]

Michael Niedermayer (12023-09-28):
> I think the 2 commmittteees we have

We do not have two committees, their mandate expired more than a year
ago.

Regards,

-- 
  Nicolas George

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

Re: [FFmpeg-devel] [RFC] Anual Committee Report

[Thilo Borgmann via ffmpeg-devel]

Hi,

> 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 ...

not sure about performance but reports should be done, +1.


> # 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
> 
> thx
> 
> PS: no i dont remember how to spell committee, if i got one corrrect that
> is unintentional.

-Thilo

_______________________________________________
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".

Re: [FFmpeg-devel] [RFC] Anual Committee Report

[Rémi Denis-Courmont]

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".

Re: [FFmpeg-devel] [RFC] Anual Committee Report

[Tomas Härdin]

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".