On Fri, 06 Jul 2012 18:22:03 +0900
"Stephen J. Turnbull"
Mike Meyer writes:
Python-dev i'm not familiar enough with to formulate an opinion, but I think it could work well for python-ideas. You're missing the point. Improving the FAQ for python-*list* is a great idea, but Mr. techtonik proposes a FAQ for python-*ideas*. IOW, if the question is actually on-topic, the answers are reasons why something isn't going to ever be in Python.
That point I got.
True, often the explanation of why a proposed feature is inappropriate is of the form "this three-line function does the job", but if the question is really a FAQ, it presumably has been asked multiple times on python-list, and should be picked up there.
That I didn't, and it's fair enough. But the onus to fix this *still* falls on the people who are answering the same question over and over. They need to start submitting the answers to the FAQ (there is a history & design FAQ that would seem to be an appropriate place for them) rather than just to the list.
This worked very well for the FreeBSD FAQ, which is a fairly large document. No, it didn't. The FreeBSD FAQ is quite obviously not oriented to telling developers what isn't going to go into the next version of FreeBSD and why not.
If you're claiming that the FreeBSD FAQ technique didn't work well for it, then I disagree. That the FreeBSD FAQ has a different orientation is true, but not clearly relevant.
If people want to move ahead with this discussion, it really ought to move to python-list IMO.
Not in mine. The problem is repeated questions on -ideas. My proposed
solution has to be implemented by -ideas readers. They need to start
submitting frequently typed answers to the appropriate FAQ, not just
to the list.