Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Leo Izen <leo.izen@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] Indefinite ban request [RFC] Was: Re: [FFmpeg-trac] #10882(undetermined:new): swscale wastefully scales luma during yuv420p -> yuv422p
Date: Mon, 11 Mar 2024 17:40:25 -0400
Message-ID: <f745c69c-dc3f-4227-a0cc-d454a669cedb@gmail.com> (raw)
In-Reply-To: <20240310012542.GA6401@pb2>


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



On 3/9/24 20:25, Michael Niedermayer wrote:
> Hi everyone
> 
> Some members of the CC want to indefinitely ban Balling
> from trac. And as our doc/community.texi says:
> "Indefinite bans from the community must be confirmed by the General Assembly, in a majority vote."
> 
> Thus some CC member wishes to involve the public here
> (really theres no other option, the GA cannot discuss/vote on what it doesnt know)
> 
> Also people have asked for more transparency and i strongly agree with transparency.
> 
> As reference, and to make it possible for the community to discuss
> this easily without too much google searching. Ive attached the
> list of all changes in trac done by Balling.
> 
> I do not and never did support permanently banning contributors.
> 
> In summary: since 2019
>      842 comment0' changed
>      389 comment1' changed
>      176 comment2' changed
>       87 comment3' changed
>       49 comment4' changed
>       24 comment5' changed
>       12 comment6' changed
>        6 comment7' changed
>        4 comment8' changed
>        3 comment9' changed
>     2194 comment' changed
>       10 component' changed
>       12 description' changed
>       29 keywords' changed
>       37 owner' changed
>        8 priority' changed
>        7 reproduced' changed
>      291 resolution' changed
>      537 status' changed
>       32 summary' changed
>        2 type' changed
>       11 version' changed
> 
> 

If these are supposed to be ticket numbers on the left, I checked the 
first two and neither have comments from Balling.

If these are summaries/counts on the left, could you please elaborate on 
how you generated this data? I'm not super familiar with the trac user 
interface, but iirc you can embed the search in a query string.

- Leo Izen (Traneptora)


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 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:[~2024-03-11 21:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <037.cb9821e3b48f657909b93eb043f05720@avcodec.org>
     [not found] ` <052.37b53673b298748e0746920ec1d4551d@avcodec.org>
     [not found]   ` <CAFXy+3iBW9fdvrWGJQF65HERwV6CoQ0iCW06Wt4GcPtJOcKHrA@mail.gmail.com>
     [not found]     ` <CAEEMt2=iWhLratoG+2DfMVPh8nOSbYPUvKgxPJi06XgY-D_01A@mail.gmail.com>
     [not found]       ` <6d595a68-14c8-4a22-b52b-a9ed98587d5c@gmail.com>
     [not found]         ` <CAEEMt2=sFTnrebPTTe_q5kx3d=RZTSqy=gAJUwTTSRZJYDq2WA@mail.gmail.com>
     [not found]           ` <CAEEMt2kJ7nk+So_aG2WG5tQOkWriaNCw2L2PpXYbFO6k6eTqsQ@mail.gmail.com>
     [not found]             ` <20240306125639.GU6401@pb2>
     [not found]               ` <170996942472.7287.4678551313607358745@lain.khirnov.net>
     [not found]                 ` <8bbbc7fa-fe0f-4dd5-bc78-aae6106413d0@betaapp.fastmail.com>
2024-03-10  1:25                   ` Michael Niedermayer
2024-03-10  1:36                     ` epirat07
2024-03-10  3:00                       ` Michael Niedermayer
2024-03-10  3:19                         ` epirat07
2024-03-10  9:23                     ` Kieran Kunhya
2024-03-10 12:21                       ` Paul B Mahol
2024-03-11 21:40                     ` Leo Izen [this message]
2024-03-13  0:27                       ` Michael Niedermayer
2024-03-12 17:14                     ` Ronald S. Bultje
2024-03-12 17:55                       ` Paul B Mahol
2024-03-12 18:11                         ` Kieran Kunhya
2024-03-12 19:11                           ` Paul B Mahol
2024-03-12 21:20                             ` Marth64
2024-03-12 21:47                               ` Vittorio Giovara
2024-03-13  1:08                       ` Michael Niedermayer

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=f745c69c-dc3f-4227-a0cc-d454a669cedb@gmail.com \
    --to=leo.izen@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