All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@citrix.com>
To: Andrew Cooper <Andrew.Cooper3@citrix.com>
Cc: Lars Kurth <lars.kurth@citrix.com>,
	Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
	"Tim \(Xen.org\)" <tim@xen.org>,
	George Dunlap <George.Dunlap@citrix.com>,
	Julien Grall <julien.grall@arm.com>,
	Paul Durrant <Paul.Durrant@citrix.com>,
	Jan Beulich <JBeulich@suse.com>,
	Xen-devel <xen-devel@lists.xenproject.org>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH] docs/sphinx: todo/wishlist
Date: Mon, 9 Sep 2019 12:02:47 +0100	[thread overview]
Message-ID: <23926.12631.330650.505179@mariner.uk.xensource.com> (raw)
In-Reply-To: <0eee7e6e-a3d9-ea86-d93b-7da6fb282ddb@citrix.com>

Andrew Cooper writes ("Re: [PATCH] docs/sphinx: todo/wishlist"):
> It has been pointed out that calling this the wishlist is a poor name. 
> A better name would be the technical debt list.  I won't resend for just
> this, but please bear it in mind when considering the suggestion.

I approve of the idea of recording technical debt in-tree.

But, do we want it as a centralised list like this ?  I think we
currently have technical debt marked as comments nearby in the
relevant code or interface definitions.  That is often more natural
when developing.

How about instead of this, we invent a fixed string which we can grep
for, which we are to put next to poor areas of interface or code.

So in this case you would add a comment near @introduceDomain or
something.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-09-09 11:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22 19:20 [Xen-devel] [PATCH] docs/sphinx: todo/wishlist Andrew Cooper
2019-07-23  4:36 ` Juergen Gross
2019-07-23 13:38   ` Andrew Cooper
2019-07-23 15:30     ` Juergen Gross
2019-07-23 19:05       ` Andrew Cooper
2019-07-24  5:04         ` Juergen Gross
2019-07-23 13:53 ` Andrew Cooper
2019-09-09 11:02   ` Ian Jackson [this message]
2019-09-09 11:56     ` Andrew Cooper
2019-07-29  3:15 ` Rich Persaud
2019-09-06  7:48 ` Lars Kurth

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=23926.12631.330650.505179@mariner.uk.xensource.com \
    --to=ian.jackson@citrix.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=George.Dunlap@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=julien.grall@arm.com \
    --cc=lars.kurth@citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.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.