MOTU Organisation
The MOTU have come together as a vital part of the Ubuntu community, playing a tremendous role in making Ubuntu more broadly useful and as a place for developers to demonstrate their skills. We will review the organisation and processes around the MOTU and see what improvements we can make.
Blueprint information
- Status:
- Complete
- Approver:
- Matt Zimmerman
- Priority:
- Medium
- Drafter:
- Daniel Holbach
- Direction:
- Needs approval
- Assignee:
- Daniel Holbach
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Daniel Holbach
- Completed by
- Daniel Holbach
Whiteboard
Review: OK -- smurf
pitti, 2006-11-30: reviewed, left some questions in the wiki; these are just suggestions, though
dholbach, 2006-11-30: improved the wording, clarified all of pitti's suggestions I understood. One item remaining. Clarified role of MC wrt TB and CC on Keybuk's request - he was happy with the spec apart from that.
mdz, 2006-11-30: How are the council members elected? Is there a standard process for this from the CC? This seems to require CC review as well, since it is a governance matter.
dholbach, 2007-02-23: MC implemented and had its first meeting. Only thing missing is the mailing list, which we need for the membership approval process: RT 26925.
dholbach, 2007-03-05: MC implemented.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
