Where should loggo live (and errgo, ...)?
Ian Booth
ian.booth at canonical.com
Thu Mar 6 02:46:53 UTC 2014
Hi
Currently, the loggo library used by juju-core is hosted on Github at
github.com/loggo/loggo.
Given juju-core is moving to github.com/juju, it's been proposed that loggo move
across to github.com/juju/loggo. We already have github.com/juju/errgo.
My question is this: when I see a project hosted at github.com/juju/..., I
immediately think that the project must be in some way related to, or only works
with, Juju. Of course, loggo and errgo are completely generic projects which
hopefully will be adopted outside of juju-core. However, if I were a random
developer and saw juju/loggo, I would not consider it for my project because I
would think it were tied to Juju somehow.
I guess this is an unfortunate consequence of the "juju" namespeace. If it were
"juju-team" or "canonical" or something, there (for me) would not be that mental
leap that all the projects under "juju" are for Juju only. I'm not asking that
we change the "juju" namespace, but suggesting that perhaps it be reserved for
"juju-core", "juju-gui" etc which are really Juju sub-projects. And that generic
libraries like errgo and loggo be hosted elsewhere.
Thoughts?
More information about the Juju-dev
mailing list