The drop is always movingYou know that saying about standing on the shoulders of giants? Drupal is standing on a huge pile of midgetsAll content management systems suck, Drupal just happens to suck less.Popular open source software is more secure than unpopular open source software, because insecure software becomes unpopular fast. [That doesn't happen for proprietary software.]Drupal makes sandwiches happen.There is a module for that

How do we deal with these kinds of contributors?

Submitted by nk on Sat, 2007-11-24 10:45

So, these guys do not observe community processes and yet they fervently patch and sometimes what they do is good. More often, it's more a hindrance than good. No plea in private email or even in public email can get them back in line. So, what can we do with friendly posts like "this issue is opened to waste testers and reviewers time and makes things more difficult"? With people who constantly put back their issues in the current version even though several high profile contributors said "wait until Drupal 7" until finally a core committer says "enough"? With people about whom a core commiter said "he is always wrong. OK, not always, but..."? I am out of ideas.

Commenting on this Story is closed.

Submitted by deekayen on Sat, 2007-11-24 15:31.

I fear it means project.module is going to end up having more restrictions so core or otherwise important people can disable the version field on issues.