Something you want to be careful about is avoiding any of your modules having names that clash with modules on Cpan, cos that would get far too confusing.

An easy way of doing this is putting them all in a namespace which identifies them as being local to your organization. The namespace Local:: is reserved for this, so you can have Local::Foo, Local::Bar, etc, or you can use Your_Organization::Foo, Your_Organization::Bar, etc; in theory putting an underscore somewhere in your organization's namespace should avoid it clashing with anything on Cpan.

We do the above for any modules which implement our business logic or are otherwise specific to us. For any more general purpose modules we give them a Cpan-type name, so we can then release them to Cpan.

Smylers