Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery
 
PerlMonks  

Re^5: Proposal: Option to Decline XP from voting

by Arunbear (Prior)
on Nov 12, 2004 at 21:08 UTC ( #407527=note: print w/replies, xml ) Need Help??


in reply to Re^4: Proposal: Option to Decline XP from voting
in thread Proposal: Option to Decline XP from voting

Thank you for posting that. In the table, what are the pmdev and developers rows referring to (since only pmdev can create patches anyway)?
  • Comment on Re^5: Proposal: Option to Decline XP from voting

Replies are listed 'Best First'.
Re^6: Proposal: Option to Decline XP from voting
by theorbtwo (Prior) on Nov 12, 2004 at 21:54 UTC

    The question is not quite "who wrote this patch", but "to whom does the node that is the patch belong". Some patches, for reasons lost on me, are owned by developers. Some are owned by pmdev to allow anyone in pmdev to modify them, thus allowing colaberation -- but that's now frowned upon, because it's annoying for various reasons not worth going into -- not the least of which is that it makes it difficult to tell who wrote what.

    Also, there's an important reason demerphq missed that the absolute count of patches isn't useful -- sometimes you're write a patch one way, and it doesn't quite work. It's your choice if you want to write another patch, or just edit the old one. I generally prefer to edit the old one; demerphq generally perfers to write a new one. Neither method is really better then the other. (This isn't to say that demerphq hasn't done more then I have; he has.)


    Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).

      I generally prefer to edit the old one; demerphq generally perfers to write a new one.

      I go both ways, but i like to have rollback patches for my major development points. So once I feel a node is stable but will continue to work on it, ill usually start a new patch at that point. Also, there is a magnification factor for whoever does minor changes on old infrastructure noes. The old node needs a backup patch first, so effectively you get 2x patches for each old code patch. Since ive done a number of "clean up old code" sessions I have a lot more patchs becuase of it. A recent one probably added about 50 patches to my roster, but only involved a few hours work.

      (This isn't to say that demerphq hasn't done more then I have; he has.)

      Personally i dont measure things like this. I may have pumped out more code (probably becuase you had a life and i didnt :-), but youve been essential to me doing so many times. As you know full well, i can ask a lot of stupid questions in a short amount of time. :-)

      ---
      demerphq

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://407527]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (4)
As of 2022-05-19 09:12 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Do you prefer to work remotely?



    Results (71 votes). Check out past polls.

    Notices?