ContributingDeveloperApplication
|
⇤ ← Revision 1 as of 2009-08-12 15:14:39
Size: 2140
Comment: first edition
|
Size: 3589
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| '''Please do not edit this page. It is a template to be used by people applying as an Ubuntu developer.''' Head over to https://wiki.ubuntu.com/YourName/YourDeveloperApplication instead and make use of this template. ---- |
|
| Line 20: | Line 12: |
| ''Tell us a bit about yourself.'' | I'm an academic researcher with a PhD in electrical engineering. |
| Line 26: | Line 18: |
| I started by setting up a Debian LAMP/samba server for my lab around 2004. I installed Debian on my desktop to learn linux when someone told me of this new distro called "Ubuntu." I've been using Ubuntu/Xubuntu since. After the release of Jaunty, I've been active with the bug squad and eventually bug control, participating in many hugdays as a triager. I adopted the gnome-power-manager package for triaging, and triaged nearly every "new" GPM bug over the course of a month (see the chart below). While triaging the bugs I worked a lot with upstream, and started writing patches to fix bugs. I think started writing patches for Ubuntu, and bringing upstream's patches to Ubuntu. Now I'm a triager/developer of sorts that can triage, write the patch, test it with PPAs, and then do the merge proposal with bzr on LP. Since GPM is a core package, I joined Ubuntu Science to get some "universe" experience. | |
| Line 27: | Line 20: |
| list from the other page | |
| Line 28: | Line 22: |
| ''Let us know what you worked on, with which development teams / developers you cooperated and how it worked out.'' ## As a per-package uploader, please give us some insight into the package maintenance and bug situation since you're working on it. |
gnome-power-manager: triage, patch writing for upstream & Ubuntu, patching Ubuntu, maintaining an experimental GPM PPA, merges for GPM's Ubuntu bzr packaging branches. Ubuntu Science: beginning to work on maintenance of packages, specifically Octave and related packages. |
| Line 32: | Line 25: |
| Understand debhelper scripts better, learn more of Debian packaging. | |
| Line 34: | Line 28: |
| Keep the Ubuntu Science packages working, and work with Debian Science to keep both Debian and Ubuntu's science offerings the best that is available. | |
| Line 36: | Line 31: |
| ''Please describe what you like least in Ubuntu and what thoughts do you have about fixing it.'' | When working with GPM, I saw the Ubuntu was user rich and developer poor. I felt "alone" triaging, patching, and testing some of the bugs. I found that this could be used as a strength - I learned to use LP to craft high quality bug reports that pin pointed bugs, and even proposed how to fix the exact line in the source code using the help from the users on LP. Frequently the upstream developers were not aware of the bugs and appreciated the percise fixes we could provide from LP GPM bug with the crash when unplugging AC GPM patch for gconf settings being incorrect |
Contents |
I, Scott Howard, apply for universe-contributor.
Name |
Scott Howard |
Launchpad Page |
|
Wiki Page |
Who I am
I'm an academic researcher with a PhD in electrical engineering.
My Ubuntu story
Tell us how and when you got involved, what you liked working on and what you could probably do better.
My involvement
I started by setting up a Debian LAMP/samba server for my lab around 2004. I installed Debian on my desktop to learn linux when someone told me of this new distro called "Ubuntu." I've been using Ubuntu/Xubuntu since. After the release of Jaunty, I've been active with the bug squad and eventually bug control, participating in many hugdays as a triager. I adopted the gnome-power-manager package for triaging, and triaged nearly every "new" GPM bug over the course of a month (see the chart below). While triaging the bugs I worked a lot with upstream, and started writing patches to fix bugs. I think started writing patches for Ubuntu, and bringing upstream's patches to Ubuntu. Now I'm a triager/developer of sorts that can triage, write the patch, test it with PPAs, and then do the merge proposal with bzr on LP. Since GPM is a core package, I joined Ubuntu Science to get some "universe" experience.
Examples of my work / Things I'm proud of
list from the other page
Areas of work
gnome-power-manager: triage, patch writing for upstream & Ubuntu, patching Ubuntu, maintaining an experimental GPM PPA, merges for GPM's Ubuntu bzr packaging branches. Ubuntu Science: beginning to work on maintenance of packages, specifically Octave and related packages.
Things I could do better
Understand debhelper scripts better, learn more of Debian packaging.
Plans for the future
Keep the Ubuntu Science packages working, and work with Debian Science to keep both Debian and Ubuntu's science offerings the best that is available.
General
What I like least in Ubuntu
When working with GPM, I saw the Ubuntu was user rich and developer poor. I felt "alone" triaging, patching, and testing some of the bugs. I found that this could be used as a strength - I learned to use LP to craft high quality bug reports that pin pointed bugs, and even proposed how to fix the exact line in the source code using the help from the users on LP. Frequently the upstream developers were not aware of the bugs and appreciated the percise fixes we could provide from LP GPM bug with the crash when unplugging AC GPM patch for gconf settings being incorrect
Comments
If you'd like to comment, but are not the applicant or a sponsor, do it here. Don't forget to sign with @SIG@.
Endorsements
As a sponsor, just copy the template below, fill it out and add it to this section.
TEMPLATE
== <SPONSORS NAME> == === General feedback === ## Please fill us in on your shared experience. (How many packages did you sponsor? How would you judge the quality? How would you describe the improvements? Do you trust the applicant?) === Specific Experiences of working together === ''Please add good examples of your work together, but also cases that could have handled better.'' === Areas of Improvement ===
ScottHoward/ContributingDeveloperApplication (last edited 2010-02-23 04:17:28 by cpe-24-58-159-82)