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 D500C49D50 for ; Sun, 10 Mar 2024 03:00:20 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 6C0FB68CC2A; Sun, 10 Mar 2024 05:00:17 +0200 (EET) Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [217.70.183.197]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 550D568C0CC for ; Sun, 10 Mar 2024 05:00:11 +0200 (EET) Received: by mail.gandi.net (Postfix) with ESMTPSA id A2C011C0004 for ; Sun, 10 Mar 2024 03:00:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1710039610; 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=Y9deblfdhC7fspcYLXxHj7P3VqjjT6EzqOOhM7xf5Dw=; b=Pg0UkHM6bQ5O2Xp1PKtvz4MoTHABxNdVBNxsNTMogIvRo7O6fB+4VXBN+tOuSsCUhmN+XV 4rwuGx+CJwGvpdnOqrO77jxdiRi8JJo/MnN3moeJ8xj36uhQHY2TOBrWjFcINjF8F15Jq5 bRY6FKav/Y+CBj8XXJfEo3K9cE75AFLFcyjy0pOqGJbi2aT2PuOoY/ceqnB35hm9+a+7n1 iOfrLGIQnEMvCKTbaaKoDA6R0yIFfRPJQh6VjQVgaOCphkUM+jzW3IpUMiWccI49Qr6mH6 4QEuE6GetAJXsrSF21DVSy347qmmY0LoIitgiS7Kz5rqft4GDi7x6ExwrdlUtA== Date: Sun, 10 Mar 2024 04:00:09 +0100 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240310030009.GL6420@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> <6CC987D1-4729-4430-B02D-0537D771B59B@gmail.com> MIME-Version: 1.0 In-Reply-To: <6CC987D1-4729-4430-B02D-0537D771B59B@gmail.com> 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="===============5726208844954822988==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============5726208844954822988== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="AqH4nK8AA+PDQ4ED" Content-Disposition: inline --AqH4nK8AA+PDQ4ED Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 10, 2024 at 02:36:48AM +0100, epirat07@gmail.com wrote: > On 10 Mar 2024, at 2:25, Michael Niedermayer wrote: >=20 > > 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 As= sembly, 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 d= oesnt 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 > > >=20 > I already have an opinion about this topic due to various things I read f= rom > 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? >=20 > Do you expect us to go through all of this list and visit each Trac ticket > and look at what they wrote there? >=20 > 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 w= ant 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 [...] --=20 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. --AqH4nK8AA+PDQ4ED Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZe0iNgAKCRBhHseHBAsP q/F8AJ0fIzP9vu9k+fZn/T0PRCPhGa/TZgCfY2ElNDvPoRg3+AIdynJTe+e+usg= =07py -----END PGP SIGNATURE----- --AqH4nK8AA+PDQ4ED-- --===============5726208844954822988== 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". --===============5726208844954822988==--