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 41BC58247 for ; Mon, 5 Sep 2011 22:39:28 +0000 (UTC) Received: (qmail 78954 invoked by uid 500); 5 Sep 2011 22:39:27 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 78871 invoked by uid 500); 5 Sep 2011 22:39:26 -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 78863 invoked by uid 99); 5 Sep 2011 22:39:26 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Sep 2011 22:39:26 +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; Mon, 05 Sep 2011 22:39:25 +0000 Received: by ewy5 with SMTP id 5so2369498ewy.6 for ; Mon, 05 Sep 2011 15:39:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.14.17.209 with SMTP id j57mr1373261eej.93.1315262363637; Mon, 05 Sep 2011 15:39:23 -0700 (PDT) Received: by 10.14.188.15 with HTTP; Mon, 5 Sep 2011 15:39:23 -0700 (PDT) In-Reply-To: <4E654A51.90508@laposte.net> References: <4E654A51.90508@laposte.net> Date: Mon, 5 Sep 2011 18:39:23 -0400 Message-ID: Subject: Re: What is needed for Support Forums to be fully integrated into the Apache OpenOffice.org project From: Rob Weir To: ooo-dev@incubator.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Sep 5, 2011 at 6:16 PM, Hagar Delest wro= te: Excellent, you agree to almost all of my proposals. If the other forum volunteers agree with what you wrote as well, then this is excellent progress! Let's look at the few items where there is still disagreement: >> 2) We need to develop a privacy policy for the Forums, also to be >> reviewed by the PPMC and Apache legal > > -1. Doesn't it come from the private forum issue? There is no issue. You'= ve > your private list, we have a private section. You want access to it? No > problem. > We handle governance issue in private? OK, we can change that. It was so > just to avoid all the lengthy discussions with users who just take the fo= rum > as a customer service and can't help complaining. > I mean site privacy policy, meaning what information (cookies, etc.) and personally identifying information you track for registered users as well as casual visitors to the website. This can sometimes be part of the Terms of Use document, but it is often in its own document. For example, the privacy policy used for the main OOo website was this: http://www.oracle.com/us/legal/privacy/index.html You link to that same policy as well within your policies page. Obviously that will need to be rewritten. But unless you have special needs (Google Analytics or other tracking software) this should be easy to draft. I assume you agree with this and your -1 was due to a misunderstanding. >> 6) Being listed as an "admin" or "moderator" on a public-facing Apache >> website suggests endorsement by the project, and aside from any >> enhanced Forum capabilities enhances your ability to keep order on the >> Forums. =C2=A0In other words, it is the star that makes the sheriff, not >> the gun. =C2=A0But this endorsement, to be meaningful, should be made >> authentic. =C2=A0 So Admins and Moderators should be approved by the PPM= C. >> This kind of routine approval is given all the time for those who want >> to be list moderators. =C2=A0I see no reason why we cannot, initially at >> least, simply receive a list of current volunteers to ooo-private and >> approve them all. > > -1. Same as Zoltan. Except if admins and moderators are PPMC themselves. > They are the ones who monitor the forum, know the users by reading their > posts and how they react. > So you want to continue picking your own admins and moderators, without ever consulting or reviewing these choices with the PPMC? I'm not sure that is really compatible with the idea of a project-wide meritocracy. You do a disservice to your own volunteers if you do not bring them to the PPMC, show their valued contributions and allow this to be recognized. Regardless of language, you should be able to say, in a sentence or two, what the volunteers have contributed, etc. This is a key role for all PPMC members, to be on the watch for future Committers and PPMC members. So I'm not sure your approach is really in the best long term interest of the project. What if we started with the admins? >> 7) Future grants of admin/moderator rights would require a proposal to >> ooo-dev seeking lazy consensus. =C2=A0Such a proposal could originate fr= om >> a forum volunteer or could originate from anyone on ooo-dev. This is >> no different than someone asking to be a moderator for a mailing list. > > -1. Same as above. > And for me, same as above. I think this goes against a project-wide meritocracy. But this is good progress. I think the remaining issue is around mapping of roles and what forum rights should require PPMC approval, signed iCLA's, Committer rights, etc. My preference is to start with the minimum, meaning just review and confirmation by the PPMC. But I hear others arguing for more stringent requirements, Regards, -Rob