launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #04207
Re: New name for 'lp.coop'.
-
To:
Launchpad Community Development Team <launchpad-dev@xxxxxxxxxxxxxxxxxxx>
-
From:
Julian Edwards <julian.edwards@xxxxxxxxxxxxx>
-
Date:
Tue, 10 Aug 2010 13:57:14 +0100
-
In-reply-to:
<1281442477.2468.52.camel@gwenhwyvar>
-
Organization:
Canonical Ltd
-
User-agent:
KMail/1.13.2 (Linux/2.6.32-24-generic; KDE/4.4.2; x86_64; ; )
On Tuesday 10 August 2010 13:14:37 Jelmer Vernooij wrote:
> On Tue, 2010-08-10 at 13:42 +0200, Henning Eggers wrote:
> > Am 09.08.2010 22:08, schrieb Jelmer Vernooij:
> > > On Tue, 2010-08-10 at 02:48 +0700, Jeroen Vermeulen wrote:
> > >> On 2010-08-05 15:29, Martin Pool wrote:
> > >>> I don't think it's an awful name, but 'general', 'shared', etc may be
> > >>> better.
> > >>
> > >> Both of those sound like they mean... well, Foundations basically.
> > >>
> > >> I like "inter." To throw a few more terms into the mix: "multi,"
> > >> "combo."
> > >
> > > I like inter, too. multi, general, shared, etc. all suggest to me like
> > > they are about code that happens to be used by more than one lp
> > > subsystem.
> >
> > I am all for "shared", though, because that's what it is about. The code
> > *will* be used by more than on lp subsystem, will it not?
> >
> > "shared" FTW! ;-)
>
> That is true for more parts of the code that, as I understand it, won't
> live under lp.shared/lp.inter. E.g. buildmaster, testing, scripts,
> services, etc.
On a related note, I am wary of slapping every "shared" module under services.
I guess I don't like typing long imports.
References