launchpad-dev team mailing list archive

[Robert Collins <robert.collins@xxxxxxxxxxxxx>]

On Wed, 2009-12-02 at 10:23 +0000, Jonathan Lange wrote:
> 
> I agree that we need to be able to coordinate work by teams smaller
> than "all the Launchpad committers".
> 
> However, I do think that ideally, we'd be modelling this by using
> teams. At the moment, we are modelling it with projects. I don't think
> there is any real sense in which, malone say, is a separate *project*
> from registry. It grates on me that we model it that way in Launchpad.
> Ideally, we'd have one project (launchpad) and many teams, and work
> could be coordinated through teams. Would you agree with this? 

I'm not entirely sure I agree with /needing/ to coordinate work on teams
smaller than 'all the launchpad committers'. I know that we *do*
coordinate work on smaller teams, but its not clear to me that we need
to - or that if we do, that the lines are sliced in the correct
dimensions. (For instance we have pillar slicing today for some subteams
(bugs, code, translations, soyuz), layers for others (design,
foundations), no slicing for others (everyone is a reviewer).

The crux of the thing, for me, is Conway's law:
http://en.wikipedia.org/wiki/Conway%27s_Law

If we really want Launchpad to be working as a smooth application,
rather than a bunch of things that sometimes work together, I think we'd
be a lot better off with a single team, shared vision and shared goals.

The major points raised against doing this were about information
overload, AIUI. I *don't* have good answers for this today, but I'd love
it if we explored it further.

-Rob

Attachment: signature.asc
Description: This is a digitally signed message part