With a little luck, I'm getting this blog posting out before midnight CET. I've just finished the draft of the open source template site and am handing over to leiger.

About a month ago we (Ed Johnson, leiger and myself) started on a project to build a blog template site and it's ready to test.

It's Tuesday, again, and that means it's time for the Tuesday Rant. This is the thread where you get to complain to us, and we get to ignore you totally without even reading your comments. Just kidding - we read every comment carefully before totally ignoring it.

I just updated my Gmail filter to send traffic from the new polls.wikidot.com project to my Wikidot Community label. Gmail said, "Updating 17,000 conversations". That's the number of conversations (not emails, but threads) that have happened on the various Wikidot community sites since I started following them all about three months ago.

Something that's happening quite regularly now is (a) someone suggests new feature or change and (b) I realize we've already got a detailed design that covers this feature, in our internal issue tracker, and (c) I explain what we want to make, and regret not telling that person in advance.

You'll have noticed that there is a very common stone-and-sand pattern: person A writes something, and people B, C, and D discuss it. Such a common pattern, but still hard to use when the discussion gets long.

Today, a question to those using Wikidot for ongoing projects. Do you make a distinction between discussions written in sand, and those written in stone? And if so, how do you make this distinction using Wikidot?