[tahoe-dev] help! how do I manage dependencies on JavaScript code?

[David-Sarah Hopwood]

Kevin Reid wrote:
> On Sep 2, 2010, at 1:52, Zooko O'Whielacronx wrote:
> 
>> Brian wrote three patches for Tahoe-LAFS recently and so far I've only
>> applied two of them to trunk. The third one doesn't change behavior or
>> performance but adds beautiful, colorful JavaScript-based
>> visualization of download behavior. I haven't applied it because it
>> includes a copy of jquery and a copy of protovis. I don't like
>> including copies of third-party libraries in our source tree.
> ...
>> I also don't like adding hundreds of KB and tens of thousands of lines
>> of code to our source tree, and neither do I like adding compressed
>> (minified) things into our source tree instead of "the preferred form
>> for modification", i.e. raw human-oriented source.
> 
> In my opinion, adding additional visualization of Tahoe operations is
> much more valuable than avoiding temporarily (until we find a good
> solution) violating this dependency management principle.

I consider this principle to be very important indeed -- to the extent that
I think a project that intentionally violates it can't seriously claim to
be a security-oriented open-source project.

Note that we recently managed to fix the only (as far as I know) other
violation of this principle, ticket #1074. I would strongly dislike to
regress on this point.

-- 
David-Sarah Hopwood  ⚥  http://davidsarah.livejournal.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 292 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20100904/3d33ae9a/attachment.pgp>