Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jackrabbit-dev@incubator.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Subject: Re: Wiki for Jackrabbit
From: Rolf Kulemann <roku@apache.org>
To: jackrabbit-dev@incubator.apache.org
In-Reply-To: <96DBDA2A-2461-11D9-9450-000A95CD7D6A@luminas.co.uk>
References: <4178B7A2.9060408@wyona.com>
	 <5C751A56-245E-11D9-BBD4-000393753936@gbiv.com>
	 <96DBDA2A-2461-11D9-9450-000A95CD7D6A@luminas.co.uk>
Content-Type: text/plain
Message-Id: <1098517962.4352.73.camel@swan.rkunet.org>
Mime-Version: 1.0
Date: Sat, 23 Oct 2004 09:52:42 +0200
Content-Transfer-Encoding: 7bit

On Fri, 2004-10-22 at 21:35, Andrew Savory wrote:
> Hi,
> 
> On 22 Oct 2004, at 20:12, Roy T. Fielding wrote:
> 
> > I'll create the wiki when I have time to do so (sometime today).
> 
> Cool, thanks.
> 
> > However, I don't want to see a bunch of crap posted on a wiki that
> > belongs in the real documentation.  Why can't folks just post patches
> > to the xdocs?
> 
> That's a bit harsh.

Up to a certain point I agree with Roy, since one needs to migrate the
doc later (painful?) to the xdoc or whatever.

> 
> Wikis have proven themselves time after time as a great way for rapid 
> prototyping of documentation. Patches to xdocs doesn't offer the 
> instant gratification of wikis, or the ability to edit/review/edit in 
> such a tight circle.

I also agree with you. Seems we need and integrated documentation system
with workflow which directly has impact to the xdoc in svn or cvs.

But since we do not have such a system, yet, a wiki is good for rapid
docu prototyping and users can help without messing around with patches.

The barrier for writing docu should be as low as possible.

-- 
Rolf Kulemann