Greetings all, I've been meaning to write this for a while now, but I've been shamelessly delaying based on some work I wanted to get together prior to sending this. You'll understand why a little later in this email... Firstly, some short-term items for discussion. I'm currently envisioning two more updates to the Bahamut 1.x - possibly with a few little patch releases as well - but two major updates. First release: - Client side SSL support - Small functionality changes - Internal and protocol support for IPV6 addresses. Second release: - Full IPV6 support - Other possible features, such as user host masking. The logic between the two separate releases is simple - we need to support ipv6 without accepting connections from ipv6 sources. Without this first step, we will break all kinds of things. NICKIP (the server<>server capab) is a good example of this. I'm hoping we can have a lively discussion on the other items. I have no doubt user hostmasking will result in some loud opinions. Lets hear them! Second, some housekeeping. As you may have noticed, we've switched to git as our version control system. This means a few different things in how we're managing code contributions. I'd really like to encourage active participation from anyone and everyone to submit patches - I will review everything that gets posted to this list, and fold them into the master tree as things go. The coding team will also play a big part of the review process. Putting it bluntly - they're on the same footing as everyone else on their ability to get code into the master tree. I'll likely review their patches less intensely, simply because I know their work... I will also shortly be changing the git tree to send an email to this list when I update the master. I'm hoping we can get enough exposure and transparency to get more of you actively involved. If you're looking for something to do, the IPv6 stuff is high on the list! The last, and final point of discussion - the infamous Bahamut 2.0. We've had a lot of discussion and, bluntly, vaporware type statements about Bahamut 2.0 in the past. It was going to be amazing, fully modular, a complete rewrite, wash your car, satisfy your wife, etc etc. Well, until about four months ago, nothing of Bahamut 2.0 ever actually got started. Four months ago I started a small framework library I wanted to use for the basis of Bahamut 2. I haven't been working too hard on it - I haven't had a lot of time.. but this week I've got it to the point of an echo server. In the next week or so, I'll make the code available. In a separate email, I'll detail a lot of the work that I've done so far, and what direction I'd like to see on the system. The currently library is far from complete, but I'm hoping we can get some involvement from the community to jump-start this effort. Look forward to another email this morning detailing the general design goals! Thanks, -epiphani