I disagree. Any patch, exciting or not, would be pushed up if many people needed it done. Same goes for documentation - if some help texts are underdeveloped, they will be brought to the visible light spectrum quicker. <div>
<br></div><div>The only thing the voting does not favour are patches for the more obscure problems or features. That is obviously sad, but by definition fewer people will be affected it, and Drupal as a project will be still better off. But still, in theory even less needed patches would accumulate enough votes over time. Also, each committed important patch would move the less popular issues up the ranking queue.</div>
<div><br></div><div><br><div><br>
<br><br><div class="gmail_quote">On Fri, Oct 31, 2008 at 5:50 PM, Brad Bowman <span dir="ltr"><<a href="mailto:brad@atendesigngroup.com">brad@atendesigngroup.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Can you guys give me the run down on how this is expected to help with<br>
newer contributors getting their work recognized? I see adding issue<br>
voting as just perpetuating the system we have now, where the most<br>
known/active contributors get their patches looked at by more people<br>
than new contributors. I see this as just pushing that problem one<br>
step further up the line, where now they'll get their issues 'dugg'<br>
more.<br>
<br>
I see this also as a potential distraction for patches that are<br>
important, but not exciting. I don't think things like documentation<br>
and coding standards would not fare too well in a voting contest, but<br>
that doesn't diminish their importance.<br>
<br>
Thanks,<br>
Brad<br>
Aten Design Group<br>
Phone: 303.831.0449<br>
<div><div></div><div class="Wj3C7c"><br>
<br>
<br>
On Fri, Oct 31, 2008 at 10:30 AM, Chris Johnson <<a href="mailto:cxjohnson@gmail.com">cxjohnson@gmail.com</a>> wrote:<br>
> Derek,<br>
> My comments were definitely not directed at you!<br>
> I'm your number 1 fan when it comes to the work you've done to support<br>
> Drupal infrastructure and project management.<br>
> ..chris<br>
><br>
> On Fri, Oct 31, 2008 at 11:18 AM, Derek Wright <<a href="mailto:drupal@dwwright.net">drupal@dwwright.net</a>> wrote:<br>
>><br>
>> On Oct 31, 2008, at 9:07 AM, Derek Wright wrote:<br>
>>><br>
>>> Only if Dries or killes agree to let us turn on VotingAPI on <a href="http://drupal.org" target="_blank">drupal.org</a>:<br>
>><br>
>> On Oct 31, 2008, at 9:07 AM, Chris Johnson wrote:<br>
>>><br>
>>> Claiming to know the "only" way to do something in an open source<br>
>>> community (or just about in any circumstance) is arrogant, or blind, or<br>
>>> defeatist, etc.<br>
>><br>
>> Sorry, I didn't mean to be arrogant, blind, or defeatist with my previous<br>
>> message. ;) If there's another way to get something deployed on d.o that<br>
>> won't be immediately disabled again, I'd love to hear it. In my experience,<br>
>> the only way code stays on d.o is if killes or Dries agree it should be<br>
>> there, which is what I meant by "only".<br>
>><br>
>> Cheers,<br>
>> -Derek (dww)<br>
>><br>
>><br>
>><br>
><br>
><br>
</div></div></blockquote></div><br></div></div>