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 D05C74CE43 for ; Wed, 12 Feb 2025 23:34:28 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 7BB6A68C110; Thu, 13 Feb 2025 01:34:24 +0200 (EET) Received: from btbn.de (btbn.de [144.76.60.213]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 27B2B68AB42 for ; Thu, 13 Feb 2025 01:34:18 +0200 (EET) Received: from [authenticated] by btbn.de (Postfix) with ESMTPSA id A0AED296C1010 for ; Thu, 13 Feb 2025 00:34:16 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rothenpieler.org; s=mail; t=1739403256; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Ws//+/NMtyFudqBbwl8N+NXMskHrH2tk7TlL47ALQO0=; b=AeOACICo3RC/WqieKGt5CWX9f1fWnGUYHsBjwF6ml2/SCbsZemXvCH9uurN+wP2Dkz3U1k QQWCnK/sYJNqE6QqtU/oe1OugfwB7ex3fkzdm+G+0UNawC4DmlSDzf942SeaH8M1XrZL+l f1wjNnSFbAC5FWWMxaIEtull60dnTbYJ92HOy29KXa75dI34CVboadyVysQK2v08k3hpc9 Ok7rdijst8ocbI5XKsoDMC/X2DIIGEmzkutoVITs5m9E2tllANR1AxDJoV/fgU/JRLjLfS kyP2QL0rhBjSWx7ixewkEc3xlKIenfZV9sGhibcbAzNCyfUzGzrCjY5nvhD6yg== Message-ID: <75b7fd65-0fb4-4551-b832-a9ac4331582b@rothenpieler.org> Date: Thu, 13 Feb 2025 00:34:18 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: ffmpeg-devel@ffmpeg.org References: <20250212180659.GP4991@pb2> <73f4b334-a4eb-4f06-b01e-e30988d49d1a@lynne.ee> <90f6d33f-65e1-4ff6-a30f-f1eee8f89d23@gmail.com> Content-Language: en-US From: Timo Rothenpieler In-Reply-To: Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests 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-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On 13.02.2025 00:07, Soft Works wrote: > >> -----Original Message----- >> From: ffmpeg-devel On Behalf Of Timo >> Rothenpieler >> Sent: Mittwoch, 12. Februar 2025 22:33 >> To: ffmpeg-devel@ffmpeg.org >> Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests >> >> On 12.02.2025 22:22, Stephen Hutchinson wrote: >>> Are all accounts restricted to owning a maximum of 0 repositories by >>> default, or is it set to 0 only for those that sign up through one of >>> the external logins? >> >> It's set to 0 by default, to avoid spammers uploading junk, or just >> people (ab)using it for non-ffmpeg things. >> >> You can open issues and comment on existing PRs. >> And also create PRs using the AGit workflow: >> https://forgejo.org/docs/latest/user/agit-support/ > > For those who are too lazy to look it up: > > The "Agit workflow" requires you to use non-standard Git "push-options" > (either -o or --push-options): > > git push origin HEAD:refs/for/master -o topic="topic-branch" \ > -o title="Title of the PR" \ > -o description="# The PR Description > This can be **any** markdown content.\n > - [x] Ok" > > This means essentially that our attempt to move away from the e-mail-based submission procedure to something easy and user-friendly, would end up in replacing the current rarely-known mechanism with another even more rare and obscure procedure which would (again) force everybody to use the Git command line because it's (again) not supported by any tooling except Git CLI. > > I'm afraid, but from my point of view, this doesn't match the objective. The only alternative is to completely lock down the instance, and not allow new users at all without manual approval of each and every one. People can just ask to be allowed to fork, but by default, allowing it is not feasible. Videolan apparently even went away from the current approach on our instance, cause there was still too much spam. So they're manual-approval-only now. _______________________________________________ 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".