At the moment, this doesn’t affect anyone but me, but I have moved development hosting of Grotesque from Sourceforge to Gitorious. There isn’t much of an effect, since generally speaking I’m just committing locally and pushing my changes to the remote Git repository; it doesn’t make much difference where that remote is. There were two main reasons for the move, one personal and one practical. On a personal level, it allows me to have all my development projects in one place, rather than spread out between several.
On a practical level, it will make future potential contributions from other developers much easier. When I started hacking on Grotesque, I did so unofficially on my own Git repository since the official one was using SVN. When I was ready to merge my changes, I had to bother the original author by email, then he had to grant me permissions, etc. With Gitorious, like Github, anyone can easily fork the repository, work on the code, and then send me merge requests to get the code included. Unlike Github, it allows me to organize a project with multiple repositories. So, both the main Grotesque repository and the external pyIFBabel (Treaty of Babel) library repository are stored under the same project.
I’ll still upload new Grotesque versions for download on Sourceforge (in addition to making them available here), since people might still go there to look for them. I’m going to try to close the issue tracker there, since for most people it’s a convoluted, overly-complicated mess. Until I find a better solution, you can just send bug reports directly to me.
As for actual progress, in a massive coding spree this weekend I rewrote much of the Treaty of Babel code to be more similar to the official C API and commandline tool. Now I’m ironing out all the bugs that creep into the code during such long sprees. This will be good in the long run because, in greatly expanding this code, I will be able to add a bunch of new features to Grotesque as a result (such as more extensive metadata handling, top- notch iFiction support or the capability to create blorbs). As an aside, somehow I managed to fail to include an AdvSys handler when I was previously working on the Treaty. That has been rectified, so future versions of Grotesque will properly handle your old AdvSys games (“.dat” extension)!