webschuur.com

I found a really nice tracking system, dedicated for feature request: FeVote.
Since I’d like to try if it actually works as one would expect, I removed the ability to request features, on Tagadelics issuetracker. openend a project for it on FeVote.

So: if you have requests for tagadelic, log in (openID) or register over there and add your request, or vote for existing ones.

If it works, then I think I will use it for more (Drupal related) projects.

The downside, I guess, is that people will start to expect a certain feature to appear, once it gains enough votes; which, obviously, may not happen. After all: development is not a democratic process.

update: after some stupid editing of mine, I brought the points down to six. thanks to Bert for telling me I am fool.

More and more often I have to cope with designers in the process of creating Drupal sites. That is a good sign: Drupal matures, so it gets used in more multitalented, professional environments. Not just a pimpled student in the attic who knows some Photoshop and some Javascript and learns some PHP, but project cycles with multidiscplinary teams involved.

The biggest bottleneck, in all this, however, I find, is the wrongly skilled designer.

Blogs. Conversation. Not exactly two words that people would fit in one sentence. Blogs don’t talk to eachother; maybe with some trackback system, or via technorati, but even then they don’t really conversate.

Wilfred Rubens pointed me to a very good post on this matter.

Dave Pollard investigated the very nature of a conversation, looked at how this applies to online communities and explains very clearly how blogs can improve the actual conversation, both within the weblogs and within their blogosphere.