Rewrite imports for new github org

This rewrites the Go imports after switching to the new github org.

Signed-off-by: Michael Crosby <crosbymichael@gmail.com>

.travis.yml

@@ -8,7 +8,7 @@ go:
   - 1.8.x
   - tip
 
-go_import_path: github.com/docker/containerd
+go_import_path: github.com/containerd/containerd
 
 addons:
   apt:

MAINTAINERS

@@ -163,7 +163,7 @@ of the pull request and which areas of the project it affects.
 
 	text = """
 The [DCO or `Sign your work`](
-https://github.com/docker/containerd/blob/master/CONTRIBUTING.md#sign-your-work)
+https://github.com/containerd/containerd/blob/master/CONTRIBUTING.md#sign-your-work)
 requirement is not intended as a roadblock or speed bump.
 
 Some containerd contributors are not as familiar with `git`, or have used a web

Makefile

@@ -7,7 +7,7 @@ DESTDIR=/usr/local
 # Used to populate version variable in main package.
 VERSION=$(shell git describe --match 'v[0-9]*' --dirty='.m' --always)
 
-PKG=github.com/docker/containerd
+PKG=github.com/containerd/containerd
 
 # Project packages.
 PACKAGES=$(shell go list ./... | grep -v /vendor/)

README.md

@@ -1,6 +1,6 @@
 ![banner](/docs/images/containerd-dark.png?raw=true)
 
-[![Build Status](https://travis-ci.org/docker/containerd.svg?branch=master)](https://travis-ci.org/docker/containerd)
+[![Build Status](https://travis-ci.org/containerd/containerd.svg?branch=master)](https://travis-ci.org/containerd/containerd)
 
 containerd is an industry-standard container runtime with an emphasis on simplicity, robustness and portability. It is available as a daemon for Linux and Windows, which can manage the complete container lifecycle of its host system: image transfer and storage, container execution and supervision, low-level storage and network attachments, etc..
 
@@ -9,7 +9,7 @@ containerd is designed to be embedded into a larger system, rather than being us
 ### State of the Project
 
 containerd currently has two active branches.
-There is a [v0.2.x](https://github.com/docker/containerd/tree/v0.2.x) branch for the current release of containerd that is being consumed by Docker and others and the master branch is the development branch for the 1.0 roadmap and feature set.
+There is a [v0.2.x](https://github.com/containerd/containerd/tree/v0.2.x) branch for the current release of containerd that is being consumed by Docker and others and the master branch is the development branch for the 1.0 roadmap and feature set.
 Any PR or issue that is intended for the current v0.2.x release should be tagged with the same `v0.2.x` tag.
 
 ### Communication
@@ -124,7 +124,7 @@ For the scope of this project to change it requires a 100% vote from all maintai
 ### Development reports.
 
 Weekly summary on the progress and what is being worked on.
-https://github.com/docker/containerd/tree/master/reports
+https://github.com/containerd/containerd/tree/master/reports
 
 ## Copyright and license
 

ROADMAP.md

@@ -2,7 +2,7 @@
 
 This is a high level roadmap for the project that outlines what is currently being worked on, what comes next, and where you can help.
 
-For a more up to date look please review the milestones on [github](https://github.com/docker/containerd/milestones).
+For a more up to date look please review the milestones on [github](https://github.com/containerd/containerd/milestones).
 
 The following are the different status the various phases of development can be in:
 * Not Started - no work or thinking has been done towards the goal
@@ -52,7 +52,7 @@ The runtime layer is responsible for the creation of containers and their manage
 
 ### Storage
 
-**Documents:** https://github.com/docker/containerd/blob/master/design/snapshots.md
+**Documents:** https://github.com/containerd/containerd/blob/master/design/snapshots.md
 
 The current graph drivers were built when we only had overlay filesystems like aufs.
 We forced the model to be designed around overlay filesystems and this introduced a lot of complexity for snapshotting graph drivers like btrfs and devicemapper thin-p.