Customers need Apache 2.0

[Ben Hyde <bh...@gensym.com>]

Just for fun lets enumerate the classes of
customers using Apache.

 1. - Folks running Web Sites
 2.  - Big manly dudes
 3.  - Nice simple dudes
 4. - Folks writing modules
 5. - Folks writing Apache
 6. - Craftsmen maintian it.
 7. - Folks repackaging Apache
 8. - Dudes from some cool "emerging market"
 9.  - Windows dudes
 10. - Random server writers needing a code base

That some polymaths even fall all these catagories
is only hope that "nice simple dudes" have that
free software will address their needs.

Are there other classes of users?

It's not uncommon for a software rev to become
the prisoner of one of these.

The process I've found useful is to:
 A. enumerate all the gifts.
 B. let the users vote.
 C. ignore vote and do what's best.
 D. later: argue if step B or C was at fault

Step A works nicely if you enumerate fast and
furious a lot of gifts.  Step B does not work
unless you structure it right, give each voter a
pool of tokens and let them spread the tokens over
the possiblities.  C is necessary since: your
voting pool won't accurately reflect your user
population (or your desired user population), and
meanwhile you can't do anything if the labor isn't
interested.

    - ben hyde

ps. The build worked fine, except NT where the
machine locked up during the build.