OpenStackDeveloperApplication

Differences between revisions 1 and 2
Revision 1 as of 2020-09-10 13:23:39
Size: 6420
Comment:
Revision 2 as of 2020-09-10 13:39:04
Size: 6437
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
'''I, Chris MacNaughton, apply for upload rights for the OpenStack package set.''' '''I, Chris !MacNaughton, apply for upload rights for the !OpenStack package set.'''
Line 5: Line 5:
|| '''Name''' || Chris MacNaughton || || '''Name''' || Chris !MacNaughton ||
Line 16: Line 16:
Hi! My name is Chris MacNaughton and I'm a Software Engineer on Canonical's OpenStack Engineering team and located in the Netherlands. When I started, I was primarily focused on the OpenStack and Ceph charms; however, I've shifted to assisting with the package maintenance of the OpenStack project . Hi! My name is Chris !MacNaughton and I'm a Software Engineer on Canonical's! OpenStack Engineering team and located in the Netherlands. When I started, I was primarily focused on the !OpenStack and Ceph charms; however, I've shifted to assisting with the package maintenance of the !OpenStack project .
Line 20: Line 20:
I started playing with Ubuntu in the Lucid timeframe, but didn't use it professionally until Precise, when the company I was working with used Ubuntu for all of our production servers. Despite being a longtime user of Ubuntu, I didn't start to contribute until fairly recently. I started working at Canonical in 2015 and, as a result of my work in the OpenStack Engineering team, began to work on OpenStack bugs with a general focus on the OpenStack Charms. I started playing with Ubuntu in the Lucid timeframe, but didn't use it professionally until Precise, when the company I was working with used Ubuntu for all of our production servers. Despite being a longtime user of Ubuntu, I didn't start to contribute until fairly recently. I started working at Canonical in 2015 and, as a result of my work in the !OpenStack Engineering team, began to work on !OpenStack bugs with a general focus on the !OpenStack Charms.
Line 22: Line 22:
In the last six months, I've moved into more direct involvement with Ubuntu itself through changing my responsibilties to focus on packaging for the OpenStack project. In the last six months, I've moved into more direct involvement with Ubuntu itself through changing my responsibilities to focus on packaging for the !OpenStack project.
Line 26: Line 26:
I'm currently involved with the Ubuntu OpenStack Team. I'm currently involved with the Ubuntu !OpenStack Team.
Line 40: Line 40:
I've primarily been working on OpenStack packaging for new and stable releases. I've participated in various packaging aspects including SRUs, FFEs, syncs, merges, backports, patches, upstreaming fixes, and backporting upstream fixes. I primarily work with Corey Bryant and James Page on OpenStack Packaging. I've primarily been working on !OpenStack packaging for new and stable releases. I've participated in various packaging aspects including SRUs, FFEs, syncs, merges, backports, patches, upstreaming fixes, and backporting upstream fixes. I primarily work with Corey Bryant and James Page on !OpenStack Packaging.
Line 42: Line 42:
I have also been working on improving the state of the Ubuntu OpenStack bug queues, for both the packages that the OpenStack team subscribes to and the Cloud Archive bugs. I have also been working on improving the state of the Ubuntu !OpenStack bug queues, for both the packages that the !OpenStack team subscribes to and the Cloud Archive bugs.
Line 46: Line 46:
While I Ihave a reasonable understanding of the OpenStack packages, there's always something new to learn. In addition to expanding my knowledge of packaging these things, I want to expand my experience with broader Ubuntu packaging experience. While I have a reasonable understanding of the !OpenStack packages, there's always something new to learn. In addition to expanding my knowledge of packaging these things, I want to expand my experience with broader Ubuntu packaging experience.

I, Chris MacNaughton, apply for upload rights for the OpenStack package set.

I am applying because:

  • I'd like to eliminate delays in getting my work sponsored.
  • I'd like to reduce the burden on my sponsors.

Who I am

Hi! My name is Chris MacNaughton and I'm a Software Engineer on Canonical's! OpenStack Engineering team and located in the Netherlands. When I started, I was primarily focused on the OpenStack and Ceph charms; however, I've shifted to assisting with the package maintenance of the OpenStack project .

My Ubuntu story

I started playing with Ubuntu in the Lucid timeframe, but didn't use it professionally until Precise, when the company I was working with used Ubuntu for all of our production servers. Despite being a longtime user of Ubuntu, I didn't start to contribute until fairly recently. I started working at Canonical in 2015 and, as a result of my work in the OpenStack Engineering team, began to work on OpenStack bugs with a general focus on the OpenStack Charms.

In the last six months, I've moved into more direct involvement with Ubuntu itself through changing my responsibilities to focus on packaging for the OpenStack project.

My involvement

I'm currently involved with the Ubuntu OpenStack Team.

Examples of my work / Things I'm proud of

These are My Sponsored Uploads

These are My direct uploads

These are My opened SRUs

These are My opened MIRs

Areas of work

I've primarily been working on OpenStack packaging for new and stable releases. I've participated in various packaging aspects including SRUs, FFEs, syncs, merges, backports, patches, upstreaming fixes, and backporting upstream fixes. I primarily work with Corey Bryant and James Page on OpenStack Packaging.

I have also been working on improving the state of the Ubuntu OpenStack bug queues, for both the packages that the OpenStack team subscribes to and the Cloud Archive bugs.

Things I could do better

While I have a reasonable understanding of the OpenStack packages, there's always something new to learn. In addition to expanding my knowledge of packaging these things, I want to expand my experience with broader Ubuntu packaging experience.

Plans for the future

General

I'm planning to improve my packaging skills in general in addition to my focus on OpenStack. I'm also planning to work with other teams to improve my broader experience by doing some +1 Maintenance and shadowing other core devs, helping where I can.

What I like least in Ubuntu

I don't like how much bugs rot in Launchpad. Whether the bug is going to be fixed or not, having a bug sitting in Triaged, or worse, Fix Committed, for a specific target shows me that more time needs to be spent cleaning up older bugs.


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.''
## Full list of sponsored packages can be generated here:
##  https://udd.debian.org/cgi-bin/ubuntu-sponsorships.cgi
=== Areas of Improvement ===


CategoryPerPackageUploaderApplication

ChrisMacNaughton/OpenStackDeveloperApplication (last edited 2020-09-23 15:19:03 by james-page)