specifically work on Wine and Wine-related packages (wine-doors, etc.) Furthermore, open source Windows programs ported with Winelib can be Debianized and tested/linked against the current version of Winelib here.

[:MOTU/Teams/Kubuntu]

kubuntu-team

#kubuntu-devel

KDE packages not in main

[:MOTU/Teams/IM]

motuim

this team will handle all aspects of all areas of Instant Messaging, with main aspect on Jabber/XMPP Services and components

[:MOTU/Teams/Ruby]

moturuby

cares for all packages related to the Ruby programming language (interpreter + packages written in Ruby)

[:MOTU/Teams/Photo]

phototeam

cares for all digital photography packages

[:MOTU/Teams/Science]

motuscience

cares for science related packages (chemistry, physics, biology, etc.) making sure packages are synced and cool new apps included in universe

[:MOTU/Teams/Java]

motujava

Grow coffee for the Ubuntu Java community

[:MOTU/Teams/UncommonProgrammingLanguages]

uncommonproglang

care for packages which use uncommon programming languages not covered by anyone else

[:MOTU/Teams/Torrent]

motu-torrent

#ubuntu-motu-torrent

we take care of all packages related to the peer-to-peer protocol named bittorrent

Your Own MOTU team

The idea behind MOTU subteams is to

separate the MOTU package maintenance work into subtopics for the different interests that

touch a set of packages in universe and

can be grouped to concentrate the work in a team rather than to put it on a single maintainer's shoulders.

be able to better

plan transitions

discuss needed changes

organize work.

MOTU teams should not only be formed by universe maintainers, but also by users and testers who help pointing out packaging bugs or testing package fixes. They should have a teamleader as a single point of contact and may have several subteams.

All teams should work together very tightly with their counterpart of the main teams found [:Teams:on this page]. Strong contact to the according Debian maintainers is highly appreciated.