Replace all instances of untitaker with pimutils

CHANGELOG.rst

@@ -7,7 +7,7 @@ package maintainers. For further info, see the git commit log.
 
 Package maintainers and users who have to manually update their installation
 may want to subscribe to `GitHub's tag feed
-<https://github.com/untitaker/vdirsyncer/tags.atom>`_.
+<https://github.com/pimutils/vdirsyncer/tags.atom>`_.
 
 Version 0.9.2
 =============

README.rst

@@ -3,7 +3,7 @@ vdirsyncer
 ==========
 
 - `Documentation <https://vdirsyncer.readthedocs.org/en/stable/>`_
-- `Source code <https://github.com/untitaker/vdirsyncer>`_
+- `Source code <https://github.com/pimutils/vdirsyncer>`_
 
 Vdirsyncer synchronizes your calendars and addressbooks between two storages_.
 The most popular purpose is to synchronize a CalDAV/CardDAV server with a local
@@ -16,11 +16,11 @@ none of which have to know or worry about syncing to a server.
 It aims to be for CalDAV and CardDAV what `OfflineIMAP
 <http://offlineimap.org/>`_ is for IMAP.
 
-.. image:: https://travis-ci.org/untitaker/vdirsyncer.png?branch=master
-    :target: https://travis-ci.org/untitaker/vdirsyncer
+.. image:: https://travis-ci.org/pimutils/vdirsyncer.png?branch=master
+    :target: https://travis-ci.org/pimutils/vdirsyncer
 
-.. image:: https://codecov.io/github/untitaker/vdirsyncer/coverage.svg?branch=master
-    :target: https://codecov.io/github/untitaker/vdirsyncer?branch=master
+.. image:: https://codecov.io/github/pimutils/vdirsyncer/coverage.svg?branch=master
+    :target: https://codecov.io/github/pimutils/vdirsyncer?branch=master
 
 Links of interest
 =================

docs/contact.rst

@@ -6,7 +6,7 @@ Support and Contact
   your timezone. Use it for support and general (including off-topic)
   discussion.
 
-* Open `a GitHub issue <https://github.com/untitaker/vdirsyncer/issues/>`_ for
+* Open `a GitHub issue <https://github.com/pimutils/vdirsyncer/issues/>`_ for
   concrete bug reports and feature requests.
 
 * Lastly, you can also `contact the author directly

docs/index.rst

@@ -3,7 +3,7 @@ vdirsyncer
 ==========
 
 - `Documentation <https://vdirsyncer.readthedocs.org/en/stable/>`_
-- `Source code <https://github.com/untitaker/vdirsyncer>`_
+- `Source code <https://github.com/pimutils/vdirsyncer>`_
 
 Vdirsyncer synchronizes your calendars and addressbooks between two
 :ref:`storages <storages>`. The most popular purpose is to synchronize a

docs/packaging.rst

@@ -20,7 +20,7 @@ junk and are more of a distraction than anything else.
 
 I give each release a tag in the git repo. If you want to get notified of new
 releases, `GitHub's feed
-<https://github.com/untitaker/vdirsyncer/releases.atom>`_ is a good way.
+<https://github.com/pimutils/vdirsyncer/releases.atom>`_ is a good way.
 
 Dependency versions
 ===================

docs/tutorial.rst

@@ -30,7 +30,7 @@ Configuration
 .. note::
 
     - The `config.example from the repository
-      <https://github.com/untitaker/vdirsyncer/blob/master/config.example>`_
+      <https://github.com/pimutils/vdirsyncer/blob/master/config.example>`_
       contains a very terse version of this.
 
     - In this example we set up contacts synchronization, but calendar sync

setup.py

@@ -29,7 +29,7 @@ requirements = [
     # verifying against CAs) with older versions of urllib3.
     'requests >=2.4.1, !=2.9.0',
     'lxml >=3.1' + (
-        # See https://github.com/untitaker/vdirsyncer/issues/298
+        # See https://github.com/pimutils/vdirsyncer/issues/298
         # We pin some LXML version that is known to work with PyPy
         # I assume nobody actually uses PyPy with vdirsyncer, so this is
         # moot
@@ -69,7 +69,7 @@ setup(
     setup_requires=['setuptools_scm'],
     author='Markus Unterwaditzer',
     author_email='markus@unterwaditzer.net',
-    url='https://github.com/untitaker/vdirsyncer',
+    url='https://github.com/pimutils/vdirsyncer',
     description='Synchronize calendars and contacts',
     license='MIT',
     long_description=open('README.rst').read(),

tests/storage/__init__.py

@@ -111,7 +111,7 @@ class StorageTests(object):
 
         new_item = get_item(uid=item.uid)
         new_etag = s.update(href, new_item, etag)
-        # See https://github.com/untitaker/vdirsyncer/issues/48
+        # See https://github.com/pimutils/vdirsyncer/issues/48
         assert isinstance(new_etag, (bytes, text_type))
         assert_item_equals(s.get(href)[0], new_item)
 

vdirsyncer/__init__.py

@@ -5,7 +5,7 @@ vdirsyncer is a synchronization tool for vdir. See the README for more details.
 
 from __future__ import print_function
 
-PROJECT_HOME = 'https://github.com/untitaker/vdirsyncer'
+PROJECT_HOME = 'https://github.com/pimutils/vdirsyncer'
 DOCS_HOME = 'https://vdirsyncer.readthedocs.org/en/stable'
 
 try:

vdirsyncer/storage/dav.py

@@ -511,9 +511,9 @@ class DavStorage(Storage):
             if href in hrefs:
                 # Servers that send duplicate hrefs:
                 # - Zimbra
-                #   https://github.com/untitaker/vdirsyncer/issues/88
+                #   https://github.com/pimutils/vdirsyncer/issues/88
                 # - Davmail
-                #   https://github.com/untitaker/vdirsyncer/issues/144
+                #   https://github.com/pimutils/vdirsyncer/issues/144
                 dav_logger.warning('Skipping identical href: {!r}'
                                    .format(href))
                 continue
@@ -561,7 +561,7 @@ class DavStorage(Storage):
             '''
 
         # We use a PROPFIND request instead of addressbook-query due to issues
-        # with Zimbra. See https://github.com/untitaker/vdirsyncer/issues/83
+        # with Zimbra. See https://github.com/pimutils/vdirsyncer/issues/83
         response = self.session.request('PROPFIND', '', data=data,
                                         headers=headers)
         root = _parse_xml(response.content)
@@ -771,7 +771,7 @@ class CaldavStorage(DavStorage):
             </C:calendar-query>'''
 
         headers = self.session.get_default_headers()
-        # https://github.com/untitaker/vdirsyncer/issues/166
+        # https://github.com/pimutils/vdirsyncer/issues/166
         # The default in CalDAV's calendar-queries is 0, but the examples use
         # an explicit value of 1 for querying items. it is extremely unclear in
         # the spec which values from WebDAV are actually allowed.

vdirsyncer/utils/vobject.py

@@ -22,7 +22,7 @@ IGNORE_PROPS = _process_properties(
     # their filesystem backend
     'X-RADICALE-NAME',
     # Apparently this is set by Horde?
-    # https://github.com/untitaker/vdirsyncer/issues/318
+    # https://github.com/pimutils/vdirsyncer/issues/318
     'X-WR-CALNAME',
     # REV is from the VCARD specification and is supposed to change when the
     # item does -- however, we can determine that ourselves