CoreDevApplication
|
Size: 3730
Comment:
|
Size: 3121
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 12: | Line 12: |
| 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 running Ubuntu with NVIDA GPUs. | |
| Line 15: | Line 16: |
| I was accepted as a MOTU in December 2013. | 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. |
| Line 27: | Line 28: |
| I would like to be able to do more in bug control such as being able to nominate bugs for series and setting their status and importance. | I'd like to do more in main without having to take up the time of a sponsor. |
| Line 34: | Line 35: |
| 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. | 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. |
| Line 43: | Line 44: |
== Stefano Rivera == === General feedback === Reviewed and sponsored a lot of Motif related packages for Graham, in both Debian & Ubuntu. Also helped Graham improve the state of CUDA and OpenCL packaging in Ubuntu, which gets rather hairy (complex tangles of virtual packages). In the process, there have been FFes, quite a few SRUs, and I don't recall any breakage. For the last while, I've had very little feedback to offer on sponsorship - the work was all pretty good. I trust Graham to ask when he needs help with something, or review on a complex issue. === Specific Experiences of working together === I've worked with Graham quite a bit over the last couple of years, helping him get involved in Debian & Ubuntu, and mentoring. === Areas of Improvement === My only criticism is an over-eagerness to SRU. We can't achieve perfection evenrywhere. |
|
| Line 71: | Line 59: |
| [[CategoryMOTUApplication]] | [[CategoryCoreDevApplication]] |
Contents |
I, Graham Inggs, apply for MOTU.
Name |
Graham Inggs |
Launchpad Page |
|
Wiki Page |
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 running Ubuntu with NVIDA GPUs.
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. 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.
My involvement
Packaging, SRUs, syncs, merges and bug triaging.
Examples of my work / Things I'm proud of
Areas of work
I try to keep in contact with the upstream developers of the packages I maintain.
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
I will be applying for Debian Maintainer soon, and if successful, will apply for Debian Developer within the next 6 months.
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.
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 ===
GrahamInggs/CoreDevApplication (last edited 2015-12-02 19:27:38 by stefanor)