Make `go get` command nice and easy

[matryer]

Installing the Go SDK should be a great experience, consider what impact the project name has on go get and rename as appropriate.

Consider:

• github.com/stretchrcom/stretchrgo
• github.com/stretchrcom/stretchr
• github.com/stretchrcom/go-sdk

Also - what impact will this have on import statements within code?

Do we include a subfolder for easy package imports?

i.e.

import "github.com/stretchrcom/sdk-go/stretchr"

So the code can be keyed off stretchr without having to name it directly.

• What impact does this have on the api package? Should that be renamed to stretchrapi so people don't write api.Something in their code and have no idea which api they're referring to?

[tylerstillwater]

I think this is just fine the way it is. The package name is "stretchr" even though it is part of the "sdk-go" repository. It works just fine in the tools for which I've used it.

Our docs reflect the "stretchr" package name, so that shouldn't be a problem.

[tylerstillwater]

I believe this is fine and this issue should be closed. Do you agree?

[matryer]

Yes

On 21 Mar 2013, at 19:10, Tyler notifications@github.com wrote:

I believe this is fine and this issue should be closed. Do you agree?

— Reply to this email directly or view it on GitHub.

[tylerstillwater]

Closing