CoreDevApplication

I, Evan Broder, apply for Ubuntu Core Developer.

Name

Evan Broder

Launchpad Page

http://launchpad.net/~broder

Who I am

I'm Evan Broder. I'm a computer systems nerd, especially when it comes to operating systems and virtualization. I like to build things - mostly in software, though occasionally in hardware - and glue software together in new and interesting ways.

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 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 - even now, 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

Some numbers - since joining MOTU:

  • I've had 27 uploads sponsored - 23 in core[*], 1 in desktop-core and ubuntu-server, 1 in ubuntu-server, 2 in ubuntu-desktop
  • I've done 61 direct non-backports uploads
  • I've sponsored 45 uploads in universe
  • I've reviewed and approved 43 backport requests

[*] Or would have been in core, had they not pre-dated packagesets.

SRUs

  • plymouth: lucid and maverick SRUs - suppress a harmless warning message that was often conflated with other more serious issues

  • update-inetd: lucid and maverick SRUs - correct an install-time hang due to interactions between debconf and inetd (backported fix)

  • initramfs-tools: maverick and natty SRUs - allow booting off of USB 3.0 drives (backported fix)

Backports

  • backportpackage - A script for automatically generating test backports and test building them

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

  • New 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], [6], [7])

NetworkManager

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

Transitions

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

Debian

I currently maintain a package in Debian (reptyr)

bzr Merge Proposals

Here are a handful of merge proposals that went directly into Ubuntu but where, for whatever reason, mine wasn't the name closing out the changelog so they're not listed on my list of uploaded packages:

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 also tend to spend time on packages which are relevant for work - generally early boot and 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.

I've also been a little concerned lately that I'm spreading myself thin. I don't think I generally fail to meet my commitments, but I worry some about falling down on implied responsibility because I spend a lot of time darting around between different things.

Plans for the future

I'm expecting to spend time this cycle working on implementing the new pre-release backports plan, which will require making changes to things like Launchpad, ubuntu-archive-tools, ubuntu-dev-tools, and probably others.

I also want to continue improving lintian.ubuntuwire.org to make it a more useful resource for Ubuntu developers. In particular, I think there's currently a lot of noise because we show tags which are in some sense Debian's "fault" and not ours, and I think it's important that lintian.uw.o have a view of tags only emitted in Ubuntu and not in Debian so that we can see where our changes and Ubuntu-specific packages are falling short against Policy.

I'm also hoping to spend time helping with sponsorship and patch piloting.

What I like least in Ubuntu

My focus is primarily on the developer side of things, so that's where I notice problems. My biggest concern is around managing to grow the developer community. Most of the new developers coming into our community (especially the MOTU community) are focused on syncs, merges, FTBFS fixes, and other sorts of archive gardening tasks. While this sort of packaging-focused development is clearly critical for the vitality of the archive, I think it's equally important to encourage developers who are less interested in the packaging arcana, because I think that's a much larger group of potential talent.

I think the distro community should be better equipped than it is now to help people who want to improve the software itself. This is especially important for people who are more interested in "hit-and-run" development and less interested in a single piece of (or small collection of) software.

I think there are cases where we should provide more support than just passing developers off to upstream, though I'm not sure what. Better documentation and better awareness of the documentation that we have is likely a big part of it. I think that doing a better job of timely patch review could help. Doubling down and expanding on the bitesize initiative might be good, too.


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've sponsored all Evan's Debian uploads (4), and he did a great job with them. I've also worked with him a fair amount in MOTU. Evan is great to work with, as he's very responsive and gets things done. I'd like to see him be a core-dev. -- stefanor 2011-12-12 13:25:36

  • I have not sponsored any non-backports uploads for Evan since he became a MOTU, but those have all been well done and I've regularly seen him in action on IRC, mailing lists, and at UDS. Socially and technically I think we would be an asset to the project as a core-dev. ScottKitterman


Endorsements

As a sponsor, just copy the template below, fill it out and add it to this section.

Barry Warsaw

General feedback

I sponsored one of Evan's uploads during the dh_python2 transition, and he did a great job on it. While I haven't sponsored any other packages, I've been watching Evan's perhaps less obvious contributions to Ubuntu on the mailing lists and irc, and there's no question he's knowledgeable and helpful, with exactly the right spirit of Ubuntu, backed by a very good technical understanding. He's conscientious and collaborative and I have no doubt that he'll ask questions when he's unsure of things, and will take the utmost care to ensure Ubuntu is solid and stable. I think he would be a great addition and so I endorse his core-dev application.


Martin Pitt

General feedback

Evan has been around in the community and IRC channels for years now. He has a profound technical knowledge, always helpful and friendly on IRC, and I trust him to ask when he encounters an unknown situation. I sponsored some 6 main packages for him, they were all in good shape and could be uploaded without further change. I support his core-dev application.

Specific Experiences of working together

Sponsored:

-- pitti 2011-12-19 08:07:55

Daniel Holbach (dholbach)

General feedback

Evan consistently does great work. I support his Core Dev application.

Specific Experiences of working together

Stéphane Graber (stgraber)

I've had the chance to work with Evan a few times both online and at the few last UDSes, I think he'll be a great core dev and fully support his application.

Specific Experiences of working together

The only package I reviewed from Evan was initramfs-tools as an SRU for 3 different releases and was ready for upload without any change. Having talked with each other quite a bit at the few last UDSes made it clear that he knows quite a bit about the inner working of a Linux distribution and Ubuntu specifically, he'd be a great addition to the team.

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

EvanBroder/CoreDevApplication (last edited 2012-01-02 18:56:27 by stgraber)