motu vs. ubuntu-dev in Launchpad (Re: Communication channels)

[Matt Zimmerman]

On Thu, Feb 22, 2007 at 09:51:53PM +0100, Stefan Potyra wrote:
> Hi,
> 
> On Thursday 22 February 2007 21:34:25 Matt Zimmerman wrote:
> > - Where is the universe-bugs mailing list used?  Is it a bug contact in
> >   Launchpad somewhere?  A team?
> 
> it's the contact address for the motu team [1], so all bugs assigned to motu 
> show up there.
> 
> However I can't remember the details why we had the extra motu team apart from 
> ubuntu-dev right now.

I think that team predated the use of Launchpad for access control in the
archive, and because it was not appropriately restricted, we created a new
team instead when it was needed.  For example, almost every member of the
motu team is also an administrator, and can thus add new members.  This
isn't workable for a team used to grant upload privileges.

With the formation of the MOTU Council, though, perhaps it is time to
revisit this.  It's confusing to have a MOTU team which doesn't correspond
to the development team in the expected way.

Here's a strawman proposal:

1. Set the motu-council team to be administered exclusively by techboard
(per MotuProcessesSpec)

2. Set the motu team to be administered exclusively by techboard (per
MotuProcessesSpec)

3. Clean up the "motu" team to have only members who are approved MOTU (by
the Tech Board or MOTU Council), correcting expiry dates to match ubuntu-dev

4. Make "motu" a member of ubuntu-dev (creating an easy-to-understand
hierarchy: ubuntu-dev = ubuntu-core-dev + motu)

5. (Optionally) clean up ubuntu-dev to remove direct members who are now
indirect members via motu

Thoughts?

-- 
 - mdz