launchpad-dev team mailing list archive

[Robert Collins <robert@xxxxxxxxxxxxx>]

On Tue, Aug 21, 2012 at 2:24 AM, Benji York <benji.york@xxxxxxxxxxxxx> wrote:
> A recent python-pgbouncer merge proposal triggered a discussion about
> whether or not we should continue to use a bit of configuration in the
> Launchpad Team's non-Launchpad-itself projects.
>
> The MP comments are short and good, so please consider them included
> here by reference:
> https://code.launchpad.net/~benji/python-pgbouncer/buildout-fixes-and-tweaks/+merge/119188#conversation

Here is my take....

We have 20+ buildout using projects.

- We should want a very high bar before we have different configs in
each one: lets keep the cost of switching between projects low.
- All the 'product' projects - launchpad, txlongpoll, datedir2amqp etc
- things with commands that are run - need to be installable by
sysadmins without internet access
- Either we need specific instructions for sysadmin installation, or
we want the default to match sysadmin needs
- We want the same instructions to work across the board (again,
consistency & cost reduction).
- Our CI story should accurately reflect whether bootstrapping and
installation will work for sysadmins.

I don't have a particular view on the specifics for achieving this,
but I will note that we currently have achieved it. So, if we change,
please:
 - change it across the board
 - don't break the sysadmin installation use cases.

-Rob