Observe:

An incredibly long standing issue, that keeps popping up, gets a handful of follow-ups, none of which actually address or even mention any of the technical problems that need to be solved.

Instead, all it gets is a bunch of "+1 Subscribe" follow-ups. Whenever I see such a comment, it tells me this:

I really want this feature, but I'm not prepared to do anything about it. I won't spend any time educating myself about it, exploring the problem space or prototyping possible solutions. I fully expect others in the community to solve it, while I reap the benefits.

Go ahead, call me cynical and misguided.

8 tips for the aspiring Drupal developer

Open source is really great. You get to cherry pick from some of the best software out there and build neat stuff with it, fast. Most open source projects will also encourage you to contribute your own work back to the project. Supposedly, so others can benefit from your work.

While that's often an easy, karma-scoring move, it can have some unintended, annoying consequences. For example, people might start sending in bug reports for your code or may offer suggestions on how to improve it. Even worse, meddling know-it-alls may even offer to 'help' with development and do things with it that you never intended. Some projects, like Drupal, even trick you into such forced participation, by automatically supplying issue trackers, RSS feeds, revision control and other, undesirable community interaction.

Luckily, there are several things you can do to keep those pesky contributors away altogether. You can participate in open source without suffering any of its extended effects. Here are some concrete tips for the aspiring Drupal developer. Of course, a true creative will find novel ways of keeping their open source involvement to an absolute minimum!