upstream patch issues
|Deletions are marked like this.||Additions are marked like this.|
|Line 82:||Line 82:|
|Ubuntu developers seem to have a hard time pushing patches upstream (either to Debian or the upstream developers). Yes, syncing and merging takes a lot longer when you do this, but it's the right thing to do and should save time in the long run. I intend to (and have begun) improve on this.
I, Stefano Rivera, apply for MOTU.
Home Page / Blog
Who I am
My main interests are in Python (I'm a core developer of ibid, a Python IRC bot), multimedia (I run a small online video service using FOSS), and general sysadmin on Debian (Amongst other things, I run a South African mirror).
I'm not an Ubuntu member, so this doubles as a membership application.
My Ubuntu story
Long version. Short Version:
I'm a long-time Debian user and sysadmin (since Woody), after starting on Linux with RedHat in the late 90s. Since Breezy, I've used Ubuntu on my laptops and been a tester and bug reporter (but not a developer).
Although I always intended to, I only got involved in Debian and Ubuntu development to get ibid into Debian & Ubuntu, early in 2010. Once I knew the procedures, I started applying them to other problems I came across in Ubuntu and have been doing some universe merging.
I keep an eye on them in Ubuntu, too. With some backports for older releases here and sync requests where necessary.
I've been involved in the organisation of a few Ubuntu-ZA events, including:
- The Karmic release party (primary organiser)
- Ubuntu Global Jam March 2010 (primary organiser and only demonstrator)
- Lucid release party (sysadmin)
I followed UDS-M remotely, participating in a few sessions via IRC, but mostly just sitting in for general interest where I didn't have any constructive input.
Examples of my work / Things I'm proud of
I try to be proud of everything I've done (although generally I'm not as happy as I should be)
(probably missing some)
I've done Debian QA work on: configobj.
Areas of work
I had some difficulty in syncing Ibid and its prerequisites in time for Lucid, but it was ACKed in the final weeks by BenjaminDrung.
Things I could do better
I could be more involved in debian-python, but choose to spend my free time on upstream work where possible.
Plans for the future
Get more involved in MOTU work and become a DD.
What I like least in Ubuntu
Ubuntu developers seem to have a hard time pushing patches upstream (either to Debian or the upstream developers). Yes, syncing and merging takes a lot longer when you do this, but it's the right thing to do and should save time in the long run. I intend to (and have begun) improve on this.
That Ubuntu has never worked flawlessly, out of the box, on my laptops (until I replace them, at which point Ubuntu supports the old one perfectly). But this is a good thing, because it keeps me running development releases
I've attempted in the past to get Ubuntu to not require access to changelogs.ubuntu.com for online upgrades, LP Spec, but haven't made significant progress yet. This affects all the users at my University, as we are behind a firewall & NTLM proxy (with an Ubuntu mirror on our side).
I've known Stefano for 7 years now via our local LUG and also Ubuntu-ZA. Stefano is extremely thorough and trustworthy. He's technically competent and very responsible. Stefano has wide interests and supports many users at the University of Cape Town. I believe that having MOTU rights would enable him to contribute bug fixes back into Ubuntu much better.
As a sponsor, just copy the template below, fill it out and add it to this section.
FYI: I sponsor 6 Stefano's Python related packages in Debian and they're in good shape.
I ACK'd 3 sync requests of Stefano's during the lucid cycle. The sync requests where for packages that had just recently been uploaded to Debian. Thanks to the debian-python team (Piotr aka POX) the packages where in very good shape. The packages built, installed, purged and functioned as expected. I would trust Stefano to take care of the above mentioned packages.
== <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 ===