The thinking was to have the bottom package as "juju" being a useful package. This scheme also enables having juju2, etc once we want to stabilize the API itself. That said, it's easy to change now and I'm not rooted on those ideas either. Let's talk next week and agree on something. gustavo @ <a href="http://niemeyer.net">http://niemeyer.net</a> <div class="gmail_quote">On Jun 7, 2012 9:58 AM, "roger peppe" <<a href="mailto:roger.peppe@canonical.com">roger.peppe@canonical.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> On 7 June 2012 12:36, Kapil Thangavelu <<a href="mailto:kapil.thangavelu@canonical.com">kapil.thangavelu@canonical.com</a>> wrote: > > > On Thu, Jun 7, 2012 at 5:03 AM, roger peppe <<a href="mailto:roger.peppe@canonical.com">roger.peppe@canonical.com</a>> > wrote: >> >> On 6 June 2012 20:43, Gustavo Niemeyer <<a href="mailto:gustavo.niemeyer@canonical.com">gustavo.niemeyer@canonical.com</a>> >> wrote: >> > As previously mentioned, we've been moving the Go development >> > activities to a new project in Launchpad: >> > >> > <a href="https://launchpad.net/juju-core" target="_blank">https://launchpad.net/juju-core</a> >> > >> > As arranged over the whole day on IRC, the trunk for the Go port is >> > now at a new location: >> > >> > <a href="http://launchpad.net/juju-core/juju" target="_blank">launchpad.net/juju-core/juju</a> >> >> Sorry, I wasn't there for the discussion, but could you briefly >> say why the import paths are "<a href="http://launchpad.net/juju-core/juju/foo" target="_blank">launchpad.net/juju-core/juju/foo</a>" rather >> than "<a href="http://launchpad.net/juju-core/foo" target="_blank">launchpad.net/juju-core/foo</a>" ? >> >> The extra "juju" seems unnecessary (and other projects such >> as goamz and gozk don't have them) >> >> One other thing: i tried "bzr branch <a href="http://launchpad.net/juju-core/trunk" target="_blank">launchpad.net/juju-core/trunk</a>" >> and got this error: >> >> bzr: ERROR: Permission denied: "Cannot create 'trunk'. Only Bazaar >> branches are allowed." >> >> Is this all because we don't want to define the Go port as "trunk" in >> juju-core? >> > > bzr branch lp:juju-core > > for an existing branch N.B. this doesn't work when bzr is aliased to cobzr, although cobzr branch lp:juju-core/juju does. </blockquote></div>