Return-Path: 
 <ooo-dev-return-2775-apmail-incubator-ooo-dev-archive=incubator.apache.org@incubator.apache.org>
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 206417D7F
	for <apmail-incubator-ooo-dev-archive@minotaur.apache.org>;
 Tue,  2 Aug 2011 00:33:08 +0000 (UTC)
Received: (qmail 30096 invoked by uid 500); 2 Aug 2011 00:33:07 -0000
Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org
Received: (qmail 30030 invoked by uid 500); 2 Aug 2011 00:33:07 -0000
Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ooo-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:ooo-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:ooo-dev@incubator.apache.org>
List-Id: <ooo-dev.incubator.apache.org>
Reply-To: ooo-dev@incubator.apache.org
Delivered-To: mailing list ooo-dev@incubator.apache.org
Received: (qmail 30022 invoked by uid 99); 2 Aug 2011 00:33:07 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Aug 2011 00:33:07 +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; Tue, 02 Aug 2011 00:32:57 +0000
Received: from host86-129-247-134.range86-129.btcentralplus.com
 ([86.129.247.134] helo=[192.168.1.69])
	by mail5.atlas.pipex.net with esmtpa (Exim 4.71)
	(envelope-from <Terry@ellisons.org.uk>)
	id 1Qo2uT-0000HV-1r
	for ooo-dev@incubator.apache.org; Tue, 02 Aug 2011 01:32:37 +0100
Message-ID: <4E3745A4.1050404@ellisons.org.uk>
Date: Tue, 02 Aug 2011 01:32:36 +0100
From: Terry Ellison <Terry@ellisons.org.uk>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.2.18) Gecko/20110617 Thunderbird/3.1.11
MIME-Version: 1.0
To: ooo-dev@incubator.apache.org
Subject: Re: Refactoring the brand: Apache ooo + OpenOffice.org? (was
 re:OpenOffice.org
 branding)
References: <008a01cc4ee7$ca79e5e0$5f6db1a0$@acm.org>
	<4E3476BB.8050506@gmail.com>
	<CAP-ksoiMVvxYJcMnJObA+JJndfC5-wrJki0MV0ZM8TwFbYLBMg@mail.gmail.com>
	<4E35D47F.6030308@gmail.com>
	<CAP-ksoiGsNW5UVkC_QOHLzmHt_3nEvE+KtgiqhJToAh3c7DRVQ@mail.gmail.com>
	<20110801081049.21190@gmx.net>
	<CAP-ksohDbBz=toPZh2_n-ueNGEKB8ngtvSJGQN0Zf3LRcw0j=Q@mail.gmail.com>
	<4E36BB1E.1050404@ellisons.org.uk>
	<CAP-ksogJ=oG3VkzZEzFDKOJfgnXGo=Fu8X2hADfoinbvEiDnoA@mail.gmail.com>
	<4E36D9E8.7020303@ellisons.org.uk>	<012401cc5091$132df240$3989d6c0$@acm.org>
	<CAP-ksog2Xi4rYGKBgv_kVto8GU_R6uP5L0jspuk5dbY1zVuRRA@mail.gmail.com>
	<CAOVv=gNynht+B9RJo5UGRue+wCOsbdBFp8=9S03je1Q4oHjdKA@mail.gmail.com>
	<4E372589.9050100@gmail.com>
 <CAP-ksogwik=HGE11bPK6AKt6HsGfWap2QRcV3Gz0NEzZ94Uexw@mail.gmail.com>
In-Reply-To: 
 <CAP-ksogwik=HGE11bPK6AKt6HsGfWap2QRcV3Gz0NEzZ94Uexw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailcore-Auth: 8445677
X-Mailcore-Domain: 884398
X-Virus-Checked: Checked by ClamAV on apache.org

<snip>
> Obviously different open source foundations or forges or projects will
> make this determination in different ways.  At Apache, the requirement
> is described as:
>
> "Using A Wiki To Create Documentation
>
> Podlings may use a wiki to create documentation (including the
> website) providing that follow the guidelines. In particular, care
> must be taken to ensure that access to the wiki used to create
> documentation is restricted to only those with filed CLAs. The PPMC
> MUST review all changes and ensure that trust is not abused."
>
> http://incubator.apache.org/guides/sites.html
>
> So documentation is special.  And a lot of what I see on the OOo is
> documentation, for end users as well as developers.  Build
> instructions, component architecture overviews, FAQ's, Admin Guides,
> etc.  These are all forms of project documentation.  I don't see how
> we avoid limiting write access to those pages.
>
> Remember, the thing that ensures that someone can take an Apache
> project and create a new distribution or a new derivative of it, is
> the Apache 2,0 license.  That ensures that they can take the code, the
> documentation, translations, etc., and reuse it.  This includes the
> documentation.
Rob,

OOo isn't a new project.  It's been in continuous development for some 
15 years, and has a user population in millions.  The active support 
community is in hundreds if not thousands.  Before we use the letter of 
some guideline to abandon a huge body of knowledge and good-faith 
contributions perhaps we should seek clarification on the interpretation 
of such guidelines by the appropriate Apache authorities?

I agree with you that the documentation that is formally distributed 
with the product such as the online documentation must be properly 
licensed to be distributed, as does website content which carries the 
Apache logo and is "Apache content".

But does this really apply to a community wiki, where some user has 
created a HowTo in Russian on using DataPilots in Calc, say.  Are you 
saying that he will have to sign an iCLA or we delete the content.  If 
some user spots a typo in the documentation and corrects it in the wiki, 
are you saying that we must ignore this unless she signs an iCLA?

I apologise if these seem trivial, but the Community wiki and forums by 
nature contain content generated by the community, and there is a true 
continuum here.  Surely, an end-user product as complex as OOo can only 
succeed in a FLOSS world if it embraces rather than rejects a community 
support model.