|Version 5 (modified by brosner, 7 years ago) (diff)|
The #django IRC channel has bot that aides everyone with some pretty basic tasks. It takes the identify of the nickname DjangoBot. It is currently written using the Twisted networking library and can be found at http://code.google.com/p/djangobot/. It is written and maintained by Brian Rosner.
Trac Ticket/Changeset Linking
It is very common for someone to reference a ticket or changeset in the IRC room. The DjangoBot will handle the linking for you if you follow the basic syntax it requires. To reference a ticket simply use the Trac syntax #13. The same applies to changesets, r530. The DjangoBot does not work with the square bracket notation due to IRC nickname collisions for those who use square brackets around their numbered name.
The excellent djangopeople.net website created by Simon Willison and Natalie Downe is integrated with the bot. If you send a privmsg to the bot you can find out a bit more information about the peers you talk with in #django. Simply do:
/msg DjangoBot who brosner
The bot will then go out and fetch information about brosner. This works with any IRC handle that is associated to a profile on DjangoPeople. The who command also accepts multiple nicknames separated by spaces. You can also do:
/msg DjangoBot who brosner empty
Multiple Channel Support
The bot has the ability to live in more than one channel. This will be useful during sprints when #django and #django-sprint channels are in use.
Ticket/Changeset Channel Notification
The bot will now notify when tickets are opened/closed/reopened and changesets to the Django source code. It follows this timeline RSS feed.
Dpaste Channel Notification
There is the possibility of doing some form of integration with the official Django pastebin, dpaste.com. There is no word on what the integration will look like, but a good future feature.
If you happen to come across a bug with the bot, please head over to http://code.google.com/p/djangobot/issues/list and check if it has already been issued, if not please create a new issue!