From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: techboard@dpdk.org, dev@dpdk.org,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: Introducing status field to MAINTAINERS?
Date: Mon, 17 Jul 2023 09:09:04 -0700 [thread overview]
Message-ID: <20230717090904.28e98135@hermes.local> (raw)
In-Reply-To: <2821945.3Lj2Plt8kZ@thomas>
On Mon, 17 Jul 2023 18:04:51 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:
> 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.
I would prefer removal as well, but there are things like KNI and that stay
around for a year. And marking it as obsolete before removal would help.
There are also some marginally useful things like ethtool which no one
is maintaining.
next prev parent reply other threads:[~2023-07-17 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 22:10 Stephen Hemminger
2023-07-17 14:12 ` Bruce Richardson
2023-07-17 16:04 ` Thomas Monjalon
2023-07-17 16:09 ` Stephen Hemminger [this message]
2023-07-17 16:11 ` Bruce Richardson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230717090904.28e98135@hermes.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=techboard@dpdk.org \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).