Markout v13 released.

We (meaning "I") have now put up the inaugural v13.0.0 release of Markout, the Markdown-based wiki parser that will become something of a fixture in boomstick... And just in time for Christmas! Yes, this holiday season, give the gift that lasts a lifetime: free software. She'll love you for it.

Also, the astute may notice that my personal vanity page has been updated accordingly.

jll:

Why don't you just name the project and list yourself as the [project name] Team. I've seen several open source projects eventually piss off the owner so much that they refuse to work on it anymore. (Or they start raking in so much dough that they don't think it is worth their valuable time anymore.) Then somebody starts up a [project name] Team to take over and the licensing and support get all screwed up. Just assume that it will be wildly popular but piss you off to no end so you will eventually abandon it, and figure out the name of the group who should take over. Name it that.

nw:

This is a remarkably lucid analysis. Here I'd been thinking of picking a name I wanted to keep, but really I should be picking a name that I feel most comfortable drunkenly cursing.

Incisive.

jll:

I find it hard to believe that you would find any name uncomfortable to drunkenly curse. You could name it after an ex.

gibo:

Au contraire, some names are definitely better than others for drunkenly cursing. For instance, drunkenly curse anyone named "Tiffany" or "Britney" and you look like a fool for caring in the first place. Drunkenly curse somebody named "Vauldevarre" and bam, you're the person who gets killed in the next fifteen minutes of a Vampire Hunter D anime. ("DAMN YOU VAULDEVARRE!!!" *slice*) Names are actually absolutely crucial for contextualizing drunken cursing. My rule of thumb is to never drunkenly curse any name that sounds like it belongs to a porn star, or which Japanese people might consider Goth.

So, I'm about to put out an open source project. It's nothing big, just a couple of classes, an extension for a markdown parser that adds a kind of freelink and thereby turns it into a simple wiki parser. Nothing fancy. Now, the reason I'm doing this is because I want to integrate it into *another* project I'm working on, which is a wonky cms thing because there aren't already eight million frickin' cms's in the world already, and that last use of the word "already" was shamefully redundant.

So, I haven't released an open source project on my own before, so I'm debating what name to use to release it. Should I use my name, or should I make up some name like "Exegetic Labs" or "Throbbing Elephant Cock" or whatever? It would be nice to release these, and any future oss projects, under one consistent name. It would probably also be nice if, in the unlikely event that anyone else ever decides to contribute, that name is not strictly mine. There is, of course, no legally-recognized corporation/organization/etc. involved. I guess it'll probably only be relevant in license text and whatnot, and to a great extent this all probably doesn't make a bit of difference, but I love to other-think simple matters.

Opinions?