From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 4262642E9E; Mon, 17 Jul 2023 18:04:56 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C1E3040A80; Mon, 17 Jul 2023 18:04:55 +0200 (CEST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mails.dpdk.org (Postfix) with ESMTP id 928884068E; Mon, 17 Jul 2023 18:04:54 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id BB4765C0079; Mon, 17 Jul 2023 12:04:53 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Mon, 17 Jul 2023 12:04:53 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1689609893; x=1689696293; bh=Pcn39fXrgqR9A5O4F3S6C2korOCo59BBDql 4Qw/ssHo=; b=Urz3gREihNjOA/E/loDDlqVSBf+Vg1ozf2yaq2uGz9qmpBFDFHg IaEX+VRWbEhDwZAWq+YoWyuu7GeWtT4SsmInCC3gQBkh1OoJ0TiFyAxxtuLe4kFn pmOjIf7CW3vsZFvYSbwyiClgy5uY4fp/MAc5Tpp8D0jMWpgCeqZu8kOr8IEi6ZCm bSdbAPM8AMgvyMomeDN/XMLvmRim0sLuA/ZIhFxUL6v+TKtBYfsUGn+Jic3AfTRS BKlXcD/dmDJK2yixrFN5FwRMV8FCAZ326JCdaWnASd5e2jbhgWDuhpw/Qr90rT7w ioxz0MOYQW2PLz5FZ3S+jsTTYU+kr/vUzYA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1689609893; x=1689696293; bh=Pcn39fXrgqR9A5O4F3S6C2korOCo59BBDql 4Qw/ssHo=; b=Bf1rHfYF8YwbMLVSQwxgtEGt4D4E8NP64HuWgto35K9PCzDoQ4L 5LZwz5g0eP6POeqqLE9MH8jjDaFHmNISNWt/GjpFOE5j1ksAa/ylYgk5I0R99OsQ jXI5VS8WaXLlQNi8tmfqaxTd176CHkUgZ8fTawIK84nrLBAGC8KeSnJSdfcsB19w oMCCOeY8qUO1El3OU6tT1Qe1HkCG6dQfRUcSpNhQZ5sjZz68ZJZPhvjvV3W8FTu5 f1JM6GBwVPb0slmSm5DuOnx9I74dAqqUoD+vn3Pa42fE3cAiDgwDlOquMlVQLE1E CvJmFo6NQXZzUaIV6JHgBEEvoUX+w8SWwHQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrgedvgdeliecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvfevufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnheptdejieeifeehtdffgfdvleetueeffeehueejgfeuteeftddtieek gfekudehtdfgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 17 Jul 2023 12:04:52 -0400 (EDT) From: Thomas Monjalon To: Stephen Hemminger Cc: techboard@dpdk.org, dev@dpdk.org, Bruce Richardson Subject: Re: Introducing status field to MAINTAINERS? Date: Mon, 17 Jul 2023 18:04:51 +0200 Message-ID: <2821945.3Lj2Plt8kZ@thomas> In-Reply-To: References: <20230703151057.303bb87a@hermes.local> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 17/07/2023 16:12, Bruce Richardson: > On Mon, Jul 03, 2023 at 03:10:57PM -0700, Stephen Hemminger wrote: > > While going through the old patches, noticed some that are in parts > > of DPDK that are pretty much abandoned. > > > > My suggestion would be introduce a subsystem status field in MAINTAINERS > > similar to what is done in Linux kernel. > > > > S: *Status*, one of the following: > > Supported: Someone is actually paid to look after this. > > Maintained: Someone actually looks after it. > > Odd Fixes: It has a maintainer but they don't have time to do > > much other than throw the odd patch in. See below.. > > Orphan: No current maintainer [but maybe you could take the > > role as you write your new code]. > > Obsolete: Old code. Something tagged obsolete generally means > > it has been replaced by a better system and you > > should be using that. > > That seems a useful addition. +1 to add the extra info. I think we prefer removing unmaintained code.