On Thu, Jun 5, 2014 at 9:28 PM, roger peppe <rogpe...@gmail.com> wrote:
> Unfortunately that means that the import identifier isn't intuitive, > but perhaps that's ok. It's not so different from the "go-thing" convention a lot of people use, where the package name is actually just "thing". If we were to change it to anything, I'd probably go with juju-. On 5 June 2014 14:27, roger peppe <rogpe...@gmail.com> wrote: > > On 5 June 2014 14:20, Nate Finch <nate.fi...@canonical.com> wrote: > >> We're making a lot of standalone repos on github so that teams external > to > >> core can reuse core's code. > >> I think we need to disambiguate between repos that are generally only > of use > >> when working with juju, and repos that are more general purpose. For > >> example, errgo is a general use package that anyone else could use. > >> However, there are some pretty vague packages under juju that are really > >> juju only, such as the names package. > >> > >> If anyone has a good idea of how to disambiguate the two, I think it > would > >> be really useful, so we can point people to all the reusable code that's > >> getting produced by Juju. > > > > Perhaps "juju-*"? > > > > e.g. > > github.com/juju/juju-names. > > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
