Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
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 04:00:09 +0100
Message-ID: <20240310030009.GL6420@pb2> (raw)
In-Reply-To: <6CC987D1-4729-4430-B02D-0537D771B59B@gmail.com>


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

On Sun, Mar 10, 2024 at 02:36:48AM +0100, epirat07@gmail.com wrote:
> On 10 Mar 2024, at 2: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
> >
> 
> I already have an opinion about this topic due to various things I read from
> him on various OSS projects communication channels, but I am wondering
> how the attached document is helpful for the GA to get an idea of  what
> this is about?
> 
> Do you expect us to go through all of this list and visit each Trac ticket
> and look at what they wrote there?
> 
> Maybe I am missing something here on the purpose of this document.

Its unbiased information, its simply the full list of changes done by the
user id on trac
One can read a random subset of the comments/changes or fetch the referred
tickets and run some AI over all and ask for a summary

If one already has formed an oppinion or does not want to vote then one can
also ignore it. Or maybe the community will decide against a vote.

I just tried to provide what i can so people have the information if they want
it.

To me, every contributor is valuable. I want people to work together as a
team. But if people are asking for others to be banned thats a sign
something is not right.

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Rewriting code that is poorly written but fully understood is good.
Rewriting code that one doesnt understand is a sign that one is less smart
than the original author, trying to rewrite it will not make it better.

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

  reply	other threads:[~2024-03-10  3:00 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 [this message]
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
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=20240310030009.GL6420@pb2 \
    --to=michael@niedermayer.cc \
    --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