naming repos on github

[Martin Packman]

On 06/06/2014, Nate Finch <nate.finch at canonical.com> wrote:
>
> As for ditching go get... yes and no (mostly no).  go get is not really
> intended for use in contributing to an external project.  It's a "download
> and install" this application.  If anything, we should be making our code
> *more* happy with go get, so if Go developers want to try out juju, they
> can do so in an intuitive fashion.  It would also remove a lot of our pain
> if we stopped hitting ourselves in the head by breaking trunk of our repos
> and depending on godeps to fix up trunk.  IMO godeps should be used on
> release branches only, to pin the revision numbers for repeatable builds.
>  Trunk of all our repos should always build, the fact that it doesn't is
> our own fault.

It's not just our fault tip of everything doesn't build, we do have
dependencies controlled by other people.

For instance: <https://github.com/juju/juju/issues/43>

To remain compatible with go 1.1 we need an old gocrypto, so, we can't
build against tip of that repo.

Martin