diff README.SVN @ 16071:5e436cd088e4

merge of '6c54a71cc08e47f3b1498c61ee62d17107165817' and 'eae479abc840db2b4808b2de16397086deefab3b'

--- a/README.SVN	Wed Apr 11 17:51:32 2007 +0000
+++ b/README.SVN	Wed Apr 11 18:03:09 2007 +0000
@@ -1,41 +1,39 @@
-If you plan to use gaim SVN, PLEASE read this message in its entirety!
+If you plan to use Pidgin, Finch & libpurple mtn, PLEASE read this message in its entirety!
 
-Gaim is a fast-moving project with a somewhat regular release schedule.
-Due to the rate of gaim development, SVN undergoes frequent bursts of
-massive changes, often leaving behind brokenness and partial
-functionality while the responsible developers rewrite some portion of
-code or seek to add new features.
+Pidgin, Finch & libpurple is a fast-moving project with a somewhat regular
+release schedule. Due to the rate of Pidgin, Finch & libpurple development,
+mtn undergoes frequent bursts of massive changes, often leaving behind
+brokenness and partial functionality while the responsible developers rewrite
+some portion of code or seek to add new features.
 
-What this all boils down to is that SVN _WILL_ sometimes be broken.
+What this all boils down to is that mtn _WILL_ sometimes be broken.
 Because of this, we ask that users who are not interested in
 personally tracking down bugs and fixing them (without a lot of
-assistance from the developers!) avoid SVN and use releases.  Since
+assistance from the developers!) avoid mtn and use releases.  Since
 releases will be made often, this should not prevent anyone from using
 the newest, shiniest features -- but it will prevent users from having
 to deal with ugly development bugs that we already know about but
 haven't gotten around to fixing.
 
-If you are interested in hacking on gaim, please read README and
-HACKING, and take note of the issues in PROGRAMMING_NOTES.  (Note that
-they may be somewhat out of date at times.) Win32 developers, please
+If you are interested in hacking on Pidgin, Finch & libpurple, please read
+README and HACKING, and take note of the issues in PROGRAMMING_NOTES.  (Note
+that they may be somewhat out of date at times.) Win32 developers, please
 read README.mingw.
 
 By far the best documentation, however, is the documented code.  Not
-all parts of gaim have yet been documented, but the major subsystems
-are falling fast.  If you have doxygen, you can use the Doxyfile in
+all parts of Pidgin, Finch & libpurple have yet been documented, but the major
+subsystems are falling fast.  If you have doxygen, you can use the Doxyfile in
 the toplevel directory to generate pretty documentation.  Otherwise
 (or even if you do!), the header files for each subsystem contain
 documentation for the functions they contain.  For instance,
-conversation.h contains documentation for the entire
-gaim_conversation_* API, and account.h contains documentation for the
-gaim_account_* API.
+conversation.h contains documentation for the entire purple_conversation_*
+API, and account.h contains documentation for the purple_account_* API.
 
-If you have questions, please feel free to contact the gaim developers
-by email at [e-mail], on IRC at
-irc.freenode.net in #gaim, or via the sourceforge forums at
-http://www.sourceforge.net/projects/gaim.  Please do as much homework
-as you can before contacting us; the more you know about your
-question, the faster and more effectively we can help you!
+If you have questions, please feel free to contact the Pidgin, Finch &
+libpurple developers by email at [e-mail] or on IRC at irc.freenode.net
+in #pidgin.  Please do as much homework as you can before contacting us; the
+more you know about your question, the faster and more effectively we can help
+you!
 
-Send patches to [e-mail] or post them in the
-Sourceforge forums at http://www.sourceforge.net/projects/gaim.
+Send patches to Pidgin, Finch & libpurple mailing list, [e-mail], or
+post them in the tracker at http://developer.pidgin.im.