PPUApplicationTools

Differences between revisions 5 and 6
Revision 5 as of 2013-04-09 08:33:30
Size: 5650
Editor: cpc3-craw6-2-0-cust180
Comment:
Revision 6 as of 2013-04-09 08:40:34
Size: 6468
Editor: dholbach
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
'''I, Colin King, apply for universe-contributor upload rights for package(s) eventstat, powerstat, fwts.''' '''I, Colin King, apply for upload rights for package(s) eventstat, powerstat, fwts.'''
Line 66: Line 66:
== Daniel Holbach (dholbach) ==
=== General feedback ===
Colin knows these tools inside out and is the de-facto maintainer. Even bigger packaging changes throughout the releases were always top-notch. I had nothing to complain about. He should definitely have upload rights for them.

=== Specific Experiences of working together ===
 * https://launchpad.net/ubuntu/+source/fwts/0.17.2
 * https://launchpad.net/ubuntu/+source/fwts/0.16.14
 * https://launchpad.net/ubuntu/+source/fwts/0.17.9
 * https://launchpad.net/ubuntu/+source/fwts/0.20.10
 * https://launchpad.net/ubuntu/+source/fwts/0.20.00
 * https://launchpad.net/ubuntu/+source/fwts/0.22.00
 * https://launchpad.net/ubuntu/+source/fwts/0.22.13
 * https://launchpad.net/ubuntu/+source/eventstat/0.01.19-1
 * https://launchpad.net/ubuntu/+source/powerstat/0.01.20-1

I, Colin King, apply for upload rights for package(s) eventstat, powerstat, fwts.

Who I am

I am a Ubuntu member and a Canonical employee and currently working as an Kernel Engineer in the Kernel Team. I have worked on various parts of the kernel subsystem with focus on suspend/resume, BIOS, ACPI, power management and eCryptfs. I developed the firmware test suite as well as tools such as eventstat and powerstat.

I write a Ubuntu related blog with postings on kernel and system related hints and tips and get thousands of page impressions per week.

My Ubuntu story

I started using Ubuntu back in 2006, and joined Canonical as a Ubuntu Kernel Developer in 2008. I've always enjoyed looking at gnarly hardware related bugs as I am a low-level engineer at heart. I got involved in debugging suspend/resume issues and before long I deep dived into Intel architectures and ACPI. I found that there are many classes of firmware bugs that could be identified programmatically so I wrote the firmware test suite (fwts). My belief is that quality can be improved if developers have access and use quality improving tools. While working on Power Management on 12.04 I developed a powerstat and eventstat to help pin point power issues. Recently I've been thrashing a lot of open source projects with tools such as smatch to try to automatically find bugs to help improve code quality.

I like working on problems that require deep diving and analysis. I am a firm believer that a bug requires a regression test associated with it to ensure we never see the bug rear it's ugly head ever again in production code. I also believe that developers should always use quality tools to catch obscure programming bugs and that code reviews are required for every patch that gets committed. Quality requires effort and time.

My involvement

Ubuntu Kernel Team - analysis, debugging, fixing bugs, ACPI + BIOS issues. Hardware Enablement projects - firmware test suite + looking at BIOS issues that relate to system certification.

Examples of my work / Things I'm proud of

As mentioned above, fwts, eventstat, powerstat. I've contributed over 2000 patches to these projects in the past few years. eventstat and powerstat were the first tools that I developed and packaged from scratch in Debian. I also quite pleased with the improved power management that I worked on in Ubuntu 12.04.

I've also contributed to the eCryptfs regression tests. I've also worked on backporting eCryptfs kernel fixes to older releases.

Areas of work

eCryptfs - worked with upstream developers and just recently was given writes to push patches to eCryptfs userland tools.

hardware enablement work - helping to shape, direct, write and improve the firmware test suite. Contributed to > ~1900 patches, fixed numours bugs. Worked to get it to build in Gentoo. Worked with Intel to support their use of fwts. Buy-in from Redhat QA. Community buy-in.

ubuntu kernel team - fixing bugs, pushing fixes upstream, doing analysis on various subsystems to shape config choices for releases.

power management - powerstat, eventstat - main developer with help from Kamal Mostafa on packaging and Debian uploading, with help from Daniel Holbach for uploads into Ubuntu. Been working with Ubuntu QA team on eventstat to improve features to track wakeup event issues over releases.

Things I could do better

I'd like to improve my packaging skills and get more of my various projects into Debian and Ubuntu.

Plans for the future

General

Looking to become a Debian Developer in the near future.

What I like least in Ubuntu

Dodgy applications that suck power. I'm working on various tools and strategies on the ARM based mobile projects to help corner, identify and fix power issues.


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.

Daniel Holbach (dholbach)

General feedback

Colin knows these tools inside out and is the de-facto maintainer. Even bigger packaging changes throughout the releases were always top-notch. I had nothing to complain about. He should definitely have upload rights for them.

Specific Experiences of working together


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


ColinKing/PPUApplicationTools (last edited 2014-10-06 18:54:59 by cpc3-craw6-2-0-cust180)