> msg247162
> It's not like we don't have several people who have macros to say the
> above (and more politely than I did) who typically respond within hours
> to off-topic posts.  What more could a FAQ say?

A FAQ would explain the "mistakes" and suggest solutions.  The content of the FAQ could also be copy-pasted directly in the reply, but at least we have standard replies for common cases that everyone can use, rather than private macros (with different wording) that just a few can use.

Off the top of my head, the common cases are:
* mails asking for help on python-dev/ideas that should go on python-list and similar;
* mails proposing ideas on python-dev that should go to python-ideas;
* mails reporting bugs or including patches should go to the bug tracker;
* mails suggesting the inclusion of a feature that doesn't belong to the stdlib;
* mails suggesting the inclusion of a feature that should be submitted and tested on PyPI first;
* mails suggesting the inclusion of an existing package that is better off on PyPI rather than in the stdlib;
* mails suggesting ideas that have already been discussed/submitted;

I think a FAQ covering these would help solve these threads quickly and save developers time.

Note that something similar was already being discussed by Nick in https://mail.python.org/pipermail/python-committers/2015-July/003454.html