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 820F44CF08 for ; Thu, 13 Feb 2025 13:32:16 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 796B868C160; Thu, 13 Feb 2025 15:32:14 +0200 (EET) Received: from btbn.de (btbn.de [144.76.60.213]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 3AD7E68C124 for ; Thu, 13 Feb 2025 15:32:08 +0200 (EET) Received: from [authenticated] by btbn.de (Postfix) with ESMTPSA id 88193296C1136 for ; Thu, 13 Feb 2025 14:32:07 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rothenpieler.org; s=mail; t=1739453527; 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=/aGkGzSVfgsBD6eXKPjEjtmCkm3Cq2Lnj1q/8QHNDMc=; b=fu+6Z5jk3cEANmO5I5dYABQw98A+qlekCUh5Q8SpmScLdkdAjj7bXjJWfPORDeaMRhHUkc jaabgzYf8HzWI7eF7joQK8903Xh5CHqxOa2lG9JmjtCqnEyw7CmIFcrbR+VR2AtF86twOo KM9BDQPMHuttLon7k/NHYISuoi4UUFyqy8OQqGQcHjnGC+ANkxs1y3Z8be9f7beSv2KNBB E/H4AdzGWXBt5EmTxVvP+Wd1wk8T57SpL6mQVrqaaPFKcO6OHH9JLp6aFVE4Q2/Md7IBYZ H3F0VhOHvWgEQgWV5oS5XpiZF5XEwi5lwIAI1OW8lTZFAXDbebPg9dz/xBleig== Message-ID: <4cce2d19-184f-48bb-9108-573c073ec63f@rothenpieler.org> Date: Thu, 13 Feb 2025 14:32:33 +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> <8887ba88-7657-4432-a8c4-6d9d0eb33f8c@rothenpieler.org> <6a5a1ba9-08c3-40fe-9313-55f82889afa2@rothenpieler.org> Content-Language: en-US, de-DE 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 09:49, Leo Izen wrote: > On 2/12/25 5:05 PM, Timo Rothenpieler wrote: >>> >> I'm really not sure what you're asking. >> PRs are not restricted. Creating repos is. >> And there is no way to NOT restrict it, unless you want to pay several >> hundred Euros a month in hosting fees extra, and constantly be on the >> lookout for hosting illegal/harmful things. > > My understanding as a Github and Gitlab user is the usual way to make a > PR is to first fork the repository, then commit changes to a branch on > your fork, and then send a PR which compares the fork to the master > branch of upstream. > > If you can't make a repository, I'm not sure how you would do a PR. It > sounds like you're saying there's another way to do it, but I'm not > familiar with it and I expect many other people are not either. The docs have been linked to twice now: https://forgejo.org/docs/latest/user/agit-support/ Again, it's not the intention to ONLY support this workflow, but it's an alternative for people who don't want to wait for admin approval for their own fork. Having your own fork still has merit, since you can develop and share your own changes that aren't necessarily intended for merge (yet). But allowing repo creation without approval is too wide open of a door to allow it by default. With the AGit workflow we at least immediately see the spam since it plopps up as PR that can then be swiftly dealt with. If anyone wants to be allowed to fork, just let me know with an account name and I'll up the limit. _______________________________________________ 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".