Service/meeting
Hostnames
- meeting.sugarlabs.org
Hosted on
Administrative contact
- meeting AT sugarlabs DOT org
Sysadmins
Notes
IRC bot with plugins and perl CGI access to IRC logs in local MySQL db using modified ilbot webui.
IRC bot
This new bot replaces the older Mootbot with Supybot.
| Home | /srv/supybot
|
|---|---|
| Daemon | /etc/init.d/supybot
|
| Logs | /srv/supybot/log
|
| Config | /srv/supybot/bot.conf
|
Everything, except owner related configuration, should happen via IRC interface with using flush command to save changes immediately.
Supybot plugins:
- MeetBot in
/srv/supybot/plugins/MeetBot
Handle meetings. - MyLogger in
/srv/supybot/plugins/MyLogger
Keep IRC logs in MySQL database. - Lingvo in
/srv/supybot/plugins/Lingvo
Online translation on IRC.
Web logs
| Home | /srv/ilbot
|
|---|---|
| Config | /etc/httpd/conf.d/ilbot.conf
|
| Source | http://git.sugarlabs.org/sl-tweaks/ilbot |
Upgrade notes
This new bot replaces the older Mootbot with Supybot.
No need in manual configuration, all happens via Puppet module.
All, except nick, directly related to bot parameters can be setup only on initialization stage. Later bot can be configured from IRC interface (preferable) or changing /srv/supybot/bot.conf.
Usage
Bot is named meeting. It supports many useful features, read the Supybook to learn them.
Join the bot
To join the bot to your IRC channel, email your request.
Logging
The bot supports keeping logs for further browsing on meeting.sugarlabs.org. This feature is disabled by default, to enable it, email your request.
Handling meetings
The bot has MeetBot plugin to handle meeting on channels it joined to. Read MeetBot tutorial to learn how to handle meetings.
Meeting logs are stored on meeting.sugarlabs.org (even if logging is disabled). Go to channel page and click Meetings link (rightmost switch in toolbar).
Multi-lingual relaying
Translation is provided by Apertium project. If it is not good, please consider possibility to improve it.
Be patent, keep special words untranslated and avoid short phrases while chatting with people on translation channels.
The bot supports language translation relaying. It is plugin implementation of transbot.
It is about implicit translation for particular IRC channel into several languages. People being in satellite channels, like #sugar-ru, can type posts in Russian, all theses posts will be translated into English and posted to #sugar. The same works in opposite direction.
The easiest way to try it is web client. On login screen, choose one of sugar channels and the language you want to type posts in. Language might be Default that means that you need to type in default language for IRC channel from the list. After being logged in, you can all time open new Sugar channel using combo boxes on the leftmost side of upper toolbar.
IRC command interface
Translation process might be managed from IRC commands sent to meeting nick.
List channels that can be translated (primal channels) with current translation status:
meeting: lingvo list [channel]
List supported languages:
meeting: lingvo langs
Open new translation channel:
meeting: lingvo join [primal-channel] lang
By default, empty translation channels will be closed in 3 days. To prevent it:
meeting: lingvo pin [translation-channel] meeting: lingvo unpin [translation-channel]
List all nicks that take part in conversation, i.e., nicks from the primal channel and nicks from all translation channels:
meeting: lingvo nicks [channel]
If command output is too big, use more command to get the rest of output:
meeting: more
Keep special phrases untranslated
While keeping phrases untranslated, the system tries to be as obvious as possible.
To not process translation where it doesn't make sense, warp the text into the double quotes. To pass entirely post untranslated, start it from the double quotes (there is no need in ending the post by second double quote).
Other cases where text won't be translated:
- channel names (words started from # symbol),
- nick names.