Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Sun, 4 Sep 2011 18:29:55 +0100
From: Rory O'Farrell <ofarrwrk@iol.ie>
To: ooo-dev@incubator.apache.org
Subject: Re: An invitation to committers to the OOo Community Forums
Message-Id: <20110904182955.1d00deb656dc50a46f93296f@iol.ie>
In-Reply-To: 
 <CAP-ksoi63n3wKJ-=CcQUMYd4T3ngT3m4NyZY3BsumhRp-EgTkw@mail.gmail.com>
References: <4E5FB6F0.2060504@ellisons.org.uk>
	<CAP-ksojj4z0Ne45FcPcu-yUstQ5MdAf4gYqWdLZvHCgbFbRDKQ@mail.gmail.com>
	<014801cc68e5$d5fd5290$81f7f7b0$@acm.org>
	<CAP-ksoiCVS5F6wG=JrwpuZYCuSte6WpdkNhZZT9B+xLWS+QfQw@mail.gmail.com>
	<1314911707.1938.55.camel@sybil>
	<CAP-ksoj=tqVBoFTso7jHc4qjki6giBqBYBAe5oFn7OKo=p5L9Q@mail.gmail.com>
	<4E60193C.4090304@shanecurcuru.org>
	<4E606C19.40005@ellisons.org.uk>
	<CAPFNckir_z5XzckS-1Hf-CvjKaDXThOr43gk8uPUiSXqOfwfKQ@mail.gmail.com>
	<CAP-ksogPkfM88_Tis+7BOBXroTG_qGOymzGADu-p3znjHZ+NMg@mail.gmail.com>
	<CAPFNckg38wiNbz22mBd6EGDwLYVk2s=iTzK1_Ui8+f4=TSV6Eg@mail.gmail.com>
	<CAP-ksohZzsKwb8fL=iyE37ea=ii9-62VW5BHaHOeQ9ZZ7zKRtg@mail.gmail.com>
	<CAPFNckhs3T9outbU6_qSbAz0rJwzs6Y+8BJT4T+OD3_jQV92Fw@mail.gmail.com>
	<CAMwm1vHGpc4p0qr_dqwXcZU=0m4WYHiAA+wGbB0-TU4Qv53aeA@mail.gmail.com>
	<CAPFNckiBX+R7B+XbCQ4DK4qLeTx8oq7c3Sueirs+iaebyrwaUQ@mail.gmail.com>
	<CAP-ksoi63n3wKJ-=CcQUMYd4T3ngT3m4NyZY3BsumhRp-EgTkw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Sun, 4 Sep 2011 12:35:05 -0400
Rob Weir <robweir@apache.org> wrote:
> This is really easy to resolve:
> 
> 1) Discussions on evolving forum policies and rules must occur on
> ooo-dev.  These are tantamount to proposals, and they are subject to
> Apache Way decision making, just like any other part of the project.
> If I wanted to suggest a different editing policy for the community
> wiki, or a new moderation policy for ooo-users, I would be slapped
> down if I raised it on ooo-private.  The transparency principle
> applies equally to the forums.

Discussions behind the scene are not proposals; they emerge into one or more consensuses, which are then considered as proposals and a selection made. I doubt there will be much objection to this.
> 
> 2) Non-confidential, day-to-day operations of the forum should occur
> in a publicly-readable forum, or on a new public mailing list. I'd let
> the forum volunteers decide which.

Such a publicly readable form is the Forum, which is openly accessible; to post to it requires a User to choose a Username and to indicate his OS and version of OOo or OOo fork,
> 
> 3) Private discussions on confidential matters, including your
> grandmother, occur either on ooo-private or on a private forum that
> echos its posts to ooo-private.  Again, I'd let the forum volunteers
> decide which.

These occur on three dedicated channels as I outlined earlier; the offer is there to allow interested Apache personel access to them immediately.  A more public (even if still private mechanism) can be worked out, such as that they can be automatically echoed to a monitorong list.  Much of the discussion is merely administrative and may increase the load on such monitoring lists.

I will echo this posting to the private OOo channels - perhaps we are now getting somewhere?


-- 
Rory O'Farrell <ofarrwrk@iol.ie>