Change onyxfish to wireservice. Fix capitalization of GitHub. #702

.github/CONTRIBUTING.md

@@ -19,14 +19,14 @@ Process for contributing code
 
 Contributors should use the following roadmap to guide them through the process of submitting a contribution:
 
-1.  Fork the project on [Github].
+1.  Fork the project on [GitHub].
 2.  Check out the [issue tracker] and find a task that needs to be done and is of a scope you can realistically expect to complete in a few days. Don’t worry about the priority of the issues at first, but try to choose something you’ll enjoy. You’re much more likely to finish something to the point it can be merged if it’s something you really enjoy hacking on.
 3.  Comment on the ticket letting everyone know you’re going to be hacking on it so that nobody duplicates your effort. It’s also good practice to provide some general idea of how you plan on resolving the issue so that other developers can make suggestions.
 4.  Write tests for the feature you’re building. Follow the format of the existing tests in the test directory to see how this works. You can run all the tests with the command `nosetests tests`. (Or `tox` to run across all supported versions of Python.)
 5.  Write the code. Try to stay consistent with the style and organization of the existing codebase. A good patch won’t be refused for stylistic reasons, but large parts of it may be rewritten and nobody wants that.
 6.  As you are coding, periodically merge in work from the master branch and verify you haven’t broken anything by running the test suite.
 7.  Write documentation. Seriously.
-8.  Once it works, is tested, and has documentation, submit a pull request on Github.
+8.  Once it works, is tested, and has documentation, submit a pull request on GitHub.
 9.  Wait for it to either be merged or to receive a comment about what needs to be fixed.
 10. Rejoice.
 
@@ -37,6 +37,6 @@ To the extent that they care, contributors should keep in mind that the source o
 
   [numpy]: http://www.numpy.org/
   [pandas]: http://pandas.pydata.org/
-  [Github]: https://github.com/onyxfish/agate
-  [issue tracker]: https://github.com/onyxfish/agate/issues
+  [GitHub]: https://github.com/wireservice/agate
+  [issue tracker]: https://github.com/wireservice/agate/issues
   [MIT license]: http://www.opensource.org/licenses/mit-license.php

CHANGELOG.rst

@@ -81,7 +81,7 @@ The complete list of changes is as follows:
 * :class:`.Any` and :class:`.All` aggregations no longer behave differently for boolean data. (#636)
 * :class:`.Any` and :class:`.All` aggregations now accept a single value as a test argument, in addition to a function.
 * :class:`.Any` and :class:`.All` aggregations now require a test argument.
-* Tables rendered by :meth:`.Table.print_table` are now Github Friendly Markdown (GFM) compatible. (#626)
+* Tables rendered by :meth:`.Table.print_table` are now GitHub Flavored Markdown (GFM) compatible. (#626)
 * The agate tutorial has been converted to a Jupyter Notebook.
 * :class:`.Table` now supports ``len`` as a proxy for ``len(table.rows)``.
 * Simple SVG charting is now integrated via `leather <http://leather.rtfd.io>`_.

agate/csv_py2.py

@@ -83,7 +83,7 @@ class UnicodeWriter(object):
     A CSV writer which will write rows to a file in the specified encoding.
 
     NB: Optimized so that eight-bit encodings skip re-encoding. See:
-        https://github.com/onyxfish/csvkit/issues/175
+        https://github.com/wireservice/csvkit/issues/175
     """
     def __init__(self, f, encoding='utf-8', **kwargs):
         self.encoding = encoding

agate/table/print_table.py

@@ -16,7 +16,7 @@ def print_table(self, max_rows=20, max_columns=6, output=sys.stdout, max_column_
     """
     Print a text-based view of the data in this table.
 
-    The output of this method is Github Friendly Markdown (GFM) compatible.
+    The output of this method is GitHub Flavored Markdown (GFM) compatible.
 
     :param max_rows:
         The maximum number of rows to display before truncating the data. This

docs/contributing.rst

@@ -13,12 +13,12 @@ Process for documentation
 
 Not a developer? That's fine! As long as you can use `git` (there are many tutorials) then you can contribute to agate. Please follow this process:
 
-#. Fork the project on `Github <https://github.com/onyxfish/agate>`_.
-#. If you don't have a specific task in mind, check out the `issue tracker <https://github.com/onyxfish/agate/issues>`_ and find a documentation ticket that needs to be done.
+#. Fork the project on `GitHub <https://github.com/wireservice/agate>`_.
+#. If you don't have a specific task in mind, check out the `issue tracker <https://github.com/wireservice/agate/issues>`_ and find a documentation ticket that needs to be done.
 #. Comment on the ticket letting everyone know you're going to be working on it so that nobody duplicates your effort.
 #. Write the documentation. Documentation files live in the `docs` directory and are in Restructured Text Format.
 #. Add yourself to the AUTHORS file if you aren't already there.
-#. Once your contribution is complete, submit a pull request on Github.
+#. Once your contribution is complete, submit a pull request on GitHub.
 #. Wait for it to either be merged by a maintainer or to receive feedback about what needs to be revised.
 #. Rejoice!
 
@@ -27,16 +27,16 @@ Process for code
 
 Hacker? We'd love to have you hack with us. Please follow this process to make your contribution:
 
-#. Fork the project on `Github <https://github.com/onyxfish/agate>`_.
-#. If you don't have a specific task in mind, check out the `issue tracker <https://github.com/onyxfish/agate/issues>`_ and find a task that needs to be done and is of a scope you can realistically expect to complete in a few days. Don't worry about the priority of the issues at first, but try to choose something you'll enjoy. You're much more likely to finish something to the point it can be merged if it's something you really enjoy hacking on.
+#. Fork the project on `GitHub <https://github.com/wireservice/agate>`_.
+#. If you don't have a specific task in mind, check out the `issue tracker <https://github.com/wireservice/agate/issues>`_ and find a task that needs to be done and is of a scope you can realistically expect to complete in a few days. Don't worry about the priority of the issues at first, but try to choose something you'll enjoy. You're much more likely to finish something to the point it can be merged if it's something you really enjoy hacking on.
 #. If you already have a task you know you want to work on, open a ticket or comment on the existing ticket letting everyone know you're going to be working on it. It's also good practice to provide some general idea of how you plan on resolving the issue so that other developers can make suggestions.
 #. Write tests for the feature you're building. Follow the format of the existing tests in the test directory to see how this works. You can run all the tests with the command ``nosetests tests``.
 #. Verify your tests work on all supported versions of Python by runing ``tox``.
 #. Write the code. Try to stay consistent with the style and organization of the existing codebase. A good patch won't be refused for stylistic reasons, but large parts of it may be rewritten and nobody wants that.
 #. As you are coding, periodically merge in work from the master branch and verify you haven't broken anything by running the test suite.
 #. Write documentation. This means docstrings on all classes and methods, including parameter explanations. It also means, when relevant, cookbook recipes and updates to the agate user tutorial.
 #. Add yourself to the AUTHORS file if you aren't already there.
-#. Once your contribution is complete, tested, and has documentation, submit a pull request on Github.
+#. Once your contribution is complete, tested, and has documentation, submit a pull request on GitHub.
 #. Wait for it to either be merged by a maintainer or to receive feedback about what needs to be revisited.
 #. Rejoice!
 

docs/cookbook/create.rst

@@ -189,7 +189,7 @@ Use the `agate-remote <http://agate-remote.readthedocs.org/>`_ extension.
 
     agateremote.patch()
 
-    table = agate.Table.from_url('https://raw.githubusercontent.com/onyxfish/agate/master/examples/test.csv')
+    table = agate.Table.from_url('https://raw.githubusercontent.com/wireservice/agate/master/examples/test.csv')
 
 agate-remote also let’s you create an Archive, which is a reference to a group of tables with a known path structure.
 

docs/install.rst

@@ -20,7 +20,7 @@ Developers
 
 If you are a developer that also wants to hack on agate, install it from git::
 
-    git clone git://github.com/onyxfish/agate.git
+    git clone git://github.com/wireservice/agate.git
     cd agate
     mkvirtualenv agate
 

docs/tutorial.rst

@@ -12,4 +12,4 @@ Find it |link-pre|\ |version|\ |link-post|
 
 .. |link-post| raw:: html
 
-	 /tutorial.ipynb">on Github</a>!
+	 /tutorial.ipynb">on GitHub</a>!

tutorial.ipynb

@@ -36,7 +36,7 @@
     "\n",
     "It can be downloaded from\n",
     "\n",
-    "    curl -L -O https://github.com/onyxfish/agate/raw/master/examples/realdata/exonerations-20150828.csv\n",
+    "    curl -L -O https://github.com/wireservice/agate/raw/master/examples/realdata/exonerations-20150828.csv\n",
     "\n",
     "The rest of this tutorial will expect that data to be located in `examples/realdata`."
    ]