LP teams for bazaar [again]

[Martin Pool]

On 16 April 2010 09:02, Robert Collins <robertc at robertcollins.net> wrote:
> So, I've done a short spike to allow the removal of bzr-pqm-submit,
> based on Martin's Hydrazine work.
>
> Launchpad has a nascent 'queue' concept for branches, which allows us to
> get rid of the email interface and have PQM talk to launchpad, which
> gives us better diagnostics (anyone can see the issue on the merge
> proposal), and less configuration issues (don't need to have working
> email in both directions).

yay


> So bzr-core has 7 people and 'bzr' as members, bzr has 28 folk (with
> some overlap).
>
> We need a team that represents 'commit access to trunk'; this could be
> bzr-core, with a couple of caveats:
>  - we'll want to audit the current members of ~bzr, it used to be an
>   open team
>  - we'll want to ask ourselves if there are any things in lp that
>   you need to be a member of ~bzr or ~bzr-core to do, which we want to
>   grant to non-committers. The new bzr-qa team has helped here already.
>
> I think using 'bzr-core' is appropriate.

That would mean booting ~25 people out of it (or deciding they are ok
to commit) which may be a bit strange.  otoh those people already have
access to the PPA so should be fairly trusted.

I am inclined to create something explicitly named ~bzr-committers,
even if it ends up just including other teams.  The function and
meaning of different teams has caused confusion in the past and I
don't want to repeat that with "does core mean the core team or the
core of bzrlib?"

I think we need to create a new team ~bzr-committers: this is more
explicit, and it also avoids bumping out people who may have a

-- 
Martin <http://launchpad.net/~mbp/>