Introduction

For this to work you need a working GZRBOT and GOZERBOT both installed from mercurial repo.

GZRBOT: hg clone http://gzrbot.googlecode.com/hg
GOZERBOT: hg clone http://core.gozerbot.org/hg/dev/0.9

Setting up the GOZERBOT

GOZERBOT needs 2 bots in the fleet to work properly .. one to IRC and one to a Jabber server so it can communicate with the GZRBOT. You can use the gozerbot.org server to register a bot there.

first connect to IRC:

from your shell do the following ..

./bin/gozerbot -n default -o <userhost of owner> -s <server> -c <\#channel> 

that should join your channel on the server provided (the \ is to escape the # in the shell) Once you got that working, try the following to connect the gozernet (jabber) bot. You need to give the gozernet bot the name 'gozernet' because the bot itself uses this name.

./bin/gozerbot -n gozernet -t gozernet -o <gtalk or jabber id of the owner> -u <jabberid of the bot>

you might need to start gozerbot twice if the regiser doesnt work the first time.

So once you got the jabber bot working as well start the bot with just ./bin/gozerbot .. this should start bot the IRC and Jabber bot.

Setting up the GZRBOT

you need to upload your GZRBOT to the GAE if you havent already done so .. make sure you have the owner set to your gtalk account so you can give the bot command from the gmail client. Once that is working add your wave account to your gtalk account with the following command:

!user-import <wave account> (from your gtalk) 

verify that this worked by typing !whoami in your wave .. this should reply with your gtalk account.

Enabling the relaying between GOZERBOT and GZRBOT

on the GOZERBOT side type the following:

!reload gozernet
!gozernet-addout <jabberid of GZRBOT>
!gozernet-forward <irc channel>
!reload watcher
!watcher-start <waveid>

on the GZRBOT side:

!gozernet-addout <jabberid of GOZERBOT>
!gozernet-forward <waveid>
!relay gozernet <irc channel>
!watcher-start <irc channel>

this should be it ! only relaying of text said in the channel is supported for now (no QUIT etc.) because for QUIT's we need to maintain a userhost cache of which user is in which channel and thats not implemented right now.