I, Simon Chopin, apply for Contributing Developer status within the Ubuntu community.

I am applying because:

* I have taken an active role within the development community that requires to be able to communicate on all dev channels, including the ubuntu-devel@lists.ubuntu.com ML, which is moderated for non-dev members.

Who I am

I am a software engineer hailing from Brittany, France, currently employed by Canonical within the Foundations team. When I'm not working on the internals of Ubuntu as part of my dayjob, you'll usually find me playing either music or videogames, both of which usually involve fiddling with my computer setup ;-).

My Ubuntu story

My Ubuntu story is, for a big part, a Debian story.

Ubuntu was my first successful attempt at Linux back in 2006 on an old laptop, thanks to the free CD shipping program that was running back then. I kept running a dual-boot until 2009, when I had a new laptop which couldn't run the latest Ubuntu but could run the latest Debian. I pragmatically switched to the mother distro, and over the years ended up involved in Python packaging, indirectly working for Ubuntu ;-).

Ironically, my FLOSS contributions died down when I used Ubuntu again, both due to my first job after college. It was only server-side, but its extra-long version strings felt very familiar indeed! I became the resident expert on deploying our applications on our servers, putting my packaging knowledge to good use. After a few years, I switched jobs, and ended up maintaining a whole internal distribution based on Debian, as well as spearheading a grassroot movement to have technical roles in the company use Linux laptops instead of OSX, insisting on Ubuntu LTS on those.

This led me to my current job at Canonical, where I'm happily greasing the internal wheels of Ubuntu so that other, more user-facing teams can deliver a good experience to all of our users, including myself and many around me who've switched to Ubuntu.

My involvement

As part of the Foundations team, my area of impact includes language toolchains, bootloaders, installer, and other core components of the system. I've touched a rather wide range of packages, mostly C libraries and utilities, but my main involvements are netplan development and OpenSSL packaging, for which I'm currently driving the transition to version 3.0.

Outside of my day job, I don't have a big impact at the moment, but my long-term aspirations are to work on reducing the gap between Ubuntu and Debian, and work upstream with the Debian QA team for the good of both their and our archive.

Examples of my work / Things I'm proud of

Overall: https://udd.debian.org/cgi-bin/ubuntu-sponsorships.cgi?render=html&sponsor=&sponsor_search=name&sponsoree=*chopin*&sponsoree_search=name

OpenSSL 3: https://lists.ubuntu.com/archives/ubuntu-devel/2021-August/041589.html https://lists.ubuntu.com/archives/ubuntu-devel/2021-October/041639.html

Areas of work

Things I could do better

Actively seek out sponsors outside of the Foundations Team! Also, pay more attention to details, as most of my uploads had small issues (no bug number, forgot to run update-maintainer, etc...)

Plans for the future

General

I plan to apply for MOTU after the impish release to help reduce the sponsorship queue. There is some selfish reasoning behind it: Core dev will have more time to review and upload my uploads to main!

Further out, I of course intend to become Core dev myself, both for my coworkers' sake and mine.

What I like least in Ubuntu

There is no clear-cut way to contribute to an existing package. Some are maintained in Launchpad in a git repository somewhere, which isn't obvious to find, some are directly using the archive as "VCS", and expect a debdiff directly on the launchpad bug, but you'll find a git repository for some of those packages still, via the git-ubuntu package, making things that much harder to grasp.

I could contrast this with many other distros, but even Debian seems clearer to me, as all "landing pages" for a given package are interlinked and most of them have a link to whatever VCS is used to maintain the package.

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

CategoryUniverseContributorApplication