After a few days of hard work, I've finally upgraded this site to Drupal 6. In the process, I had to give up quite a few features, but overall, I think the transition was worth it. There will be a few major changes, but only one that will concern the majority of users that visit this site.

The minor changes involve a revamped post flow. That is, no longer will there be a separate section for announcements, thoughts, articles, and tutorials. Instead everything is treated as the same content type, and taxonomy is used to distinguish them.

But the main change concerns project issue tracking. Like many others, after ages of waiting for the Project module to be ported to Drupal 6, I've given up. So in the meantime, I will setup Trac and see how it works out. It's unfortunate that it's separate from Drupal, but hopefully it's powerful features will make it worthwhile.

For a while, I've promoted the use of the issue queue for every project of mine, even if they were hosted on Drupal too. The idea was to centralize all my issues, but unfortunately things didn't really work out that way, and some issues are here, and some issues are on drupal.org.

Because giving credit to fixed issues is so important to projects, I've decided to use Drupal's issue tracker exclusively for projects hosted on both sites. That way I can use issue numbers without ambiguity as to what site the issue number applies to.

Remember, this only applies to projects hosted on both sites, as is the case with Gallerix, CCK Multimage, and JSFX. Projects like the Gallerix Widget Engine are only hosted here, and thus retain the issue queue.

I've been working a lot on Gallerix recently, and I'm really trying to revamp some of the features. And whenever I'm revamping features, I'm faced with certain difficult decisions. Chief among these: Should I aim for simplicity, or power?

One of my long term goals for Gallerix is to make the entire node to picture, and picture to node relationships abstract, that is, an album is simply a grouping of pictures that exist already. This can prove very powerful because you only have to upload pictures once, and "categorize" into albums as you see fit. Unfortunately, for the traditional web user, this could easily get confusing.

Although Gallerix is a robust module capable of managing all of your image needs, it becomes even more useful and powerful when paired with the Gallerix Widget Engine. When enabled, the engine will allow a variety to widgets to attach themselves to each image. The engine itself is bundled with multiple widgets. A few of these are: