linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: lsf-pc@lists.linux-foundation.org,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	linux-scsi@vger.kernel.org, linux-block@vger.kernel.org
Subject: [LSF/MM/BPF TOPIC] Limits of development
Date: Wed, 11 Jan 2023 12:49:43 +0100	[thread overview]
Message-ID: <06e4d03c-3ecf-7e91-b80e-6600b3618b98@suse.de> (raw)

Hi all,

given the recent discussion on the mailing list I would like to propose 
a topic for LSF/MM:

Limits of development

In recent times quite some development efforts were left floundering 
(Non-Po2 zones, NVMe dispersed namespaces), while others (like blk-snap) 
went ahead. And it's hard to figure out why some projects are deemed 
'good', and others 'bad'.

I would like to have a discussion at LSF/MM about what are valid reasons 
for future developments, and maybe even agree on common guidelines where 
developers can refer to when implementing new features.

Cheers,

Hannes

             reply	other threads:[~2023-01-11 11:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11 11:49 Hannes Reinecke [this message]
2023-01-11 12:55 ` [LSF/MM/BPF TOPIC] Limits of development James Bottomley
2023-01-11 13:17   ` Hannes Reinecke
2023-01-11 14:04     ` James Bottomley

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=06e4d03c-3ecf-7e91-b80e-6600b3618b98@suse.de \
    --to=hare@suse.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.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 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).