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 ESMTPS id B805C4AFF9 for ; Tue, 21 Jan 2025 17:48:13 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 45D4468B6F0; Tue, 21 Jan 2025 19:48:10 +0200 (EET) Received: from relay8-d.mail.gandi.net (relay8-d.mail.gandi.net [217.70.183.201]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 57F9F68A753 for ; Tue, 21 Jan 2025 19:48:04 +0200 (EET) Received: by mail.gandi.net (Postfix) with ESMTPSA id B77641BF20A for ; Tue, 21 Jan 2025 17:48:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1737481682; 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=mgkfKoXL0cL9bmLzcfAePcyC/VvfMZMYjN80+wtUlGA=; b=GF1g22A6m/S/lym+VuqljUZjXK2mlw13CHYW6mdIYYp0r3wgUYzKWZ+PFsaEtCHuZK6uuE a/CVYSw7AJA+6ECbli0vu2SyBm5cY2wwLBRboDqaOs21lJ09KtZwgLbIRObtHQB8s8YSxd 8XgZqoSGCkHTn9tmAU2LQCI9lE1uoXDvFOY2bcSHSBAXe51cF4sWTg2vP+EAR0h7N3yKSR 0JKdNeODf9IJPvC7ZgmmC3H9KcJLd+xJ3myxExNH/QaU2LUKYZY0zifM5/eAzp4TlNpxqM 2fiM8AY5pmOfA056QKdG/TJQBtVr65BFkunleEuEQZAcR5yHkvP4I+LSS4LOBQ== Date: Tue, 21 Jan 2025 18:48:01 +0100 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20250121174801.GM4991@pb2> References: <20250121130445.GD9168@haasn.xyz> <20250121155421.GH4991@pb2> MIME-Version: 1.0 In-Reply-To: X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] Regarding Git Tooling 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="===============2775076736049700963==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============2775076736049700963== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="34c0n5q9YKXSNx99" Content-Disposition: inline --34c0n5q9YKXSNx99 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi James On Tue, Jan 21, 2025 at 01:22:52PM -0300, James Almer wrote: > On 1/21/2025 12:54 PM, Michael Niedermayer wrote: > > Hi > >=20 > > On Tue, Jan 21, 2025 at 01:04:45PM +0100, Niklas Haas wrote: > > > On Mon, 20 Jan 2025 14:39:29 -0600 Marth64 wrot= e: > > > > Hello, in the context of a GA member, > > > >=20 > > > > I think there is general interest in modernizing technical tooling > > > > specifically regarding ML/patch workflow vs. integrated git solutio= n. > > > > Both have their merits. I think what we have today is optimized for > > > > some but cumbersome for many. Like shopping for a drill, it is good= to > > > > step back from time to time and ensure we have the right tools. > > > >=20 > > > > I think the problem statement of productivity being impacted from > > > > outgrowing the current tooling is different from who is hosting it. > > > >=20 > > > > These are some options I noticed interest in (in no particular orde= r): > > > > - Forgejo > > > > - GitLab > > > > - Mailing List/Patch Workflow (current solution) > > >=20 > > > Since our last discussion at VDD, I have come to prefer Forgejo over = GitLab > > > and would be in favor of hosting an instance on ffmpeg.org. > > >=20 > >=20 > > > What are the current barriers to doing this. Michael, since you said = that you > > > are in favor iff the community agrees with it, should we start a GA v= ote on > > > the matter? > >=20 > > I would instead of a secret GA vote, maybe wait a few days for discussi= on > > to settle down and then just ask people on the ML about (yes vs no) (st= rong vs weak) > > and a short paragraph about a switch to Forgejo >=20 > We can always start a Condorcet vote where the requirement is that only > non-anonymous votes are considered, if you think that will help (Maybe it > can even be forced to actually cast your vote?). A vote using mail replies > in a thread with yes/no is hard to follow. we can force non anonymous voting, this isnt the main concern >=20 > Also, the vote can happen after a thread with replies stating support for > one or another solution, with optional argumentation if there's something= to > say that hasn't been said already. >=20 > >=20 > > As well as a 2nd question: > > namely on the threshold > > should we switch if we have 51% ? or no strong opposition ? or how to d= raw > > the line? >=20 > Ideally, there would be two votes. One to open the question if we move aw= ay > from ML patches, and then one to choose between Forgejo/Gitlab, if the fi= rst > vote succeeds. But i don't know if people will be ok with that. that can be done too or a condorcet of gitlab/Forgejo/ML patches can be done my concern is that the community is not just 49 people. and before people attack me. the choice of Forgejo/gitlab/git send email af= fects many more than 49 people. Every person submiting a patch or contribution is affected. In fact everyone on ffmpeg-devel is bascially thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Avoid a single point of failure, be that a person or equipment. --34c0n5q9YKXSNx99 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEKAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZ4/d0QAKCRBhHseHBAsP q0bHAJ9s/AB61X5cMi4QhFXr+KsQElWpqgCdHUpyuLAfV9ykI5UG+ZoLoPxjkqs= =OaVU -----END PGP SIGNATURE----- --34c0n5q9YKXSNx99-- --===============2775076736049700963== 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". --===============2775076736049700963==--