Lighttpd

Assumptions
As the Lighttpd 1.5.x branch is starting, there are a couple of deficiencies in the development process that should be addressed.

The overall impression of the quality of Lighttpd 1.4.x as a product can vary quite a lot depending on where you're looking. So, seeing Lighttpd in retrospect:

=== Basic design, features, performance ===
There is no denying that "less is more" sometimes, Lighty being one of those cases. The basic design laid out by Jan is ambitious enough to provide a good number of features, yet retaining the "lightweight" overall feel of the program.

• Overall: Good.

=== The code ===
It builds without ''too'' many warnings ;-). The fact that it ''has'' a test framework is just super.

• The tests need to be maintained (maybe assigned/delegated to a specific developer).
• Successfully executing the tests should be a part of the release procedure :-)

=== Documentation ===
We have several up to date tutorials on the wiki, that's great. But for reference?

• Most of the documentation could move from the main web page to the wiki (to enable joint maintenance).

=== Project group ===

• Overall: What persons, other than Jan, are SVN commiters? What other people are accountable, and for what?

(... more to come)