UbuntuSRUDeveloperApplication
|
Size: 5636
Comment:
|
← Revision 44 as of 2017-10-23 15:07:25 ⇥
Size: 8459
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''<<BR>><<TableOfContents(2)>>|| ---- '''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. ---- |
## page was copied from ddstreet/UbuntuContributingDeveloperApplication ## page was copied from UbuntuDevelopment/DeveloperApplicationTemplate ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents(2)>>|| |
| Line 13: | Line 8: |
| '''I, <YOUR NAME>, apply for <universe-contributor|MOTU|core-dev|upload rights for package(s) <X>>.''' | |
| Line 15: | Line 9: |
| || '''Name''' || <YOUR NAME> || || '''Launchpad Page''' || <link to your launchpad page> || || '''Wiki Page''' || <link to your Wiki page> || |
'''I, Dan Streetman, apply for SRU Developer.''' || '''Name''' || Dan Streetman || || '''Launchpad Page''' || https://launchpad.net/~ddstreet || || '''Wiki Page''' || https://wiki.ubuntu.com/ddstreet || |
| Line 20: | Line 16: |
| ''Tell us a bit about yourself.'' | I started with UNIX is 1993, using Solaris, and then moved to Linux in 1997 using Slackware, Red Hat, and now Ubuntu. I began Linux kernel development in 2001, in the USB subsystem, and have contributed since then in various kernel subsystems including memory management, networking, and crypto. |
| Line 23: | Line 19: |
| ''Tell us how and when you got involved, what you liked working on and what you could probably do better.'' | I joined Canonical in 2015 as part of the Support and Technical Services Engineering team, and have been working on problems that reach into many different parts of Ubuntu; the kernel, networking, multipath, udev, and more. I enjoy digging deep into technical details and solving problems. |
| Line 27: | Line 23: |
| My sponsored uploads: * http://ubuntu-dev.alioth.debian.org/cgi-bin/ubuntu-sponsorships.cgi?render=html&sponsoree=Dan+Streetman * https://launchpad.net/~ddstreet/+uploaded-packages Ubuntu Kernel bug fix contributions not shown in above sponsored uploads: * attached block devices not showing up * https://bugs.launchpad.net/ubuntu/precise/+source/linux/+bug/1479031 * using ipsec, many connections result in no buffer space error * https://bugs.launchpad.net/ubuntu/vivid/+source/linux/+bug/1486670 * Soft lockup with "block nbdX: Attempted send on closed socket" spam * https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564 * kswapd0 100% CPU usage * https://bugs.launchpad.net/ubuntu/yakkety/+source/linux/+bug/1518457 * lots of printk to serial console can hang system for long time * https://bugs.launchpad.net/ubuntu/xenial/+source/linux/+bug/1534216 * bonded interfaces in bridge do not have LRO turned off * https://bugs.launchpad.net/ubuntu/trusty/+source/linux/+bug/1547680 * nvme drive probe failure * https://bugs.launchpad.net/ubuntu/xenial/+source/linux/+bug/1626894 * move nvme driver to linux-image * https://bugs.launchpad.net/ubuntu/trusty/+source/linux/+bug/1640275 * NVMe drives in Amazon AWS instance fail to initialize * https://bugs.launchpad.net/ubuntu/yakkety/+source/linux/+bug/1648449 * export nvme drive model/serial strings via sysfs * https://bugs.launchpad.net/ubuntu/trusty/+source/linux/+bug/1649635 * NVMe driver regression for non-smp/1-cpu systems * https://bugs.launchpad.net/ubuntu/xenial/+source/linux/+bug/1651602 * Xen MSI setup code incorrectly re-uses cached pirq * https://bugs.launchpad.net/ubuntu/zesty/+source/linux/+bug/1656381 * VLAN SR-IOV regression for IXGBE driver * https://bugs.launchpad.net/ubuntu/xenial/+source/linux/+bug/1658491 * Amazon I3 Instance Buffer I/O error on dev nvme0n1 * https://bugs.launchpad.net/ubuntu/xenial/+source/linux-aws/+bug/1668129 |
|
| Line 28: | Line 72: |
| Non-checkbox areas of work within Ubuntu include [[https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/727416|Ubiquity]] and [[https://code.launchpad.net/~roadmr/ubuntu/natty/casper/709364||Casper]] (that bug resurfaced [[https://bugs.launchpad.net/ubuntu/+source/casper/+bug/809885|here]] and Stéphane Graber was kind enough to squash it). The folks in charge of these projects are always very responsive and patient, which I really appreciate. | |
| Line 30: | Line 73: |
| Checkbox's situation has changed in the past several months. The Hardware Certification team has been growing in terms of people who can devote time working on Checkbox. This has meant we're much more able to tackle the large bug backlog the project had, while also adding new features and keeping up to date with Ubuntu's evolution. Since a large part of Checkbox are the test scripts, and these need to interact with the kernel and other APIs that keep evolving, they need constant maintenance and updating. Examples that come to mind are the recent migration to UDisks2 (for Ubuntu Quantal), the upgrade to Python3 (Quantal as well), migration to Gtk3 (for Ubuntu 11.10), and changes to APIs for Network Manager. As a team we've managed to greatly reduce the amount of open and new bugs for [https://bugs.launchpad.net/ubuntu/+source/checkbox/||ubuntu/checkbox]] (Currently 16 open bugs and 2 new ones). Checkbox's trunk/upstream branch still has a large number of open bugs (bug list [[https://bugs.launchpad.net/checkbox/|here]]). However we've drastically reduced the number of open (unlooked-at) ones, and I've been focusing on analyzing open bugs and giving them a clear "statement of work" for developers to work on; this way they can potentially jump straight into coding a solution. I felt this was more conducent to many people working on these triaged bugs, as opposed to i.e. me going over them one-by-one, analyzing, and fixing them. This way developers, both from our team and outside, can work in "parallel" to fix these bugs, and they also don't need to spare brainpower finding a bug to fix. I've also been trying to tag smaller bugs with "bitesize" to encourage community participation. This has indeed resulted in a few of these bugs being fixed by community members. We've also tried to be extra responsive to contributions to Checkbox from outside the certification team, to further encourage contributions, this has also resulted in more people knowing about checkbox and potentially considering it when searching for a test runner application. As a result the number of commits per release has grown dramatically, from 30 for the Natty cycle to 217 for the Oneiric cycle, 334 for Precise and 301 for Quantal. Particularly for the Precise cycle, this resulted in our uploads to Ubuntu having very large changelogs, which made reviewers' lives difficult. So for Quantal, despite having slightly less commits and bugfixes, we had a more regular upload cadence, with smaller changesets to ease work for reviewers and sponsors. Also, in order to ensure our package uploads are sane, we've been ramping up our "unit test" coverage, which also validates that data files contain no errors, that translated versions don't cause crashes, and that the code passes some basic "lint" tests. These processes have already caught a few errors. We complement this with a daily from-trunk PPA build which sends a notification if these automated tests fail, so we can catch these basic problems even if some bogus code makes it into the trunk branch. |
Most of my work is done in the kernel, both upstream and in Ubuntu's branches. However, I also make fixes to various packages as I, or Canonical customers or public Ubuntu users, find bugs in them that I am in a position to fix. |
| Line 42: | Line 77: |
| = Plans for the future = == General == |
Time management is difficult for everyone, as we never have enough time to complete everything we want to do. I hope to manage my time better, balancing work and family while also continuing to contribute upstream. == Plans for the future == Keep improving Ubuntu and Linux in general! |
| Line 45: | Line 84: |
| ''Please describe what you like least in Ubuntu and what thoughts do you have about fixing it.'' | Documentation is sometimes hard to come by, or out of date. |
| Line 50: | Line 91: |
| I have had the privilege of working with Dan for the past year and I know him as a knowledgable, thorough and steady colleague. He has made many contributions to Ubuntu and it would be a great win for all of us to have Dan approved as a SRU Developer. -- [[LaunchpadHome:fnordahl]] <<DateTime(2017-09-06T17:56:08+0200)>> |
|
| Line 51: | Line 94: |
| Dan has the follow through, positive attitude and drive to get things upstream that is essential for any SRU. Been working with him as part of my role in Support. Definite +1. -- [[LaunchpadHome:bryanquigley]] <<DateTime(2017-09-07T12:07:21-0400)>> Dan has helped me with a number of bugs, and I've followed his work on several of the NVME bugs listed above. I'm always impressed with his commitment to the quality of his work. This is a logical next step, and a good thing for the community. -- [[LaunchpadHome:markthomas]] <<DateTime(2017-09-07T10:44:24-0700)>> I had various opportunities to see Dan's work on SRUs and I remember them to be of sufficient high quality, demonstrating more than enough knowledge of the SRU process. -- [[LaunchpadHome:sil2100]] <<DateTime(2017-10-23T17:06:08+0200)>> |
|
| Line 54: | Line 102: |
| == Eric Desrochers == === General feedback === |
|
| Line 55: | Line 105: |
| I have sponsored a few packages from Dan over the year and the ones I have seen were high quality. Dan has the desire to do things right and he always accept constructive comments/feedbacks with a positive attitude. He understands the principles of debian packaging and the SRU process and he is not afraid to ask questions when needed. As a SRU uploader, it is always a pleasure to sponsor a patch from Dan, and I think he would be a great addition to the SRU uploader launchpad team. === Specific Experiences of working together === Dan is a colleague and I work with him for the past 2 years now. Dan's role is to drive bugs into resolution by troubleshooting, fixing bugs, providing guidance & workarounds, for different areas of expertise which may cover areas such as: kernel, drivers, virtualization, network, cloud, storage setups, ... and physical/virtual environment orchestration. === Areas of Improvement === Nothing I can think of... -- [[LaunchpadHome:slashd]] <<DateTime>> == Martin Pitt == I only sponsored one SRU ([[https://launchpad.net/bugs/1609898|isc-dhcp]]) for Dan, which was relatively simple: backporting a patch from Debian to a native package (so no patch system involved). He handled all the SRU description, documentation, changelog, policy, following up to questions, etc. correctly, and all went well with this SRU. However, this is a sample size of one, so I abstain from a recommendation and just add it as a data point. -- [[LaunchpadHome:pitti]] <<DateTime(2017-09-08T17:53:07+0200)>> == Nishanth Aravamudan == === General feedback === I sponsored two packages for Dan. I found an issue with them (no bug closure), but Dan was responsive on IRC to amending the uploads (I ended up doing it as part of the sponsorship). In my non-sponsorship interaction with Dan, he has always been prompt and willing to adjust to recommendations. === Specific Experiences of working together === While not strictly relevant to this membership, I also have worked with Dan in the past at a prior company and had an excellent working relationship with him. Similar to Martin, my sample size is small, so I think I need to abstain from a recommendation. -- [[LaunchpadHome:nacc]] <<DateTime>> |
|
| Line 65: | Line 149: |
| ## Full list of sponsored packages can be generated here: ## http://ubuntu-dev.alioth.debian.org/cgi-bin/ubuntu-sponsorships.cgi? |
|
| Line 66: | Line 152: |
I, Dan Streetman, apply for SRU Developer.
Name |
Dan Streetman |
Launchpad Page |
|
Wiki Page |
Who I am
I started with UNIX is 1993, using Solaris, and then moved to Linux in 1997 using Slackware, Red Hat, and now Ubuntu. I began Linux kernel development in 2001, in the USB subsystem, and have contributed since then in various kernel subsystems including memory management, networking, and crypto.
My Ubuntu story
I joined Canonical in 2015 as part of the Support and Technical Services Engineering team, and have been working on problems that reach into many different parts of Ubuntu; the kernel, networking, multipath, udev, and more. I enjoy digging deep into technical details and solving problems.
My involvement
Examples of my work / Things I'm proud of
My sponsored uploads:
Ubuntu Kernel bug fix contributions not shown in above sponsored uploads:
- attached block devices not showing up
- using ipsec, many connections result in no buffer space error
- Soft lockup with "block nbdX: Attempted send on closed socket" spam
- kswapd0 100% CPU usage
- lots of printk to serial console can hang system for long time
- bonded interfaces in bridge do not have LRO turned off
- nvme drive probe failure
- move nvme driver to linux-image
- NVMe drives in Amazon AWS instance fail to initialize
- export nvme drive model/serial strings via sysfs
- NVMe driver regression for non-smp/1-cpu systems
- Xen MSI setup code incorrectly re-uses cached pirq
- VLAN SR-IOV regression for IXGBE driver
- Amazon I3 Instance Buffer I/O error on dev nvme0n1
Areas of work
Most of my work is done in the kernel, both upstream and in Ubuntu's branches. However, I also make fixes to various packages as I, or Canonical customers or public Ubuntu users, find bugs in them that I am in a position to fix.
Things I could do better
Time management is difficult for everyone, as we never have enough time to complete everything we want to do. I hope to manage my time better, balancing work and family while also continuing to contribute upstream.
Plans for the future
Keep improving Ubuntu and Linux in general!
What I like least in Ubuntu
Documentation is sometimes hard to come by, or out of date.
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@.
I have had the privilege of working with Dan for the past year and I know him as a knowledgable, thorough and steady colleague. He has made many contributions to Ubuntu and it would be a great win for all of us to have Dan approved as a SRU Developer. -- fnordahl 2017-09-06 15:56:08
Dan has the follow through, positive attitude and drive to get things upstream that is essential for any SRU. Been working with him as part of my role in Support. Definite +1. -- bryanquigley 2017-09-07 16:07:21
Dan has helped me with a number of bugs, and I've followed his work on several of the NVME bugs listed above. I'm always impressed with his commitment to the quality of his work. This is a logical next step, and a good thing for the community. -- markthomas 2017-09-07 17:44:24
I had various opportunities to see Dan's work on SRUs and I remember them to be of sufficient high quality, demonstrating more than enough knowledge of the SRU process. -- sil2100 2017-10-23 15:06:08
Endorsements
As a sponsor, just copy the template below, fill it out and add it to this section.
Eric Desrochers
General feedback
I have sponsored a few packages from Dan over the year and the ones I have seen were high quality. Dan has the desire to do things right and he always accept constructive comments/feedbacks with a positive attitude.
He understands the principles of debian packaging and the SRU process and he is not afraid to ask questions when needed. As a SRU uploader, it is always a pleasure to sponsor a patch from Dan, and I think he would be a great addition to the SRU uploader launchpad team.
Specific Experiences of working together
Dan is a colleague and I work with him for the past 2 years now. Dan's role is to drive bugs into resolution by troubleshooting, fixing bugs, providing guidance & workarounds, for different areas of expertise which may cover areas such as: kernel, drivers, virtualization, network, cloud, storage setups, ... and physical/virtual environment orchestration.
Areas of Improvement
Nothing I can think of...
-- slashd 2025-10-08 12:26:21
Martin Pitt
I only sponsored one SRU (isc-dhcp) for Dan, which was relatively simple: backporting a patch from Debian to a native package (so no patch system involved). He handled all the SRU description, documentation, changelog, policy, following up to questions, etc. correctly, and all went well with this SRU.
However, this is a sample size of one, so I abstain from a recommendation and just add it as a data point.
-- pitti 2017-09-08 15:53:07
Nishanth Aravamudan
General feedback
I sponsored two packages for Dan. I found an issue with them (no bug closure), but Dan was responsive on IRC to amending the uploads (I ended up doing it as part of the sponsorship). In my non-sponsorship interaction with Dan, he has always been prompt and willing to adjust to recommendations.
Specific Experiences of working together
While not strictly relevant to this membership, I also have worked with Dan in the past at a prior company and had an excellent working relationship with him.
Similar to Martin, my sample size is small, so I think I need to abstain from a recommendation.
-- nacc 2025-10-08 12:26:21
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.'' ## Full list of sponsored packages can be generated here: ## http://ubuntu-dev.alioth.debian.org/cgi-bin/ubuntu-sponsorships.cgi? === Areas of Improvement ===
ddstreet/UbuntuSRUDeveloperApplication (last edited 2017-10-23 15:07:25 by sil2100)