Renaming: MeatBot->MeetBot

- Holger and I agreed that this will replace the current eggdrop-based
  meetbot.  But plus, the module can be named better regardless of the
  irc nick of our bot.

darcs-hash:20090507231702-82ea9-5268cfbcc36208515436d5669f45b2f494e608a0.gz

1 files changed, 7 insertions, 5 deletions

diff --git a/README.txt b/README.txt
index dfec6a6..6525013 100644
--- a/README.txt
+++ b/README.txt
@@ -1,8 +1,10 @@
 USAGE
 ~~~~~
-http://wiki.debian.org/MeatBot
+http://wiki.debian.org/MeetBot
 
-Inspired by http://wiki.debian.org/MeetBot
+Inspired by the original MeetBot, by Holger Levsen, which was itself a
+derivative of Mootbot (https://wiki.ubuntu.com/ScribesTeam/MootBot),
+by the Ubuntu Scribes team.
 
 /usr/share/doc/supybot/GETTING_STARTED.gz (on Debian systems) provides
 information on configuring supybot the first time, including taking
@@ -23,7 +25,7 @@ Requirements:
       supybot.reply.whenAddressedBy.chars: 
     in the config file - leave it blank afterwards.)
 
-* Move the MeatBot directory into your plugins directory of Supybot.
+* Move the MeetBot directory into your plugins directory of Supybot.
 
 * Make supybot join any channels you are interested in.  The wizard
   handles this for the first part.  After that, I guess you have to
@@ -32,12 +34,12 @@ Requirements:
   command the bot after it's online.
 
 * Make sure the plugin is loaded.
-    supybot.plugins: Admin Misc User MeatBot Owner Config Channel
+    supybot.plugins: Admin Misc User MeetBot Owner Config Channel
   (can also control loading after the bot is started)
 
 Supybot does a lot, but I don't know much about it.  Hopefully Supybot
 expert users can enlighten me as to better ways to do things.
 
 In particular, supybot has a large configuration system, which I know
-nothing about.  It may be worth hooking MeatBot into that system.
+nothing about.  It may be worth hooking MeetBot into that system.