s/coderefinery/dev-cafe/; closes #244

doc/developers/bootstrap.rst

@@ -12,7 +12,7 @@ infrastructure files which will be needed to build the project::
 
   $ mkdir cmake  # does not have to be called "cmake" - take the name you prefer
   $ cd cmake
-  $ wget https://github.com/coderefinery/autocmake/raw/master/update.py
+  $ wget https://github.com/dev-cafe/autocmake/raw/master/update.py
   $ virtualenv venv
   $ source venv/bin/activate
   $ pip install pyyaml
@@ -20,7 +20,7 @@ infrastructure files which will be needed to build the project::
 
 On the MS Windows system, you can use the PowerShell wget-replacement::
 
-  $ Invoke-WebRequest https://github.com/coderefinery/autocmake/raw/master/update.py -OutFile update.py
+  $ Invoke-WebRequest https://github.com/dev-cafe/autocmake/raw/master/update.py -OutFile update.py
 
 This creates (or updates) the following files (an existing ``autocmake.yml`` is
 not overwritten by the script)::

doc/developers/configuration.rst

@@ -19,7 +19,7 @@ below::
     - C
     - CXX
 
-  url_root: https://github.com/coderefinery/autocmake/raw/master/
+  url_root: https://github.com/dev-cafe/autocmake/raw/master/
 
   modules:
   - compilers:
@@ -80,7 +80,7 @@ As a minimal example we take an ``autocmake.yml`` which only contains::
 
 If you don't have the ``update.py`` script yet, you need to fetch it from the web::
 
-  $ wget https://github.com/coderefinery/autocmake/raw/master/update.py
+  $ wget https://github.com/dev-cafe/autocmake/raw/master/update.py
 
 First we make sure that the ``update.py`` script is up-to-date and that it has access
 to all libraries it needs::
@@ -181,7 +181,7 @@ Fetching files without including them in CMakeLists.txt
 Sometimes you want to fetch a file without including it in ``CMakeLists.txt``.
 This can be done with the ``fetch`` option.  This is for instance done by the
 ``git_info.cmake`` module (see
-https://github.com/coderefinery/autocmake/blob/master/modules/git_info/git_info.cmake#L10-L13).
+https://github.com/dev-cafe/autocmake/blob/master/modules/git_info/git_info.cmake#L10-L13).
 
 If ``fetch`` is invoked in ``autocmake.yml``, then the fetched file is placed
 under ``downloaded/``.  If ``fetch`` is invoked from within a CMake module
@@ -235,6 +235,6 @@ for many core modules which come with own options once you have sourced them.
 The lines following ``# autocmake.yml configuration::`` are
 understood by the ``update.py`` script to infer ``autocmake.yml`` code from the
 documentation. As an example consider
-https://github.com/coderefinery/autocmake/blob/master/modules/cc.cmake#L20-L26.
+https://github.com/dev-cafe/autocmake/blob/master/modules/cc.cmake#L20-L26.
 Here, ``update.py`` will infer the configurations for ``docopt``, ``export``,
 and ``define``.

doc/developers/customizing-modules.rst

@@ -48,10 +48,10 @@ settings imported by a sourced module.
 
 As an example consider the Boost module which defines and uses
 interpolation variables ``major``, ``minor``, ``patch``, and ``components``, see
-https://github.com/coderefinery/autocmake/blob/master/modules/boost/boost.cmake#L52-L55.
+https://github.com/dev-cafe/autocmake/blob/master/modules/boost/boost.cmake#L52-L55.
 
 The recommended way to customize these is in ``autocmake.yml``, e.g.:
-https://github.com/coderefinery/autocmake/blob/master/test/boost_libs/cmake/autocmake.yml#L12-L17.
+https://github.com/dev-cafe/autocmake/blob/master/test/boost_libs/cmake/autocmake.yml#L12-L17.
 
 
 Create own CMake modules
@@ -65,5 +65,5 @@ Contribute customizations to the "standard library"
 
 If you think that your customization will be useful for other users as well,
 you may consider contributing the changes directly to
-https://github.com/coderefinery/autocmake/. We very much encourage such
+https://github.com/dev-cafe/autocmake/. We very much encourage such
 contributions. But we also strive for generality and portability.

doc/developers/example.rst

@@ -25,7 +25,7 @@ Now we create ``cmake/`` and fetch ``update.py``::
 
   $ mkdir cmake  # does not have to be called "cmake" - take the name you prefer
   $ cd cmake
-  $ wget https://github.com/coderefinery/autocmake/raw/master/update.py
+  $ wget https://github.com/dev-cafe/autocmake/raw/master/update.py
   $ python update.py --self
 
 Now from top-level our file tree looks like this::
@@ -60,7 +60,7 @@ Now we edit ``cmake/autocmake.yml`` to look like this::
     - Fortran
     - C
 
-  url_root: https://github.com/coderefinery/autocmake/raw/master/
+  url_root: https://github.com/dev-cafe/autocmake/raw/master/
 
   modules:
   - compilers:

doc/developers/faq.rst

@@ -138,7 +138,7 @@ can include the latter in ``autocmake.yml`` using::
 
   - my_sources:
     - source:
-      - https://github.com/coderefinery/autocmake/raw/master/modules/src.cmake
+      - https://github.com/dev-cafe/autocmake/raw/master/modules/src.cmake
 
 If you really do not like to do it this way, you can describe your sources and
 targets in a custom module in a local file and include it like this::

doc/developers/interpolation.rst

@@ -8,7 +8,7 @@ In a custom extension to the YAML specification you can define and reuse
 variables like this (observe how we interpolate ``url_root``, ``major``,
 ``minor``, ``patch``, and ``components`` in this example)::
 
-  url_root: https://github.com/coderefinery/autocmake/raw/master/
+  url_root: https://github.com/dev-cafe/autocmake/raw/master/
   major: 1
   minor: 48
   patch: 0

doc/developers/updating-modules.rst

@@ -21,10 +21,10 @@ rather fetch an older version, for example with the hash ``abcd123``. To
 achieve this, instead of::
 
   - my_feature:
-    - source: https://github.com/coderefinery/autocmake/raw/master/modules/foo.cmake
+    - source: https://github.com/dev-cafe/autocmake/raw/master/modules/foo.cmake
 
 pin the version to ``abcd123`` (you do not need to specify the full Git hash, a unique
 beginning will do)::
 
   - my_feature:
-    - source: https://github.com/coderefinery/autocmake/raw/abcd123/modules/foo.cmake
+    - source: https://github.com/dev-cafe/autocmake/raw/abcd123/modules/foo.cmake