Reply to thread

Message

[QUOTE="Joshua J. Kugler, post: 4466687"]
<SNIP>

It really does come down to a matter of trust.  You can put strong
language in a license agreement, but it does rely on trusting your
customer to not "take your code and run."  Really.  There are lots of
examples, but a good one is:

[URL]http://www.brownbearsw.com/calcium/WhatIsIt.html[/URL]

Brownbear makes a great bit of calendaring software. So good in fact,
that I went with it for a project over every other open source
calendaring solution I could find.  Their entire product is written in
Perl, which means you get (and can modify, but not distribute) the
source code.  They are still going strong, if their client list
<[URL]http://www.brownbearsw.com/clients.html[/URL]> is any indication.  Can
someone steal your code?  Yep.  Do you then crawl in a hole and program
no more?  Well, that's really up to you.  Everything with possible
benefit involves risk, so you just have to decide how much risk you
want to take.  That's really the bottom line.

Sorry if that was a downer...wasn't meant to be.

j----- k-----
[/QUOTE]

Verification