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

Again on subsystem maintainers

Submitted by nk on Sat, 2009-10-31 03:11

Two important points were brought up with my previous idea. One, communication and direction and so forth. Any patch needing that is branch maintainer territory. The subsystem maintainers are taking care of the small patches so the branch maintainers only need to deal with the bigger patches. Then comes the "but if it's a small patch then it takes no time to commit". This is simply not true -- everything takes some time -- if it takes only one minutes (I doubt they can be done so quick) then thirty of them takes away the time from a bigger one. Edit: We just had a discussion on IRC where went through a bunch of commits checking whether they are on subsystem or branch level and we found that most patches that operate on a subsystem level are really small so it might be that instead we want to name a 'code janitor' or 'yard sweeper' who can save the branch maintainers from "death by ten thousand cuts" and sweep in the minute fixes which drain the branch maintainer's time. This would just add one or at most two people making the communication overhead really small.

Another concern was that what if the subsystem maintainer rewrites a patch in the guise of a review. Well, I have been able to give directions without actually writing the code so I do not fear this either.

Commenting on this Story is closed.

Submitted by on Sat, 2009-10-31 06:28.

I couldn't believe it in the first place, and I finally had the chance to ask webchick about the reality.

"small" patches do not really add up and do not occupy resources like you imagine. Instead, they are a nice target to get "warmed up" in the dialy maintainer work, before you go ahead and tackle the stuff that needs more attention.

This is more or less what webchick replied, and I'm 100% in line with that based on my very own maintainer experience in contrib.

The real problem is when patches are marked as RTBC when they are not really RTBC. That wastes core maintainer resources to a totally ugly extent.

Submitted by Anonymous on Thu, 2010-11-11 10:12.

I like posting on new sites.

Submitted by drupaLA on Wed, 2009-12-16 10:13.

From the small patches may occur a big trouble. I will write my essay about later.