ContributingDeveloperApplication

Differences between revisions 12 and 13
Revision 12 as of 2009-11-03 01:56:32
Size: 5187
Editor: cpe-67-244-39-144
Comment:
Revision 13 as of 2009-11-04 03:51:30
Size: 7086
Editor: cpe-67-244-39-144
Comment:
Deletions are marked like this. Additions are marked like this.
Line 18: 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, and I now review bug control applications. 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. I started by setting up a Debian LAMP/samba server for my lab around 2004. I installed Debian on my desktop to learn Linux, but switched when someone told me of this new distro called "Ubuntu." I've been using Ubuntu/Xubuntu since. After the release of Jaunty, I joined the bug squad and eventually bug control, participating in many hugdays as a triager, and I now review bug control applications and mentor a new bug squad member. 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 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. I now am a member of the MOTU Science team and have done triaging, bug fixing/patching, packaging, merges, syncs, upgrades, FFEs, and recently a very important SRU. I have upload permission to GNOME, confident with git, bzr, PPAs, package building, new packages (I'm actually looking for someone to sponsor a new package to Debian non-free if you have the time!)
Line 20: Line 21:
list from the other page
apport hook for GPM (we now use upstream's standard bug report script)
 * GPM Bug fixing massacre of June. Wrote patches, coordinated with upstream, and brought patches into GPM during June:
Line 23: Line 23:

more cool bugs: something with gconf settings in GPM, default for on lid close
inhibit fixing
combo box broken (not remembering settings) bug (wrote patch for upstream, tested on LP/ubuntu, brought patch to ubuntu, tested it)
tried to update gnome-power-manager: https://bugs.launchpad.net/bugs/419628, after it was done i did the following:
https://bugs.edge.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/419858 --remove unnecessary patch
https://bugs.launchpad.net/ubuntu/+source/octave3.0/+bug/422058 --fixed a ftbfs by simply rebuilding (bug in a depend. package)
https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/424385 --did necessary work for freeze exception and built ppa for testing
https://bugs.launchpad.net/ubuntu/+source/k3dsurf/+bug/295140 --upgraded k3dsurf to new version to fix bug, ppa for testing

while trying to get this synced, found upstream bug, patched it into ubuntu, got a needed library synced and tested:
https://bugs.launchpad.net/ubuntu/+source/qtiplot/+bug/374543
https://bugs.launchpad.net/ubuntu/+source/qwt/+bug/433718
GPM bug with the crash when unplugging AC
GPM patch for gconf settings being incorrect
GPM patch for crashing when plugging in/out AC https://bugzilla.gnome.org/show_bug.cgi?id=598221

synced/uploaded/worked on:
qtiplot
flashrom
k3dsurf (debian bug 547344 got it upgraded in deb)
https://bugs.launchpad.net/ubuntu/+source/qtiplot/+bug/471238 -- SRU for bug in qtiplot
 * I updated the apport hook for gnome-power-manager so we now use upstream's standard bug report script, and will update it for Lucid to attach hardware information (since we've had LOTS of bugs with brightness lately). [[http://bazaar.launchpad.net/~ubuntu-desktop/gnome-power/ubuntu/revision/163.2.1|LP commit]]
 * Debugged this bug on LP, worked with upstream author, wrote the patch, tested on LP with a PPA, got it accepted upstream in gnome-power-manager and patched in Ubuntu [[https://bugs.launchpad.net/bugs/407491|LP link]]
 * Inhibit applet was completely broken at the beginning of Karmic. I worked with the original reporter and upstream to get it working and maintained the PPA for testing. Throughout Karmic's development, I maintained a testing PPA of gnome-power-manager for many bugs and upstream fixes [[https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/389857|LP bug]]. While we fixed the bug there, the OP was not satisfied with gnome-session's inhibit behavior, so it is still open.
 * After FF, I continued working on GPM, tried to help with an update but it was passed over for a more experienced developer [[https://bugs.launchpad.net/bugs/419628|LP link]]. I then helped remove the unnecessary patch from the source package [[https://bugs.edge.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/419858|LP link]]
 * Fixed a FTBFS [[https://bugs.launchpad.net/ubuntu/+source/octave3.0/+bug/422058|LP link]] in octave (science package)
 * did necessary work for freeze exception and built ppa for testing [[https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/424385|flashrom package]]
 * upgraded k3dsurf to new version to fix bug, ppa for testing [[https://bugs.launchpad.net/ubuntu/+source/k3dsurf/+bug/295140|LP link]]
 * sent fixes and patches I wrote for Ubuntu with upstream (both Debian and original authors) for MANY bugs and packages. While writing this application I actually just got an email for this one I forgot about [[http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550721|Debian BTS link]]
 * Major bug fixed right before Karmic release that was causing a lot of bug reports. Fixed and tested in [[https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/447304|Ubuntu]], got it adopted [[https://bugzilla.gnome.org/show_bug.cgi?id=598221|upstream]].
 * I officially "uploaded" with a sponsor: k3dsurf, gnome-power-manager, qwt, pymol, and qtiplot. I also did all the work for the most recent flashrom sync.
 * My most proud achievement: Fixed a major day 0 bug that needed an SRU. [[https://bugs.launchpad.net/ubuntu/+source/qtiplot/+bug/471238|link is here]].
Line 46: Line 35:
gnome-power-manager: triage, patch writing for upstream & Ubuntu, patching Ubuntu, maintaining an experimental GPM PPA, merges for GPM's Ubuntu bzr packaging branches. I have upload permission at the gnome git for GPM.
Ubuntu Science: beginning to work on maintenance of packages.
 * gnome-power-manager: triage, patch writing for upstream & Ubuntu, patching Ubuntu, maintaining an experimental GPM PPA, merges for GPM's Ubuntu bzr packaging branches. I have upload permission at the gnome git for GPM.
 * Ubuntu Science: Patching, upgrades, merges, syncs, SRU, coordinating with debian/upstream (there are many more bugs I've worked on than I listed above, those were the ones I could remember writing this.)
Line 49: Line 38:
Understand debhelper scripts better, learn more of Debian packaging. Practice, practice, practice! Get more experience packaging and learning Ubuntu policies through practice.
Line 53: Line 42:
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. 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. I'm going to start the Debian new maintainer process (I just got my key signed by a DD, so I'm on my way!)
Line 55: Line 44:
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 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 precise fixes we could provide from LP


I, Scott Howard, apply for universe-contributor.

Name

Scott Howard

Launchpad Page

https://launchpad.net/~showard314

Wiki Page

https://wiki.ubuntu.com/ScottHoward/

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, but switched when someone told me of this new distro called "Ubuntu." I've been using Ubuntu/Xubuntu since. After the release of Jaunty, I joined the bug squad and eventually bug control, participating in many hugdays as a triager, and I now review bug control applications and mentor a new bug squad member. 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 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. I now am a member of the MOTU Science team and have done triaging, bug fixing/patching, packaging, merges, syncs, upgrades, FFEs, and recently a very important SRU. I have upload permission to GNOME, confident with git, bzr, PPAs, package building, new packages (I'm actually looking for someone to sponsor a new package to Debian non-free if you have the time!)

Examples of my work / Things I'm proud of

  • GPM Bug fixing massacre of June. Wrote patches, coordinated with upstream, and brought patches into GPM during June:

https://wiki.ubuntu.com/ScottHoward?action=AttachFile&do=get&target=GPM_newbug_cleaning_jun09.png

  • I updated the apport hook for gnome-power-manager so we now use upstream's standard bug report script, and will update it for Lucid to attach hardware information (since we've had LOTS of bugs with brightness lately). LP commit

  • Debugged this bug on LP, worked with upstream author, wrote the patch, tested on LP with a PPA, got it accepted upstream in gnome-power-manager and patched in Ubuntu LP link

  • Inhibit applet was completely broken at the beginning of Karmic. I worked with the original reporter and upstream to get it working and maintained the PPA for testing. Throughout Karmic's development, I maintained a testing PPA of gnome-power-manager for many bugs and upstream fixes LP bug. While we fixed the bug there, the OP was not satisfied with gnome-session's inhibit behavior, so it is still open.

  • After FF, I continued working on GPM, tried to help with an update but it was passed over for a more experienced developer LP link. I then helped remove the unnecessary patch from the source package LP link

  • Fixed a FTBFS LP link in octave (science package)

  • did necessary work for freeze exception and built ppa for testing flashrom package

  • upgraded k3dsurf to new version to fix bug, ppa for testing LP link

  • sent fixes and patches I wrote for Ubuntu with upstream (both Debian and original authors) for MANY bugs and packages. While writing this application I actually just got an email for this one I forgot about Debian BTS link

  • Major bug fixed right before Karmic release that was causing a lot of bug reports. Fixed and tested in Ubuntu, got it adopted upstream.

  • I officially "uploaded" with a sponsor: k3dsurf, gnome-power-manager, qwt, pymol, and qtiplot. I also did all the work for the most recent flashrom sync.
  • My most proud achievement: Fixed a major day 0 bug that needed an SRU. link is here.

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. I have upload permission at the gnome git for GPM.

  • Ubuntu Science: Patching, upgrades, merges, syncs, SRU, coordinating with debian/upstream (there are many more bugs I've worked on than I listed above, those were the ones I could remember writing this.)

Things I could do better

Practice, practice, practice! Get more experience packaging and learning Ubuntu policies through practice.

Plans for the future

General

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. I'm going to start the Debian new maintainer process (I just got my key signed by a DD, so I'm on my way!)

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 precise fixes we could provide from LP


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 ===


CategoryUniverseContributorApplication

ScottHoward/ContributingDeveloperApplication (last edited 2010-02-23 04:17:28 by cpe-24-58-159-82)