Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 1A08F6349C9 for ; Thu, 16 Apr 2009 11:05:15 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 71100-04 for ; Thu, 16 Apr 2009 11:05:03 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by mail.postgresql.org (Postfix) with ESMTP id 3D0CA63491D for ; Thu, 16 Apr 2009 11:05:12 -0300 (ADT) Received: by yw-out-2324.google.com with SMTP id 3so317583ywj.73 for ; Thu, 16 Apr 2009 07:05:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.150.11.6 with SMTP id 6mr2105122ybk.4.1239890710644; Thu, 16 Apr 2009 07:05:10 -0700 (PDT) In-Reply-To: <16454.1239890476@sss.pgh.pa.us> References: <937d27e10904160107t6406b64cxddec956619c3374@mail.gmail.com> <16454.1239890476@sss.pgh.pa.us> Date: Thu, 16 Apr 2009 15:05:10 +0100 Message-ID: <937d27e10904160705y3f59662r3161d9bcd0add30b@mail.gmail.com> Subject: Re: Archives policy From: Dave Page To: Tom Lane Cc: PostgreSQL www Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.086 tagged_above=0 required=5 tests=AWL=0.086 X-Spam-Level: X-Archive-Number: 200904/69 X-Sequence-Number: 16936 On Thu, Apr 16, 2009 at 3:01 PM, Tom Lane wrote: > Dave Page writes: >> Can I get comments/objections/opinions on this draft policy please? >> http://wiki.postgresql.org/wiki/Archives_Policy > > Hmm, the first section suggests that there are cases where we will > de-archive messages, and then the second lays out all the reasons > why we won't and why it's useless to ask. =A0So I'm still confused > what the policy is. =A0I would be happy with a policy that says > "The archives are graven on stone tablets. =A0Don't bother asking." > but if we are willing to editorialize in extreme cases then maybe > the second part needs to be modified. I don't think we can refuse if there is anything illegal, defamatory, extremist, pornographic etc. It's everything else that should be set in stone though I think. I've since found similar policies on other sites (thanks Stefan) which might useful to look at/borrow. The W3C's for example seems pretty good: http://www.w3.org/Mail/ArchiveEditingPolicy --=20 Dave Page EnterpriseDB UK: http://www.enterprisedb.com