Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6328A83BE for ; Mon, 5 Sep 2011 07:36:32 +0000 (UTC) Received: (qmail 2455 invoked by uid 500); 5 Sep 2011 07:36:30 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 2159 invoked by uid 500); 5 Sep 2011 07:36:21 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 1895 invoked by uid 99); 5 Sep 2011 07:36:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Sep 2011 07:36:18 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [94.136.40.64] (HELO mailex.mailcore.me) (94.136.40.64) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Sep 2011 07:36:10 +0000 Received: from host86-129-239-17.range86-129.btcentralplus.com ([86.129.239.17] helo=[192.168.1.69]) by mail6.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from ) id 1R0TiZ-0000tt-Kw for ooo-dev@incubator.apache.org; Mon, 05 Sep 2011 08:35:44 +0100 Message-ID: <4E647BD4.1090103@ellisons.org.uk> Date: Mon, 05 Sep 2011 08:35:48 +0100 From: Terry Ellison User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.21) Gecko/20110831 Thunderbird/3.1.13 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: Dissatisfaction amongst the community admins, moderators and volunteers References: <4E6361AE.3070907@ellisons.org.uk> <4E638B48.9020200@ellisons.org.uk> <1315157787.63820.YahooMailNeo@web161423.mail.bf1.yahoo.com> <4E63BD2B.7070104@ellisons.org.uk> <4E63EFA4.3050701@ellisons.org.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailcore-Auth: 8445677 X-Mailcore-Domain: 884398 X-Virus-Checked: Checked by ClamAV on apache.org On 04/09/11 23:22, Ross Gardler wrote: > On 4 September 2011 22:37, Terry Ellison wrote: >> On 04/09/11 22:13, Dave Fisher wrote: >>> On Sep 4, 2011, at 11:13 AM, Rob Weir wrote: >>> >>>> On Sun, Sep 4, 2011 at 2:02 PM, Terry Ellison > ... > >>> If several members of the PPMC are participating as forum volunteers and >>> all the conversations in these private lists are immutable and available to >>> the whole PPMC and Apache Members why would we need a feed to ooo-private? >>> This really isn't any different from the PPMC trusting a small number of ML >>> moderators. >> One specific technical point: the content of no forums or posts is >> immutable. Originators and moderators can change their content or even >> withdraw it by deleting the post. We do this regularly with spam. No forum >> models that I am familiar with embeds versioning. > One of the reasons for allowing Member level access to PMC lists is to > ensure that there is some way to escalate a dispute to an independent > third party. This happens very rarely, but when it does it really is > not fun for the people involved, as you can imagine. > > One other reason (which fortunately is even rarer) is that we > sometimes need to provide materials as part of some court case or > other. IN these circumstances lawyers spend a long time ensuring that > no unnecessary information is shared and that private information is > provided with the appropriate confidences. > > Requiring those people to trawl logs to ensure no edits have been made > in private discussions is adding unnecessary work that, I hope, can be > avoided. > > Would it be possible/make sense to provide a read-only archive of the > private forums in the private PMC list? I'm not saying discussion > should necessarily move to that list (although I think this should be > the end goal, but lets take baby steps and keep options open). This > approach would have the added benefit of providing PPMC oversight on > the private discussions. > > I'm not concerned about edits in public posts, particularly with the > existing practice of marking such posts as edited. > > Ross Yes it is technically possible to do this Ross. The short term constraint is a matter of scheduling resource to this.