Re: Policy for expiring lists WAS: Idea for a secondary list server

Josh Berkus wrote:

> OK, here's my proposal:

The archival issue, together with the possibility of reactivation, is
precisely what makes deletion difficult.  What you seem to want is not
to delete them, but to make them inactive, so that they can be activated
later for whatever reason.  Right?

(Majordomo does have the feature to set lists as inactive, which means
no email is distributed through them.  They can later be reactivated.)

Your comments on the usefulness of the SFPUG list are pretty surprising.
If SFPUG works well without a list, why do other PUGs need one?
Maybe mailing lists for PUGs are a thing of the past -- perhaps we need
to be thinking on getting the @postgres twitter account to re-tweet
announcements posted by PUGs, or something like that, more suited to
today's usage of comm channels rather than 1990's.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services