Update links to github.com/torchbox to point to github.com/wagtail

CONTRIBUTING.md

@@ -7,7 +7,7 @@ documentation, translations or just feature requests.
 
 ## Using the issue tracker
 
-The [issue tracker](https://github.com/torchbox/wagtail/issues) is
+The [issue tracker](https://github.com/wagtail/wagtail/issues) is
 the preferred channel for [bug reports](#bugs), [features requests](#features)
 and [submitting pull requests](#pull-requests). Please don't use the issue tracker
 for support - use our [Wagtail support group](https://groups.google.com/forum/#!forum/wagtail).
@@ -17,11 +17,11 @@ for support - use our [Wagtail support group](https://groups.google.com/forum/#!
 Please review the 
 [contributing guidelines](http://docs.wagtail.io/en/latest/contributing/index.html). 
 You might like to start by checking issues with the 
-[difficulty:Easy](https://github.com/torchbox/wagtail/labels/difficulty%3AEasy) label.
+[difficulty:Easy](https://github.com/wagtail/wagtail/labels/difficulty%3AEasy) label.
 
 ## Code reviews
 
-We welcome code reviews from everyone. There's always a list of pull requests tagged ['Needs review'](https://github.com/torchbox/wagtail/pulls?q=is%3Apr+is%3Aopen+label%3A%22Needs+review%22).
+We welcome code reviews from everyone. There's always a list of pull requests tagged ['Needs review'](https://github.com/wagtail/wagtail/pulls?q=is%3Apr+is%3Aopen+label%3A%22Needs+review%22).
 
 ## Translations
 

README.rst

@@ -1,5 +1,5 @@
-.. image:: https://api.travis-ci.org/torchbox/wagtail.svg?branch=master
-    :target: https://travis-ci.org/torchbox/wagtail
+.. image:: https://api.travis-ci.org/wagtail/wagtail.svg?branch=master
+    :target: https://travis-ci.org/wagtail/wagtail
 .. image:: https://img.shields.io/pypi/l/wagtail.svg
     :target: https://pypi.python.org/pypi/wagtail/
 .. image:: https://img.shields.io/pypi/v/wagtail.svg
@@ -76,6 +76,6 @@ Contributing
 ~~~~~~~~~~~~
 If you're a Python or Django developer, fork the repo and get stuck in! We run a separate group for developers of Wagtail itself at https://groups.google.com/forum/#!forum/wagtail-developers (please note that this is not for support requests).
 
-You might like to start by reviewing the `contributing guidelines <http://docs.wagtail.io/en/latest/contributing/index.html>`_ and checking issues with the `difficulty:Easy <https://github.com/torchbox/wagtail/labels/difficulty%3AEasy>`_ label.
+You might like to start by reviewing the `contributing guidelines <http://docs.wagtail.io/en/latest/contributing/index.html>`_ and checking issues with the `difficulty:Easy <https://github.com/wagtail/wagtail/labels/difficulty%3AEasy>`_ label.
 
 We also welcome translations for Wagtail's interface. Translation work should be submitted through `Transifex <https://www.transifex.com/projects/p/wagtail/>`_.

docs/advanced_topics/api/index.rst

@@ -11,7 +11,7 @@ There are currently two versions of the API available: v1 and v2. Both versions
 are "stable" so it is recommended to use v2. V1 is only provided for backwards
 compatibility and will be removed from Wagtail soon.
 
-See `RFC 8: Wagtail API <https://github.com/torchbox/wagtail-rfcs/blob/master/accepted/008-wagtail-api.rst#id4>`_
+See `RFC 8: Wagtail API <https://github.com/wagtail/wagtail-rfcs/blob/master/accepted/008-wagtail-api.rst#id4>`_
 for full details on our stabilisation policy.
 
 Version 2 (recommended)

docs/contributing/committing.rst

@@ -22,7 +22,7 @@ Check out the code locally
 
 If the code has been submitted as a pull request,
 you should fetch the changes and check them out in your Wagtail repository.
-A simple way to do this is by adding the following ``git`` alias to your ``~/.gitconfig`` (assuming ``upstream`` is ``torchbox/wagtail``):
+A simple way to do this is by adding the following ``git`` alias to your ``~/.gitconfig`` (assuming ``upstream`` is ``wagtail/wagtail``):
 
 .. code-block:: text
 

docs/contributing/developing.rst

@@ -3,9 +3,9 @@
 Development
 -----------
 
-Setting up a local copy of `the Wagtail git repository <https://github.com/torchbox/wagtail>`_ is slightly more involved than running a release package of Wagtail, as it requires `Node.js <https://nodejs.org/>`_ and NPM for building Javascript and CSS assets. (This is not required when running a release version, as the compiled assets are included in the release package.)
+Setting up a local copy of `the Wagtail git repository <https://github.com/wagtail/wagtail>`_ is slightly more involved than running a release package of Wagtail, as it requires `Node.js <https://nodejs.org/>`_ and NPM for building Javascript and CSS assets. (This is not required when running a release version, as the compiled assets are included in the release package.)
 
-If you're happy to develop on a virtual machine, the `vagrant-wagtail-develop <https://github.com/torchbox/vagrant-wagtail-develop>`_ setup script is the fastest way to get up and running. This will provide you with a running instance of the `Wagtail demo site <https://github.com/torchbox/wagtaildemo/>`_, with the Wagtail and wagtaildemo codebases available as shared folders for editing on your host machine.
+If you're happy to develop on a virtual machine, the `vagrant-wagtail-develop <https://github.com/wagtail/vagrant-wagtail-develop>`_ setup script is the fastest way to get up and running. This will provide you with a running instance of the `Wagtail demo site <https://github.com/wagtail/wagtaildemo/>`_, with the Wagtail and wagtaildemo codebases available as shared folders for editing on your host machine.
 
 (Build scripts for other platforms would be very much welcomed - if you create one, please let us know via the `Wagtail Developers group <https://groups.google.com/forum/#!forum/wagtail-developers>`_!)
 
@@ -17,11 +17,11 @@ Setting up the Wagtail codebase
 
 Install Node.js, v5.3.0 or higher. Instructions for installing Node.js can be found on the `Node.js download page <https://nodejs.org/download/>`_. You will also need to install the **libjpeg** and **zlib** libraries, if you haven't done so already - see Pillow's `platform-specific installation instructions <http://pillow.readthedocs.org/en/latest/installation.html#external-libraries>`_.
 
-Clone a copy of `the Wagtail codebase <https://github.com/torchbox/wagtail>`_:
+Clone a copy of `the Wagtail codebase <https://github.com/wagtail/wagtail>`_:
 
 .. code-block:: console
 
-    $ git clone https://github.com/torchbox/wagtail.git
+    $ git clone https://github.com/wagtail/wagtail.git
     $ cd wagtail
 
 With your preferred virtualenv activated, install the Wagtail package in development mode with the included testing and documentation dependencies:
@@ -42,7 +42,7 @@ Compile the assets:
 
     $ npm run build
 
-Any Wagtail sites you start up in this virtualenv will now run against this development instance of Wagtail. We recommend using the `Wagtail demo site <https://github.com/torchbox/wagtaildemo/>`_ as a basis for developing Wagtail.
+Any Wagtail sites you start up in this virtualenv will now run against this development instance of Wagtail. We recommend using the `Wagtail demo site <https://github.com/wagtail/wagtaildemo/>`_ as a basis for developing Wagtail.
 
 .. _testing:
 

docs/contributing/index.rst

@@ -4,7 +4,7 @@ Contributing to Wagtail
 Issues
 ~~~~~~
 
-The easiest way to contribute to Wagtail is to tell us how to improve it! First, check to see if your bug or feature request has already been submitted at `github.com/torchbox/wagtail/issues <https://github.com/torchbox/wagtail/issues>`_. If it has, and you have some supporting information which may help us deal with it, comment on the existing issue. If not, please `create a new one <https://github.com/torchbox/wagtail/issues/new>`_, providing as much relevant context as possible. For example, if you're experiencing problems with installation, detail your environment and the steps you've already taken. If something isn't displaying correctly, tell us what browser you're using, and include a screenshot if possible.
+The easiest way to contribute to Wagtail is to tell us how to improve it! First, check to see if your bug or feature request has already been submitted at `github.com/wagtail/wagtail/issues <https://github.com/wagtail/wagtail/issues>`_. If it has, and you have some supporting information which may help us deal with it, comment on the existing issue. If not, please `create a new one <https://github.com/wagtail/wagtail/issues/new>`_, providing as much relevant context as possible. For example, if you're experiencing problems with installation, detail your environment and the steps you've already taken. If something isn't displaying correctly, tell us what browser you're using, and include a screenshot if possible.
 
 .. toctree::
     :maxdepth: 2
@@ -14,7 +14,7 @@ The easiest way to contribute to Wagtail is to tell us how to improve it! First,
 Pull requests
 ~~~~~~~~~~~~~
 
-If you're a Python or Django developer, `fork it <https://github.com/torchbox/wagtail/>`_ and read the :ref:`developing docs <developing>` to get stuck in! We welcome all contributions, whether they solve problems which are specific to you or they address existing issues. If you're stuck for ideas, pick something from the `issue list <https://github.com/torchbox/wagtail/issues?state=open>`_, or email us directly on `hello@wagtail.io <mailto:hello@wagtail.io>`_ if you'd like us to suggest something!
+If you're a Python or Django developer, `fork it <https://github.com/wagtail/wagtail/>`_ and read the :ref:`developing docs <developing>` to get stuck in! We welcome all contributions, whether they solve problems which are specific to you or they address existing issues. If you're stuck for ideas, pick something from the `issue list <https://github.com/wagtail/wagtail/issues?state=open>`_, or email us directly on `hello@wagtail.io <mailto:hello@wagtail.io>`_ if you'd like us to suggest something!
 
 .. toctree::
     :maxdepth: 2

docs/contributing/issue_tracking.rst

@@ -1,7 +1,7 @@
 Issue tracking
 ==============
 
-We welcome bug reports, feature requests and pull requests through Wagtail's `Github issue tracker <https://github.com/torchbox/wagtail/issues>`_.
+We welcome bug reports, feature requests and pull requests through Wagtail's `Github issue tracker <https://github.com/wagtail/wagtail/issues>`_.
 
 Issues
 ------

docs/contributing/python_guidelines.rst

@@ -71,4 +71,4 @@ Tests
 
 Wagtail has a suite of tests, which we are committed to improving and expanding. See :ref:`testing`.
 
-We run continuous integration at `travis-ci.org/torchbox/wagtail <https://travis-ci.org/torchbox/wagtail>`_ to ensure that no commits or pull requests introduce test failures. If your contributions add functionality to Wagtail, please include the additional tests to cover it; if your contributions alter existing functionality, please update the relevant tests accordingly.
+We run continuous integration at `travis-ci.org/wagtail/wagtail <https://travis-ci.org/wagtail/wagtail>`_ to ensure that no commits or pull requests introduce test failures. If your contributions add functionality to Wagtail, please include the additional tests to cover it; if your contributions alter existing functionality, please update the relevant tests accordingly.

docs/getting_started/demo_site.rst

@@ -5,4 +5,4 @@ Demo site
 
 To create a new site on Wagtail we recommend the ``wagtail start`` command in :doc:`index`, however a demo site exists containing example page types and models. We also recommend you use the demo site for testing during development of Wagtail itself.
 
-The repo and installation instructions can be found here: `https://github.com/torchbox/wagtaildemo <https://github.com/torchbox/wagtaildemo>`_
+The repo and installation instructions can be found here: `https://github.com/wagtail/wagtaildemo <https://github.com/wagtail/wagtaildemo>`_

docs/releases/0.7.rst

@@ -100,5 +100,5 @@ Update to ``focal_point_key`` field on custom Rendition models
 
 The ``focal_point_key`` field on wagtailimages.Rendition has been changed to ``null=False``, to fix an issue with duplicate renditions being created. If you have defined a custom Rendition model in your project (by extending the ``wagtailimages.AbstractRendition`` class), you will need to apply a migration to make the corresponding change on your custom model. Unfortunately neither South nor Django 1.7's migration system are able to generate this automatically - you will need to customise the migration produced by ``./manage.py schemamigration`` / ``./manage.py makemigrations``, using the wagtailimages migration as a guide:
 
- - https://github.com/torchbox/wagtail/blob/master/wagtail/wagtailimages/south_migrations/0004_auto__chg_field_rendition_focal_point_key.py (for South / Django 1.6)
- - https://github.com/torchbox/wagtail/blob/master/wagtail/wagtailimages/migrations/0004_make_focal_point_key_not_nullable.py (for Django 1.7)
+ - https://github.com/wagtail/wagtail/blob/master/wagtail/wagtailimages/south_migrations/0004_auto__chg_field_rendition_focal_point_key.py (for South / Django 1.6)
+ - https://github.com/wagtail/wagtail/blob/master/wagtail/wagtailimages/migrations/0004_make_focal_point_key_not_nullable.py (for Django 1.7)

docs/releases/1.0.rst

@@ -299,7 +299,7 @@ EditHandler internal API has changed
 
 While it is not an official Wagtail API, it has been possible for Wagtail site implementers to define their own ``EditHandler`` subclasses for use in panel definitions, to customise the behaviour of the page / snippet editing forms. If you have made use of this facility, you will need to update your custom EditHandlers, as this mechanism has been refactored (to allow EditHandler classes to keep a persistent reference to their corresponding model). If you have only used Wagtail's built-in panel types (``FieldPanel``, ``InlinePanel``, ``PageChooserPanel`` and so on), you are unaffected by this change.
 
-Previously, functions like ``FieldPanel`` acted as 'factory' functions, where a call such as ``FieldPanel('title')`` constructed and returned an ``EditHandler`` subclass tailored to work on a 'title' field. These functions now return an object with a ``bind_to_model`` method instead; the EditHandler subclass can be obtained by calling this with the model class as a parameter. As a guide to updating your custom EditHandler code, you may wish to refer to `the relevant change to the Wagtail codebase <https://github.com/torchbox/wagtail/commit/121c01c7f7db6087a985fa8dc9957bc78b9f6a6a>`_.
+Previously, functions like ``FieldPanel`` acted as 'factory' functions, where a call such as ``FieldPanel('title')`` constructed and returned an ``EditHandler`` subclass tailored to work on a 'title' field. These functions now return an object with a ``bind_to_model`` method instead; the EditHandler subclass can be obtained by calling this with the model class as a parameter. As a guide to updating your custom EditHandler code, you may wish to refer to `the relevant change to the Wagtail codebase <https://github.com/wagtail/wagtail/commit/121c01c7f7db6087a985fa8dc9957bc78b9f6a6a>`_.
 
 chooser_panel templates are obsolete
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

docs/releases/1.1.rst

@@ -29,7 +29,7 @@ The Elasticsearch search backend now accepts an experimental ``ATOMIC_REBUILD``
 The :mod:`~wagtail.contrib.wagtailapi` module now uses Django REST Framework
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-The ``wagtailapi`` module is now built on Django REST Framework and it now also has a `library of serialisers <https://github.com/torchbox/wagtail/blob/stable/1.1.x/wagtail/contrib/wagtailapi/serializers.py>`_ that you can use in your own REST Framework based APIs. No user-facing changes have been made.
+The ``wagtailapi`` module is now built on Django REST Framework and it now also has a `library of serialisers <https://github.com/wagtail/wagtail/blob/stable/1.1.x/wagtail/contrib/wagtailapi/serializers.py>`_ that you can use in your own REST Framework based APIs. No user-facing changes have been made.
 
 We hope to support more REST framework features, such as a browsable API, in future releases.
 

docs/support.rst

@@ -9,7 +9,7 @@ If you have general questions about Wagtail, or you're looking for help on how t
 Issues
 ~~~~~~
 
-If you think you've found a bug in Wagtail, or you'd like to suggest a new feature, please check the current list at `github.com/torchbox/wagtail/issues <https://github.com/torchbox/wagtail/issues>`_. If your bug or suggestion isn't there, raise a new issue, providing as much relevant context as possible.
+If you think you've found a bug in Wagtail, or you'd like to suggest a new feature, please check the current list at `github.com/wagtail/wagtail/issues <https://github.com/wagtail/wagtail/issues>`_. If your bug or suggestion isn't there, raise a new issue, providing as much relevant context as possible.
 
 Torchbox
 ~~~~~~~~

docs/topics/pages.rst

@@ -88,7 +88,7 @@ This example represents a typical blog post:
 
 .. important::
 
-    Ensure that none of your field names are the same as your class names. This will cause errors due to the way Django handles relations (`read more <https://github.com/torchbox/wagtail/issues/503>`_). In our examples we have avoided this by appending "Page" to each model name.
+    Ensure that none of your field names are the same as your class names. This will cause errors due to the way Django handles relations (`read more <https://github.com/wagtail/wagtail/issues/503>`_). In our examples we have avoided this by appending "Page" to each model name.
 
 
 Writing page models

package.json

@@ -1,7 +1,7 @@
 {
   "name": "wagtail",
   "version": "1.0.0",
-  "repository": "https://github.com/torchbox/wagtail",
+  "repository": "https://github.com/wagtail/wagtail",
   "private": true,
   "browser": {},
   "browserify": {

wagtail/wagtailadmin/tests/test_edit_handlers.py

@@ -756,7 +756,7 @@ class TestInlinePanel(TestCase, WagtailTestUtils):
         """
         Test that the USE_THOUSAND_SEPARATOR setting does not screw up the rendering of numbers
         (specifically maxForms=1000) in the JS initializer:
-        https://github.com/torchbox/wagtail/pull/2699
+        https://github.com/wagtail/wagtail/pull/2699
         """
         SpeakerObjectList = ObjectList([
             InlinePanel('speakers', label="Speakers", panels=[

wagtail/wagtailcore/blocks/base.py

@@ -481,7 +481,7 @@ class BlockWidget(forms.Widget):
 
     # Flag used by Django 1.10.1 (only) to indicate that this widget will not necessarily submit
     # a postdata item with a name that matches the field name -
-    # see https://github.com/django/django/pull/7068, https://github.com/torchbox/wagtail/issues/2994
+    # see https://github.com/django/django/pull/7068, https://github.com/wagtail/wagtail/issues/2994
     dont_use_model_field_default_for_empty_data = True
 
     def __init__(self, block_def, attrs=None):

wagtail/wagtailcore/tests/tests.py

@@ -91,7 +91,7 @@ class TestSiteRootPathsCache(TestCase):
         site and return None as their url.
 
         Fix: d6cce69a397d08d5ee81a8cbc1977ab2c9db2682
-        Discussion: https://github.com/torchbox/wagtail/issues/7
+        Discussion: https://github.com/wagtail/wagtail/issues/7
         """
         # Get homepage, root page and site
         root_page = Page.objects.get(id=1)
@@ -129,7 +129,7 @@ class TestSiteRootPathsCache(TestCase):
         the site and return None as their url.
 
         Fix: d6cce69a397d08d5ee81a8cbc1977ab2c9db2682
-        Discussion: https://github.com/torchbox/wagtail/issues/157
+        Discussion: https://github.com/wagtail/wagtail/issues/157
         """
         # Get homepage
         homepage = Page.objects.get(url_path='/home/')

wagtail/wagtailsearch/backends/elasticsearch2.py

@@ -109,7 +109,7 @@ class Elasticsearch2Index(ElasticsearchIndex):
         # Put mapping
         self.es.indices.put_mapping(
             # pass update_all_types=True as a workaround to avoid "Can't redefine search field" errors -
-            # see https://github.com/torchbox/wagtail/issues/2968
+            # see https://github.com/wagtail/wagtail/issues/2968
             index=self.name, doc_type=mapping.get_document_type(), body=mapping.get_mapping(),
             update_all_types=True
         )

wagtail/wagtailsearch/tests/test_elasticsearch2_backend.py

@@ -150,7 +150,7 @@ class TestElasticsearch2SearchBackend(BackendTests, TestCase):
         This tests that punctuation characters are treated the same
         way in both indexing and querying.
 
-        See: https://github.com/torchbox/wagtail/issues/937
+        See: https://github.com/wagtail/wagtail/issues/937
         """
         # Reset the index
         self.reset_index()

wagtail/wagtailsearch/tests/test_elasticsearch5_backend.py

@@ -149,7 +149,7 @@ class TestElasticsearch5SearchBackend(BackendTests, TestCase):
         This tests that punctuation characters are treated the same
         way in both indexing and querying.
 
-        See: https://github.com/torchbox/wagtail/issues/937
+        See: https://github.com/wagtail/wagtail/issues/937
         """
         # Reset the index
         self.reset_index()

wagtail/wagtailsearch/tests/test_elasticsearch_backend.py

@@ -149,7 +149,7 @@ class TestElasticsearchSearchBackend(BackendTests, TestCase):
         This tests that punctuation characters are treated the same
         way in both indexing and querying.
 
-        See: https://github.com/torchbox/wagtail/issues/937
+        See: https://github.com/wagtail/wagtail/issues/937
         """
         # Reset the index
         self.reset_index()

wagtail/wagtailusers/tests.py

@@ -91,7 +91,7 @@ class TestUserIndexView(TestCase, WagtailTestUtils):
         self.assertContains(response, 'testuser')
 
     def test_allows_negative_ids(self):
-        # see https://github.com/torchbox/wagtail/issues/565
+        # see https://github.com/wagtail/wagtail/issues/565
         get_user_model().objects.create_user('guardian', 'guardian@example.com', 'gu@rd14n', pk=-1)
         response = self.get()
         self.assertEqual(response.status_code, 200)