Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
This came up from an incidental issue about a month ago. I have been told that if I wish to continue being employed, I cannot post code.

This is extremely bad form on the part of your employer. Companies that implement this type of policy are shooting themselves in the foot, unfortunately they can do a lot of damage to others, including free software organizations, in the process.

I'm not a lawyer, but it seems this all pretty much comes down to the agreement that was signed. A brief reference on the issue is available here. From the part that describes what a 'Work for hire' is:

Section 101 of the U.S. copyright law defines "work for hire" as follows:

  1. a work prepared by an employee within the scope of his or her employment; or,
  2. a work specially ordered or commissioned for use as: a contribution to a collective work, a part of a motion picture or other audiovisual work, a translation, a supplementary work, a compilation, an instructional text, a test, answer material for a test, a sound recording, or an atlas; or,
  3. if the parties expressly agree in a written instrument signed by them that the work shall be considered a work made for hire.

Assuming this is still relevant, Number 3 is the problem. I haven't heard of anything that specifically says employers own all the rights to all work done by professional employees by default but if the contract signed says so, there doesn't seem to be a whole lot you can do.

Excellent post though. This is an issue that has important consequences for free software and should be receiving far more attention than it has been.

Update: Here's another good article on the subject.

In reply to Re: Professional Employees and Works for Hire by cjf
in thread Professional Employees and Works for Hire by tilly

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others taking refuge in the Monastery: (8)
    As of 2020-01-23 13:14 GMT
    Find Nodes?
      Voting Booth?