Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of dave2wave@comcast.net
 designates 76.96.30.80 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Wiki for the project
From: Dave Fisher <dave2wave@comcast.net>
In-Reply-To: <7D6EB66F-37A0-4A17-BF66-7CCB4D2F4FB9@comcast.net>
Date: Tue, 14 Jun 2011 15:46:58 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8D4A7709-B6F1-4BAA-BC26-06F77BFD3245@comcast.net>
References: <4DF6C223.9080508@gmx.ch>
 <BANLkTi==7v2gdS82EYmS504gMEzYoA4L=Q@mail.gmail.com>
 <4DF75A21.8080001@gmail.com> <00a701cc2aac$de6c9020$9b45b060$@acm.org>
 <4DF796FB.8060208@gmail.com> <00f001cc2ab8$6feffe50$4fcffaf0$@acm.org>
 <4DF79EE9.70907@gmail.com> <014201cc2aca$cf1fa620$6d5ef260$@acm.org>
 <4DF7BF03.6000804@gmail.com>
 <B5122017-C871-4CC7-83F3-01928E28DA01@comcast.net>
 <4DF7D0D0.1000700@gmail.com>
 <BE7AA5BC-571E-4F05-9EEA-BA88FF0FD9FB@comcast.net>
 <BANLkTinLUXbz___CwRBx+__jSDDEHNhGLw@mail.gmail.com>
 <7D6EB66F-37A0-4A17-BF66-7CCB4D2F4FB9@comcast.net>
To: ooo-dev@incubator.apache.org


On Jun 14, 2011, at 3:35 PM, Dave Fisher wrote:

>=20
> On Jun 14, 2011, at 3:08 PM, Rob Weir wrote:
>=20
>> Note the requirements here under "Using a wiki to Create =
Documentation".  It
>> looks like we need to restrict write access to that wiki to those who =
have
>> returned iCLA's to Apache.
>>=20
>> http://incubator.apache.org/guides/sites.html
>>=20
>> I wonder if this becomes easier if we segregate the documentation =
onto its
>> own wiki?
>=20
> Yes. See =
https://cwiki.apache.org/confluence/display/CWIKI/Index#Index-Butwhatifwew=
ouldlikethecommunityatlargetohelpmaintainthespace%3F
>=20
> I suggested ooo-dev and ooo-user as different spaces because=20
>=20
> (1) The list of who edits and who comments can differ.
>=20
> (2) It is not known what Wiki our user facing community will really =
want to use while ooo-dev wants a wiki now.

Now I see this: =
https://cwiki.apache.org/confluence/display/CWIKI/Index#Index-Canweusethea=
utoexportsiteaspartofourmainwebsite%3F

We are being directed towards the CMS - or other SVN based tools of the =
project website. I wonder...

Regards,
Dave

>=20
> Regards,
> Dave
>=20
>=20
>=20
>>=20
>> -Rob
>>=20
>>=20
>> On Tue, Jun 14, 2011 at 5:53 PM, Dave Fisher <dave2wave@comcast.net> =
wrote:
>>=20
>>>>> If we want to have different groups of users with update rights we
>>>>> should definitely have two wikis.
>>>>>=20
>>>>> See https://cwiki.apache.org/CWIKI/ for the instructions regarding
>>>>> confluence.
>>>>>=20
>>>>> We could start with the following confluence wiki spaces:
>>>>>=20
>>>>> (1) ooo-dev - for developer facing documentation.
>>>>>=20
>>>>> (2) ooo-user - for a prospective user wiki. We can debate whether
>>>>> confluence, MediaWiki, moinmoin or ? are best by experimenting =
with
>>>>> various approaches.
>>>>=20
>>>> I don't understand, you just said you would start to create a
>>>> Confluence ooo-user space to debate whether to use a different
>>>> engine?
>>>>=20
>>>> There is probably overlap between (1) and (2) so it needs to
>>>> be clearly defined what goes where. With (1) you are probably
>>>> referring to core development (coding OOo), but there is also
>>>> extension development (using UNO to develop extra functionality)
>>>> or office automation that probably are better placed in (2) (for
>>>> the developer-user).
>>>=20
>>> For (1) you understand me correctly. This is the space we need now =
to start
>>> doing all the planning and development blueprints.
>>>=20
>>> For (2) I mean a possible way to handle the package user and/or =
developer
>>> user documentation that will be migrated from the wiki at =
openoffice.org.
>>>=20
>>> BTW - It should not be hard to move content between two confluence =
spaces
>>> if it is put in the wrong location.
>>>=20
>>>>=20
>>>> If we plan to reuse existing wiki content for docs, it would be
>>>> easiest to continue to use MediaWiki (if this is an option)
>>>> since this is where all content currently is. A lot of the
>>>> content in the docs section uses MW features like
>>>> subpages, auto page lists, templates/transclusions etc that
>>>> may be cumbersome to migrate.
>>>=20
>>> To use MediaWiki someone will need to contribute at =
infrastructure-dev.
>>> Otherwise it is moinmoin or confluence. I don't care so much, but =
confluence
>>> is well supported here at Apache so it is an easy choice.
>>>=20
>>> For (3) the options are greater and we can change.
>>>=20
>>> I know we need (1) and it is not much harder to do (2) and (3)
>>> prospectively and let the rest of the PPMC decide.
>>>=20
>>> Here is the jira issue:  (INFRA-3684) Create 3 CWiki Spaces for =
OpenOffice
>>>=20
>>> Regards,
>>> Dave
>>>=20
>>>>=20
>>>> Frank
>>>=20
>>>=20
>=20