Find something descriptive. How does your code improve on Net::IRC? Is it faster (Net::IRC::Fast)? Is it easier to use (Net::IRC::Simple)? Is it just an alternate take (Net::IRC::Neo).
My problem with that suggestion is I think nicely stated by sintadil
Considering the flakiness and oft brokenness of Net::IRC (and the very admission of its author of these points), I'd completely avoid anything containing that. People are weird creatures, and they often associate bad things with an object just by appearances. If someone feels (like I do) that Net::IRC is broken, and sees "Net::IRC" in your module name(s), that someone will probably think that your module is broken in the same way(s) -- and thus they'll avoid it. It's regrettable, but it is human nature.
Since, hypothetically, my module has nothing at all to do with Net::IRC in any shape or fashion, other than filling some of the same niche, I really don't want to be associated with it in the manner that Net::IRC::<anything> would give me. Also as rcaputo
POE components tend to have "POE" in their names because they don't live separate lives from that framework. The implication is "You need POE to use this." In that vein, BUU::IRC implies that some BUU module is necessary to use it.
So Net::IRC::<anything> seems to imply that some Net::IRC module is necessary to use it. Which wouldn't be true. I guess my best solution is to simple find a new name below net, Net::FrameworkIRC or something similiar, but those are the reasons I don't want to be under Net::IRC.