Teams

Differences between revisions 49 and 52 (spanning 3 versions)
Revision 49 as of 2007-10-08 20:11:50
Size: 5056
Editor: 133
Comment:
Revision 52 as of 2007-12-12 23:33:37
Size: 4778
Editor: c-67-166-147-83
Comment: Fix WineTeam link
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:


## page was renamed from MOTUTeams
This shall become the rootlevel page for the ubuntu MOTU team pages.

The idea 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 [http://www.ubuntulinux.org/community/teams on this page]. Strong contact to the according Debian maintainers is highly appreciated.

If you're eager and don't know where, how to start your team: ["BuildingCommunity/CreatingTeamGuide"]

We listed some ideas on teams on ["MOTU/Teams/Ideas"]
Line 42: Line 21:
|| [:MOTU/Teams/Wine] || || || specifically work on Wine and Wine-related packages (winetools, etc.) Furthermore, open source Windows programs ported with Winelib can be Debianized and tested/linked against the current version of Winelib here. || || [:WineTeam] || || || 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. ||
Line 52: Line 31:
=== Comments ===
If you have additional ideas about this topic or want to add a team, feel free to change this page as you like.
=== Your Own MOTU team ===
Line 55: Line 33:
----
Related Pages
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.
Line 58: Line 42:
[[FullSearch()]] 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.

If you're eager and don't know where, how to start your team: ["BuildingCommunity/CreatingTeamGuide"]

We listed some ideas on teams on ["MOTU/Teams/Ideas"]

Include(MOTU/Headers/Menu)

The Teams

Team

Launchpad name

Contact information

Vision

[:MOTU]

motu

#ubuntu-motu

the mother of all Universe development

[:MOTU/Mentoring/Mentor:MOTU Mentors]

Take care of new MOTU Contributors, help them get going and become good MOTUs quickly

[:MOTU/Teams/GNOME] (now [:DesktopTeam])

gnome

#ubuntu-desktop

gives users the nice, squashy, comfortable GNOME experience, introduces new features, fixes bugs and takes care of the overall GNOME integration

[:MOTU/Teams/Security]

cares for vulnerabilitys in universe, works together very tight with the main security team

[:MOTU/Teams/Python]

guess what this team cares for (this is a subset of the main python team that cares specific for universe packages)

[:MOTUAlternateDesktop]

caring for alternative windowmanagers in ubuntu universe, subteams for each WM are possible (keeps in contact with the main desktop team)

[:MOTU/Teams/ZopePlone]

pkg-zope

zope and plone integration team, a subset of the main server team

[:MOTU/Teams/Games]

motugames

THIS TEAM IS NOT ACTIVE ANYMORE. See wiki page for more information.

[:MOTUDbServer]

care for universe db server integration. subteams for any kind of db server are possible (subset of the main server team)

[:MOTU/Teams/Media]

motumedia

the team that cares for multimedia in universe, subteams for audio and video would be desirable in tight contact with the main desktop team

[:MOTU/Teams/Audio]

the team who packages professional audio software

[:MOTU/Teams/Nettools]

the universe networkers crew, subteams for dialup, router or firewall would be possible

[:MOTU/Teams/Hardware]

cares for hardware specfic configuration frontends for the desktop/commandline (printer inklevel meter, touchpad configuration, monitor calibration, etc.) (keeps a loose connection to the kernel, laptop and desktop teams)

[:WineTeam]

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 Wink ;)

[: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.

If you're eager and don't know where, how to start your team: ["BuildingCommunity/CreatingTeamGuide"]

We listed some ideas on teams on ["MOTU/Teams/Ideas"]


Go back to [:MOTU].BR ["CategoryMOTU"]

MOTU/Teams (last edited 2012-12-06 15:48:53 by andrewsomething)