I, Evan Broder, apply for Ubuntu Core Developer.

Who I am

I'm Evan Broder. I like anything that involves computer systems and OS, and have a tendency to enjoy playing with virtualization projects.

I graduated from college last year and started at a San Francisco-area startup. We're using virtualization to revolutionize how large enterprise IT departments manage their employees' workstations. I'm the lead developer on one of our products, an OS based on the core Ubuntu stack that runs our management software. I focus mostly on integrating our software with the underlying components in the OS.

My Ubuntu story

I don't remember when I started tried Ubuntu - I think it was around Breezy or so. But I've definitely used every version since Dapper, and about 6 months ago I finally saw the light and started using Ubuntu on my primary laptop. While I was at MIT I was a heavy contributor to the student computing organization and their VM hosting service and Debian- and Ubuntu-based distribution used on the public computer lab machines.

While at college, I began contributing to Ubuntu through backports and then moved on to fixing bugs that affected the SIPB projects I was involved in (primarily things like Xen, OpenAFS, and krb5 mixed with a little bit of everything).

Since graduating, I've been fortunate enough to attend the last three UDS's (UDS-N, -O, and -P). I found UDS to be incredibly motivating for me - I feel like I'm still riding the high from October. I really appreciated that it's possible for someone to show up and usefully contribute to the development process.

Examples of my work / Things I'm proud of

Backports

• backportpackage - I wrote a script for automatically generating test backports and test building them

• backport-helper (plus some follow-up patches - [1], [2], [3]) - A wrote a new tool for ubuntu-archive-tools that looks for and runs approved backport requests

• Docs for end-users and developers - I re-wrote the documentation to clarify the current backports procedures

• Pre-release backports - I wrote the proposal and advocated it to the TB, who approved it at their November 28th meeting

Lintian

I set-up http://lintian.ubuntuwire.org/ and have been working with Lintian upstream to fix some issues affecting Ubuntu ([1], [2], [3], [4], [5])

NetworkManager

I've developed a couple patchsets for NetworkManager while doing integration work with it:

• 4f38f02a, ca968105 0b8097a2 - fixing a long-standing limitation of 802.1x support

• 1e2984a5

• ef9551bc, 2c484fbc, dc92d125, b08e2b89, 9fc134ee - adding support for non-ASCII passwords in MS-CHAPv2-based 802.1x

Transitions

I've made some small contributions to various transition efforts:

• "perlsectomy" ([1], [2]) - an aborted attempt to drop the perl package (note: not perl-base) from our base install

• dh_python2 ([1], [2]) transition from dh_pysupport and dh_pycentral

• multiarch - I've developed, tested, and submitted multiarch patches for libsigc++-2.0, glibmm2.4, atkmm1.6, openssl098, and zephyr

Debian

I currently maintain a package in Debian (reptyr)

Areas of work

I've mostly given up on trying to qualify specific areas I work on - it tends to be a little bit of anything and everything.

I have a particular interest in backports and SRUs, because I like that they're one of our most direct ways we can improve Ubuntu for our users. I wrote up and advocated the new policy to allow backports uploads pre-release, which I hope will be a way for us to limit the pain our freeze process can cause for new contributors.

I also tend to spend time on packages which are relevant for work - generally low-level stuff like NetworkManager, initramfs-tools, or libgnome-desktop.

Things I could do better

I like to help with transition projects such as .la file cleanup, dh_python2, or multiarch, but I find that I tend to execute poorly at that sort of largely-but-not-totally repetitive packaging tasks. I've caught myself after the fact cutting corners. I think I need to be more deliberate working on those sorts of projects, or leave them to others.

Plans for the future

General

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

CategoryCoreDevApplication