In case you didn’t know, WPML has a twin brother. It’s a Drupal module called Translation Management. WPML wants to be more like Translation Management, who’s mature and bug-free.
When fellow developers report issues in for Drupal modules, they always include specific information on what’s causing the problem, how to reproduce it and often, a patch.
As a result, Translation Management is maturing rapidly. You don’t get to hear complaints like:
we’ve had this problem since version 1.3 and it still exists!!!
Instead, every issue is fixed before every minor release. Yup, you hear that right. Issues are not carried from one release to the other.
The “secret” to closing issues is being able to handle them. We want to close all bugs, just that we often cannot. Getting complete reports, with full debug information and patches would help speed things up enormously.
Remember Canonical Plugins?
Some time ago, Automattic folks suggested to make some plugins “Canonical”. It’s exactly what we would have needed. The problem is, it’s not here. So, we’re thinking about taking matters to our own hands and setting up the issue tracking tools for WPML.
Now, I’m putting it to a vote. If we get enough response from developers willing to lend a hand, we’ll set it up for WPML immediately.
Do You Want to Contribute?
Please leave a comment with answers to:
- I will follow up on issues that I report and help test fixes.
- I can include code references and suggest patches when I report bugs.
- I know how to use Subversion (SVN) to create .patch files.
Here’s our pledge:
We will close and handle all bugs that are reported using an issue tracking system. All bugs will be closed before any minor release.
Quick update: we’re giving Google Code a try. Here is WPML project tracking on Google Code.
When you have new issues, open them there. Let’s see how it works!