Processing your MOTU application via email

Mathieu Trudel-Lapierre mathieu-tl at ubuntu.com
Thu Apr 14 14:38:55 UTC 2011


On Thu, Apr 14, 2011 at 9:19 AM, Iain Lane <laney at ubuntu.com> wrote:
> Hi,
>
> The DMB has had problems achieving quorum in the past few weeks. This
> has resulted in a backlog of applications to be heard.
>
> Given that, we'd like to invite you to have your application processed
> by email. We'll have a 'questioning' period for at most 1 week, and
> then voting for 2-3 days thereafter.
>
> If you'd rather be processed on IRC, let us know.
>
> Initial question.
>
>  - Can you explain what you see as the main function(s) of MOTU?
>    Where do you see yourself fitting in to achieve these functions?

I see the main function of the MOTU team as analoguous to those of the
Debian QA team: to uphold the quality of the distribution in general,
whereas the MOTU team would focus more on the unseeded packages, given
that others tend to be handled by other teams. These quality assurance
tasks include fixing FTBFS, NBS, etc.

I already focus on a few network-related packages (especially
network-manager plugins, for which my work predates my joining
Canonical to maintain NetworkManager), as well as the few packages I
maintain in both Debian and Ubuntu (concordance, congruity, etc.).

Lately, I've found myself touching more and more packages in main and
getting fixed sponsored. I believe it ties in to the MOTU team's
responsibilities to provide assistance to other developers in bug
fixing.

I also think it's up to the MOTU team as a starting point for new
contributors wanting to become Ubuntu developers, which is why I
joined a new attempt to re-start the MOTU mentorship program.
Unfortunately, this still doesn't seem to be going anywhere yet, but I
do feel it deserves another honest attempt. I think I would do well as
a mentor and in organizing mentorship activities.

Mathieu Trudel-Lapierre <mathieu-tl at ubuntu.com>
Freenode: cyphermox, Jabber: mathieu.tl at gmail.com
4096R/EE018C93 1967 8F7D 03A1 8F38 732E  FF82 C126 33E1 EE01 8C93




More information about the Devel-permissions mailing list