Actually, the web site only lists a single channel @ - users joining that channel end up with everyone else.

Talking of the website, and the reference to team and keeping everyone in the loop - could someone direct me to a link or forward the post to the mailing list about the new website going live 2-3 weeks ago as I think it may have got spam filtered at my end. Thanks in advance


On Mon, Mar 3, 2014 at 11:14 PM, Damien Regad <> wrote:
On 2014-03-03 21:29, Paul Richards wrote:
> John merged #mantisbt-help into #mantisbt for me so that we are better
> aligned to what other projects do.

WTF !?

I mean, I don't care whether we have 1, 2 or 357 IRC channels, and in
fact it kind of makes sense to only have one especially considering that
there's hardly anyone on it nowadays.

I really do believe however, that this kind of decision and subsequent
action should have been discussed and agreed with the team first, if
only to coordinate the necessary actions such as updating the website &
log archives and the bot.

Paul you *really* need to behave like a responsible member of the team,
instead of always being a loose cannon. Or if you don't want to do that,
maybe you should just go fork yourself - and please excuse the horrible
pun, I just couldn't resist ;-)

> The bot needs updating to reflect this. I did try messaging victor twice
> over the weekend to do this but didn't get a response.

And it didn't even occur to you to just wait until he or someone else
was available, before making the change ?

>  In addition, Victor's still not fixed my access to the
> <> box, so i've not been able to update myself.

I'm sorry to say that, but he's certainly not done it for a reason, and
right now I'm thinking he was absolutely right not to grant you access.

And I would like to add that if you're going to do something, then at
least you should do it right...

/join #mantisbt
-ChanServ- [#mantisbt] For questions or support, please join #mantisbt-help

/join #mantisbt-help
* Cannot join #mantisbt-help (Channel is invite only).


Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
mantisbt-dev mailing list