From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 47989475F2 for ; Wed, 13 Mar 2024 00:27:27 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 51D3C68CF5C; Wed, 13 Mar 2024 02:27:25 +0200 (EET) Received: from relay7-d.mail.gandi.net (relay7-d.mail.gandi.net [217.70.183.200]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id A6EFA68CD6D for ; Wed, 13 Mar 2024 02:27:18 +0200 (EET) Received: by mail.gandi.net (Postfix) with ESMTPSA id C952520002 for ; Wed, 13 Mar 2024 00:27:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1710289638; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=j0jKsIrdNAMTtN3dwD26q+STXrf/T+yIOjZFW92bnwQ=; b=JOii+7Ul29e5FARUOeShLGbJf/UgG56aitq3n/SYkf8D9JgiH95DY7ik4xDKi7y281Poav hdBfQjVXr6bFrgemQ59yi9AtRBv7+5AmvgAJrUct7YET/OPj0hL4CXl6SBHGMmcKIGciC4 piH8OkJijzS2EPx4d5xmWJWHbJE9zun6RCpAmmc8a9mGs1laWox98eFRvrA2ZrdInXAcYP pq8BoNxCXJEIE2yYDeNHCpftfcXN1gvYrJFui6ONdVYoKNPVGVG0Nf8Uz0lTiVsLnEhNXU H0n/+A4zjsHAaj5WBbCm9/eJY0P8x7w9dIs4bSizlSg/t7DRACxjK61cZ05YJw== Date: Wed, 13 Mar 2024 01:27:17 +0100 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240313002717.GX6420@pb2> References: <6d595a68-14c8-4a22-b52b-a9ed98587d5c@gmail.com> <20240306125639.GU6401@pb2> <170996942472.7287.4678551313607358745@lain.khirnov.net> <8bbbc7fa-fe0f-4dd5-bc78-aae6106413d0@betaapp.fastmail.com> <20240310012542.GA6401@pb2> MIME-Version: 1.0 In-Reply-To: X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] Indefinite ban request [RFC] Was: Re: [FFmpeg-trac] #10882(undetermined:new): swscale wastefully scales luma during yuv420p -> yuv422p X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: multipart/mixed; boundary="===============4465524535841418639==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============4465524535841418639== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ojnjlqlzaxTbajyB" Content-Disposition: inline --ojnjlqlzaxTbajyB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 11, 2024 at 05:40:25PM -0400, Leo Izen wrote: >=20 >=20 > On 3/9/24 20:25, Michael Niedermayer wrote: > > Hi everyone > >=20 > > 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 As= sembly, in a majority vote." > >=20 > > Thus some CC member wishes to involve the public here > > (really theres no other option, the GA cannot discuss/vote on what it d= oesnt know) > >=20 > > Also people have asked for more transparency and i strongly agree with = transparency. > >=20 > > 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. > >=20 > > I do not and never did support permanently banning contributors. > >=20 > > 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 > >=20 > >=20 >=20 > If these are supposed to be ticket numbers on the left, I checked the fir= st > two and neither have comments from Balling. >=20 > 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. The data is taken from an admin page of trac that AFAIK lists all activities a user did then email addresses where manually removed to preserve privacy the summary was created using egrep -o '(comment|status|resolution|keyword|version|component|summary|owne= r|priority|reproduced|type|description).*changed' Balling.txt | sort | uni= q -c The numbers on the left are counts not ticket numbers, that is Balling seems to have edited 2194 times a comment field according to grep comment Balling.txt | grep -o 'Ticket [0-9]*' | sort -n | uniq -c | wc grep status Balling.txt | grep -o 'Ticket [0-9]*' | sort -n | uniq -c | wc grep resolution Balling.txt | grep -o 'Ticket [0-9]*' | sort -n | uniq -c |= wc he changed the comment fields in 922 distinct tickets he changed the status field in 449 distinct tickets he changed the resolution field in 248 distinct tickets thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Concerning the gods, I have no means of knowing whether they exist or not or of what sort they may be, because of the obscurity of the subject, and the brevity of human life -- Protagoras --ojnjlqlzaxTbajyB Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZfDy2wAKCRBhHseHBAsP qwNcAKCIse7NC4dT7j4toHfE/E7bWu8UlwCglk2Q2YnjYPvPRZiPNNRyf6t0ZtU= =0bHY -----END PGP SIGNATURE----- --ojnjlqlzaxTbajyB-- --===============4465524535841418639== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --===============4465524535841418639==--