Don't aim to have patchwork send email

Getting things like SPF and DKIM right for this would be nigh-on
impossible, plus it would mean sysadmins would have to let patchwork
send email, which is a risk to the reputation of their systems.

Let's just aim for being a read-only representation of the mailing
list for now.

Reviewed-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
Signed-off-by: Daniel Axtens <dja@axtens.net>

diff --git a/docs/usage/design.rst b/docs/usage/design.rst
index 2d8fea7d9a4351db98a0b9e8a0ab14366cfd0045..56719eed4576fc4ed9dd71018553e7790e339ace 100644 (file)
--- a/docs/usage/design.rst
+++ b/docs/usage/design.rst
@@ -10,10 +10,6 @@ be two forums of discussion on patches, which fragments the patch review
 process. Developers who don't use Patchwork would get left out of the
 discussion.
 
-However, a future development item for Patchwork is to facilitate on-list
-commenting, by providing a "send a reply to the list" feature for logged-in
-users.
-
 Don't pollute the project's changelogs with Patchwork poop
 ----------------------------------------------------------