http://qs321.pair.com?node_id=735566


in reply to Organizational CPAN Accounts?

I acquired one of those organizational CPAN accounts, WHITEPAGE. The idea of an organizational CPAN account isn't entirely uncontroversial with the CPAN maintainers. I think it was only on even odds that I acquired it. The default idea is that individuals do the work so that's who the CPAN account should belong to.

⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊

Replies are listed 'Best First'.
Re^2: Organizational CPAN Accounts?
by JavaFan (Canon) on Jan 13, 2009 at 10:35 UTC
    The default idea is that individuals do the work so that's who the CPAN account should belong to.
    Funny. Individuals (plural) do the work, so that's who the CPAN account (singular) should belong to.

    Seems like a pretty good definition of an organizational CPAN account to me! ;-)

    Having said that, there are some difficulties. If I were to work at $ORG which releases a package $PACK on CPAN, using account $NAME (be it a personal or a organizational account), with $NAME comes password $PASS. Now I stop working for $ORG. I probably shouldn't have write access to $PACK anymore. But that would require changing $PASS, and distributing passwords. It's even worse if $PACK was distributed on my personal CPAN account. Then maintainership of $PACK would need to be passed, and if me parting with the company was not on friendly terms, I might not want to cooperate.

[reply]
Re^2: Organizational CPAN Accounts?
by hobbs (Monk) on Jan 17, 2009 at 07:50 UTC
    Thanks for your input. I got the organizational account I was after approved, and I'm going to trial publishing under that, but if there's any big deal I can just transfer the module to my own name.
[reply]

In Section Seekers of Perl Wisdom