[dev] Horde framework package directory structure

[Michael Rubinsky]

Quoting Chuck Hagenbuch <chuck at horde.org>:
<snip>
> 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).
>
> Thoughts?

lib/ makes more sense to me then src/, but for some reason, docs/  
seems more appropriate to me then doc/ although I don't feel *that*  
strongly about it.  Perhaps it's because our apps contain docs/  
directories, and not doc/.


Thanks,
mike

--
The Horde Project (www.horde.org)
mrubinsk at horde.org

"Time just hates me. That's why it made me an adult." - Josh Joplin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 2200 bytes
Desc: PGP Public Key
Url : http://lists.horde.org/archives/dev/attachments/20080222/c4962e93/attachment.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: PGP Digital Signature
Url : http://lists.horde.org/archives/dev/attachments/20080222/c4962e93/attachment-0001.bin