There is a very interesting thread on Perlmonks where someone asks "How can I persuade my non-technical boss that open sourcing some of my code is a good idea?".
It's interesting because it's very good timing: we have been having similar thoughts at work, and some of the comments are the ones we already thought off. Most of the arguments appeal to human nature: greed - this will save us money or decency - we are paying back to the community that we have greatly benefited from. While I can see the logic of these arguments they don't overcome corporate phobia of liability or paranoia.
The arguments are pretty much:
The counter arguments from a non-technical boss are fairly strait forwards, and while some of them may result from general ignorance, they must be countered if we are to overcome.
Now you can always release on CPAN and strip the companies name out, or even publish under a pseudonym, there is a VERY long history of this already, but it's stupid and potentially risky...
What is a community spirited perl hacker to do... ?