GettingStarted
4077
Comment:
|
4005
|
Deletions are marked like this. | Additions are marked like this. |
Line 64: | Line 64: |
* https://wiki.ubuntu.com/MOTU/School/PatchingSources to learn how to create a patch and apply it to a package | * https://wiki.ubuntu.com/MOTU/Recipes |
Include(DesktopTeam/MenuHeader)
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?
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
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
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
- 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)
Packaging
Most of the work for a distribution is at the packaging level which means there is some place to contribute there too
- 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
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.
If you want to have new software included in the Ubuntu Deskop, head to ["DesktopTeam/NewSoftware"]
- ...
Useful places to start
* 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]
Go back to [:DesktopTeam].BRBR [:CategoryDesktopTeam]
DesktopTeam/GettingStarted (last edited 2020-03-25 22:46:40 by 3v1n0)