I'm all for goofing off, being sarcastic and making odd comments that only I laugh at, but let's please try to keep this thread from heading into the need-to-be-locked thread and stay on topic.

I really want to rally for Alex. I know, I know, I've said it several times and there are many reservations to consider, but seriously, the majority felt agreeable with him as the mascot/logo and with this community, a majority in anything is remarkable and rare. We should first try and look at any way possible of using Alex without having to change any kind of item within the license. If all routes are exhausted, then we should go with plan B. It seems illogical to me to be attempting this "let's choose something else route" when maybe there's still a path to having Alex.

Thus, we need to bring Johan here. It's his and if there's anything we can do to obtain the rights to Alex, he would let us know. If he wants a sum of money (even if it is really high), then that is an option. If he wants something else, then that could be an option. We've got some sexy women if it comes to that...

Anywho, I think Alex being the official mascot/logo could only be a good thing for FLD (Free Lunch Design). Ultimately, if we have the rights, Alex will still have ties with FLD and any publicity is good for him. Someone who sees the unfamiliar logo might try to look up allegro or the alligator, which will ultimately lead to allegro and FLD. Surely that's a good thing.

Closing the thread because 1) most people aren't serious, 2) it doesn't concern Allegro development, and 3) I would never hold any sort of public vote on a.cc for a mascot as its totally against my anti-democracy ideals.

As a tip, here's how Allegro related stuff works:

ask a general question to make sure your idea won't be shot down.

Do it!

Throwing 200 opinions into the mix is just a recipe for disaster.

So it would go like this:

Ask the question: "Would anyone be opposed to a mascot."

Developers give a clear outline of where it would and wouldn't be used.

Create one. A final version. A complete working copy.

Submit it to the developers.

They accept or reject it.

See how easy that is?

If we held these sorts of committee discussions where everyone who has never given a real thought about Allegro before got to give input, we'd still be using Allegro 0.1.