aboutsummaryrefslogtreecommitdiff
path: root/docs/usage
diff options
context:
space:
mode:
authorDaniel Axtens <dja@axtens.net>2018-02-15 12:04:53 +1100
committerDaniel Axtens <dja@axtens.net>2018-02-22 02:06:36 +1100
commit3cfe618e5e8f9f079713324442c7c0777d2a7bcd (patch)
treebe40d56c8e5b7c8346e24d06b1d679df86b79c27 /docs/usage
parent9411c795758cf4b9a35ff5cf88bd36bf7a4f3eda (diff)
downloadpatchwork-3cfe618e5e8f9f079713324442c7c0777d2a7bcd.tar
patchwork-3cfe618e5e8f9f079713324442c7c0777d2a7bcd.tar.gz
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>
Diffstat (limited to 'docs/usage')
-rw-r--r--docs/usage/design.rst4
1 files changed, 0 insertions, 4 deletions
diff --git a/docs/usage/design.rst b/docs/usage/design.rst
index 2d8fea7..56719ee 100644
--- 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
----------------------------------------------------------