Return-Path: 
 <ooo-dev-return-2834-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 BE0F765D6
	for <apmail-incubator-ooo-dev-archive@minotaur.apache.org>;
 Tue,  2 Aug 2011 16:54:15 +0000 (UTC)
Received: (qmail 48811 invoked by uid 500); 2 Aug 2011 16:54:15 -0000
Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org
Received: (qmail 48769 invoked by uid 500); 2 Aug 2011 16:54:14 -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 48761 invoked by uid 99); 2 Aug 2011 16:54:14 -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 16:54:14 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of dennis.hamilton@acm.org
 designates 75.98.160.130 as permitted sender)
Received: from [75.98.160.130] (HELO a2s15.a2hosting.com) (75.98.160.130)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Aug 2011 16:54:06 +0000
Received: from 63-226-210-225.tukw.qwest.net ([63.226.210.225] helo=Astraendo)
	by a2s15.a2hosting.com with esmtpa (Exim 4.69)
	(envelope-from <dennis.hamilton@acm.org>)
	id 1QoIDx-00058J-EE
	for ooo-dev@incubator.apache.org; Tue, 02 Aug 2011 12:53:45 -0400
Reply-To: <dennis.hamilton@acm.org>
From: "Dennis E. Hamilton" <dennis.hamilton@acm.org>
To: <ooo-dev@incubator.apache.org>
References: <008a01cc4ee7$ca79e5e0$5f6db1a0$@acm.org>
	<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>
	<4E3745A4.1050404@ellisons.org.uk>
	<CAP-ksoj2_9ZHoLAhzawtMcQkbk2ZQhYBYqavv3NOymmhkYG88A@mail.gmail.com>
	<1312247462.2068.46.camel@jean-laptop15>
	<CAP-ksoiZu_9-a10x-0jM0dYSvpfA83WbX1C-dehNPwk=gLXBGw@mail.gmail.com>
	<1312252687.2068.81.camel@jean-laptop15>
	<CAP-ksohAgF5m0jtpN6sj5QaSsfOTvVeZ2dnTO1zsZYAWW_DwCA@mail.gmail.com>
	<CAOVv=gOaDdRExnR9HKDeoHz6=BzbkZPt7BzcewFmfRY=dDRjRA@mail.gmail.com>
	<4E37F50B.1040405@ellisons.org.uk>
	<CAP-ksohNZFBRdrSVw+kE67JksCD_5_9h80sOX+gfer4-4+rNwQ@mail.gmail.com>
	<4E380C1F.20509@ellisons.org.uk>
	<CAP-ksojnUTo71Fmks4LbJ8+LhZgStGgRsxgkRhBWAPrLPPTAfQ@mail.gmail.com>
	<4E382162.4070003@the-ma
 rtin-byrd.net> <CAP-ks
	oiCkAV=uBc-R7UU4w7wde9mfemRVvB+A1J9Fr-08tk3jQ@mail.gmail.com>
In-Reply-To: 
 <CAP-ksoiCkAV=uBc-R7UU4w7wde9mfemRVvB+A1J9Fr-08tk3jQ@mail.gmail.com>
Subject: RE: Refactoring the brand: Apache ooo + OpenOffice.org? (was
 re:OpenOffice.org branding)
Date: Tue, 2 Aug 2011 09:54:17 -0700
Organization: NuovoDoc
Message-ID: <011101cc5134$d1668d50$7433a7f0$@acm.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: 
 AQMLwMRZrpmbA0RR+3fLK/78OrmxZAGQeBuQATyCzakBykXJGgGcTFKwAXHLDlQCI322LAJaRXQvAdBP0kQAuNNDvwNcNAs6ApqT+4ECPX/zlQKp806WAiJNQSACGU5CpwLRmiFRAZmocYsBrAGUOgFcITsOkWEaOwA=
Content-Language: en-us
X-AntiAbuse: This header was added to track abuse,
 please include it with any abuse report
X-AntiAbuse: Primary Hostname - a2s15.a2hosting.com
X-AntiAbuse: Original Domain - incubator.apache.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - acm.org
X-Virus-Checked: Checked by ClamAV on apache.org

I'm not sure we are all talking about the same documentation.  I suppose =
the OOODEV wiki is the appropriate place to be doing that documentation, =
whatever it is, that is intended in the guidelines.

When we see the equivalent on OpenOffice.org, we should, on a per-case =
basis, redirect it to OOODEV perhaps.

But we do need to get to specific cases and handle them individually.

For a general-public editable wiki, I think sticking with the Creative =
Commons Attribution license should be just fine where it is already =
supplied.  More people seem to know what that is, and it is fully =
permissive without what appears to be such high ceremony as the ALv2.

And we should look around at some of the TLP project wikis that allow =
public contributions.

 - Dennis

-----Original Message-----
From: Rob Weir [mailto:apache@robweir.com]=20
Sent: Tuesday, August 02, 2011 09:28
To: ooo-dev@incubator.apache.org
Subject: Re: Refactoring the brand: Apache ooo + OpenOffice.org? (was =
re:OpenOffice.org branding)

On Tue, Aug 2, 2011 at 12:10 PM, Andy Brown <andy@the-martin-byrd.net> =
wrote:
> Rob Weir wrote:
>
>> At Apache, every committer has the ability to veto a change.  Not =
just
>> me.  Far from it.
>
> True.
>
>> In any case, in order to move the argument forward, I'd like to
>> reiterate thecific concerns that I have, to which I've seen no
>> response other than "we don't want to change".  But no one is
>> addressing the fundamental questions:
>>
>> 1) How do we ensure that the future documentation is under the Apache
>> 2.0 license so that it can be copied, modified and redistributed
>> freely by others?
>
> If you talking the wiki, instead of requiring an ICLA as a person has =
to
> create an account, why not make it part of that process that "All =
submitted
> contributions are under AL2 license".  Would that not be sufficient?
>

The IPMC guidance, via the Podling Guide that they have published [1] =
is:

"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."

I personally like your idea of having a click-through-license grant on
the wiki itself, either as part of account creation or on the edit
page itself.  But if we did that, I'd suggest some related issues to
address:

1) We shouldn't just ignore IPMC guidance.  There may be some
allowance for variation in procedures, but that should not be assumed.
 If we want to do something differently, then we need to write up that
proposal, get consensus here among PPMC members, and then take it to
the IPMC and probably Apache Legal Affairs (to review whatever
language we use).  I'd gladly support that.

2) We need a credible security mechanism for the wiki.  Today, for
example, it is not required for a user to give their real name (the
field is optional).  And the password can be as little as 1 character.
 (Yup, I just created an account with password=3D"x").  With 15,000
zombie accounts, lack of real names and the ability for users to
create trivially crackable accounts, it would be hard to really
identify a change to a particular person.

[1] http://incubator.apache.org/guides/sites.html

>> 2) How do we ensure that the documentation is under PPMC oversight =
and
>> remains high quality?
>
> I received a daily report of all changes to the wiki, there is also =
the
> option for "as done" report.  It would only take a few minutes to do a =
quick
> review of those changes, an revert them if needed.
>

OK.  Maybe that report could be directed to the ooo-commits list as =
well?

>> I'm open to discussions of various technical and procedural means to
>> achieve these goals.  But I am adamant in achieving them one way or
>> another.
>
> Would the above listed work?
>

I think that takes us in the right direction.  Thanks.

> Andy
>