CoreDeveloperApplication
|
Size: 2142
Comment:
|
Size: 3611
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 14: | Line 14: |
| ''I've been a Debian Developer for ~12 years, and a Canonical employee for ~3 years.'' | ''I've been a Debian Developer for ~12 years, and a Canonical employee for ~3 years. I like both free software and free beer. I'm experienced working with the kernel, server installer, security issues, autobuilders, packaging, etc.'' |
| Line 17: | Line 17: |
| ''Tell us how and when you got involved, what you liked working on and what you could probably do better.'' | ''My first real involvement with Ubuntu was in a previous job at HP, probably sometime in 2009. I would resolve hardware support issues (often out of date drivers) with Ubuntu found by our QA team (sometimes working w/ Canonical). I also worked directly with HP customers that used Ubuntu to help resolve issues, and packaged up various HP software components for Ubuntu on HP servers. What did I like about it? Helping users resolve real problems. What could I have done better? Actively seek out ProLiant/Ubuntu users to get a macro level view of the issues they were facing. I was otherwise mostly reactive. |
| Line 21: | Line 21: |
| * LP: #1053306: User had an intermittent - but severe - issue with open-iscsi hanging. Used online analysis to root cause, created a simple reproducer, found a fix upstream, backported & got it SRU'd. * LP: #1035110 - root caused a MAAS issue with highbank platforms due to a missing driver, identified a fix & got it SRU'd * Created a project to add unofficial support for the Arndale development board (https://launchpad.net/~arndale-team) * Got a couple of my patches SRU'd so that users could use LTS qemu to emulate highbank (LP: #1030594, LP: 1030588) I try to take an Upstream-first approach though, so a lot of the things I've worked on have come in indirectly e.g. via debian, or kernel.org. |
|
| Line 22: | Line 29: |
| ''Let us know what you worked on, with which development teams / developers with whom 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. |
''These days I mostly work with the Ubuntu ARM and MAAS teams to add and maintain support for ARM SoCs. I often find myself needing to fix bugs in core packages - often just backporting changes from upstream - and it'd probably be more efficient to do so w/o seeking a sponsor.'' |
| Line 26: | Line 32: |
| ''Keep up with more mailing lists. I suck at following high-traffic lists.'' | |
| Line 30: | Line 37: |
| ''Please describe what you like least in Ubuntu and what thoughts do you have about fixing it.'' | ''Unnecessary divergences from upstream. I hope to maintain rigor about pushing things back upstream.'' |
Contents |
I, dann frazier, apply for core-dev.
Name |
dann frazier |
Launchpad Page |
|
Wiki Page |
Who I am
I've been a Debian Developer for ~12 years, and a Canonical employee for ~3 years. I like both free software and free beer. I'm experienced working with the kernel, server installer, security issues, autobuilders, packaging, etc.
My Ubuntu story
My first real involvement with Ubuntu was in a previous job at HP, probably sometime in 2009. I would resolve hardware support issues (often out of date drivers) with Ubuntu found by our QA team (sometimes working w/ Canonical). I also worked directly with HP customers that used Ubuntu to help resolve issues, and packaged up various HP software components for Ubuntu on HP servers. What did I like about it? Helping users resolve real problems. What could I have done better? Actively seek out ProLiant/Ubuntu users to get a macro level view of the issues they were facing. I was otherwise mostly reactive.
LP: #1053306: User had an intermittent - but severe - issue with open-iscsi hanging. Used online analysis to root cause, created a simple reproducer, found a fix upstream, backported & got it SRU'd. LP: #1035110 - root caused a MAAS issue with highbank platforms due to a missing driver, identified a fix & got it SRU'd Created a project to add unofficial support for the Arndale development board (https://launchpad.net/~arndale-team) I try to take an Upstream-first approach though, so a lot of the things I've worked on have come in indirectly e.g. via debian, or kernel.org.
My involvement
Examples of my work / Things I'm proud of
Areas of work
These days I mostly work with the Ubuntu ARM and MAAS teams to add and maintain support for ARM SoCs. I often find myself needing to fix bugs in core packages - often just backporting changes from upstream - and it'd probably be more efficient to do so w/o seeking a sponsor. Things I could do better
Keep up with more mailing lists. I suck at following high-traffic lists. Plans for the future
General
What I like least in Ubuntu
Unnecessary divergences from upstream. I hope to maintain rigor about pushing things back upstream. 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 ===
DannFrazier/CoreDeveloperApplication (last edited 2014-08-26 22:08:45 by dannf)