I, Andreas Wenning, apply for MOTU.

Who I am

Who am I? First of all I am 23 years and from Denmark. I usually live in Glostrup, Denmark but I'm currently studying in Bangkok, Thailand. I have a bachelor in IT and Telecommunication with focus on networks (2008), and is currently studying to become for Master in Telecommunication.

Apart from my involvement with Kubuntu/Ubuntu I'm a hardcore scout, and loves spending time outdoor (hey, you need some counter-weight to all the time you spend in from of the computer).

My Ubuntu story

I actually switched to Kubuntu directly from Windows back when dapper was the new thing. After using it as a second workstation/server for some time, I ended up switching to use Kubuntu edgy as my primary operating system on all I have of hardware. I quickly started developing some interest in how it all worked behind the scene; upgrading to alpha/beta releases and reporting bugs.

My more serious involvement started in the beginning of 2007. Ubuntu was changing to apache2 only and all apache1 only modules needed to go away or get updated; I helped investigating possibilities, filing removal reports, sharing my investigations with Debian and taking maintainership in Debian for the modules to be kept without a maintainer. After that I started helping out some more with Kubuntu during the last part of the hardy cycle.

My involvement

Kubuntu Member since November 2008

Ubuntu-dk loco member since October 2008

Examples of my work / Things I'm proud of

Getting kde-guidance somewhat in shape for hardy: https://launchpad.net/ubuntu/+source/kde-guidance

My first security update, couldn't even remember that one: https://bugs.launchpad.net/ubuntu/+source/sdl-image1.2/+bug/185782

Helping to get kde3.5.10 ready for hardy-updates by fixing regressions, example: https://launchpad.net/ubuntu/+source/kdepim https://launchpad.net/ubuntu/+source/kdebase

I've been looking at a number of kde/qt apps making sure that they were as good as possible for release, including: kdesvn - https://launchpad.net/ubuntu/+source/kdesvn kile - https://launchpad.net/ubuntu/+source/kile

Helping with the arts-removal process involving quite many packages: https://bugs.launchpad.net/ubuntu/+source/kile/+bug/320915

Large security-update for mediawiki: https://bugs.launchpad.net/ubuntu/+source/mediawiki/+bug/323842

Helping getting kde4.1.4 ready for intrepid-updates, including some regression fixing as well: https://launchpad.net/ubuntu/+source/kdepim/4:4.1.4-0ubuntu1~intrepid2

Areas of work

In general I'm very focused on stability and security.

When I encounter a problem, I'll always give it a thought if it is feasible for an SRU; and have done quite a number of SRU's. To account for that I also do some SRU verification / testing as well.

I have my primary focus on Kubuntu packages either in main or universe, but I'm in no way limited to that. Apart from the general helping out with kde/qt applications I try to conquer packages one by one. This includes going through a lot (in many cases all bugs) trying to fix as many of them, subscribe to the bugmail so the shape doesn't lower when I move on to the next package. For now these includes: kile kdesvn qtoctave varnish imapsync offlineimap mediawiki squirrelmail ... and of course packages I'm maintainer for in Debian. I've probably forgot some, but I'll remember as soon as I get a bug from the package.

Some universe packages has a high "visibility" security-wise from outside, when being installed on the machine. And I've started making a personal commitment to be sure to do regular security-updates for some packages in this category. This includes subscribing to info from upstream as well as Debian to be able to pick fixes as quickly as possible. For now this is: mediawiki - hardy onwards (as the packaging prior to hardy is some script downloading the upstream tarball; not good). squirrelmail - dapper onwards (I have a security-update waiting for sponsoring, if someone feels for it https://bugs.launchpad.net/ubuntu/+source/squirrelmail/+bug/328938 )

Things I could do better

There is always ways to improve; and I'm confident that some more experience will give me that. One thing I know, is that I should be better to remember to include bug numbers in my changelog.

Plans for the future

General

Keep helping out to improve Kubuntu in any way possible.

Look out for some more packages to commit myself to.

Start venture more into new areas; I'm very keen on the Ubuntu server and could see myself helping out there eventually.

What I like least in Ubuntu

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