I, Leann Ogasawara, apply for upload rights for package(s) linux and friends (see detailed list below)>.

Who I am

Hi, I'm Leann Ogasawara. I'm a member of the Ubuntu Kernel Team and employed by Canonical. I originally started as the Ubuntu Kernel Team's QA/Triage Engineer but have since transitioned into a full Kernel Dev position. I've since been focused on helping with the stable kernel maintenance which includes processing CVE's, reviewing and applying upstream stable patch sets, and bug triaging/fixing.

My Ubuntu story

I got my first taste of Linux while attending college back in the early 2000's where our CS lab ran with Red Hat installations. As a recent college graduate, I was fortunate enough to land a job at the Open Source Development Lab where I began focusing on the kernel. I started with the usual kernel janitor work and also kernel QA. While at OSDL I began hearing about this new distribution called Ubuntu. I installed Dapper and have been a faithful Ubuntu user ever since. I was amazed at it's ease of use and that everything "just worked". In 2007 I was lucky enough to get the opportunity to come work for Canonical as a member of the Ubuntu QA Team and have since made a full transition to the Ubuntu Kernel Team.

My involvement

As noted above, my current involvement is with stable kernel maintenance. This involves the following:

• Applying and backporting patches for CVE's
• Building, testing, and packaging the security kernels
• Reviewing and applying upstream stable patch sets
• Bug triage and fixes - particularly focusing on regressions and SRU's

Going forward I'm going to be the Ubuntu kernel maintainer for Lucid+1 and have already started the prep work for the Ubuntu M kernel. This is the primary reason why I'm requesting kernel upload rights.

Examples of my work / Things I'm proud of

Kernel security updates for the Dapper, Hardy, Intrepid, Jaunty, and Karmic from October 2009 through end of January 2010 were a direct result of work I'd done. I found this work to be very fulfilling and dare I say fun. Also, due to my CVE work, I was granted full git commit privileges to all the Ubuntu kernel trees.

During the same time frame I was also heavily involved with reviewing stable patch sets from upstream and applying them to our Ubuntu Karmic kernel for SRU. All of these kernels have since moved through -proposed and into -updates.

Areas of work

• Kernel CVE's. I processed 4 rounds of Kernel CVE's from Oct 2009 through Jan 2010. The work included investigation of each CVE, finding appropriate fixes, and applying patches to Dapper, Hardy, Intrepid, Jaunty, Karmic, and Lucid where applicable. In addition to this, I was also responsible for performing build tests, boot tests, and qa regression tests for each security kernel. As a final step, I packaged each kernel and meta package to be handed off to the security team to do a final set of build tests, re-sign, and upload to the security pocket. I primarily worked with Stefan Bader (Ubuntu Kernel Team) and Kees Cook (Ubuntu Security Team). As of Feb 2010 we've been bringing another Kernel Team member up to speed on processing CVE's but I've continued to provide feedback for patch reviews as well as help testing.
• Upstream Stable Patch Sets. I reviewed and applied the upstream 2.6.31.6, 2.6.31.7, 2.6.31.8, and 2.6.31.9 stable patch sets. I also helped upload these packages to our pre-proposed kernel-ppa and had a few linux-ec2 uploads to -proposed sponsored by Stefan Bader. I've since continued to help review the 2.6.31.10, 2.6.31.11, and 2.6.31.12 upstream patch sets while another member of the team has applied them. I primarily worked with Stefan Bader (Ubuntu Kernel Team).
• As I begin ramping up for Lucid+1, ie M, I've done some misc work with other members of the Ubuntu kernel team. I worked with Tim Gardner to apply and package some fixes for our Freescale iMX51 package. Tim subsequently sponsored this upload for me. Also per Tim's request I sync'd the OEM Hardy LUM and LBM tarballs into our main Hardy git repo and Stefan handled the upload to the netbook-lpia pocket. I've also made Andy Whitcroft my new BFF for M's release cycle :). I fully expect to work more closely with him between the months leading up to M all the way through M's release. He's already got me started prepping ubuntu-m's git repo.

I'd also like to make a note here about our kernel bug situation. Having transitioned from the Kernel QA/Triage role to a Kernel Dev role I still consider bug triage a big area of work that I plan to stay involved in. I've witnessed first hand the insane volume of kernel bugs that get reported against the linux kernel package. I think we're taking a step in the right direction by staying up to date with the latest upstream stable patch sets as their primary purpose is to fix kernel bugs. I also believe the work we've started doing with the kernel arsenal scripts has allowed us to manage such a large volume of bugs in a somewhat automated fashion and a limited amount of resources.

Things I could do better

Upload Rights

I'm requesting upload rights for the following kernel packages:

linux
linux-ec2
linux-fsl-imx51
linux-mvl-dove
linux-ports
linux-qcm-msm
linux-ti-omap
linux-meta
linux-meta-ec2
linux-meta-fsl-imx51
linux-meta-mvl-dove
linux-ports-meta
linux-meta-qcm-msm
linux-meta-ti-omap
linux-restricted-modules
linux-backports-modules-2.6.24
linux-backports-modules-2.6.27
linux-backports-modules-2.6.28
linux-backports-modules-2.6.31
linux-backports-modules-2.6.32
linux-ubuntu-modules-2.6.24
linux-source-2.6.15
linux-restricted-modules-2.6.15
linux-restricted-modules-2.6.24
initramfs-tools
linux-firmware
linux-firmware-nonfree

Plans for the future

General

I'm really looking forward to being Lucid+1's, ie M's, Ubuntu kernel maintainer. Having already gotten a taste of the stable maintenance kernel tasks I'm excited to get more involved with the the current development/release oriented tasks and live on the bleeding edge

What I like least in Ubuntu

Please describe what you like least in Ubuntu and what thoughts do you have about fixing it.

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