Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kieran Kunhya <kierank@obe.tv>
To: FFmpeg development discussions and patches <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: Sun, 10 Mar 2024 09:23:40 +0000
Message-ID: <CAK+ULv4JHZZuUqxa83Kpvs+T9Kieovy43eBFOshpWyLqwygRcQ@mail.gmail.com> (raw)
In-Reply-To: <20240310012542.GA6401@pb2>

On Sun, 10 Mar 2024, 01:25 Michael Niedermayer, <michael@niedermayer.cc>
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
>
>
> On Sat, Mar 02, 2024 at 10:23:32PM +0100, Michael Niedermayer wrote:
> > The CC has no authority for permanent bans
> > "Indefinite bans from the community must be confirmed by the General
> Assembly, in a majority vote."
> >
> > I checked and it seems there are over 4800 events in trac from Balling,
> 3783 match the word "comment"
> > since 2019
> >
> > By what rules does the CC deal out warnings and bans ?
> >
> > I think this needs to be put in writing in the docs because
> > currently its pretty much arbitrary. Some people get multiple
> > warnings, some people get nothing, some people are suggested to be
> > just banned with no prior warning
>
>
> On Sat, Mar 09, 2024 at 11:06:39AM +0100, Jean-Baptiste Kempf wrote:
> > Hello,
> >
> > On Sat, 9 Mar 2024, at 08:30, Anton Khirnov wrote:
> > > Quoting Michael Niedermayer (2024-03-06 13:56:39)
> > >> Balling does have a quite different style in his language. Not sure
> > >> what is a good term, street style, ghetto style?
> > >>
> > >> He used the same style of language towards me 10 days ago:
> > >> https://trac.ffmpeg.org/ticket/10824#comment:18
> > >
> > > This is not a "style", he understands perfectly well what he is doing.
> >
> > Come on, the guy is a troll.
> > We're not talking about a developer from FFmpeg, but an external troll,
> contributing nothing.
> > Kick him out.
>

Do you have permission to post private CC discussion on the ML?

Kieran

>
_______________________________________________
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-10  9:24 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 [this message]
2024-03-10 12:21                       ` Paul B Mahol
2024-03-11 21:40                     ` Leo Izen
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=CAK+ULv4JHZZuUqxa83Kpvs+T9Kieovy43eBFOshpWyLqwygRcQ@mail.gmail.com \
    --to=kierank@obe.tv \
    --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