larsivi

A few weeks ago, I entered Tango as a project for the Hackontest - a 24 hour hacking contest for 3 select features for various open source projects. The hacking will be done by teams of 3. For those attending, there will be cash prizes and most likely an exciting trip to Zurich, Switzerland.

Now, the catch is that a jury will select the 3 projects/features that will be part of the competition proper, and these will be chosen from those entered at the site linked further up.

When I registered Tango, there was a

KeYeR (Piotr) called upon me in #D and said that my statement "This is one of the worse decisions among the bad ones in the D history." was bad English. No, not really. He said that it was a strong statement, and sure, it is. I tend to be (unnecessarily so?) strong in my rather few statements on design choices in the D language. Peter added that he was afraid that I was right.

As I see it, Walter here is willingly implementing a solution that 99% of the community seems to hate. He even had a different implementation, the manifest keyword, that was applauded

When I talked about the three T's, the last one stood for TODO. Well, in the Tango world, i probably should have made that Ticket. Since our latest release, the reactions have been relaxed, mostly due to the holidays I guess (and partially because the contents were well known). Only 9 tickets have been created since then, and at least 5 of them were web and documentation related. The web part is natural, as I redid the layout of the Tango frontpage, hopefully for the much better (at least visually, I believe we could do it in a more proper styles based manner, please join us if you think so). I think the tickets related to this change were all resolved.

As for the docs, one ticket was about private members in the DDoc output. Now, this is easily removed by changing the style of the source code comments, but do anyone know if this is

We just released the next version of Tango, 0.99.1, which is mostly a bugfix release. To the Tango team, events surrounding it are encouraging though, as they show that Tango gains more users and more compatible libraries.

In addition to the compression stream filters by Daniel Keep, many of the bugfixes in this release, were due to patches and suggestions by users. As such, one bug in the collections package was reported 4 times over a

From time to time, Walter says that we need to do things that will increase the visibility of D outside of the D community. Each little effort is in itself probably too small for a noticable effect, but over time and with many such efforts, we make a difference.

I try to take every opportunity, both because I want D to succeed, but also because I want to succeed in having D programming as my main source of income. Of course, when I discuss and plug D, I usally

After 3 days of pure D'ness, the conference is now over. And yes, the trip was definately worth it! Putting faces to those I hadn't seen pictures of was very good, and it was very nice to talk to people in person that I previously may spent a few harsh words with on the newsgroup. It's so much easier to understand the full length of the other's meaning when one is face-to-face.

It was also funny being greeted with "Hey, I read your blog!" (Good meeting you, Paul ;). Other surprises included another Norwegian (who's even situated north of me), Brynjard.

The first and second day included the talks as can

Last wednesday (or thursday in my timezone), we released the first beta version of Tango, a library for the D programming language that replaces the runtime, and adds another, more object oriented set of functionality to the core application interfaces. There's also a listing of the current features.

Using Tango means that one switch out Phobos, the D standard library, although it has been mentioned that someone may

The upgrade is complete, it went fairly well, although I had to fiddle a bit with some of the more esoteric "fixes" I had for the previous version.

Also, I haven't looked up the old favicon from my backup yet. If something looks totally out of hand, please tell me.

Sometime, probably tonight, I will upgrade the Drupal installation. Although a minor reason, it has been one of the reasons for me not writing too much lately. This version is not particularly capable of preventing comment spam, leaving me with about 1000 SPAM comments to deal with (to get through to any possible real comments) over the last couple of months.

I've heard that 4.7 has a very good filter, which I want to try. It also makes it easier to mass delete spam comments without leafling through each and everyone.

I might possibly also upgrade the theme if all else goes well.

The

My last post was about project trackers in general, and some of the discussions around the D Bugzilla, now D Issuezilla. But most of the D projects around use Trac, much due to the fact that that is the project installed on DSource.

Bugzilla is probably still one of the most comprehensive bugtrackers around, but I find that the totality of Trac's features is much more useful. In addition to being just a system for registering and keeping tabs on them, Trac consists of