[development] How to post bug reports and patches

Tomas Fulopp tomi at vacilando.org
Fri Oct 31 12:10:27 UTC 2008


Just my two cents - while there are systemic reasons why this happens, the
community needs to be able to see the issue purely from Markus's point of
view. He seems to be a devoted Drupal developer who has put a lot of his
time into developing patches only to see that they are not checked and not
committed. That is to say, he has provided what he believes are solutions
for various problems in several versions of Drupal, but there is nobody to
actually apply them for the benefit of others. I am amazed he wrote such a
polite and friendly message, asking what did he do wrong.

I think it is not enough to be just defensive and say core maintainers are
busy with Drupal 7 (thousands of people are using D5 and D6), advise to
check other people's patches and they might check yours (I know it works
that way, but I think it is not healthy; he already provided a service), or
provide statistics on how many people complain and don't review (it is a
fact it is easier and faster to spot problems than to solve them). I would
be surprised if developers like Markus became a trifle discouraged from
providing new patches.

To summarize: this is just to show that the answers provided in this thread
are unlikely to provide an efficient solution for developers like Markus. We
must not be satisfied with such answers and keep searching more effective
methods of recognizing and applying results of good coding. And I am sure
we'll manage, for this is a marvellous community.

Tomáš




On Thu, Oct 30, 2008 at 2:50 PM, Darren Oh <
darrenoh at sidepotsinternational.com> wrote:

> I've experienced the problem you describe many times. It depends on the
> maintainer for the version of Drupal. killes has been quick to apply fixes
> to Drupal 4.7. drumm seems to hope people that people will just stop using
> Drupal 5. Other core maintainers criticize patches for problems they are not
> interested in, then ignore the patches when they are fixed, apparently
> hoping the contributor will give up. The most common reason maintainers are
> not interested in a patch is that they are working on a new version of
> Drupal which makes the patch obsolete.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20081031/9560b253/attachment-0001.htm 


More information about the development mailing list