Differences between revisions 12 and 13
Revision 12 as of 2009-04-21 07:26:03
Size: 5312
Editor: i59F774C1
Revision 13 as of 2009-05-06 03:36:25
Size: 5460
Editor: cpe-72-229-211-120
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
|| '''Debian QA Page''' || ||
Line 22: Line 23:
Well, I suppose I'd be most proud of the three packages that I maintain directly in Debian:
Well, I suppose I'd be most proud of the three packages that I maintain directly in Debian: [[ | parcellite]], [[ | file-browser-applet]], and [[ | ttf-rufscript]].

I, Andrew Starr-Bochicchio, apply for MOTU.

Who I am

Tell us a bit about yourself.

My Ubuntu story

My involvement

Examples of my work / Things I'm proud of

Well, I suppose I'd be most proud of the three packages that I maintain directly in Debian: parcellite, file-browser-applet, and ttf-rufscript.

In my upload of evolution 2.25.91 I split out the documentation into separate locales. It's probably one of my most complicated uploads:

I've also done a number of security and SRU uploads, showing that I have a good understanding of Ubuntu processes.

Areas of work

Most of my work probably falls into the category of low hanging fruit. In my work triaging bugs I often come across things with simple fixes that just haven't seen any attention from a developer. While not the hardest work technically speaking, I think it is very important. If for no other reason, users are very often frustrated by such bugs. Especially in cases where someone has taken the time to file a bug and even find a solution, but just doesn't understand Ubuntu processes (i.e. turn their work around into a patch, create a debdiff, or even just know what team needs to be subscribed). So in general, I'm interested in getting Universe into a better state. Something which I suppose must be a good quality in a MOTU.

As a GNOME user, I'm of course interested in the Ubuntu desktop, and have done some work in main with the desktop team. (See the "What I like least in Ubuntu" for some difficulties I've had here.)

One package I've worked on quite a bit during Jaunty was deluge (and the related libtorrent-rasterbar and qbittorent packages). Doing so I have built a working relationship with the Debian maintainer. I was able to turn our out-dated version into a sync until the python 2.6 transition which I handled (patch submitted to Debian). I've handled the merges since that point. I'm glad to say that Jaunty will ship with the most resent version.

More recently, I've been getting involved with the artwork team. I'm not an artist, but I am generally interested in having beautiful GNOME desktop choices for our users. I noticed that one of the things that the artwork team lacks are people familiar with packaging and Ubuntu processes in general. I've worked on both the gnome-themes-ubuntu and community-themes packages. Becoming a MOTU will be helpful with this work (the community-themes package in particular) as there aren't any MOTUs active in the team. I'm also preparing GNOME-Colors and Shiki-Colors packages for Debian with the goal of having them synced into Karmic.

Things I could do better

Plans for the future


As a contributor, I've benefited greatly from the activity of the Universe Sponsors. With 50+ uploads during the Jaunty cycle, I feel that I owe the Sponsors team a lot of work if I become a MOTU. This fits well with my general goals of helping new contributors learn Ubuntu processes and helping to pick off some of the low hanging fruit.

What I like least in Ubuntu

One issue I face constantly is the problem of IRC. While I appreciate its usefulness and the importance of real time communication, I'm not capable of idling in IRC channels all day. I feel that in some ways it is very hard to connect with the Ubuntu developer community if you are not very active in IRC. For instance, I feel that I could be much more useful for the desktop-team than I have been, but assignments are mostly dealt with through the IRC channel.


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.


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


Andrewsomething/MOTUApplication (last edited 2009-05-14 21:10:51 by 94-169-116-60)