From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 832714BEBB for ; Mon, 3 Nov 2025 17:44:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ffmpeg.org; i=@ffmpeg.org; q=dns/txt; s=mail; t=1762191878; h=date : message-id : to : in-reply-to : references : mime-version : reply-to : subject : list-id : list-archive : list-archive : list-help : list-owner : list-post : list-subscribe : list-unsubscribe : from : cc : content-type : content-transfer-encoding : from; bh=iC9FQ/E6rleO7LgVrznOSpJnkw1QU2At8bl/CKd0N9g=; b=lirTt/sTTeWlRPLnCvoCPcohskfVbYwqggm5Zk4/vLQqwhNGyiIXb6yquINmlhvcR6FVm HwYV5RSNmsTZaEu1yxqooK7+i1LKN92tM5JnTtZ1dXoasBiv7xhLeiRhSugkxLT666IrhMo jlIG/RTZ6bbCfO3DBL+bXoxbhblXE6f6VlT7eJEOAa46OGYzhEvl3D2/1O0FsAN0pY+wOh4 qIke0ZoPzfRxX2eviRakAvFvZgEtuh7pcT5czLcEbVG2W6XdiP+jW1EW0JneOoY8Ebb/xrd SP3cS5qZJZ01qs0U/9qGP6EwBcUnqkB8YUQebBTrPKzlOAqwGR/DxqZPr/6A== Received: from [172.19.0.2] (unknown [172.19.0.2]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 2D6A668F9AF; Mon, 3 Nov 2025 19:44:38 +0200 (EET) ARC-Seal: i=1; cv=none; a=rsa-sha256; d=ffmpeg.org; s=arc; t=1762191861; b=B2XyzGrbxQORu5vJ98knAadnT/WzfuzQmn2bUJPeU3nGLYKqlNH9FJ1cWcj8MyvWAdNOT 4lUgi/pe1HDZ5Lv5ws9RJVyKDLELFgf9ozmFLxrfHUJnJPhtDH1OOCCLMonmlZtAQAbice/ OZ4USsSlXrlGmGuuH0IvZBqgryLFdRhqHBdnJJX4IKkDlcPi3wG6wneskUn9txQC8ssgaae o16EskJ7QDJp6g4mW6AoeFZkIjYskxI2EoNmc2dd1AHJ4DGbJ1Qt5hI4wMqJnTTCrJl3Hme wv8Z49c1qaD3wu+HBmXjieNsEx184AvxOLZF3haUrfyAblyMVWlVz9J1HcZg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=ffmpeg.org; s=arc; t=1762191861; h=from : sender : reply-to : subject : date : message-id : to : cc : mime-version : content-type : content-transfer-encoding : content-id : content-description : resent-date : resent-from : resent-sender : resent-to : resent-cc : resent-message-id : in-reply-to : references : list-id : list-help : list-unsubscribe : list-subscribe : list-post : list-owner : list-archive; bh=TZpB71gAhWmwTPnzJJ7UfBxDeTew6gmPytht1n5nmlY=; b=iWGS3zrKg00SxiINw6C815j0JUQrokSiR80hUz3r1lkxev+i7zkGYdu0ZmjOO6qoUY1xP yIgTRMJsBmghT0JdPmtm6fWbMIDsXNSxLPICIXeZPNZx3/zCAqFEUWcx+A6tTYxRzZX9wyT nhctNORQ4FBBz5RN68yWzGaEqBv1jR4pKS5KEr0q2HOV6fBkbYxJi2F9qf7/ALd/EUlpPGB BaxqYtHeujzmgBUlaSW50LX5IDt428lTR7jLTLhlnwzT08u9in8+itHKsouzZFGA/ZArB/w 2S6n2BAhzQ3Nsva9Z7wLZIRIOd/k+qic2WSaP/sdvLaGxEZw/7Rval0SFpQw== ARC-Authentication-Results: i=1; ffmpeg.org; dkim=fail; arc=none; dmarc=none Authentication-Results: ffmpeg.org; dkim=fail; arc=none (Message is not ARC signed); dmarc=none Received: from haasn.dev (haasn.dev [78.46.187.166]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 7CCA168021E for ; Mon, 3 Nov 2025 19:44:08 +0200 (EET) Received: from haasn.dev (unknown [10.30.1.1]) by haasn.dev (Postfix) with ESMTP id 4BE7A4054F; Mon, 3 Nov 2025 18:44:08 +0100 (CET) Date: Mon, 3 Nov 2025 18:44:08 +0100 Message-ID: <20251103184408.GB74644@haasn.xyz> To: FFmpeg development discussions and patches In-Reply-To: References: <20251101233846.GB1030693@haasn.xyz> MIME-Version: 1.0 Content-Disposition: inline Message-ID-Hash: KXSNHQIFZM4RCAHJ2ORVHX5WWQ2PH5RN X-Message-ID-Hash: KXSNHQIFZM4RCAHJ2ORVHX5WWQ2PH5RN X-MailFrom: SRS0=kMay=5L=haasn.dev=nand@ffmpeg.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-ffmpeg-devel.ffmpeg.org-0; header-match-ffmpeg-devel.ffmpeg.org-1; header-match-ffmpeg-devel.ffmpeg.org-2; header-match-ffmpeg-devel.ffmpeg.org-3; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list Reply-To: FFmpeg development discussions and patches Subject: [FFmpeg-devel] Re: [RFC] Funded Task Ideas List-Id: FFmpeg development discussions and patches Archived-At: Archived-At: List-Archive: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: From: Niklas Haas via ffmpeg-devel Cc: Michael Niedermayer , Niklas Haas Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Archived-At: List-Archive: List-Post: On Sun, 02 Nov 2025 03:09:39 +0100 Michael Niedermayer via ffmpeg-devel wrote: > I like the idea > > Note, the SPI Vice President, who helped us with the STF stuff is possibly > on vacation ATM (not 100% sure). And also this is the first sw development task we do without > STF/GSoC/OPW. So there could be some extra delay. > I thus suggest if we want to do this, that we move forward with it ASAP so that > we dont add additional delay What should the process be? Do I sign a SoW / contract with SPI first? Or does e.g. Stefano just agree to the bounty? Who decides if a given merged patch qualifies as satisfying the criteria? Should the GA have to vote on approving bug bounties? What if somebody else decides to "snipe" a bug bounty while the developer who proposed it is still working on it? I personally think: 1. A contract is not necessary for a one-off bug bounty, just a written approval from SPI should be enough. 2. If there is a dispute, the TC should decide if a patch sufficiently addresses the bug bounty. (Of course, in such a case as the bug bounty involving a member of the TC, they would recuse themselves due to CoI) 3. A GA vote is only necessary if there are dissenting opinions, or ongoing disputes about the scope and amount of the bounty; let's say a week without objections should be enough to greenlight a bounty. 4. Developers should announce when they begin working on a bounty, and then nobody else should be able to claim it until a reasonable amount of time has passed. (Perhaps 12 weeks) _______________________________________________ ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org