My thoughts:

Once again making money is the reason to own and conduct a business. Unfortunately, in this scenario you have "personal" reasoning that can be used. It must all be weighed out impartially with "the business" first and foremost in mind.

The one point that I don't think you addressed directly, is the issue of "proprietary" code. If your "business" uses this code, and you "give" it to the client, they could then claim it as their own and stop you from using it. Management needs to be alerted to this fact and quickly.

Since the client has not paid for the development of the code, it would be a really poor business decision to "give" it to them. They should be charged for it. It would also be a bad business decision to allow someone else to use your code to cripple your operation, which is one of the concerns I believe you have.

Evaluate your code and decide what percentage is client related. Then once you know that you can easily deduce what percent is "the business's" and you can make a better decision from there.

This has always been an interesting subject for me, so I would like to see what the final outcome is.

GOOD LUCK!

In reply to Re: Commercial Security versus Open Source Ideals by fmogavero
in thread Commercial Security versus Open Source Ideals by rob_au

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.