We've gotten some comments/suggestions over the last year or so about becoming more "IRCv3" compliant...More info available here: http://ircv3.atheme.org/ And I know we've beaten this to death before, but I'm still very much in favor of some sort of user hostmasking, whether hash-based in the ircd, or tied to services - in such a way where staff (and law enforcement if necessary) would still be able to see real IPs. :) Brandon brandon@dalnet [irc.dal.net] Routing & Peering Team Lead On 5/24/2013 8:27 AM, Aaron Wiebe wrote:
Hi all,
The bug in 2.0.6 should have been identified in the code review and testing phase - and I feel like we got some egg on our face as a result. I wanted to take a moment to comment on it, and apologize.
The fact that this bug, being fairly big and obvious, got through the process reflects that I've been a bit lax in reviews and testing. I'm personally going to change my review and approval process to try to resolve these issues, through a more formal off-trunk review.
Bahamut as a project is effectively in a maintenance phase, as we don't have anyone working on it as actively as we previously have. We release new versions sporadically, and don't have a roadmap or any "next big thing". This is actually part of the problem - without goals, we have a lot fewer eyes on individual changes, and we're not all driving towards anything.
So with that said, I'd like to put it to the community to discuss what we could put on our roadmap. Little things and big things. Let's brainstorm - what would you like to see in Bahamut? And out of this discussion, maybe we can line up a roadmap for 2.1, 2.2 and maybe even a 3.0.
What would you like to see in Bahamut?
-Aaron