6 files changed, 19 insertions, 26 deletions
diff --git a/doc/_static/github.png b/doc/_static/github.png
new file mode 100644
index 00000000..5d146adc
--- /dev/null
+++ b/doc/_static/github.png
diff --git a/doc/_templates/indexsidebar.html b/doc/_templates/indexsidebar.html
index 50653d75..5544f98a 100644
--- a/doc/_templates/indexsidebar.html
+++ b/doc/_templates/indexsidebar.html
@@ -3,8 +3,8 @@
 <p>This documentation is for version <b>{{ version }}</b>, which is
   not released yet.</p>
 <p>You can use it from the
-  <a href="http://bitbucket.org/birkenfeld/sphinx/">Mercurial repo</a> or look for
-  released versions in the <a href="http://pypi.python.org/pypi/Sphinx">Python
+  <a href="http://github.com/pygments/pygments/">Git repo</a> or look for
+  released versions in the <a href="http://pypi.python.org/pypi/Pygments">Python
     Package Index</a>.</p>
 {% else %}
 <p>Current version: <b>{{ version }}</b></p>
@@ -15,9 +15,10 @@
 
 <h3>Questions? Suggestions?</h3>
 
-<p>Clone at <a href="https://bitbucket.org/birkenfeld/pygments-main">Bitbucket</a></p>
+<p><img src="{{ pathto("_static/github.png", 1) }}" width="24" />
+    Clone at <a href="https://github.com/pygments/pygments">GitHub</a>.</p>
 <p>You can also open an issue at the
-  <a href="https://www.bitbucket.org/birkenfeld/pygments-main/issues/">tracker</a>.</p>
+  <a href="https://github.com/pygments/pygments/issues">tracker</a>.</p>
 
 <p class="logo">A <a href="http://pocoo.org/">
-    <img src="{{ pathto("_static/pocoo.png", 1) }}" /></a> project</a></p>
-\ No newline at end of file
+    <img src="{{ pathto("_static/pocoo.png", 1) }}" /></a> project</a></p>
diff --git a/doc/docs/lexerdevelopment.rst b/doc/docs/lexerdevelopment.rst
index 63bd01a3..5b6813fb 100644
--- a/doc/docs/lexerdevelopment.rst
+++ b/doc/docs/lexerdevelopment.rst
@@ -136,7 +136,7 @@ have to perform the following steps.
 
 First, change to the current directory containing the Pygments source code.  You
 will need to have either an unpacked source tarball, or (preferably) a copy
-cloned from BitBucket.
+cloned from GitHub.
 
 .. code-block:: console
 
@@ -611,7 +611,7 @@ possibility to influence the position.
 There are not really any simple examples for lexer callbacks, but you can see
 them in action e.g. in the `SMLLexer` class in `ml.py`_.
 
-.. _ml.py: http://bitbucket.org/birkenfeld/pygments-main/src/tip/pygments/lexers/ml.py
+.. _ml.py: https://github.com/pygments/pygments/blob/master/pygments/lexers/ml.py
 
 
 The ExtendedRegexLexer class
@@ -667,7 +667,7 @@ For example, this is how the hypothetical lexer above would be written with the
 This might sound confusing (and it can really be). But it is needed, and for an
 example look at the Ruby lexer in `ruby.py`_.
 
-.. _ruby.py: https://bitbucket.org/birkenfeld/pygments-main/src/tip/pygments/lexers/ruby.py
+.. _ruby.py: https://github.com/pygments/pygments/blob/master/pygments/lexers/ruby.py
 
 
 Handling Lists of Keywords
diff --git a/doc/download.rst b/doc/download.rst
index cf32f481..975c41b0 100644
--- a/doc/download.rst
+++ b/doc/download.rst
@@ -18,17 +18,15 @@ manager as usual.
 Development sources
 -------------------
 
-We're using the `Mercurial <http://selenic.com/mercurial>`_ version control
-system.  You can get the development source using this command::
+We're using the Git version control system.  You can get the development source
+using this command::
 
-    hg clone http://bitbucket.org/birkenfeld/pygments-main pygments
+    git clone https://github.com/pygments/pygments
 
-Development takes place at `Bitbucket
-<http://bitbucket.org/birkenfeld/pygments-main>`_, you can browse the source
-online `here <http://bitbucket.org/birkenfeld/pygments-main/src>`_.
+Development takes place at `GitHub <https://github.com/pygments/pygments>`_.
 
 The latest changes in the development source code are listed in the `changelog
-<http://bitbucket.org/birkenfeld/pygments-main/src/tip/CHANGES>`_.
+<https://github.com/pygments/pygments/blob/master/CHANGES>`_.
 
 .. Documentation
    -------------
@@ -36,6 +34,6 @@ The latest changes in the development source code are listed in the `changelog
 .. XXX todo
 
    You can download the <a href="/docs/">documentation</a> either as
-      a bunch of rst files from the Mercurial repository, see above, or
+      a bunch of rst files from the Git repository, see above, or
       as a tar.gz containing rendered HTML files:</p>
       <p><a href="/docs/download/pygmentsdocs.tar.gz">pygmentsdocs.tar.gz</a></p>
diff --git a/doc/faq.rst b/doc/faq.rst
index 172929e0..28db1d2a 100644
--- a/doc/faq.rst
+++ b/doc/faq.rst
@@ -62,9 +62,9 @@ Please see the :doc:`documentation on styles <docs/styles>`.
 How can I report a bug or suggest a feature?
 --------------------------------------------
 
-Please report bugs and feature wishes in the tracker at Bitbucket.
+Please report bugs and feature wishes in the tracker at GitHub.
 
-You can also e-mail the author or use IRC, see the contact details.
+You can also e-mail the authors, see the contact details.
 
 I want this support for this language!
 --------------------------------------
diff --git a/doc/index.rst b/doc/index.rst
index 26114045..3a2d88c9 100644
--- a/doc/index.rst
+++ b/doc/index.rst
@@ -26,15 +26,9 @@ Like every open-source project, we are always looking for volunteers to help us
 with programming. Python knowledge is required, but don't fear: Python is a very
 clear and easy to learn language.
 
-Development takes place on `Bitbucket
-<https://bitbucket.org/birkenfeld/pygments-main>`_, where the Mercurial
-repository, tickets and pull requests can be viewed.
+Development takes place on `GitHub <https://github.com/pygments/pygments>`_.
 
-Our primary communication instrument is the IRC channel **#pocoo** on the
-Freenode network. To join it, let your IRC client connect to
-``irc.freenode.net`` and do ``/join #pocoo``.
-
-If you found a bug, just open a ticket in the Bitbucket tracker. Be sure to log
+If you found a bug, just open a ticket in the GitHub tracker. Be sure to log
 in to be notified when the issue is fixed -- development is not fast-paced as
 the library is quite stable.  You can also send an e-mail to the developers, see
 below.