ContributingDeveloperApplication
Size: 5636
Comment:
|
← Revision 39 as of 2016-03-07 15:36:45 ⇥
Size: 6593
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)>>|| | ## 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 3: | Line 4: |
'''I, Eric Desrochers, apply for Contributing Developer.''' | |
Line 4: | Line 6: |
---- '''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. ---- '''I, <YOUR NAME>, apply for <universe-contributor|MOTU|core-dev|upload rights for package(s) <X>>.''' || '''Name''' || <YOUR NAME> || || '''Launchpad Page''' || <link to your launchpad page> || || '''Wiki Page''' || <link to your Wiki page> || |
|| '''Name''' || Eric Desrochers || || '''Launchpad Page''' || https://launchpad.net/~slashd || || '''Wiki Page''' || https://wiki.ubuntu.com/slashd || |
Line 20: | Line 11: |
''Tell us a bit about yourself.'' | I joined Canonical in August 2014 as a Technical Account Manager within Canonical's STS team. As a result of hard work and effort, I earned respect from my peers. Since then, along with the Canonical Technical Services Engineering team, some of my responsibilities are fixing userland/kernel bugs filed by Ubuntu Advantage customers, providing hotfix, backporting, making them (patch/fix/backport) available in stable through the SRU process, collaborating with upstream developers, ... |
Line 23: | Line 14: |
''Tell us how and when you got involved, what you liked working on and what you could probably do better.'' | I officially started to used Ubuntu in 2006 for my personal computers. In the same time, in my professional life, I was also deploying a few hundreds OpenVZ (Virtuozzo) containers running Ubuntu 6.06 LTS (Dapper Drake). Ten years later, I am still running Ubuntu on my personal computers and now have the chance to work for Canonical, the company behind Ubuntu, as a Technical Account Manager fixing userspace and kernel bugs. |
Line 27: | Line 20: |
* crash starting at kernel v3.13.0-72 in timer code https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546320 * read() from pty doesn't finish https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512815 * libpam-sshauth dropped support for publickey authentication https://bugs.launchpad.net/ubuntu/trusty/+source/libpam-sshauth/+bug/1507798 * ambiguous error message "sh: echo: I/O error https://bugs.launchpad.net/ubuntu/+source/ifenslave/+bug/1326854 * NTP : Use-after-free in routing socket code after dropping root: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388 * ntpd rejects source UDP ports less than 123 as bogus https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1479652 * Targets are not consistently shown with large numbers of targets: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697 * sosreport does not collect logs for Landscape Dedicated Server 15.01 and newer: https://bugs.launchpad.net/ubuntu/trusty/+source/sosreport/+bug/1449131 * openipmi package compile without SSL https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1546735 |
|
Line 28: | Line 56: |
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. 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. |
I've been mostly involved in fixing userland and kernel bugs for Canonical's UA customers. Working on various packaging aspects including hotfix/testfix, SRUs, backports, patches, debian patch, ... I worked with the sustaining engineering team at Canonical. |
Line 41: | Line 59: |
Build and consistently sustain my network by attending more local networking events in my area. | |
Line 44: | Line 62: |
I wish one day I can become a core developper and I also hope to have the chance to give back by mentoring someone the same way I've been mentored. | |
Line 45: | Line 64: |
''Please describe what you like least in Ubuntu and what thoughts do you have about fixing it.'' | In general, documentation is good but unfortunately not maintained nor updated, which have the effect to turn out-to-date very quickly. |
Line 54: | Line 73: |
== Robie Basak == | |
Line 55: | Line 75: |
=== General feedback === I'm happy to endorse Eric's application for Contributing Developer. Our interactions are not extensive, but I appreciate that he has worked on small pieces with various Ubuntu developers, so I'm providing this endorsement so that the DMB can more effectively consider his contributions in aggregate. I've worked with Eric on one bug. He is courteous and communicates well. ## 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 === ## Full list of sponsored packages can be generated here: ## http://ubuntu-dev.alioth.debian.org/cgi-bin/ubuntu-sponsorships.cgi? We worked on [[https://launchpad.net/bugs/1479652|bug 1479652]] together. I sponsored three debdiffs for the SRUs. Eric was aware of SRU policy and process, handled the SRU paperwork and coordinated with me for the "Fixed in development release" SRU requirement. His debdiffs were good, and functionally perfect. There were only some minor DEP-3 additions I wanted. === Areas of Improvement === Please try to communicate in public channels wherever possible. This helps with coordination and in training others. I appreciate it is trickier to do this effectively when dealing with Canonical customers (whose identity may need to remain private), but most discussion could still happen in #ubuntu-devel or #ubuntu-server on Freenode. == Chris J Arges == === General Feedback / Specific Experiences of Working Together === I've worked with Eric on [[https://launchpad.net/bugs/1498697|bug 1498697]]. I sponsored debdiffs for all stable series. Eric showed an understanding of the SRU process and attention to detail. I think he'd make a good contributing developer. === Areas of Improvement === I'd like to see more uploads as well as more discussion in public channels. I think this will happen as Eric fixes more things in Ubuntu. -- [[LaunchpadHome:arges]] <<DateTime(2016-03-07T15:36:45Z)>> |
|
Line 65: | Line 115: |
## Full list of sponsored packages can be generated here: ## http://ubuntu-dev.alioth.debian.org/cgi-bin/ubuntu-sponsorships.cgi? |
I, Eric Desrochers, apply for Contributing Developer.
Name |
Eric Desrochers |
Launchpad Page |
|
Wiki Page |
Who I am
I joined Canonical in August 2014 as a Technical Account Manager within Canonical's STS team. As a result of hard work and effort, I earned respect from my peers. Since then, along with the Canonical Technical Services Engineering team, some of my responsibilities are fixing userland/kernel bugs filed by Ubuntu Advantage customers, providing hotfix, backporting, making them (patch/fix/backport) available in stable through the SRU process, collaborating with upstream developers, ...
My Ubuntu story
I officially started to used Ubuntu in 2006 for my personal computers. In the same time, in my professional life, I was also deploying a few hundreds OpenVZ (Virtuozzo) containers running Ubuntu 6.06 LTS (Dapper Drake).
Ten years later, I am still running Ubuntu on my personal computers and now have the chance to work for Canonical, the company behind Ubuntu, as a Technical Account Manager fixing userspace and kernel bugs.
My involvement
Examples of my work / Things I'm proud of
* crash starting at kernel v3.13.0-72 in timer code
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546320
* read() from pty doesn't finish
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512815
* libpam-sshauth dropped support for publickey authentication
https://bugs.launchpad.net/ubuntu/trusty/+source/libpam-sshauth/+bug/1507798
* ambiguous error message "sh: echo: I/O error
https://bugs.launchpad.net/ubuntu/+source/ifenslave/+bug/1326854
* NTP : Use-after-free in routing socket code after dropping root:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388
* ntpd rejects source UDP ports less than 123 as bogus
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1479652
* Targets are not consistently shown with large numbers of targets:
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697
* sosreport does not collect logs for Landscape Dedicated Server 15.01 and newer:
https://bugs.launchpad.net/ubuntu/trusty/+source/sosreport/+bug/1449131
* openipmi package compile without SSL
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1546735
Areas of work
I've been mostly involved in fixing userland and kernel bugs for Canonical's UA customers. Working on various packaging aspects including hotfix/testfix, SRUs, backports, patches, debian patch, ... I worked with the sustaining engineering team at Canonical.
Things I could do better
Build and consistently sustain my network by attending more local networking events in my area.
Plans for the future
General
I wish one day I can become a core developper and I also hope to have the chance to give back by mentoring someone the same way I've been mentored.
What I like least in Ubuntu
In general, documentation is good but unfortunately not maintained nor updated, which have the effect to turn out-to-date very quickly.
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.
Robie Basak
General feedback
I'm happy to endorse Eric's application for Contributing Developer. Our interactions are not extensive, but I appreciate that he has worked on small pieces with various Ubuntu developers, so I'm providing this endorsement so that the DMB can more effectively consider his contributions in aggregate.
I've worked with Eric on one bug. He is courteous and communicates well.
Specific Experiences of working together
We worked on bug 1479652 together. I sponsored three debdiffs for the SRUs. Eric was aware of SRU policy and process, handled the SRU paperwork and coordinated with me for the "Fixed in development release" SRU requirement. His debdiffs were good, and functionally perfect. There were only some minor DEP-3 additions I wanted.
Areas of Improvement
Please try to communicate in public channels wherever possible. This helps with coordination and in training others. I appreciate it is trickier to do this effectively when dealing with Canonical customers (whose identity may need to remain private), but most discussion could still happen in #ubuntu-devel or #ubuntu-server on Freenode.
Chris J Arges
General Feedback / Specific Experiences of Working Together
I've worked with Eric on bug 1498697. I sponsored debdiffs for all stable series. Eric showed an understanding of the SRU process and attention to detail. I think he'd make a good contributing developer.
Areas of Improvement
I'd like to see more uploads as well as more discussion in public channels. I think this will happen as Eric fixes more things in Ubuntu.
-- arges 2016-03-07 15:36:45
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 ===
slashd/ContributingDeveloperApplication (last edited 2016-03-07 15:36:45 by localhost)