GettingStarted
|
Size: 1257
Comment:
|
Size: 3782
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| <<Include(DesktopTeam/MenuHeader)>> |
|
| Line 8: | Line 10: |
| || 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/ubuntu-desktop || our mailing list, currently low traffic, but expect the new stuff there || || https://launchpad.net/people/desktop-bugs || Launchpad team || |
| 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}}} |
Triage [[http://tinyurl.com/5mflk3|Desktop opportunities in Harvest]]. === 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. * 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, upstream, Debian, etc === We want to have a good relationship with the people we work with * 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 === 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 (https://wiki.ubuntu.com/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 * check our mentored bugs https://launchpad.net/~desktop-bugs/+mentoring We are experimenting with bzr to do our packaging work. You can find more details on how to use it [[DesktopTeam/Bzr|here]]. === 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. |
| Line 23: | Line 64: |
== Useful places to start == * [[MOTU/GettingStarted]] ---- Go back to '''[[DesktopTeam]]'''.<<BR>><<BR>> [[CategoryDesktopTeam]] |
So this all sounds cool to you? You want to get involved in the Desktop Team?
Brilliant!
Places to sign up
What |
Why |
our mailing list, currently low traffic, but expect the new stuff there |
|
Launchpad team |
|
Bugzilla Bugs, QUITE high-traffic, but worthwhile to catch up |
|
|
|
What can I do?
Triage Desktop opportunities in Harvest.
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.
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, upstream, Debian, etc
We want to have a good relationship with the people we work with
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
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 (https://wiki.ubuntu.com/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
check our mentored bugs https://launchpad.net/~desktop-bugs/+mentoring
We are experimenting with bzr to do our packaging work. You can find more details on how to use it here.
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.
- ...
Useful places to start
Go back to DesktopTeam.
CategoryDesktopTeam
DesktopTeam/GettingStarted (last edited 2020-03-25 22:46:40 by 3v1n0)