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: What would you like in your omelette?
    Martin: Nothing in the omelette. Nothing at all.
    Waitress: Well, that's not technically an omelette.
    Martin: Look, I don't want to get into a semantic argument about it, I just want the protein, all right?

    To add context of why the FOTANGO company account was set up, it was a reaction to the opposite problem we had: Employees are short lived too. Traditionally Fotango let people release modules on their own accounts. But then we had a case of someone leaving the company and then going unresponsive to patches to a module they originally developed for the company that the company was still developing.

    I guess you're damned if you do, you're damned if you don't.

    I'd suggest for all future people doing this that they give co-maint rights to all the authors. That still leaves the question of how to change primary owner rights; Some sort of dead man's handle where co-maints can take over primary ownership? A bigger issue than I need to address today.

    Still, the thing about making omelets is that you have to break a few eggs (groan.)
    • 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.