CoreDevApplication

Differences between revisions 2 and 3
Revision 2 as of 2013-01-16 21:51:33
Size: 6079
Editor: cpe-24-27-40-10
Comment:
Revision 3 as of 2013-01-18 03:37:21
Size: 6346
Editor: cpe-24-27-40-10
Comment:
Deletions are marked like this. Additions are marked like this.
Line 27: Line 27:

I'd like to thank the following people for sponsoring my uploads:
TimGardner, AdamConrad, BarryWarsaw, SebastienBacher, AndyWhitcroft
ColinWatson, JamesPage, KeesCook, MarcDeslauriers, MartinPitt,
MichaelTerry, OliverGrawert, StefanoRivera, and StéphaneGraber

I, Chris J Arges, apply for core-dev.

Name

Chris J Arges

Launchpad Page

http://launchpad.net/~arges

Wiki Page

http://wiki.ubuntu.com/christopherarges

Who I am

My name is Chris J Arges and I am a member of the Canonical Sustaining Engineering Group (SEG). I primarily fix kernel and userspace bugs filed by Ubuntu Advantage customers. In practice this results to many stable fixes not only for the customers but for all Ubuntu users. My focus is not only fixing bugs, but also helping to maintain a high quality Linux distribution through data, tools and communication.

My Ubuntu story

My first distribution of Linux was RedHat 5 installed with a few floppy disks. Throughout college I used Linux for development and learning, and I switched full time to Ubuntu Linux in 2006. My first job out of college was working for IBM's Linux Technology Center, and I deep dove into writing libraries, maintaining spec and ebuild files, and debugging Linux kernel issues. At this point I started to file bugs against Ubuntu when I could to solve issues I thought other people might be interested in. In 2011 I was hired by Canonical to help fix customer bugs and help build the SEG team. I have also been involved in helping with LTS point-releases, helping with testing for the Kernel team, and doing plus-one maintenance. So far it has been fun being able to spend most of my day making Ubuntu better.

My involvement

I joined the Sustaining Engineering Group at Canonical in 2011 as the second team member. I helped build this team along with JosePlans as the bridge between Ubuntu Advantage support and Ubuntu Engineering. From building this team I realized that development of tools to help with the many bugs our team needed to fix was important. I read many wikis about the Ubuntu development processes and learned how to contribute effectively. I also have looked for ways to help out the Ubuntu community when I can.

Examples of my work / Things I'm proud of

I've produced many kernel patches for Ubuntu which can be found on the kernel-team mailing list. Some of these ranged from simple fixes to debugging that took many weeks of hard work. I've also fixed many bugs in Ubuntu for Ubuntu Advantage users, myself, and the community. I've written a paper about data-mining the Ubuntu distribution which can be found on my webpage. I've written a tool called shadow-database which allows me to download bug information to help determine which bugs need attention and calculate relevant statistics. This project also gave me some insight into debian and python packaging. I've also helped with point-releases, participated in blueprints, and try to help where I can on mailing lists and IRC.

Areas of work

My fixes and uploads are mostly related to bug fixes for Ubuntu Advantage users. A good chunk of these fixes are kernel patches which are submitted through the kernel team mailing list. In addition, code fixes are submitted and can be seen through my uploaded packages.

In addition to bug fixes, I've fixed many packages that FTBFS during my PlusOne rotations.

A list of packages I have fixed can be seen here: https://launchpad.net/~arges/+uploaded-packages

I'd like to thank the following people for sponsoring my uploads: TimGardner, AdamConrad, BarryWarsaw, SebastienBacher, AndyWhitcroft ColinWatson, JamesPage, KeesCook, MarcDeslauriers, MartinPitt, MichaelTerry, OliverGrawert, StefanoRivera, and StéphaneGraber

Things I could do better

While I primarily fix bugs in the kernel, I'd like to continue to fix more non-kernel packages and expand my packaging knowledge. I'd like to help Debian/Ubuntu further by participating in PlusOne rotations as well as. I'd like to also help to improve debugging tools, test cases, development tools, and ways of displaying information that would be useful in making Ubuntu better like bug dashboards.

Plans for the future

General

I would like to continue to help make Ubuntu better by additional Plus One rotations and other areas where I can help out. I'd like to continue to fix problematic packages and ensure that various features and tools are working not only in development releases but in LTS releases as well. I will continue to develop skills in the Linux kernel as well as Debian packaging. In addition, I'd like to help others become involved with Ubuntu.

What I like least in Ubuntu

When fixing a package there are multiple ways the fix could be contributed back to the Ubuntu maintainer. One could attach a debdiff patch to a bug, link a Bzr branch, or provide a patch via e-mail. It would be great to have the maintainer indicate preferred method of patches. Also, when I did my study of all Ubuntu bugs in 2012, I noticed that many teams have different bug workflows. Some keep the person assigned after the upload, some remove the name, some use status fields a bit differently. Finally, one thing I noticed is the proliferation of bug bots. While I'm guilty of using them myself, perhaps there are better way to introduce this functionality server-side instead of cobbling these solutions together.


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


arges/CoreDevApplication (last edited 2016-10-06 12:48:09 by localhost)