Status of the category module: buggy but bright

Over the past three months or so, the development of the categoryi module has basically ground to a halt. This happened because I have been very busy working on another of my Drupal projects, the Import / Export API module, as part of the 2006 Google Summer of Code. Unfortunately, I am still the only real maintainer of the module, and so when I'm not around, not very much happens.

During my "absence", the bug queue for the category module grew tremendously, into the monster that it currently is. This bugginess, combined with the recent lack of developer activity, has made people worried about whether the category module will continue to be maintained for the future, and about whether the many bugs that are currently in the module will be fixed. I am pleased to say that the answer is yes: the category module will continue to not only be maintained, but also improved and developed further, for at least the next version of Drupal; and the bugs that are currently plaguing the module will be fixed.

Long-time category module fan and sponsor kiteatlas recently posted a call to support the future of the category module on drupal.org. I recommend that all of you read this post, in which kiteatlas lists the major concerns that he has with the category module, and in which he offers a monetary bounty as a way of sponsoring bug-fixing (and he encourages others to do the same). This is very much a response to that post.

The bug queue

Now that the Summer of Code is over, I am giving the category module bug queue top priority as something that needs to be dealt with. I have already started fixing some bugs, and I intend to continue doing this over the next few weeks.

As with everything in the Drupal community, the category module bug queue will be shortened a lot faster if it's a team effort. Drupal.org user bdragon has recently joined the team, by submitting bug fixes in the form of patches (thanks!). At the moment, developers with knowledge of bug fixing and patching are what the category module needs most. Of course, patch reviewers, patch testers, and bug reporters are also all needed. I am very interested in seeing more developers join the team, as this will mean that bugs get fixed faster, and as it will also guarantee the long-term survival of the module, by making it an entity that outlives the efforts of any one individual.

The future

Once the category module has become reasonably stable and bug-free again, I intend to upgrade it to the new Drupal 5.0 platform. The 4.7 branch of the module will also continue to be actively maintained for some time.

I am going on an extended vacation next year. As of February 2007, I will be embarking on a world trip that will last about 12 months. Sadly, this trip will be a vacation not just from my work and study, but also from Drupal (including the category module). So, I really can't guarantee that the category module will continue to be actively supported next year. I will probably put the module up for adoption, and hopefully some other experienced developers will agree to become the new module maintainers. I am on the lookout for anyone who might be interested in taking on this role, and I would be very happy to start teaching and mentoring developers in preparation for this role.

Bounties

I have always worked on the category module because I need it for my own personal use. This is the main reason why I bothered to write the module in the first place, and as long as I still need the module, it is the main reason why I will continue to work on it. My plan has always been to convert my own site, GreenAsh, to use the category module, and I still need to (and intend to) do this. I see this as a pretty big reason for me to keep working on the module, and as a pretty big guarantee to you (the users) that the module will continue to be maintained.

Money is also welcome. Experience has shown that money will make me (and others) work harder and faster. But be aware that money cannot buy any guarantees. The category module (and, for that matter, most other things in Drupal) hasn't gotten to where it is now because of bounties or sponsorships - on the contrary, it's reached its current state despite very little sponsorship, and a lot of unpaid time and effort. The thing that really drives me (and others) is (a) an itch to scratch, and (b) passion.

Having said all that, feel free to contact me if you're interested in sponsoring development or bug fixing for the category module.

I hope that this announcement answers most of the questions and concerns that you, the module's amazing community, have raised recently. And thank you very much to everyone who has put their time and their effort into supporting the category module so far, in whatever shape or form. It's all appreciated. You're all part of the team.