Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I am that fateful ex-employee that Alias is describing. For the record, I didn't ask to take over FOTANGO, but said that I'd like to take over the modules, and I'm up for whatever's the easiest way to do that, giving me access back to the fotango account, changing the email address, or just giving me co-maint on the modules.

    To quote Gross Pointe Blank (mainly because I like quoting Gross Pointe Blank, rather than for any real reason)

    Martin: Whole grain pancakes and an egg-white omelette, please.
    Waitress: W
    • My apologies.

      I didn't suggest to imply it was some kind of surreptitious takeover

    • My apologies.

      I didn't suggest to imply it was some kind of surreptitious takeover.

      For smaller companies, the way we recommend you set up shared release is to identify one person as a responsible headline/lead developer.

      In this scenario we're talking the likes of Matt Sergeant, Brad Fitzpatrick, Jesse Vincent. People with a more public profile, people who won't just vanish, and ideally people that are part owners.

      When an employee uploads a package, you transfer all of the primary namespace rights to this hea

      • Making me personally the maintainer for all the modules released by staff at my company is...very not right. Often, I have nothing to do with the modules other than that I pay the wonderful perl hackers who produce them. I've been procrastinating getting a 'BPS' or 'BESTPRACTICAL' PAUSE account for the company, but it (or some other affordance) that allows collective maintainership by me and my coworkers really needs to happen.
        • If we were to start allowing company logins in numbers, I suspect we'd really need to look at some kind of function to say what to do on the death of the company.

  • According to Companies House (the keeper of records for UK companies), Fotango Limited is in liquidation. Strictly speaking the account is an asset of the company and you would need to contact the liquidator to get permission to re-assign it (unless the PAUSE T&Cs allow you to re-assign stale accounts) but the code has been released to the public domain (within the bounds of the perl licence) so adding a co-maintainer shouldn't be a problem.

    • Since PAUSE (and to a lesser extend CPAN) were created and being run by volunteers that provide a free service, I very much doubt that anybody has any legal handle on PAUSE accounts. The reason why us PAUSE admins are treading very carefully is because we're simply trying to "do the right thing" and accommodate everyone. That's not entirely unselfish: It would be a disaster if users (both owners of PAUSE accounts and "ordinary" CPAN users) lost trust in PAUSE and CPAN.

      In the end, I believe, it comes down to

  • So, just to keep people updated:

    After getting suggestions from people on who to contact, I've sent emails to people in Fotango's parent company. They've responded positively, but said that people needed to make the final decision are on holiday until at least the end of the month.

    Given that prompt response it seems the prudent thing to do now is wait for them to get back, thus sidestepping the need for any further debate over the right course of action.

    Thanks again for everyone's help in this matter.