Differences between revisions 26 and 27
Revision 26 as of 2008-09-17 15:42:58
Size: 3782
Editor: host200-210-dynamic
Revision 27 as of 2010-08-17 07:26:09
Size: 3786
Editor: p5DDC367C
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
== What can I do? == ##== What can I do? ==
Line 18: Line 18:
Triage [[|Desktop opportunities in Harvest]]. ##Triage [[|Desktop opportunities in Harvest]].

So this all sounds cool to you? You want to get involved in the Desktop Team?


Places to sign up



our mailing list, currently low traffic, but expect the new stuff there

Launchpad team

Bugzilla Bugs, QUITE high-traffic, but worthwhile to catch up

Work on Bugs

Bug management is an important task for the desktop team at the moment. It is required to prioritise bugs and what issues should be tackled first.

Communication with other teams, upstream, Debian, etc

We want to have a good relationship with the people we work with

  • work on forwarding patches upstream (, having a low delta is better for everybody

  • become point of contact between the distribution and upstream for packages you have an interest in
  • work with other teams and Debian


Good documentation helps new contributors to know where to start and also not-so-new team members how to do specific things; you can help with

  • writing specifications (i.e: documents on launchpad and the wiki that describes the changes we want to get implemented and how)
  • update wiki pages for the DesktopTeam ( (goals, list of things to do, documentation, how to start, etc)


This is also an important task for the Team. You can

  • help doing desktop packages updates (update the package, test the new version, communicate issues with upstream if there is any)
  • pick a package you have interest in (contacting the usual maintainer before starting to work on it might be a good idea) and start working on it. No need to have uploads right to start on a package, having your first updates mentored is usually a good start to learn. If you do a good job you can quickly become the maintainer for that package
  • work on fixing issues by writing patches or backporting them from upstream and applying those fixes to the packages
  • package new software
  • check our mentored bugs

We are experimenting with bzr to do our packaging work. You can find more details on how to use it here.


  • help testing GNOME, write specific test plans


  • new ideas: bring your good ideas of changes for the Ubuntu desktop and help to implement them
  • teams: if you can motivate several people to work on a project creating a team around it is a good way to organize work: pda, printing, mono, telepathy, etc
  • If you have crazy ideas, write them up on DesktopTeam/Visions and discuss them on the mailing list.

  • ...

Useful places to start

* MOTU/GettingStarted

Go back to DesktopTeam.


DesktopTeam/GettingStarted (last edited 2020-03-25 22:46:40 by 3v1n0)