Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of dave2wave@comcast.net
 designates 76.96.30.17 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: <4DF7BF03.6000804@gmail.com>
Date: Tue, 14 Jun 2011 13:46:06 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B5122017-C871-4CC7-83F3-01928E28DA01@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>
To: ooo-dev@incubator.apache.org

>> 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.
>>=20
>> That was my thinking.
>=20
> 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.
>=20
> 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.
>=20
> 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, ...

I'll make the request from Infra. I have experience with Confluence and =
will do the initial setup once Infrastructure creates the space(s). I'll =
add all committers that are on the project page to the committers group =
as we go.

Regards,
Dave

>=20
> Frank
>=20
>> -----Original Message----- From: Frank Peters
>> [mailto:frank.thomas.peters@googlemail.com] Sent: Tuesday, June 14,
>> 2011 10:48 To: ooo-dev@incubator.apache.org Subject: Re: Wiki for the
>> project
>>=20
>> Dennis,
>>=20
>>> Um, so where would that and other thoughts be on-topic?  I have
>>> many thoughts about on-/off-line help bridging too.  Is this the
>>> ooo-issues list.  (I really must catch up on my reading of the
>>> groundrules here.)
>>>=20
>>> I take it that the on-line help is under Oracle copyright and can
>>> be/has been licensed by Oracle then?
>>=20
>> Yes. "Online" help (that is, the application help) is a module in the
>> source tree (helpcontent2) and under Oracle Copyright. I guess it was
>> part of the bits donated to Apache?
>>=20
>>> What do you mean by one wiki for both the project and the product?
>>> I
>>=20
>> One for contributors (project planning, drafts, developer docs +
>> guidelines) one for consumers (user manuals, online help, training,
>> tutorials).
>>=20
>>> am always concerned that non-developing users, even power users
>>> have collaborative resources that work in the context of their
>>> needs and interests.
>>=20
>> I'm sorry but I don't think that I get your point here.
>>=20
>> Frank
>>=20
>=20