This morning I received a request from a former employee of Fotango to take over the FOTANGO CPAN account. Of course, I can't give it to him. I also can't give him control of his own code that he wrote while at the company to maintain.
This sort of thing is exactly the reason that we strongly try to discourage the creation of "company" CPAN authors. A company is a short-lived entity, and most will die or be shut down or be bought out or merge or otherwise change during the time it exists. Companies also rarely die outright, they liquidate. Their property becomes the property of some other company, endless recycled between various legal entities that might have no idea about the original.
When a company vanishes or gets bought out, any ability to control those modules as a primary author vanish as well.
This CPAN author is now going to have to apply for co-maintainer rights to his own code in order to keep maintaining it, and demonstrate in the usual way that he has attempted to make contact with the original author (the legal remains of Fotango, wherever they exist).
Of course, if someone knows what the ultimate fate of the Fotango corporate entity is, and can arrange for someone representing the current state of that entity to inform me of who I should reissue a password to for the FOTANGO login, I'd prefer to do that.