I would publish under an individual's name, and have reference to their workplace.
I would think the copyright notice is the authoritative part here, not the account. The cpan account just holds the stuff. It's the docs of the distro that say who's what.- aha.. corrected- thank you ikegami, makes total sense, everyone, anyone, is authorized to distribute.
I can go copy PDF::API2 code right now, call it Agent::Orange, and distribute it- provided I state what the code is based on.. etc. This is the whole point of releasing under the perl license and using open source/gnu what have you- that code cannot be held hostage!
It's kinda like a capitalist free market science information model. If I release X and you start maintaining a version in better shape than my X, then more people will download, use it. That's what gives you 'authority' - or close enough.
-
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.
|