I, Chris Peterson, apply for core-dev
DRAFT
Name |
Chris Peterson |
Launchpad Page |
|
Wiki Page |
|
IRC |
cpete |
I am applying because:
- I'd like to eliminate delays in getting my work sponsored.
- I'd like to reduce the burden on my sponsors.
- I'd like to be more involved in the community (sponsoring, patch pilot, etc.)
- My work may require touching various packages, including those in main, for which there is no distinct package-set goal and PPU/MOTU won't cover packages in main.
- It will facilitate my general distro related work (+1 maintenance, proposed-migrations, etc.)
Who I am
Hi, my name is Chris Peterson and I am a software engineer on Canonical's Foundations team.
Prior to joining Canonical, I received my Master's in Computer Science from the University of California, Davis, where I researched semantic parsing in the areas Natural Language Processing and Computational Linguistics. Before that, I received my Bachelor's in Computer Science & Engineering from the University of Nevada, Reno, where I performed research in a Social Robotics laboratory.
I live in California, United States, and when I'm not writing software I enjoy building keyboards, playing the bass guitar, or playing video games.
My Ubuntu story
Back in my first year of college when I started to learn programming and what Linux was all about, I started with Ubuntu (Trusty). For a short time I bounced around different distributions, though mostly Ubuntu based, and eventually came back to Ubuntu after working in a robotics lab which relied on it for its software (ROS). Since then it's been my daily driver for everything I do. I am passionate about open source and working on Ubuntu everyday brings me great joy.
Tell us how and when you got involved, what you liked working on and what you could probably do better.
An exhaustive search of my Sponsored Uploads https://bugs.launchpad.net/ubuntu/+source/python-aiohttp/+bug/2048808 A sort of pseudo-MIR, where I performed a comprehensive analysis of python-aiohttp, a dependency of Subiquity, and determined it's not a good candidate for MIR but still merits some serious security review. I received positive remarks for this MIR by Seth Arnold on the security team, which felt nice considering it was my first MIR https://bugs.launchpad.net/ubuntu/+source/libsub-prototype-perl/+bug/2067654 Update the wiki on Mirrors to explicitly list how to find existing mirror information: https://wiki.ubuntu.com/Mirrors?action=info Improved error handling and UX in Subiquity to inform users about avoidable errors caused by faulty autoinstall configurations. I re-wrote the autoinstall validation script and made it user facing so users can prevalidate their autoinstall configurations.
As part of Canonical's Foundations Team I spend a majority of my time working on installer related things, primarily Subiquity. While this often includes work in other projects which are also not conventionally packaged, such as Curtin or Probert, it may also include work in archive packages such as livecd-rootfs, Casper, or ubuntu-meta. I expect core dev privileges will most facilitate my work by removing the need for sponsorship to make changes to these packages. However, given my experience is still limited with some of these core archive packages, I certainly still expect to ask for review before making changes I'm not 100% certain about. I also spend time working on Apport, fixing bugs and working to improve bug reporting in the installers. In particular, over the last two release cycles I have been collaborating within Foundations and across Desktop and Server to improve the Apport bug reporting process in general among the various installer related tools. As part of my more general packaging related responsibilities on the Foundations team, I also participate in regular +1 maintenance and proposed-migration work.
Ubuntu development process documentation is very disjoint, which makes things difficult for newcomers. Best practices are not always clear and may also depend on who you ask. Continued work on centralized documentation, like the ubuntu-packaging-guide, is sorely needed.
My involvement
Examples of my work / Things I'm proud of
Areas of work
Things I could do better
Plans for the future
General
What I like least in Ubuntu
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.''
## Full list of sponsored packages can be generated here:
## https://udd.debian.org/cgi-bin/ubuntu-sponsorships.cgi
=== Areas of Improvement ===