CoreDev

Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2024-08-14 19:18:56 →
Size: 9085
Editor: cpete
Comment:
← Revision 3 as of 2024-09-04 16:42:03 → ⇥
Size: 10609
Editor: sil2100
Comment: Adding my endorsement
Deletions are marked like this. Additions are marked like this.
Line 113: Line 113:
== Łukasz 'sil2100' Zemczak ==
=== General feedback ===
Chris, even though still relatively new in the Ubuntu ecosystem, demonstrated multiple times his passion, determination and growing experience with regards to distro-work. Chris actively participated in multiple archive activities, such as helping with transitions, +1 maintenance, proposed-migration etc. Chris also is never afraid to ask for clarification or help when in doubt, which is essential when starting off as a core developer. Furthermore, Chris seeks mentorship actively, being trained by more experienced core-developers on a weekly basis.
I gladly endorse Chris on his road to an official Ubuntu Core Developer. I think he's ready.

=== Specific Experiences of working together ===
I have officially sponsored only one package for Chris so far, but as his manager and co-mentor, I have insight into all the great work that Chris is performing. In my mind he demonstrated particular excellence during the infamous xzutils vulnerability and time_t crunches: when we announced an all-hands-on-deck, Chris answered. And even though he didn't yet feel 100% comfortable back then with distro-related topics, his help was invaluable.
At the same time, as a main developer of subiquity, Chris by default has a lot of contact with Ubuntu per-se, making him a great candidate.

=== Areas of Improvement ===
Chris sometimes can be overly ambitious, taking on his back too much for comfort. So I would like him to be a bit more mindful of his limits.

I, Chris Peterson, apply for core-dev

DRAFT

Name

Chris Peterson

Launchpad Page

https://launchpad.net/~cpete

Wiki Page

https://wiki.ubuntu.com/cpete

IRC

cpete

Email

chris.peterson@canonical.com

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.
  • I'd like to be more involved in the community (sponsoring, patch pilot, etc.)
  • My work may require touching various packages, including those in main, for which there is no distinct package-set goal and PPU/MOTU won't cover packages in main.
  • It will facilitate my general distro related work (+1 maintenance, proposed-migrations, etc.)

Who I am

Hi, my name is Chris Peterson and I am a software engineer on Canonical's Foundations team.

Prior to joining Canonical, I received my Master's in Computer Science from the University of California, Davis, where I researched semantic parsing in the areas Natural Language Processing and Computational Linguistics. Before that, I received my Bachelor's in Computer Science & Engineering from the University of Nevada, Reno, where I performed research in a Social Robotics laboratory.

I live in California, United States, and when I'm not writing software I enjoy building keyboards, playing the bass guitar, or playing video games.

My Ubuntu story

Back in my first year of college when I started to learn programming and what Linux was all about, I started with Ubuntu (Trusty). For a short time I bounced around different distributions, though mostly Ubuntu based, and eventually came back to Ubuntu after working in a robotics lab which relied on it for its software (ROS). Since then it's been my daily driver for everything I do. I am passionate about open source and working on Ubuntu everyday brings me great joy.

Tell us how and when you got involved, what you liked working on and what you could probably do better.

My involvement

Examples of my work / Things I'm proud of

Areas of work

As part of Canonical's Foundations Team I spend a majority of my time working on installer related things, primarily Subiquity. While this often includes work in other projects which are also not conventionally packaged, such as Curtin or Probert, it may also include work in archive packages such as livecd-rootfs, Casper, or ubuntu-meta. I expect core dev privileges will most facilitate my work by removing the need for sponsorship to make changes to these packages. However, given my experience is still limited with some of these core archive packages, I certainly still expect to ask for review before making changes I'm not 100% certain about.

I also spend time working on Apport, fixing bugs and working to improve bug reporting in the installers. In particular, over the last two release cycles I have been collaborating within Foundations and across Desktop and Server to improve the Apport bug reporting process in general among the various installer related tools.

As part of my more general packaging related responsibilities on the Foundations team, I also participate in regular +1 maintenance and proposed-migration work.

Things I could do better

  • Get more familiar with the automation/tooling that's available to better standardize my workflow.
  • Increase my participation on IRC
  • Improve my knowledge of Debian and their processes/tooling.

Plans for the future

General

  • Continue to make contributions to Subiquity, making it more robust and improving the overall installation experience.
  • I would also like to leverage my upload privileges to help sponsor work within my team, engage in patch piloting, and conduct more effective +1 shifts.

What I like least in Ubuntu

  • Ubuntu development process documentation is very disjoint, which makes things difficult for newcomers. Best practices are not always clear and may also depend on who you ask. Continued work on centralized documentation, like the ubuntu-packaging-guide, is sorely needed.

    • The Launchpad UI. Finding what you are looking for can be difficult if you don't know exactly where it is. Dedicated sections in the developer documentation would greatly help with this.

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.

Łukasz 'sil2100' Zemczak

General feedback

Chris, even though still relatively new in the Ubuntu ecosystem, demonstrated multiple times his passion, determination and growing experience with regards to distro-work. Chris actively participated in multiple archive activities, such as helping with transitions, +1 maintenance, proposed-migration etc. Chris also is never afraid to ask for clarification or help when in doubt, which is essential when starting off as a core developer. Furthermore, Chris seeks mentorship actively, being trained by more experienced core-developers on a weekly basis. I gladly endorse Chris on his road to an official Ubuntu Core Developer. I think he's ready.

Specific Experiences of working together

I have officially sponsored only one package for Chris so far, but as his manager and co-mentor, I have insight into all the great work that Chris is performing. In my mind he demonstrated particular excellence during the infamous xzutils vulnerability and time_t crunches: when we announced an all-hands-on-deck, Chris answered. And even though he didn't yet feel 100% comfortable back then with distro-related topics, his help was invaluable. At the same time, as a main developer of subiquity, Chris by default has a lot of contact with Ubuntu per-se, making him a great candidate.

Areas of Improvement

Chris sometimes can be overly ambitious, taking on his back too much for comfort. So I would like him to be a bit more mindful of his limits.

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

cpete/CoreDev (last edited 2024-09-30 18:21:27 by cpete)