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: local policy)
Message-ID: <4DF7D7AB.10009@xs4all.nl>
Date: Tue, 14 Jun 2011 23:50:35 +0200
From: Simon Brouwer <simon.oo.o@xs4all.nl>
Reply-To: simon.oo.o@xs4all.nl
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; nl;
 rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: ooo-dev@incubator.apache.org
Subject: Re: Wiki for the project
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>
In-Reply-To: <B5122017-C871-4CC7-83F3-01928E28DA01@comcast.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Op 14-6-2011 22:46, Dave Fisher schreef:
>>> I prefer not to mix developer/project-facing material and user-facing
>>> material on the same wiki, because it is difficult enough to maintain
>>> a consistent voice for the user-facing material.  Also, users should
>>> be able to easily subscribe to and make additions to the
>>> user-oriented wiki without contending with the project-oriented
>>> organization.
>>>
>>> That was my thinking.
>> I see and I get your point now. I agree we need a certain
>> degree of separation but that does not necessarily need to
>> be in the form of two distinct wikis.
>>
>> Having two sections in a common wiki would allow to easily
>> move content over, as occasionally done with OOo where
>> feature developers kept draft documentation for their
>> features while in development and then docs folks
>> clean it up and move the content over to the documentation
>> section.
>>
>> Also, a common entry portal then leading off to user-facing
>> documentation or developer documentation or project related
>> pages would reveal the mechanics of the project to those
>> who are unfamiliar with how open source projects work and
>> may help make this more transparent.
> If we want to have different groups of users with update rights we should definitely have two wikis.
>
> See https://cwiki.apache.org/CWIKI/ for the instructions regarding confluence.
>
> We could start with the following confluence wiki spaces:
>
> (1) ooo-dev - for developer facing documentation.
>
> (2) ooo-user - for a prospective user wiki. We can debate whether confluence, MediaWiki, moinmoin or ? are best by experimenting with various approaches.
>
> (3) ooo - for the project website. There are options here as well CMS, moinmoin, Forrest, ...

What would the ooo wiki contain that wouldn't fit in the ooo-dev wiki?

-- 

Vriendelijke groet,
Simon Brouwer.

| http://nl.openoffice.org | http://www.opentaal.org |