[development] Voting on issues (was Re: How to post bug reports and patches)

Brad Bowman brad at atendesigngroup.com
Fri Oct 31 16:50:59 UTC 2008

Can you guys give me the run down on how this is expected to help with
newer contributors getting their work recognized?  I see adding issue
voting as just perpetuating the system we have now, where the most
known/active contributors get their patches looked at by more people
than new contributors. I see this as just pushing that problem one
step further up the line, where now they'll get their issues 'dugg'

I see this also as a potential distraction for patches that are
important, but not exciting. I don't think things like documentation
and coding standards would not fare too well in a voting contest, but
that doesn't diminish their importance.

Aten Design Group
Phone: 303.831.0449

On Fri, Oct 31, 2008 at 10:30 AM, Chris Johnson <cxjohnson at gmail.com> wrote:
> Derek,
> My comments were definitely not directed at you!
> I'm your number 1 fan when it comes to the work you've done to support
> Drupal infrastructure and project management.
> ..chris
> On Fri, Oct 31, 2008 at 11:18 AM, Derek Wright <drupal at dwwright.net> wrote:
>> On Oct 31, 2008, at 9:07 AM, Derek Wright wrote:
>>> Only if Dries or killes agree to let us turn on VotingAPI on drupal.org:
>> On Oct 31, 2008, at 9:07 AM, Chris Johnson wrote:
>>> Claiming to know the "only" way to do something in an open source
>>> community (or just about in any circumstance) is arrogant, or blind, or
>>> defeatist, etc.
>> Sorry, I didn't mean to be arrogant, blind, or defeatist with my previous
>> message. ;)  If there's another way to get something deployed on d.o that
>> won't be immediately disabled again, I'd love to hear it.  In my experience,
>> the only way code stays on d.o is if killes or Dries agree it should be
>> there, which is what I meant by "only".
>> Cheers,
>> -Derek (dww)

More information about the development mailing list