Dropped doxygen

[Benedikt Meurer]

Olivier FOURDAN wrote:
> 1) Do we include configure, Makefiles and docbook documentation in CVS
> 2) Do we exclude them all

We should not limit our policy to either "include everything" or "exclude 
everything", but we should doe "fine-tuning". Besides that I'd like to see an 
up-to-date HTML API documentation in some central place (on the website or in 
CVS, or both). I already tried to discuss this issue some time ago, so here we 
go once again:

  1) Can we have an API documentation area on the website (maybe something 
like developer.xfce.org to be consistent)?

  2) Can we have a cronjob on the webserver or some other computer to generate 
the API docs nightly?

 From my experience, these question are more important than what to put in CVS 
exactly, since most of the people I know tend to use the online documentation 
or download documentation tarballs from the developer websites rather than 
checking out documentation from CVS. Lets first discuss what to do with 
documentation and then decide how to handle it best.

> 3) Shouldn't we switch to subversion ? :)
> 
> (Ok, question #3 is definitely another matter :)

*Plonk*

> Cheers,
> Olivier.

regards,
Benedikt

-- 
NetBSD Operating system:                       http://www.NetBSD.org/
pkgsrc "Work in progress":                  http://pkgsrc-wip.sf.net/
XFce desktop environment:                        http://www.xfce.org/
German Unix-AG Association:                   http://www.unix-ag.org/
os-network:                                 http://www.os-network.de/

OpenPGP Key: http://www.home.unix-ag.org/bmeurer/#gpg