wiki's for presentation
I've found that using wikis as a sort of developer-blog is extremely effective, especially with many people working on different aspects of one project at a time. I've personally used a few different flavors of wikis, and use the TWiki flavor quite regularly. With a few plugins, it becomes a dangerous tool :)
That said, i've seen a somewhat negative trend for some projects to start offering their entire site as a huge wiki. This might seem good in theory, but doesn't seem to work so well in practice. I often find myself spending more time looking for something that "used to be right there", and, in a few cases, finding that what I am looking for is a topic that needs to be created.
Wiki's have a purpose, and serve it very well, but it should be noted that applying them outside that purpose can be bad :) It shouldn't be used for serving up information en masse.
Re: auto* work fine
> projects. As you said, a well written
> configure script is a thing of wonder.
I'd have to mostly agree, most of the autoconf nghtmare things are from very vey poorly written configure scripts and/or makefiles. configure should never need to run more than once (should never happen in a makefile), among other stupid things developers often seem to do (this one has caused me to most problems).
to me, it almost seems like some projects put too much effort into their configure.. it _doesn't_ need to do all that much; check some headers, some library versions, and then some system stuff (type sizes etc), and then you should have essentially all that most projects will ever need.