Slashdot Mirror


Ask Slashdot: Does your Employer have an OSS Policy?

osjedi submitted this tidbit for your toughts: "I have heard from a few people that the companies they work for have issued a statements to the IT departments stating that they are forbiden to utilize any open source software. Obviously this is short-sighted. I would be interested to know from fellow Slashdoters what stance (if any) their employer has taken regarding the use of OSS. I would like to compile a list of the companies forbiding the use of OSS. It would be fun to create a "Open Source Users" stock index, and a coresponding "Open Source Refusers" index." It would be interesting to know which companies actively promote Open Source as these might be good places for those OSS Coders who are currently looking for day jobs. What do you all think?

1 of 150 comments (clear)

  1. My cat likes cat food by coredog · · Score: 4

    I look at the thread, and the subject appears
    to be why would a company have a "no OSS" policy?

    However, the thread quickly degenerated into
    "I use Perl and it works, NT sucks, blah blah blah"

    There were a few posts that mentioned what is the probable reason (IMHO) for the no OSS policy. A no OSS policy means that you have to get approval to install software. This lets legal check the license and avoid any problems where someone installs something that is not freeware in a corporate setting (Applixware anyone?).

    BTW, the subject was a poke at those who quickly
    took this thread off topic. Why not post some relevant comments about how to create a business case to get OSS software approved?

    --
    Do anal-retentive people hyphenate 'anal retentive'?