GettingStarted

Differences between revisions 1 and 30 (spanning 29 versions)
⇤ ← Revision 1 as of 2005-11-30 06:44:58 →
Size: 1257
Editor: i577B0F29
Comment:
← Revision 30 as of 2016-10-27 07:44:43 → ⇥
Size: 3062
Editor: dholbach
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
So this all sounds cool to you? You want to get involved in the Desktop Team? <<Include(DesktopTeam/MenuHeader)>>

= Get Involved =

So building a world-class desktop sounds cool to you? You want to get involved in the Desktop Team?
Line 5: Line 9:
== Places to sign up == == Keeping in Touch ==
Line 7: Line 11:
|| '''What''' || '''Why''' ||
|| http://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop-bugs || our mailing list, currently low traffic, but expect the new stuff there ||
|| https://launchpad.net/people/gnome || The Launchpad team - Launchpad bugs go there, currently medium traffic mails ||
|| http://lists.ubuntu.com/mailman/listinfo/desktop-bugs || Bugzilla Bugs, QUITE high-traffic, but worthwhile to catch up ||
|| || ||		  * Join our [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop|mailing list]] (medium traffic)
 * Join us on IRC in #ubuntu-desktop on Freenode.
Line 13: Line 14:
== Work on Bugs ==
Line 14: Line 16:
== What can I do? == 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. Here are some ways you can help.
Line 16: Line 18:
 * If you want to get involved in bug triage, visiting ["UbuntuBugDay"] is a good idea. It has lists of bugs, we're currently trying to solve. ["HelpingWithBugs"] has the general overview.
  * {{{desktop-bugs@lists.ubuntu.com}}} is the QA Contact on Bugzilla, you need to look for.
  * {{{gnome}}} is the assignee of bugs on Launchpad, you need to look for.
 * If you have crazy ideas, write them up on ["DesktopTeam/Visions"] and discuss them on the mailing list.
 * If you want to have new software included in the Ubuntu Deskop, head to ["DesktopTeam/NewSoftware"]
 * If you want to join us for a chat, visit {{{#ubuntu-desktop}}} on {{{irc.freenode.net}}}
 * ...		  * Join the [[LaunchpadHome:desktop-bugs|Desktop bug team]]
 * See the main [[DesktopTeam/Bugs|Desktop bug page]] for more information about how we stay on top of bugs and how to find more opportunities to help.

== Communication with other teams ==

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

 * Work on [[Bugs/Upstream/GNOME|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

== Documentation ==

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 [[DesktopTeam/Specs|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)

== Packaging ==

This is also an important task for the Team. You can
 
 * Help doing desktop [[http://people.canonical.com/~platform/desktop/versions.html|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

To learn how to package well, you should read the following:

 * [[MOTU/GettingStarted|Getting started]] becoming an Ubuntu Developer.
 * How the Desktop Team uses [[DesktopTeam/Bzr|bzr]].

== Testing ==
 * Help testing GNOME, write specific test plans

== Other ==
 * 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.

----
Go back to '''[[DesktopTeam]]'''.<<BR>><<BR>>
[[CategoryDesktopTeam]]

Get Involved

So building a world-class desktop sounds cool to you? You want to get involved in the Desktop Team?

Brilliant!

Keeping in Touch

  • Join our mailing list (medium traffic)

  • Join us on IRC in #ubuntu-desktop on Freenode.

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. Here are some ways you can help.

Communication with other teams

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

Documentation

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)

Packaging

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

To learn how to package well, you should read the following:

Testing

  • Help testing GNOME, write specific test plans

Other

  • 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.

Go back to DesktopTeam.

CategoryDesktopTeam

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