Drop IRC

Freenode imploded, and there doesn't appear to be enough interest
to justify setting up and maintaing a new chat forum.

CONTRIBUTING

@@ -3,7 +3,7 @@ Issue Guidelines
 
 1) Issues should only be created for things that are definitely bugs.
    If you are not sure that the behavior is a bug, ask about it on
-   IRC or the sequel-talk Google Group.  GitHub Issues should not be
+   the sequel-talk Google Group.  GitHub Issues should not be
    used as a help forum.
 
 2) If you are sure it is a bug, then post a complete description of
@@ -41,7 +41,7 @@ Pull Request Guidelines
    be merged.  Pull requests should not be used to "start a
    conversation" about a possible code change.  If the pull
    request requires a conversation, that conversation should take
-   place on the sequel-talk Google Group or IRC.
+   place on the sequel-talk Google Group.
 
 7) Pull requests are generally closed as soon as it appears that the
    branch will not be merged.  However, discussion about the code can
@@ -54,8 +54,7 @@ Code of Conduct
 
 This code of conduct applies to all of the project's "collaborative
 space", which is defined as community communications channels,
-including the Google Group, GitHub project, source code repository,
-and IRC channel.
+including the Google Group, GitHub project, and source code repository.
 
 1) Participants must ensure that their language and actions are free
    of personal attacks and remarks disparaging to people or groups.

ISSUE_TEMPLATE.md

@@ -1,6 +1,6 @@
 Note: If you have a question about Sequel, would like help using
 Sequel, want to request a feature, or do anything else other than
-submit a bug report, please use the sequel-talk Google Group or IRC.
+submit a bug report, please use the sequel-talk Google Group.
 
 ### Complete Description of Issue
 

README.rdoc

@@ -22,10 +22,9 @@ RDoc Documentation :: http://sequel.jeremyevans.net/rdoc
 Source Code :: https://github.com/jeremyevans/sequel
 Bug tracking (GitHub Issues) :: http://github.com/jeremyevans/sequel/issues
 Discussion Forum (sequel-talk Google Group) :: http://groups.google.com/group/sequel-talk
-IRC Channel (#sequel) :: irc://irc.freenode.net/sequel
 
 If you have questions about how to use Sequel, please ask on the
-sequel-talk Google Group or IRC.  Only use the the bug tracker to report
+sequel-talk Google Group.  Only use the the bug tracker to report
 bugs in Sequel, not to ask for help on using Sequel.
 
 To check out the source code:

www/pages/development.html.erb

@@ -1,18 +1,18 @@
 <h2>Development</h2>
 
-<p>Sequel is being actively developed.  New versions of Sequel are generally released monthly during the first week of the month. You can join in on the discussions, ask questions, suggest features, and discuss Sequel in general by joining our Google Group - <a href='http://groups.google.com/group/sequel-talk'>Sequel Talk</a> or our <a href='irc://irc.freenode.net/sequel'>IRC channel</a>.</p>
+<p>Sequel is being actively developed.  New versions of Sequel are generally released monthly during the first week of the month. You can join in on the discussions, ask questions, suggest features, and discuss Sequel in general by joining our Google Group, <a href='http://groups.google.com/group/sequel-talk'>Sequel Talk</a>.</p>
 
 <h3>Reporting Bugs</h3>
 
-<p>To report a bug in Sequel, use <a href="https://github.com/jeremyevans/sequel/issues">GitHub Issues</a>.  If you aren't sure if something is a bug, post a question on the <a href='http://groups.google.com/group/sequel-talk'>Google Group</a> or ask on <a href='irc://irc.freenode.net/sequel'>IRC</a>.  Note that GitHub Issues should not be used to ask questions about how to use Sequel, use the Google Group or IRC for that.</p>
+<p>To report a bug in Sequel, use <a href="https://github.com/jeremyevans/sequel/issues">GitHub Issues</a>.  If you aren't sure if something is a bug, post a question on the <a href='http://groups.google.com/group/sequel-talk'>Google Group</a>.  Note that GitHub Issues should not be used to ask questions about how to use Sequel, use the Google Group for that.</p>
 
 <h3>Source Code</h3>
 
 <p>The master source code repository is <a href="https://github.com/jeremyevans/sequel/">jeremyevans/sequel on github</a>.</p>
 
 <h3>Submitting Patches</h3>
 
-<p>The easiest way to contribute is to use git, post the changes to a public repository, and send a pull request, either via GitHub, the Google Group, or IRC.  Posting patches to the bug tracker or the Google Group works fine as well.</p>
+<p>The easiest way to contribute is to use git, post the changes to a public repository, and send a pull request, either via GitHub or the Google Group.  Posting patches to the bug tracker or the Google Group works fine as well.</p>
 
 <h3>License</h3>