I, Graham Inggs, apply for core-dev.

Who I am

I'm a sysadmin for the Faculty of Engineering and the Built Environment at the University of Cape Town. I support staff and post-graduates who use Linux-based desktops (primarily Ubuntu) and an HPC cluster running Rocks/CentOS. I also look after an under-graduate teaching lab of 30 PCs with NVIDA GPUs that run Ubuntu.

My Ubuntu story

I've been using Ubuntu as my primary desktop operating system since Gutsy Gibbon. I started contributing to Ubuntu in late 2012 fixing bugs in packages we use at our university; cntlm, (open)motif and CUDA.

My involvement

Packaging, SRUs, syncs, merges and bug triaging. I was accepted as a MOTU in December 2013 and since then have sponsored a few syncs and merges, and fixed some FTBFS that were stuck in -proposed. I became a Debian Maintainer in February 2014 and a Debian Developer in August 2015.

Examples of my work / Things I'm proud of

• List of packages maintained and co-maintained by me in Debian

• List of uploads sponsored for me in Ubuntu

• A complicated merge of nvidia-settings (main)

Areas of work

While supporting users of Ubuntu desktops, I end up reporting and fixing bugs in all kinds of packages. I am also involved with packaging being a member of the Debian-Science and Debi-Chem teams.

Things I could do better

I'd like to do more in main without having to take up the time of a sponsor.

Plans for the future

General

There are several science-related packages I intending packaging for Debian for use at the university and I also plan to make these work well in Ubuntu.

What I like least in Ubuntu

Sometimes bugs are fixed in the development release and those fixes never make it into the stable release, leaving users to live with annoyances for 6 months and wondering why the bug status is "fix released" while it is still broken for them. I think there should be more SRUs.

I wrote the above for my MOTU application, and since becoming a MOTU, I think I've done fewer SRUs. I think I've gotten better at fixing bugs before the release date.

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

CategoryCoreDevApplication