Slash Boxes
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.
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.

      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 headline person, retaining co-maint rights for the original uploader and anyone else that needs to upload.

      If employees leave, you still have the most reliable (and just as importantly, the easiest person to hunt down and contact) person able to push new co-maint bits out to anyone necessary.

      If the company goes under, this person is easy for CPAN admins to find and obtain rights to hand off the namespace.

      If the person dies or leaves the company, again this is much easier for us as admins to deal with, especially if all the copyright statements still retain the company name.

      This method should work for anything but the largest organisations. For them, there is a special type of "mailing list" permissions artifact that Andreas can set up for these special cases. So far there are no more than about 10 of these.

      • 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.