Skip to content

Commit 6ccf57a

Browse files
committed
Drop IRC
Freenode imploded, and there doesn't appear to be enough interest to justify setting up and maintaing a new chat forum.
1 parent c676b28 commit 6ccf57a

File tree

4 files changed

+8
-10
lines changed

4 files changed

+8
-10
lines changed

CONTRIBUTING

+3-4
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ Issue Guidelines
33

44
1) Issues should only be created for things that are definitely bugs.
55
If you are not sure that the behavior is a bug, ask about it on
6-
IRC or the sequel-talk Google Group. GitHub Issues should not be
6+
the sequel-talk Google Group. GitHub Issues should not be
77
used as a help forum.
88

99
2) If you are sure it is a bug, then post a complete description of
@@ -41,7 +41,7 @@ Pull Request Guidelines
4141
be merged. Pull requests should not be used to "start a
4242
conversation" about a possible code change. If the pull
4343
request requires a conversation, that conversation should take
44-
place on the sequel-talk Google Group or IRC.
44+
place on the sequel-talk Google Group.
4545

4646
7) Pull requests are generally closed as soon as it appears that the
4747
branch will not be merged. However, discussion about the code can
@@ -54,8 +54,7 @@ Code of Conduct
5454

5555
This code of conduct applies to all of the project's "collaborative
5656
space", which is defined as community communications channels,
57-
including the Google Group, GitHub project, source code repository,
58-
and IRC channel.
57+
including the Google Group, GitHub project, and source code repository.
5958

6059
1) Participants must ensure that their language and actions are free
6160
of personal attacks and remarks disparaging to people or groups.

ISSUE_TEMPLATE.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
Note: If you have a question about Sequel, would like help using
22
Sequel, want to request a feature, or do anything else other than
3-
submit a bug report, please use the sequel-talk Google Group or IRC.
3+
submit a bug report, please use the sequel-talk Google Group.
44

55
### Complete Description of Issue
66

README.rdoc

+1-2
Original file line numberDiff line numberDiff line change
@@ -22,10 +22,9 @@ RDoc Documentation :: http://sequel.jeremyevans.net/rdoc
2222
Source Code :: https://github.com/jeremyevans/sequel
2323
Bug tracking (GitHub Issues) :: http://github.com/jeremyevans/sequel/issues
2424
Discussion Forum (sequel-talk Google Group) :: http://groups.google.com/group/sequel-talk
25-
IRC Channel (#sequel) :: irc://irc.freenode.net/sequel
2625

2726
If you have questions about how to use Sequel, please ask on the
28-
sequel-talk Google Group or IRC. Only use the the bug tracker to report
27+
sequel-talk Google Group. Only use the the bug tracker to report
2928
bugs in Sequel, not to ask for help on using Sequel.
3029

3130
To check out the source code:

www/pages/development.html.erb

+3-3
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,18 @@
11
<h2>Development</h2>
22

3-
<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>
3+
<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>
44

55
<h3>Reporting Bugs</h3>
66

7-
<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>
7+
<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>
88

99
<h3>Source Code</h3>
1010

1111
<p>The master source code repository is <a href="https://github.com/jeremyevans/sequel/">jeremyevans/sequel on github</a>.</p>
1212

1313
<h3>Submitting Patches</h3>
1414

15-
<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>
15+
<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>
1616

1717
<h3>License</h3>
1818

0 commit comments

Comments
 (0)