launchpad-dev team mailing list archive

[Marc Tardif <marc.tardif@xxxxxxxxxxxxx>]

* Sidnei da Silva <sidnei.da.silva@xxxxxxxxxxxxx> [2010-11-02 01:12 -0200]:
> On Tue, Nov 2, 2010 at 1:09 AM, Robert Collins
> <robert.collins@xxxxxxxxxxxxx> wrote:
> > What do you mean by 'lp namespace'? If you mean the python code is
> > lp.SOMETHING, then I would rather you don't do that - we don't have a
> > good story for working with packages like that, and it would be much
> > easier if your package was lpSOMETHING instead - for now.
> 
> There's a bunch of packages under the lazr.* namespace. Maybe that's
> safer to use.

Thanks for the suggestion, I had considered that namespace too. However,
my understanding was that the lazr.* namespace was for general purpose
libraries whereas the lp.* namespace could eventually be for services
which might be specifically branded as Launchpad. For example, if we
were to extract Answers from Launchpad, should it be under the lp.* or
lazr.* namespace? In the end, I simply want to be consistent with the
direction Launchpad is most likely to take when extracting components
as standalone services. And, if there is no good story for this as
pointed out by Robert, I'd like to help build one.

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