launchpad-dev team mailing list archive

[Marc Tardif <marc.tardif@xxxxxxxxxxxxx>]

* Francis J. Lacoste <francis.lacoste@xxxxxxxxxxxxx> [2010-11-02 11:09 -0400]:
> On November 2, 2010, Marc Tardif wrote:
> > * Robert Collins <robert.collins@xxxxxxxxxxxxx> [2010-11-03 03:48 +1300]:
> > > On Wed, Nov 3, 2010 at 3:39 AM, Francis J. Lacoste
> > > <francis.lacoste@xxxxxxxxxxxxx> wrote:
> > > > lp isn't a namespace package in Launchpad. I guess that's what Robert
> > > > is hinting at by the "no good story". It was meant to be, but it seems
> > > > that we added .py directly in it, at some point. And it misses the
> > > > namespace registration declaration. I've filed bug 669938 about this.
> > > > 
> > > > In the mean time, we could use a lpx namespace for applications
> > > > building on top of Launchpad?
> > > 
> > > I'd be fine with having a namespace package for lpx, fwiw. I think
> > > that would be better in fact, than having external trees directly
> > > injecting code into 'lp'.
> > 
> > I like it, my concern is mostly to be consistent with Launchpad moving
> > forward. For example, since I have a fixation with the Librarian, would
> > it make sense if I eventually extracted it as a standalone package to
> > have it also reside under the lpx namespace?
> 
> I don't think the librarian is something that would be released under lpx. 
> Since it's in a way a generic thing, lazr pour make more sense.

Agreed and, following Robert's response, it may not even make sense
to extract the Librarian in the first place. As for other components,
it may not make sense to extract them either considering the high cost
to benefit ratio.

When sleeping, I dream of seeing each Launchpad component extracted
as standalone services. After waking up, I realize this might not be
sensible for existing components but certainly possible for future
components. The Results Tracker will attempt to make this dream reality
and I hope the lpx namespace will inspire others to do the same.

Thanks for having taken the time to provide a detailed explanation
about the implications for introducing the lp namespace. I'm quite
confident the lpx namespace will serve the same purpose just as
well and avoid disrupting the Launchpad project itself.

-- 
Marc Tardif <marc.tardif@xxxxxxxxxxxxx>
Freenode: cr3, Jabber: cr3@xxxxxxxxxx
1024D/72679CAD 09A9 D871 F7C4 A18F AC08 674D 2B73 740C 7267 9CAD