Slashdot Mirror

← Back to Stories (view on slashdot.org)

Properly Contributing to Open Source While on Company Time?

Posted by Cliff on from the avoiding-the-SCOrn-of-your-superiors-isn't-a-WASTE-of-time dept.

egeorge asks: "I was wondering what kind of paperwork/policies developers have at their jobs concerning contribution to open source projects. I develop software at a company that derives almost its entire revenue from software. Some software is licensed to customers, some is run internally in a service model, but the software is our whole business. We have recently been doing more and more modification and customization of open source products, and we would love to give some of this back. As developers, though, some of us are a little hesitant to just start flinging code that technically still belongs to the company out into the world. We want to make sure we get clarification about what is or is not covered by our NDAs. So, what kind of procedures do other developers have to go through to get adequate coverage for Open Source submissions? I would like to suggest a policy to my superiors, and could use a few good suggestions."

11 of 400 comments (clear)

  1. A quick list by Anonymous Coward · · Score: 5, Funny
    • Don't ask for permission. What they don't know, can't hurt them!
    • Be like Nike; Just Do It! Need to write a routine for the internal process? Just slap the GPL on top and release it on Sourceforge.
    • Make use of the resources available. Do you not have enough time to work on your own projects? Just circumvent the firewall and telnet to your home machine. The office is more comfortable, anyway.
    • It works the other way you know. Need a routine for an internal project? Just use it and release the changes.
    • If all else fails; lie. Claim it wasn't you. Cover your tracks. Call the BSA if you need a diversion in a hurry.

    Thats what I did when I was at SCO, anyway!
  2. Anyone know of some OSS MRP Software? by Real+World+Stuff · · Score: 0, Funny

    TIA

    --
    If we don't fight for ourselves no one will.
  3. And in other news... by Anonymous Coward · · Score: 5, Funny

    ...How to run an ebay business selling your company's items

  4. What! by PS-SCUD · · Score: 4, Funny

    I'd never do something so dishonest as to develop OSS on company time. I just look at pr0n and DL some music on Kazaa ;-)

    --


    "Much work is lost, for the lack of a little more." -Edward H. Harriman
  5. Government Copyrights in Canada by IncohereD · · Score: 5, Funny

    Lucky bastard....Her Majesty the Queen of England of all people holds the copyrights on MY code. :)

    1. Re:Government Copyrights in Canada by GoofyBoy · · Score: 3, Funny


      But in exchange, you get full rights and privliages as a loyal British citizen!

      --
      The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
    2. Re:Government Copyrights in Canada by brer_rabbit · · Score: 2, Funny
      Geez, I could understand your Copyrights belonging to PARLIMENT, but the Queen!!!!!!

      I suggest everyone Give Up The Funk to Parliament. Your code would rest easier with George Clinton anyway.

      Free Your Code and Your Ass Will Follow!

  6. Re:Well by Anonymous Coward · · Score: 1, Funny

    TATMA(There Are Too Many Acronyms)

  7. Re:Careful! by Anonymous Coward · · Score: 1, Funny

    So if anyone wonders why nothing good ever gets done from our company, this is why.

    So if your remarks are legally owned by your company, then your remark is your company's, and therefor, your company is essentially saying what you're saying, then your company's saying that nothing good ever happens at.. ...

    Lawyer time, dude. ;)

  8. Re:Simply put: I DO by orev · · Score: 2, Funny

    It's easier to apologize afterward than it is to get permission beforehand.

  9. Re:Simply put: I DO by Anonymous Coward · · Score: 1, Funny

    Remember that when you're in the unemployment line.