Change of all imports and import of legacy AddressHelper and Scheduler

changed from /lucas-clemente/quic-go to /boisjacques/qed

Author: mkieweg

.circleci/config.yml

@@ -1,5 +1,5 @@
 defaults: &defaults
-  working_directory: /go/src/github.com/lucas-clemente/quic-go
+  working_directory: /go/src/github.com/boisjacques/qed
   steps:
     - checkout
     - run:

.gometalinter.json

@@ -19,6 +19,6 @@
   "Linters": {
     "vet": "go tool vet -printfuncs=Infof,Debugf,Warningf,Errorf:PATH:LINE:MESSAGE",
     "misspell": "misspell -i ect:PATH:LINE:COL:MESSAGE",
-    "megacheck": "megacheck -ignore github.com/lucas-clemente/quic-go/h2quic/response_writer_closenotifier.go:SA1019:PATH:LINE:COL:MESSAGE"
+    "megacheck": "megacheck -ignore github.com/boisjacques/qed/h2quic/response_writer_closenotifier.go:SA1019:PATH:LINE:COL:MESSAGE"
   }
 }

.idea/inspectionProfiles/Project_Default.xml

@@ -36,8 +36,8 @@
 - Add a `quic.Config` option to configure keep-alive
 - Rename the STK to Cookie
 - Implement `net.Conn`-style deadlines for streams
-- Remove the `tls.Config` from the `quic.Config`. The `tls.Config` must now be passed to the `Dial` and `Listen` functions as a separate parameter. See the [Godoc](https://godoc.org/github.com/lucas-clemente/quic-go) for details.
-- Changed the log level environment variable to only accept strings ("DEBUG", "INFO", "ERROR"), see [the wiki](https://github.com/lucas-clemente/quic-go/wiki/Logging) for more details.
+- Remove the `tls.Config` from the `quic.Config`. The `tls.Config` must now be passed to the `Dial` and `Listen` functions as a separate parameter. See the [Godoc](https://godoc.org/github.com/boisjacques/qed) for details.
+- Changed the log level environment variable to only accept strings ("DEBUG", "INFO", "ERROR"), see [the wiki](https://github.com/boisjacques/qed/wiki/Logging) for more details.
 - Rename the `h2quic.QuicRoundTripper` to `h2quic.RoundTripper`
 - Changed `h2quic.Server.Serve()` to accept a `net.PacketConn`
 - Drop support for Go 1.7 and 1.8.

.idea/misc.xml

@@ -2,25 +2,25 @@
 
 <img src="docs/quic.png" width=303 height=124>
 
-[![Godoc Reference](https://img.shields.io/badge/godoc-reference-blue.svg?style=flat-square)](https://godoc.org/github.com/lucas-clemente/quic-go)
-[![Travis Build Status](https://img.shields.io/travis/lucas-clemente/quic-go/master.svg?style=flat-square&label=Travis+build)](https://travis-ci.org/lucas-clemente/quic-go)
-[![CircleCI Build Status](https://img.shields.io/circleci/project/github/lucas-clemente/quic-go.svg?style=flat-square&label=CircleCI+build)](https://circleci.com/gh/lucas-clemente/quic-go)
-[![Windows Build Status](https://img.shields.io/appveyor/ci/lucas-clemente/quic-go/master.svg?style=flat-square&label=windows+build)](https://ci.appveyor.com/project/lucas-clemente/quic-go/branch/master)
-[![Code Coverage](https://img.shields.io/codecov/c/github/lucas-clemente/quic-go/master.svg?style=flat-square)](https://codecov.io/gh/lucas-clemente/quic-go/)
+[![Godoc Reference](https://img.shields.io/badge/godoc-reference-blue.svg?style=flat-square)](https://godoc.org/github.com/boisjacques/qed)
+[![Travis Build Status](https://img.shields.io/travis/boisjacques/qed/master.svg?style=flat-square&label=Travis+build)](https://travis-ci.org/boisjacques/qed)
+[![CircleCI Build Status](https://img.shields.io/circleci/project/github/boisjacques/qed.svg?style=flat-square&label=CircleCI+build)](https://circleci.com/gh/boisjacques/qed)
+[![Windows Build Status](https://img.shields.io/appveyor/ci/boisjacques/qed/master.svg?style=flat-square&label=windows+build)](https://ci.appveyor.com/project/boisjacques/qed/branch/master)
+[![Code Coverage](https://img.shields.io/codecov/c/github/boisjacques/qed/master.svg?style=flat-square)](https://codecov.io/gh/boisjacques/qed/)
 
 quic-go is an implementation of the [QUIC](https://en.wikipedia.org/wiki/QUIC) protocol in Go. It roughly implements the [IETF QUIC draft](https://github.com/quicwg/base-drafts), although we don't fully support any of the draft versions at the moment.
 
 ## Version compatibility
 
 Since quic-go is under active development, there's no guarantee that two builds of different commits are interoperable. The QUIC version used in the *master* branch is just a placeholder, and should not be considered stable.
 
-If you want to use quic-go as a library in other projects, please consider using a [tagged release](https://github.com/lucas-clemente/quic-go/releases). These releases expose [experimental QUIC versions](https://github.com/quicwg/base-drafts/wiki/QUIC-Versions), which are guaranteed to be stable.
+If you want to use quic-go as a library in other projects, please consider using a [tagged release](https://github.com/boisjacques/qed/releases). These releases expose [experimental QUIC versions](https://github.com/quicwg/base-drafts/wiki/QUIC-Versions), which are guaranteed to be stable.
 
 ## Google QUIC
 
 quic-go used to support both the QUIC versions supported by Google Chrome and QUIC as deployed on Google's servers, as well as IETF QUIC. Due to the divergence of the two protocols, we decided to not support both versions any more.
 
-The *master* branch **only** supports IETF QUIC. For Google QUIC support, please refer to the [gquic branch](https://github.com/lucas-clemente/quic-go/tree/gquic). 
+The *master* branch **only** supports IETF QUIC. For Google QUIC support, please refer to the [gquic branch](https://github.com/boisjacques/qed/tree/gquic).
 
 ## Guides
 
@@ -65,4 +65,4 @@ http.Client{
 
 ## Contributing
 
-We are always happy to welcome new contributors! We have a number of self-contained issues that are suitable for first-time contributors, they are tagged with [help wanted](https://github.com/lucas-clemente/quic-go/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22). If you have any questions, please feel free to reach out by opening an issue or leaving a comment.
+We are always happy to welcome new contributors! We have a number of self-contained issues that are suitable for first-time contributors, they are tagged with [help wanted](https://github.com/boisjacques/qed/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22). If you have any questions, please feel free to reach out by opening an issue or leaving a comment.