I, Barry Warsaw, apply for upload rights for package(s):
I have already been granted upload permission to these packages:
- Computer Janitor
- gtimelog (GTimelog Time Tracker)
- python-flufl.enum (renamed from munepy)
Who I am
I have been developing software professionally since the early 1980's. I did a lot of Emacs development in a previous life, and since 1995 I have been a core Python developer, including serving as release manager for Python 2.6, 3.0 and a few earlier versions. I was once lead maintainer for Jython. Since about 1998, I have been the project leader for GNU Mailman. I have been involved in free software and open source for a long time. I currently work for Canonical on the Ubuntu Platform Foundations team, and before that on the Launchpad team.
My Ubuntu story
I've been an Ubuntu user for the last 4 years or so, and have been working for Canonical since January 2007. I've been a Linux user since the late 90's and a Unix user since the mid-80's. I run Ubuntu servers for my own domains, and have several Ubuntu machines running on various flavors of laptops, desktops, and VMs. I originally begin using Ubuntu when I got tired of Gentoo for my primary Linux desktops (I'd previously switched to Gentoo around the RedHat 9 days). I've helped friends break the chains of proprietary operating systems by installing Ubuntu for them, and I am a member of the Washington DC LoCo.
I'm keenly interested a wide array of issues relating to Python on Ubuntu. While I'm comfortable in C, C++, Java and other languages, Python is my first and favorite choice. As a long-time core Python developer and new member of the Foundations team, I'm especially focused these days on bridging the gap between upstream Python and its deployment on Ubuntu and Debian. I write lots of Python packages, and am very comfortable fixing bugs and helping to sync many other Python packages, as seen by the list above.
Areas of work
I am of course very interested in having upload rights to packages for which I am also the upstream maintainer. Not all of my packages are in Ubuntu (or Debian for that matter), but I am working on that. I contribute to lots of projects upstream and now I'd like to translate that into helping to provide improvements to those same packages in Ubuntu. The list above is a start.
Some concrete examples:
- I fixed bugs and performed sync's for python-argparse, python-virtualenv, and python-lazr.restfulclient so that they would be usable on Ubuntu.
- I refactored Computer Janitor to use a dbus backend, thus allowing the front-end to be rewritten for single-threadedness and eliminating many long outstanding crashes and freezes. Unfortunately, this didn't make it into Lucid in time, but it will be in Maverick.
Things I could do better
I want to improve my understanding of how Debian and Ubuntu are related, get more of my packages into Debian and sync them to Ubuntu, and better understand some of the trickier details of packaging (e.g. python-central and python-support).
Plans for the future
Of course, as part of my job in Foundations, I will be working on many aspects of Ubuntu. Computer Janitor, Update Manager, and Software Center are immediate interests. I want to improve several aspects of Python deployment on Ubuntu. An example here is my implementation of PEP 3147 to allow multiple versions of Python to coexist on the same system. Along those lines, I will be working on PEP 382 for namespace packages and PEP 384 for an ABI, all of which have direct impact on the quality of Python's live on Ubuntu. I will not just be an upstream developer here; I will be contributing to the deployment of these features on Ubuntu.
What I like least in Ubuntu
Sorry, but there seems to be a lot of bureaucracy! For a newcomer, it seems like it's difficult to navigate through this to find the places where you want to participate. I will have some conversations at UDS-M about this!
Technologically, Ubuntu is fantastic, and there's very little I don't like. Well, maybe the fact that Claws isn't as well supported email client as it should be.
If you'd like to comment, but are not the applicant or a sponsor, do it here. Don't forget to sign with @SIG@.
As a sponsor, just copy the template below, fill it out and add it to this section.
I worked with Barry during the lucid cycle. His work is high quality even though he is relatively new to packaging.
Specific Experiences of working together
My specific example is computer-janitor. We worked on a big refactor that moved the backend code into a dbus daemon. Both the code and the packaging changes where well done.
Socially Barry is great to work with and clearly very committed to improving the Ubuntu -Debian Python community relationship (which definitely can use the help). I have only reviewed one or two packages of Barry's (including a distribute merge), but they were good. Barry is deeply pythonic and learning Debian/Ubuntu packaging rapidly. I definitely trust him to upload or ask questions if he is unsure.
Specific Experiences of working together
We have collaborated a lot on planning for Python in Maverick and how to better work with Debian. Barry was also a very valuable contributor to Python policy updates in Debian and moving the Debian/Ubuntu Python stack forward. PEP 3147 will be huge for this. I have always found him very collaborative and willing to try and see both sides of a discussion.
Areas of Improvement
Barry still has some things to learn about Debian packaging, but he is learning them. Within Python packages though, I trust his knowledge is more than adequate for what he is requesting.
== <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 ===