I'm currently working with a fellow monk on an article (hopefully out soon); it's a joint effort as opposed to this other monk offering critism. Most likely, it will be posted by me when it is ready, but I would like to be able to split the credit when it comes to XP gains with this other monk. Obviously, said monk will be already indicated at the top as a co-author on it, so he would not be a silent partner here.
Obviously, one could suggest changes at the programming level, but I feel there's a better solution: First, after posting it, I would tell the other monk to immediately reply to the post, such that he has a votable note associated with it. Then, at the top of the article, I would include text that this is a joint effort and explain what the other monk has done, and then point readers to vote for this other monk at the node that has just been posted if they find his contributions useful. It might end up that people use two votes on the article, one for my posting, and one for the co-author, so I would think to strongly encourage spending only one vote between the two authors.
Does this sound like a reasonable idea in order to make sure that credit is equally split? Or has anyone found a better way to do this?
Dr. Michael K. Neylon - email@example.com
"You've left the lens cap of your mind on again, Pinky" - The Brain
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.