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 9A47A40807 for ; Tue, 28 Mar 2023 11:37:27 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 53F6C68CB22; Tue, 28 Mar 2023 14:37:25 +0300 (EEST) Received: from mail0.khirnov.net (red.khirnov.net [176.97.15.12]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 669A368CAB4 for ; Tue, 28 Mar 2023 14:37:19 +0300 (EEST) Received: from localhost (localhost [IPv6:::1]) by mail0.khirnov.net (Postfix) with ESMTP id AA8AA2404EE for ; Tue, 28 Mar 2023 13:37:18 +0200 (CEST) Received: from mail0.khirnov.net ([IPv6:::1]) by localhost (mail0.khirnov.net [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id gEtI0IksjdqP for ; Tue, 28 Mar 2023 13:37:17 +0200 (CEST) Received: from lain.khirnov.net (lain.khirnov.net [IPv6:2001:67c:1138:4306::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "lain.khirnov.net", Issuer "smtp.khirnov.net SMTP CA" (verified OK)) by mail0.khirnov.net (Postfix) with ESMTPS id E0F512404EC for ; Tue, 28 Mar 2023 13:37:17 +0200 (CEST) Received: by lain.khirnov.net (Postfix, from userid 1000) id BD8D41601B2; Tue, 28 Mar 2023 13:37:17 +0200 (CEST) From: Anton Khirnov To: FFmpeg development discussions and patches In-Reply-To: <20230325001445.GQ375355@pb2> References: <167966815810.27013.14421474053930764026@lain.khirnov.net> <20230325001445.GQ375355@pb2> Mail-Followup-To: FFmpeg development discussions and patches Date: Tue, 28 Mar 2023 13:37:17 +0200 Message-ID: <168000343774.27013.7248555421089758280@lain.khirnov.net> User-Agent: alot/0.8.1 MIME-Version: 1.0 Subject: Re: [FFmpeg-devel] [RFC] the role of maintainers 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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: Quoting Michael Niedermayer (2023-03-25 01:14:45) > On Fri, Mar 24, 2023 at 03:29:18PM +0100, Anton Khirnov wrote: > > Hi, > > during the recent discussion on git repo push rights vs maintainership > > there was some disagreement on what does (or should) it mean to be a > > maintainer of a piece of code. It seems that different people have very > > different ideas on this, so I think it would be good to reach some kind > > of consensus. > > > > I propose that people submit their opinions on what the rights and > > responsibilities of a maintainer should be to this thread, so their > > relative merits can be discussed. > > The we have a GA vote, and write down the result in the dev rules. > > > > To start, some of the specific questions that I believe should be > > considered are: > > 1. Should the concept of maintainership exist at all? Does it serve a > > useful purpose? If so, what is it? > > (further questions assume that the answer to 1. is yes) > > Ultimately someone does fix issues, improve some code and takes some > responsibility related to that code, aka "caring about it" > > If noone does that, well ok, you have no maintainer. OTOH if someone > does these things, thats what i would call a maintainer. The term > "maintainer" is juat a label for that. > The same way a software developer is a label for someone creating > software. Thats at least the way i see it. The question is whether we benefit from this being a formal role. You can just as well fix issues and improve code without being called the maintainer. And it seems to me that your "just a label" claim is not consistent with the rest of your reply, where you say that maintainer automatically gets certain privileges, such as git push access. IMO these roles should be decoupled, because someone who authored a specific module (like a filter or decoder) might still not know how his code interacts with the rest of the project. -- Anton Khirnov _______________________________________________ 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".