[dev] Horde framework package directory structure

[Chuck Hagenbuch]

Quoting Chuck Hagenbuch <chuck at horde.org>:

> The questions are: doc vs. docs, lib vs. src, and test vs. tests. I
> have an aesthetic leaning towards doc, lib, test, which are consistent
> with ruby and python and have a great unix-y three-letter cleanliness
> to them. However, one could also make an argument for being consistent
> with PEAR2:
>
> http://wiki.pear.php.net/index.php/PEAR2_Standards#Directory_structure
>
> However, we can always bundle PEAR dependencies in our own structure,
> and advanced users can just put our lib directory and PEAR2's src
> directory both into the include_path (and I just don't like src - src
> is for compiled languages, it seems to me).

I also meant to say that I lean against PEAR2's usage because it's  
internally inconsistent - doc, src, and tests. One plural, two  
singular. Plus it adds a top-level examples dir - the only other  
plural - instead of sticking that inside doc.

-chuck