[dev] [cvs] commit: horde/docs LICENSES horde/services/csstidy class.csstidy.php class.csstidy_optimise.php class.csstidy_print.php data.inc.php

[Jan Schneider]

Zitat von Chuck Hagenbuch <chuck at horde.org>:

> Quoting Michael M Slusarz <slusarz at horde.org>:
>
>> It also makes more sense to move the info located on the wiki to a
>> file (LICENSES?) distributed with the code itself.
>
> I've seen other projects with a directory of licenses, so that we  
> can just toss each file in there.
>
> And from a followup message:
>
>> 2.) This approach makes the most sense - we (I) just need to remember
>> to import the entire unchanged file into git first, and then make any
>> local modifications (if necessary) in a separate commit.  Don't know
>> if there is a place to document this or if this is something we just
>> need to self-police.
>
> Sounds like a brief "Use of 3rd party libraries" section should be  
> added to the wiki.

Or maybe rather CODING_STANDARDS.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
URL: <http://lists.horde.org/archives/dev/attachments/20090531/dcb8030f/attachment.bin>