All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: techboard@dpdk.org
Cc: dev@dpdk.org
Subject: Introducing status field to MAINTAINERS?
Date: Mon, 3 Jul 2023 15:10:57 -0700	[thread overview]
Message-ID: <20230703151057.303bb87a@hermes.local> (raw)

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.

             reply	other threads:[~2023-07-03 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03 22:10 Stephen Hemminger [this message]
2023-07-17 14:12 ` Introducing status field to MAINTAINERS? Bruce Richardson
2023-07-17 16:04   ` Thomas Monjalon
2023-07-17 16:09     ` Stephen Hemminger
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=20230703151057.303bb87a@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=techboard@dpdk.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.