DeveloperApplicationPPU

Differences between revisions 4 and 5
⇤ ← Revision 4 as of 2010-04-09 15:55:20 →
Size: 6606
Editor: d14-69-66-169
Comment:
← Revision 5 as of 2010-04-11 18:23:08 → ⇥
Size: 7010
Editor: d14-69-66-169
Comment:
Deletions are marked like this. Additions are marked like this.
Line 37: Line 37:
 * upstart: Bug:524484
Line 63: Line 64:
 * [[https://launchpad.net/~smoser/+archive/ppa|personal ppa]]
Line 65: Line 67:
 * UEC in Lucid. Because of my efforts and those of the rest of the Ubuntu Server team, UEC is much more functional, stable and usable than it was in Jaunty. Some things I've contributed to this are end-user fixes and tools (uec-publish-tarball, uec-publish-image) for making usage easier.  
 * 		 * UEC in Lucid. Because of my efforts and those of the rest of the Ubuntu Server team, UEC is much more functional, stable and usable than it was in Jaunty. Some things I've contributed to this are end-user fixes and tools (uec-publish-tarball, uec-publish-image) for making usage easier.
 * Debian moved to python-boto version 1.9. Eucatools was only officially supported on boto 1.8. I made a few backwards compatible fixes that made Ubuntu's euca2ools work with either boto 1.8 or 1.9, and ran euca2ools through a fairly complete [[Boto19TestCoverage|set of tests]] to verify it was functioning correctly.

I, Scott Moser, wist to apply for MOTU.

Name

Scott Moser

Launchpad Page

http://launchpad.net/~smoser

Wiki Page

ScottMoser

Who I am

I'm Scott Moser, a member of the Ubuntu Server team. I'm personally in charge of building, publishing and maintaining the Official Ubuntu images for EC2. These same images are made available for UEC. Along with the rest of the Ubuntu Server team, I help to make Ubuntu Server and Ubuntu Enterprise Cloud great.

My Ubuntu story

I began using Ubuntu around the Warty time frame. Prior to that I had used Debian since around 2001 and other Linux distributions starting with Slackware in 1995. When ubuntu appeared, I was in the same boat as many others. I loved using Debian. However, due to the long release cycle I wasn't ever satisfied with the 'stable', but wasn't so interested in keeping an 'unstable' system working. Ubuntu's 6 month stable release cycle was a perfect fit.

I remember a conversation with Manoj Iyer where I introduced him to Ubuntu after I had previously gotten him hooked on Debian. He was complaining about his custom kernels not functioning perfectly with his Thinkpad. I asked him why he wanted to spend his days maintaining a custom kernel, and told him that these guys (handing him a Warty CD) had people that did that as their day job. My persuasion half worked, Manoj was converted to Ubuntu, but still spends time maintaining a kernel (He's on the Ubuntu Kernel Team now).

I became involved in the development of Ubuntu in August of 2009. Since then, I've loved working with other Ubuntu developers and putting contributing to making Ubuntu better. The thing I've most enjoyed so far is 1x1 interactions with other developers where I learn from them and occasionally share knowledge.

The thing most difficult for me in Ubuntu is the fast pace of development. My background prior to Ubuntu development was in "Enterprise". Products there didn't have 6 month release cycles. You didn't "just do something", there was always planning involved and long cycles. Because of this, I can procrastinate on work items. The waiting till the last minute causes an even *shorter* period for development.

My involvement

EC2/UEC Images:

  • Create and maintain the official Ubuntu images on EC2 and UEC

  • I simplified and stabilized the production of these images. It is completely automated now, with nightly builds automatically published to ec2 and made available for download to UEC.

  • I also added creation of EBS root images to the above process.

  • Developed use a test suite for the EC2 images

Bug Fixes sponsored:

MainInclusionRequests:

New Packaging: I did the initial packaging of the following new Ubuntu packages:

Cloud-init / Ec2-init:

  • Maintain ec2-init in karmic and hardy

  • develop and maintain cloud-init Lucid. cloud-init represents presents a great deal more functionality and power than ec2-init did.

PPAs maintained:

Examples of my work / Things I'm proud of

  • UEC in Lucid. Because of my efforts and those of the rest of the Ubuntu Server team, UEC is much more functional, stable and usable than it was in Jaunty. Some things I've contributed to this are end-user fixes and tools (uec-publish-tarball, uec-publish-image) for making usage easier.

  • Debian moved to python-boto version 1.9. Eucatools was only officially supported on boto 1.8. I made a few backwards compatible fixes that made Ubuntu's euca2ools work with either boto 1.8 or 1.9, and ran euca2ools through a fairly complete set of tests to verify it was functioning correctly.

Areas of work

Let us know what you worked on, with which development teams / developers you cooperated and how it worked out.

Things I could do better

Plans for the future

General

What I like least in Ubuntu

Please describe what you like least in Ubuntu and what thoughts do you have about fixing it.

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

ScottMoser/DeveloperApplicationPPU (last edited 2010-04-27 15:16:11 by 95)