Personally, any module that's released via any work-related entity that I run into trouble with I patch and release publicly ASAP. That's just the most efficient way of dealing with it, but that's just because I'm usually the public maintainer of that code. When you're working with a large group so that changes may take more time, it might be a good idea to put the bug (and possibly patch) in whatever public ticketing system is the most useful - rt.cpan.org is available for all CPAN modules, but if you have your own system, it may be better to use that.
in reply to Reporting bugs in corporate-sponsored CPAN code
Aside from that, if you're putting up modules as "open source", I just want to plug http://github.com as a code repository. It makes publicly forking / patching other people's code a breeze and gives you a very clear view of whatever other people are doing with the code.
edited to add: my repos @ github