Different tacks I could have taken?
Couple of ideas which may have helped (and I have used in the past).

  1. Follow up any verbal agreement with an email, with a first line something like "This is just a quick note to confirm the recent discussions."
    You can then argue (quite reasonably) that the agreement was in writing, since, if "they" don't agree, it is up to them to replay and follow up.
  2. Post the code regularly to somewhere public, if that is your final intention anyway.
    It is too late to do this after the legal people are involved, but if you set an early precedent, it is easy to continue.
  3. Assuming you submit reports "up the chain of command", then you can add the one liner under achievements for the month that "Version 0.93 has been submitted to the XXX archive for review". Again, assuming that either the report isn't read, or that the implications aren't picked up, you have set the precedent.
    If the implications are picked up, then you get an early warning of problems ahead. Either way, you get a chance to end up with a better result, with at least a chance to have the argument early on.

--
Brovnik

In reply to Re: Non-Disclosure Legal Fun w/ my ex-Employer by Brovnik
in thread Non-Disclosure Legal Fun w/ my ex-Employer by idnopheq

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.