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 36AEC7AD5 for ; Sun, 4 Sep 2011 18:13:29 +0000 (UTC) Received: (qmail 68688 invoked by uid 500); 4 Sep 2011 18:13:28 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 68656 invoked by uid 500); 4 Sep 2011 18:13:28 -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 68648 invoked by uid 99); 4 Sep 2011 18:13:28 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Sep 2011 18:13:28 +0000 Received: from localhost (HELO mail-ew0-f47.google.com) (127.0.0.1) (smtp-auth username robweir, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Sep 2011 18:13:28 +0000 Received: by ewy5 with SMTP id 5so1988065ewy.6 for ; Sun, 04 Sep 2011 11:13:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.14.5.206 with SMTP id 54mr907463eel.157.1315160006817; Sun, 04 Sep 2011 11:13:26 -0700 (PDT) Received: by 10.14.188.15 with HTTP; Sun, 4 Sep 2011 11:13:26 -0700 (PDT) In-Reply-To: <4E63BD2B.7070104@ellisons.org.uk> References: <4E6361AE.3070907@ellisons.org.uk> <4E638B48.9020200@ellisons.org.uk> <1315157787.63820.YahooMailNeo@web161423.mail.bf1.yahoo.com> <4E63BD2B.7070104@ellisons.org.uk> Date: Sun, 4 Sep 2011 14:13:26 -0400 Message-ID: Subject: Re: Dissatisfaction amongst the community admins, moderators and volunteers From: Rob Weir To: ooo-dev@incubator.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sun, Sep 4, 2011 at 2:02 PM, Terry Ellison wrote= : > On 04/09/11 18:36, Joe Schaefer wrote: >> >> Being a member-based organization the ASF requires >> that all foundation activities be subject to member >> scrutiny (with only a handful of operational exceptions). >> >> I would be perfectly satisfied if the private forums >> are fully archived and made available to any ASF member on >> request, without undue delay. > > +1 > I personally agree that we should have the absolute minimum as world-no > access, and clear and valid reasons to limit such access. =C2=A0I think t= hat it's > something that we could sell to the community. =C2=A0 The main hassle is = trolls > and flamers posting into the moderation forums, so it would be better to > limit write access. > I'd distinguish private forums where you discuss confidential/sensitive matters from public forums where forum volunteers discuss evolution of policies, future directions, etc., and reach consensus on these topics. For the private forums you have no need to fear trolls or flamers, right? In theory, we could get a troll post to ooo-private, but I've never seen that happen. As for the other forum, the public forum, I see no place for a read-only public forum where volunteers discuss things but the general public cannot post. If they flame or otherwise abuse the forum, then moderate them. That is one of your competencies. > I don't think that granting any ASF member read or read/write access to > *all* forums would be an issue as long as they broadly respect the rules = of > the forum. > The rules of the forum are subject to PPMC review and approval, just like any other part of the project. So I think it would be very unlikely that there would be a conflict between Apache Member expectations and forum rules. > Both of these options are reasonable and therefore could be quickly "sold= " > to the community, IMHO. =C2=A0However, this is a very different and easie= r pitch > than the hard line that Rob proposes. > > It would also be possible for someone to develop (as Rob suggests) a feed > from such forums into a DL such as ooo-private. =C2=A0However, this would= be a > non-trivial bit of custom code development as this isn't standard phpBB > functionality and the Logical Data Model for a rich-text Topic/Post parad= igm > would require a bit of massage to flatten into a plain text email format. > =C2=A0We might have resourcing issues here. > I think we need this part as well. Remember, Joe was speaking from a Member perspective. I am speaking from a PPMC perspective. There are similar, but non-identical concerns here. >