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 44A734C954 for ; Thu, 15 Aug 2024 11:30:48 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id DAD2B68DB64; Thu, 15 Aug 2024 14:30:45 +0300 (EEST) Received: from relay6-d.mail.gandi.net (relay6-d.mail.gandi.net [217.70.183.198]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 64BED68D83C for ; Thu, 15 Aug 2024 14:30:39 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id B6AE7C0007 for ; Thu, 15 Aug 2024 11:30:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1723721438; 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=sJ6/u2USHvv3MvZQXMhfC4wjQ0BlwwAtM5wQPQS1JVY=; b=nvYyrCjboG5BX/oe2d4N3+xExbuuLZ/ILCox48AoAt0CJBMPootZkvinHJQCkyV2LOd5LF 32HohTtj/Qu4dLk1ERHYPBT5C20BQ+hqaIL6JcTXHN8KOuRGDslo3KRbnKFxkDfvkCkLds Qc1Dpz157xhWqeziEwbjACtDv+xfasN/s3ihqM96dAkiQ3IDnfw78nIgBBO4B4eJbi6KT4 sYafiQ4Wq8M2NnKHbBH99PDq7/hOC4Rh3Bi4cxZnHjtqOjIKxrN70Vqct5rxa6fA9gNM1E 6LvTBiWFTrlduL8MxAf/OJqdCltyzAYR6W439ydfhCK3Nh8zM5yjJWtB6dSSaw== Date: Thu, 15 Aug 2024 13:30:38 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240815113038.GA4991@pb2> References: <20240815073307.2441983-1-michael@niedermayer.cc> MIME-Version: 1.0 In-Reply-To: X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] [PATCH] MAINTAINERS: Add more fields based on the linux kernel 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: multipart/mixed; boundary="===============2552659036553794883==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============2552659036553794883== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="x1+AGLzVZdX4V68E" Content-Disposition: inline --x1+AGLzVZdX4V68E Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi On Thu, Aug 15, 2024 at 11:24:31AM +0300, R=E9mi Denis-Courmont wrote: >=20 >=20 > Le 15 ao=FBt 2024 10:33:07 GMT+03:00, Michael Niedermayer a =E9crit=A0: > >Text was stolen from the linux kernel > >This is thus identical to the kernel just a different more compact forma= t. > >I am very happy also to switch the file entirely to the format of the li= nux kernel maintainer list > >if people prefer > > > >This allows tracking the status of each sub system, if it needs new bloo= d or not > > > >It allows people to specify a separate webpage / document describing the= subsystem > >It allows people to ask for bug reports to be mailed to them instead of = just > >sent to trac. > >It allows listing things like gitlab or github or anything else where to > >submit patches. This could be used both for testing new patch submission= systems > >as well as permanently honoring the preferance of the developers maintai= ning a > >subsystem. >=20 > We don't really have a process for managing subsystems, and however large= FFmpeg is (compared to most OSS projects), it's only about as active as a = single active Linux subsystem. >=20 > If people feel that Ffmpeg-devel has too much traffic then I'll gladly mo= ve RISC-V to code.videolan.org. But I haven't really noticed anybody making= such complaint. >=20 > I don't think we should break FFmpeg development up into silos unless it'= s become unmanageably large otherwise. Nothing in this patch suggests to break FFmpeg development up into silos But how many developers can follow the mailing list fully ? how many developers can follow trac and notice if their code has a bug repo= rted against it ? I certainly am failing to follow trac at that level, and i would appreciate= if people would CC me if they open a bug related to code i maintain or a change i pushed. It seems like a good idea if i could specify that i prefer that somewhere Also some people do develop code outside the main ffmpeg git master. Someti= mes thats temporary sometimes permanent. It could make sense if patches get sent agai= nst these to reduce rebasing work. IMO patches should always still be sent to ffmpeg-devel. The idea is not to break anything up, its really the opposit, to glue things together where they are broken up for social or technical reasons. An example could be that someone, who maintains code outside git master alr= eady now, could list that fact in MAINTAINERs. Also there are different preferrances on how to submit patches, some people= want a switch to a webapp based system, some people oppose this. This change to MAINTAINERs would allow both to have what they prefer. It doesnt mean thats what we will do, just that the file would allow to represent that state. Also last but not least, I ommited "C: URI for *chat* protocol, server and = channel where developers" =66rom the kernel MAINTAINERs, for the very reason not to create silos. we = have our communication channels and we should not split these. but at the same time we have things like ffmpeg-security and ffmpeg-devel-o= wner as seperate entities for the maintaince for the respective "subsystem" argu= ably "subsystem" is maybe an ill choosen term here thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The misfortune of the wise is better than the prosperity of the fool. -- Epicurus --x1+AGLzVZdX4V68E Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEKAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZr3m1gAKCRBhHseHBAsP q50HAJ9Za9NY1aYR9ELZYO/F1G1J8w6EHACeIaOBPKDs1Ynx0vyB3Rl0+SWpbNk= =olFc -----END PGP SIGNATURE----- --x1+AGLzVZdX4V68E-- --===============2552659036553794883== 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". --===============2552659036553794883==--