[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: VOLUNTEER: Port dev docs to a wiki

From: Daniel Berlin <dberlin_at_dberlin.org>
Date: 2005-10-21 04:07:01 CEST

On Fri, 2005-10-21 at 02:56 +0200, Branko ╚ibej wrote:
> Justin Erenkrantz wrote:
>
> > --On October 20, 2005 8:32:08 PM +0200 Branko ╚ibej <brane@xbc.nu> wrote:
> >
> >> If the wiki can be made to commit changes to our repository, then I'll
> >> support CTR for the docs, because we'll get the usual commit e-mails for
> >> review.
> >
> > CTR for everyone or just the committers? -- justin
>
> Ah, good question. Only for committers, but maybe we should lower the
> bar for getting docs commit access. Anyone who's willing to take the
> time to improve our documentation gets my +1.
>
>

Maybe this is the time where i chime in and say i've been fighting for a
while to try to get gcc to put a lot more of it's docs in wiki form, and
just generate xhtml/pdf versions from those.

Be glad you guys don't have to deal with texinfo.

I also set up gcc's wiki, and can tell you if you want something you can
maintain the *code* for, don't use phpwiki.
We're moving to moin-moin.

It even supports writing pages in docbook, and having them display
nicely as html.

(It has a couple "formatters", which allow you to write wiki page in
things other than the moin-moin normal wiki syntax. I wrote one for
texinfo that works nicely).

I'm +1 on having a wiki.

The only thing i can say is be careful what software you choose. Not
necessarily for syntax, but for being able to maintain it. Some of the
more well known wikis apparently have very bad codebases from a
maintainability standpoint.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 21 04:07:46 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.