comment on

I don't see anything wrong with it. To some extent, it may depend on who is claiming the copyright. If you, personally, are taking the copyright and making it open source, and your $WORK is licensing it to use it, then release it under your author ID. If $WORK is keeping the copyright, then maybe release it under a $work ID to help make that distinct from any other work you release on your own.

I'd think about adding your personal ID as a 'co-maintainer'. And you'd want to make sure that the XXXX at cpan.org email forwarding goes somewhere that won't disappear if you leave the company.

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

In reply to Re: Organizational CPAN Accounts? by xdg
in thread Organizational CPAN Accounts? by hobbs

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


more useful options
	PerlMonks