EasierMotuing

Revision 1 as of 2006-06-09 20:15:37

Clear message

Summary

In the specification process we'd like to figure out problems we currently face in the MOTU world. Identifying bottlenecks and off-putting processes and areas lacking involvement.

Rationale

The MOTU activities should

  • be more inviting,
  • try to target more of the interested and technically apt users and
  • make it easy for them to get involved and to find their place in the community.

Use cases

Martin joins the channel #ubuntu-motu and tries to figure out how to help out. Nobody answers him, everybody is busy with their own packages or geek discussions.

Matt wants to help out as well and asks on the mailing list. Somebody replies "Look at Universe bugs."

Mark fought his way through documentation, but tries to find "Live Examples" and how to actually get things done.

Matthew knows quite a bit about packaging, but has no idea, how the build daemons work, where and why to get a key signed. Apart from that he doesn't know the people involved in Ubuntu and those with key roles.

Scope

Design

Implementation

One key to some of the problems would be to revive the MOTU school again and feature short sessions with Ubuntu developers every now and then, possible topics could be:

  • "How to update a package properly?"
  • "What do I have to do, if I maintain a package?"
  • "Cool things to do with python-apt."
  • "Soyuz and all that Jazz"
  • ...

A lot of other problems could be adressed initially by fleshing out use cases and imagining our way through them in a Brainstorm session.

Code

Data preservation and migration

Outstanding issues

BoF agenda and discussion

CategorySpec