Canonical repo moved to github.com/celery/celery

Changelog

@@ -228,7 +228,7 @@ Security Fixes
 
 
 .. _`CELERYSA-0001`:
-    http://github.com/ask/celery/tree/master/docs/sec/CELERYSA-0001.txt
+    http://github.com/celery/celery/tree/master/docs/sec/CELERYSA-0001.txt
 
 .. _v244-fixes:
 
@@ -603,7 +603,7 @@ Security Fixes
 
 
 .. _`CELERYSA-0001`:
-    http://github.com/ask/celery/tree/master/docs/sec/CELERYSA-0001.txt
+    http://github.com/celery/celery/tree/master/docs/sec/CELERYSA-0001.txt
 
 Fixes
 -----
@@ -644,7 +644,7 @@ News
 * Improved Contributing guide.
 
     If you'd like to contribute to Celery you should read this
-    guide: http://ask.github.com/celery/contributing.html
+    guide: http://celery.github.com/celery/contributing.html
 
     We are looking for contributors at all skill levels, so don't
     hesitate!
@@ -959,7 +959,7 @@ Security Fixes
 
 
 .. _`CELERYSA-0001`:
-    http://github.com/ask/celery/tree/master/docs/sec/CELERYSA-0001.txt
+    http://github.com/celery/celery/tree/master/docs/sec/CELERYSA-0001.txt
 
 .. _version-2.2.7:
 
@@ -2645,7 +2645,7 @@ Experimental
 
 * Added generic init.d script using `celeryd-multi`
 
-    http://github.com/ask/celery/tree/master/contrib/generic-init.d/celeryd
+    http://github.com/celery/celery/tree/master/contrib/generic-init.d/celeryd
 
 .. _v210-documentation:
 
@@ -3220,7 +3220,7 @@ Backward incompatible changes
     =====================================  =====================================
 
 .. _`deprecation timeline`:
-    http://ask.github.com/celery/internals/deprecation.html
+    http://celery.github.com/celery/internals/deprecation.html
 
 * The `celery.task.rest` module has been removed, use :mod:`celery.task.http`
   instead (as scheduled by the `deprecation timeline`_).
@@ -4431,7 +4431,7 @@ News
 * celeryd now sends events if enabled with the `-E` argument.
 
     Excellent for monitoring tools, one is already in the making
-    (http://github.com/ask/celerymon).
+    (http://github.com/celery/celerymon).
 
     Current events include: worker-heartbeat,
     task-[received/succeeded/failed/retried],
@@ -4744,7 +4744,7 @@ Important changes
     See `Cookbook: Retrying Tasks`_ for more information.
 
 .. _`Cookbook: Retrying Tasks`:
-    http://ask.github.com/celery/cookbook/task-retries.html
+    http://celery.github.com/celery/cookbook/task-retries.html
 
 * We now have an AMQP result store backend.
 
@@ -5179,7 +5179,7 @@ arguments, so be sure to flush your task queue before you upgrade.
 
 .. _`Can I send some tasks to only some servers?`:
         http://bit.ly/celery_AMQP_routing
-.. _`FAQ`: http://ask.github.com/celery/faq.html
+.. _`FAQ`: http://celery.github.com/celery/faq.html
 
 * Task errors are now logged using log level `ERROR` instead of `INFO`,
   and stacktraces are dumped. Thanks to Grégoire Cachet.

FAQ

@@ -95,7 +95,7 @@ These "virtual transports" may have limited broadcast and event functionality.
 For example remote control commands only works with AMQP and Redis.
 
 .. _`Using other queues`:
-    http://ask.github.com/celery/tutorials/otherqueues.html
+    http://celery.github.com/celery/tutorials/otherqueues.html
 
 Redis or a database won't perform as well as
 an AMQP broker. If you have strict reliability requirements you are
@@ -125,7 +125,7 @@ information you can even create simple web servers that enable preloading of
 code. See: `User Guide: Remote Tasks`_.
 
 .. _`User Guide: Remote Tasks`:
-    http://ask.github.com/celery/userguide/remote-tasks.html
+    http://celery.github.com/celery/userguide/remote-tasks.html
 
 .. _faq-troubleshooting:
 

README.rst

@@ -4,10 +4,10 @@
 
 .. image:: http://cloud.github.com/downloads/ask/celery/celery_128.png
 
-:Version: 2.5.2
+:Version: 2.5.3
 :Web: http://celeryproject.org/
 :Download: http://pypi.python.org/pypi/celery/
-:Source: http://github.com/ask/celery/
+:Source: http://github.com/celery/celery/
 :Keywords: task queue, job queue, asynchronous, rabbitmq, amqp, redis,
   python, webhooks, queue, distributed
 
@@ -76,10 +76,10 @@ integration packages:
 .. _`pyramid_celery`: http://pypi.python.org/pypi/pyramid_celery/
 .. _`django-celery`: http://pypi.python.org/pypi/django-celery
 .. _`celery-pylons`: http://pypi.python.org/pypi/celery-pylons
-.. _`flask-celery`: http://github.com/ask/flask-celery/
+.. _`flask-celery`: http://github.com/celery/flask-celery/
 .. _`web2py-celery`: http://code.google.com/p/web2py-celery/
 .. _`operate with other languages using webhooks`:
-    http://ask.github.com/celery/userguide/remote-tasks.html
+    http://celery.github.com/celery/userguide/remote-tasks.html
 .. _`limited support`:
     http://kombu.readthedocs.org/en/latest/introduction.html#transport-comparison
 
@@ -222,10 +222,13 @@ Features
 Documentation
 =============
 
-The `latest documentation`_ with user guides, tutorials and API reference
-is hosted at Github.
+Documentation for the production version can be found here:
 
-.. _`latest documentation`: http://ask.github.com/celery/
+    http://docs.celeryproject.org/en/latest
+
+and the documentation for the development version can be found here:
+
+    http://celery.github.com/celery/
 
 .. _celery-installation:
 
@@ -299,7 +302,7 @@ Using the development version
 
 You can clone the repository by doing the following::
 
-    $ git clone git://github.com/ask/celery.git
+    $ git clone git://github.com/celery/celery.git
 
 .. _getting-help:
 
@@ -333,21 +336,21 @@ Bug tracker
 ===========
 
 If you have any suggestions, bug reports or annoyances please report them
-to our issue tracker at http://github.com/ask/celery/issues/
+to our issue tracker at http://github.com/celery/celery/issues/
 
 .. _wiki:
 
 Wiki
 ====
 
-http://wiki.github.com/ask/celery/
+http://wiki.github.com/celery/celery/
 
 .. _contributing-short:
 
 Contributing
 ============
 
-Development of `celery` happens at Github: http://github.com/ask/celery
+Development of `celery` happens at Github: http://github.com/celery/celery
 
 You are highly encouraged to participate in the development
 of `celery`. If you don't like Github (for some reason) you're welcome
@@ -356,7 +359,7 @@ to send regular patches.
 Be sure to also read the `Contributing to Celery`_ section in the
 documentation.
 
-.. _`Contributing to Celery`: http://ask.github.com/celery/contributing.html
+.. _`Contributing to Celery`: http://celery.github.com/celery/contributing.html
 
 .. _license:
 

TODO

@@ -1,11 +1,5 @@
 Please see our Issue Tracker at GitHub:
-    http://github.com/ask/celery/issues
-
-Kombu
-=====
-
-Redis: Better acks by moving reserved messages into a temporary queue.
-       Can we use multi commands for anything?
+    http://github.com/celery/celery/issues
 
 Celerymon
 =========

celery/apps/worker.py

@@ -240,7 +240,7 @@ class Worker(configurated):
             # into the background.
             if self.app.IS_OSX:
                 # OS X can't exec from a process using threads.
-                # See http://github.com/ask/celery/issues#issue/152
+                # See http://github.com/celery/celery/issues#issue/152
                 install_HUP_not_supported_handler(worker)
             else:
                 install_worker_restart_handler(worker)
@@ -251,7 +251,7 @@ class Worker(configurated):
         install_rdb_handler()
 
     def osx_proxy_detection_workaround(self):
-        """See http://github.com/ask/celery/issues#issue/161"""
+        """See http://github.com/celery/celery/issues#issue/161"""
         os.environ.setdefault("celery_dummy_proxy", "set_by_celeryd")
 
     def set_process_status(self, info):

contrib/supervisord/celerybeat.conf

@@ -4,7 +4,7 @@
 
 ; NOTE: If you're using Django, you shouldn't use this file.
 ; Use
-; http://github.com/ask/django-celery/tree/master/contrib/supervisord/celerybeat.conf
+; http://github.com/celery/django-celery/tree/master/contrib/supervisord/celerybeat.conf
 ; instead!
 
 [program:celerybeat]

contrib/supervisord/celeryd.conf

@@ -4,7 +4,7 @@
 
 ; NOTE: If you're using Django, you shouldn't use this file.
 ; Use
-; http://github.com/ask/django-celery/tree/master/contrib/supervisord/celeryd.conf
+; http://github.com/celery/django-celery/tree/master/contrib/supervisord/celeryd.conf
 ; instead!
 
 [program:celery]

docs/.templates/page.html

@@ -12,7 +12,7 @@
         {% else %}
         <p>
         This document describes Celery {{ version }}. For development docs,
-        <a href="http://ask.github.com/celery/{{ pagename }}{{ file_suffix }}">go here</a>.
+        <a href="http://celery.github.com/celery/{{ pagename }}{{ file_suffix }}">go here</a>.
         </p>
     {% endif %}
 

docs/community.rst

@@ -21,14 +21,14 @@ Resources
 Who's using Celery
 ------------------
 
-http://wiki.github.com/ask/celery/using
+http://wiki.github.com/celery/celery/using
 
 .. _res-wiki:
 
 Wiki
 ----
 
-http://wiki.github.com/ask/celery/
+http://wiki.github.com/celery/celery/
 
 .. _res-stackoverflow:
 

docs/contributing.rst

@@ -151,11 +151,11 @@ Issue Trackers
 Bugs for a package in the Celery ecosystem should be reported to the relevant
 issue tracker.
 
-* Celery: http://github.com/ask/celery/issues/
-* Django-Celery: http://github.com/ask/django-celery/issues
+* Celery: http://github.com/celery/celery/issues/
+* Django-Celery: http://github.com/celery/django-celery/issues
 * Flask-Celery: http://github.com/ask/flask-celery/issues
 * Celery-Pylons: http://bitbucket.org/ianschenck/celery-pylons/issues
-* Kombu: http://github.com/ask/kombu/issues
+* Kombu: http://github.com/celery/kombu/issues
 
 If you are unsure of the origin of the bug you can ask the
 :ref:`mailing-list`, or just use the Celery issue tracker.
@@ -180,12 +180,12 @@ Branches
 
 Current active version branches:
 
-* master (http://github.com/ask/celery/tree/master)
-* 3.0-devel (http://github.com/ask/celery/tree/3.0-devel)
+* master (http://github.com/celery/celery/tree/master)
+* 3.0-devel (http://github.com/celery/celery/tree/3.0-devel)
 
 You can see the state of any branch by looking at the Changelog:
 
-    https://github.com/ask/celery/blob/master/Changelog
+    https://github.com/celery/celery/blob/master/Changelog
 
 If the branch is in active development the topmost version info should
 contain metadata like::
@@ -305,7 +305,7 @@ When the repository is cloned enter the directory to set up easy access
 to upstream changes::
 
     $ cd celery
-    $ git remote add upstream git://github.com/ask/celery.git
+    $ git remote add upstream git://github.com/celery/celery.git
     $ git fetch upstream
 
 If you need to pull in new changes from upstream you should

docs/cookbook/daemonizing.rst

@@ -22,7 +22,7 @@ This directory contains generic bash init scripts for :program:`celeryd`,
 that should run on Linux, FreeBSD, OpenBSD, and other Unix platforms.
 
 .. _`contrib/generic-init.d/`:
-    http://github.com/ask/celery/tree/master/contrib/generic-init.d/
+    http://github.com/celery/celery/tree/master/contrib/generic-init.d/
 
 .. _generic-initd-celeryd:
 
@@ -295,7 +295,7 @@ actual resulting output::
 * `contrib/supervisord/`_
 
 .. _`contrib/supervisord/`:
-    http://github.com/ask/celery/tree/master/contrib/supervisord/
+    http://github.com/celery/celery/tree/master/contrib/supervisord/
 .. _`supervisord`: http://supervisord.org/
 
 .. _daemon-launchd:
@@ -306,7 +306,7 @@ launchd (OS X)
 * `contrib/mac/`_
 
 .. _`contrib/mac/`:
-    http://github.com/ask/celery/tree/master/contrib/mac/
+    http://github.com/celery/celery/tree/master/contrib/mac/
 
 
 .. _daemon-windows:

docs/includes/installation.txt

@@ -27,4 +27,4 @@ Using the development version
 
 You can clone the repository by doing the following::
 
-    $ git clone git://github.com/ask/celery.git
+    $ git clone git://github.com/celery/celery.git

docs/includes/introduction.txt

@@ -1,7 +1,7 @@
 :Version: 2.5.3
 :Web: http://celeryproject.org/
 :Download: http://pypi.python.org/pypi/celery/
-:Source: http://github.com/ask/celery/
+:Source: http://github.com/celery/celery/
 :Keywords: task queue, job queue, asynchronous, rabbitmq, amqp, redis,
   python, webhooks, queue, distributed
 
@@ -70,10 +70,10 @@ integration packages:
 .. _`pyramid_celery`: http://pypi.python.org/pypi/pyramid_celery/
 .. _`django-celery`: http://pypi.python.org/pypi/django-celery
 .. _`celery-pylons`: http://pypi.python.org/pypi/celery-pylons
-.. _`flask-celery`: http://github.com/ask/flask-celery/
+.. _`flask-celery`: http://github.com/celery/flask-celery/
 .. _`web2py-celery`: http://code.google.com/p/web2py-celery/
 .. _`operate with other languages using webhooks`:
-    http://ask.github.com/celery/userguide/remote-tasks.html
+    http://celery.github.com/celery/userguide/remote-tasks.html
 .. _`limited support`:
     http://kombu.readthedocs.org/en/latest/introduction.html#transport-comparison
 
@@ -217,10 +217,13 @@ Features
 Documentation
 =============
 
-The `latest documentation`_ with user guides, tutorials and API reference
-is hosted at Github.
+Documentation for the production version can be found here:
 
-.. _`latest documentation`: http://ask.github.com/celery/
+    http://docs.celeryproject.org/en/latest
+
+and the documentation for the development version can be found here:
+
+    http://celery.github.com/celery/
 
 .. _celery-installation:
 
@@ -294,4 +297,4 @@ Using the development version
 
 You can clone the repository by doing the following::
 
-    $ git clone git://github.com/ask/celery.git
+    $ git clone git://github.com/celery/celery.git

docs/includes/resources.txt

@@ -30,21 +30,21 @@ Bug tracker
 ===========
 
 If you have any suggestions, bug reports or annoyances please report them
-to our issue tracker at http://github.com/ask/celery/issues/
+to our issue tracker at http://github.com/celery/celery/issues/
 
 .. _wiki:
 
 Wiki
 ====
 
-http://wiki.github.com/ask/celery/
+http://wiki.github.com/celery/celery/
 
 .. _contributing-short:
 
 Contributing
 ============
 
-Development of `celery` happens at Github: http://github.com/ask/celery
+Development of `celery` happens at Github: http://github.com/celery/celery
 
 You are highly encouraged to participate in the development
 of `celery`. If you don't like Github (for some reason) you're welcome
@@ -53,7 +53,7 @@ to send regular patches.
 Be sure to also read the `Contributing to Celery`_ section in the
 documentation.
 
-.. _`Contributing to Celery`: http://ask.github.com/celery/contributing.html
+.. _`Contributing to Celery`: http://celery.github.com/celery/contributing.html
 
 .. _license:
 

docs/releases/1.0/announcement.rst

@@ -28,7 +28,7 @@ databases is also available.
 Features
 --------
 
-See http://ask.github.com/celery/getting-started/introduction.html#features
+See http://celery.github.com/celery/getting-started/introduction.html#features
 
 Stable API
 ==========
@@ -50,7 +50,7 @@ that existed in Celery 1.0:
 See the `Celery Deprecation Timeline`_ for a list of pending removals.
 
 .. _`Celery Deprecation Timeline`:
-    http://ask.github.com/celery/internals/deprecation.html
+    http://celery.github.com/celery/internals/deprecation.html
 
 What's new?
 ===========
@@ -76,7 +76,7 @@ What's new?
     workers. This is the basis for the new real-time web monitor we're working on
     (`celerymon`_).
 
-.. _`celerymon`: http://github.com/ask/celerymon/
+.. _`celerymon`: http://github.com/celery/celerymon/
 
 * Rate limiting
 
@@ -137,7 +137,7 @@ the `changelog`_. This document contains crucial information for those
 upgrading from a previous version of Celery, so be sure to read the entire
 change set before you continue.
 
-.. _`changelog`: http://ask.github.com/celery/changelog.html
+.. _`changelog`: http://celery.github.com/celery/changelog.html
 
 **TIP:** If you install the :mod:`setproctitle` module you can see which
 task each worker process is currently executing in `ps` listings.
@@ -154,9 +154,9 @@ Resources
 
 * Changelog: http://docs.celeryproject.org/changelog.html
 
-* Code: http://github.com/ask/celery/
+* Code: http://github.com/celery/celery/
 
-* FAQ: http://ask.github.com/celery/faq.html
+* FAQ: http://celery.github.com/celery/faq.html
 
 * Mailing-list: http://groups.google.com/group/celery-users
 

docs/userguide/concurrency/eventlet.rst

@@ -59,5 +59,5 @@ some examples taking use of Eventlet support.
     http://en.wikipedia.org/wiki/Asynchronous_I/O#Select.28.2Fpoll.29_loops
 .. _`Coroutines`: http://en.wikipedia.org/wiki/Coroutine
 .. _`Eventlet examples`:
-    https://github.com/ask/celery/tree/master/examples/eventlet
+    https://github.com/celery/celery/tree/master/examples/eventlet
 

docs/userguide/monitoring.rst

@@ -333,7 +333,7 @@ or help this project in any way, please get in touch!
 :Tip: The Django admin monitor can be used even though you're not using
       Celery with a Django project.  See :ref:`monitoring-nodjango`.
 
-.. _`celerymon`: http://github.com/ask/celerymon/
+.. _`celerymon`: http://github.com/celery/celerymon/
 
 .. _monitoring-rabbitmq:
 

docs/userguide/remote-tasks.rst

@@ -119,4 +119,4 @@ Since applying tasks can be done via HTTP using the
 :func:`djcelery.views.apply` view, executing tasks from other languages is easy.
 For an example service exposing tasks via HTTP you should have a look at
 `examples/celery_http_gateway` in the Celery distribution:
-http://github.com/ask/celery/tree/master/examples/celery_http_gateway/
+http://github.com/celery/celery/tree/master/examples/celery_http_gateway/

funtests/setup.py

@@ -41,7 +41,7 @@ setup(
     description="Functional test suite for Celery",
     author="Ask Solem",
     author_email="ask@celeryproject.org",
-    url="http://github.com/ask/celery",
+    url="http://github.com/celery/celery",
     platforms=["any"],
     packages=[],
     data_files=[],