GettingStarted
Differences between revisions 12 and 31 (spanning 19 versions)
|
Size: 3901
Comment:
|
← Revision 31 as of 2020-03-25 22:46:40 ⇥
Size: 3062
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| [[Include(DesktopTeam/MenuHeader)]] | <<Include(DesktopTeam/MenuHeader)>> |
| Line 3: | Line 3: |
| So this all sounds cool to you? You want to get involved in the Desktop Team? | = Get Involved = So building a world-class desktop sounds cool to you? You want to get involved in the Desktop Team? |
| Line 7: | Line 9: |
| == Places to sign up == | == Keeping in Touch == |
| Line 9: | Line 11: |
| || '''What''' || '''Why''' || || http://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop || our mailing list, currently low traffic, but expect the new stuff there || || https://launchpad.net/people/desktop-bugs || Launchpad team || || 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 15: | Line 14: |
| == Work on Bugs == | |
| Line 16: | 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 18: | Line 18: |
| === Work on Bugs === Bugs managements is a good part of the work for the desktop team at the moment and required to prioritise the work and now what problems should worked first |
* 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. |
| Line 21: | Line 21: |
| * Places for desktop bugs: https://bugs.launchpad.net/people/desktop-bugs/+assignedbugs, https://wiki.ubuntu.com/DesktopTeam/Bugs * You can help the Desktop Team by joining the bug squad (http://wiki.ubuntu.com/BugSquad) * 236 members to date * ~60000 bug mails in the last year ;-) * Hug Days * forward useful bugs and investigate with upstream * make bug useful (reassign them to the right place, ask for required details, get debug backtrace for crashers, clean bugs that should be closed) * help listing bugs that should be fixed for the next version of Ubuntu (or fixes to backport) |
== Communication with other teams == |
| Line 30: | Line 23: |
| === Communication with other teams, upstream, Debian, etc === We want to have a good relationship with the people we work with |
We want to have a good relationship with the people we work with. |
| Line 33: | Line 25: |
| * work on forwarding patches upstream (https://wiki.ubuntu.com/DesktopTeam/UpstreamDelta), 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 |
* 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 |
| Line 37: | Line 29: |
| === Documentation === A good documentation help new contributors to know where to start and also not-so-new team members how to do specific things, or what is to do by example |
== Documentation == |
| Line 40: | Line 31: |
| * help by 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 (https://wiki.ubuntu.com/DesktopTeam) (goals, list of things to do, documentation, how to start, etc) |
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 |
| Line 43: | Line 33: |
| === Packaging === Most of the work for a distribution is at the packaging level which means there is some place to contribute there too :) |
* 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 |
| Line 46: | Line 40: |
| * help doing desktop packages updates (update the package, test the new version, communicate issues with upstream is 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 and way to learn. If you do a good job you can quickly become the maintainer for that package * work on fixing issues by writting patches or backporting them from upstream and applying those fixes to the packages * package new software * https://launchpad.net/~desktop-bugs/+mentoring |
* 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 |
| Line 52: | Line 45: |
| === Testing === * help testing GNOME, write specific test plans |
To learn how to package well, you should read the following: |
| Line 55: | Line 47: |
| === 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. * ... |
* [[MOTU/GettingStarted|Getting started]] becoming an Ubuntu Developer. * How the Desktop Team uses [[DesktopTeam/git|git]]. |
| Line 61: | Line 50: |
| == Useful places to start == | == Testing == * Help testing GNOME, write specific test plans |
| Line 63: | Line 53: |
| * https://wiki.ubuntu.com/MOTU/Recipes == Weekly TODO == ---- [https://wiki.ubuntu.com/DesktopTeam/WeeklyTODO?action=edit edit weekly TODO] [[Include(DesktopTeam/WeeklyTODO)]] [https://wiki.ubuntu.com/DesktopTeam/WeeklyTODO?action=edit edit weekly TODO] ---- |
== 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. |
| Line 73: | Line 59: |
| Go back to '''[:DesktopTeam]'''.[[BR]][[BR]] [:CategoryDesktopTeam] |
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.
Join the Desktop bug team
See the main 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 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:
Getting started becoming an Ubuntu Developer.
How the Desktop Team uses git.
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)