+1 for the idea, and +1 for the Zork reference. Hello sailor.
On 4/8/2010 1:11 AM Greg Stark wrote:
I've often said in the past that we have too many mailing lists with overlapping and vague charters. I submit the following thread as evidence that this causes real problems. http://archives.postgresql.org/message-id/g2o4b46b5f01004010610ib8625426uae6ee90ac1435...@mail.gmail.com Because the poster chose to send it to pgsql-admin instead of pgsql-general (or pgsql-bugs) very few of the usual suspects had a chance to see it. 7 days later a question about a rather serious database corruption problem had no responses. I've never understand what the point of pgsql-admin is; just about every question posted is an "admin" question of some sort. Likewise I don't think we should have pgsql-performance or pgsql-sql or pgsql-novice -- any thread appropriate for any of these would be better served by sending it to pgsql-general anyways (with the exception of pgsql-performance which has a weird combination of hacker threads and user performance tuning threads). Sending threads to pgsql-general would get more eyes on them and would avoid a lot of the cross-posting headaches. What would someone subscribed to one of these lists but not pgsql-general get anyways but some random sample of threads that might be vaguely performance or admin related. They would still miss most of the administration and performance questions and discussions which happen on -general and -hackers as appropriate.
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
