I, Heinrich Schuchardt, apply for MOTU.
I am applying because:
- As as sponsor I will be able to contribute to the review process of updated packages.
- I am contributing to Ubuntu packages on a regular basis as an employee of Canonical. As a member of MOTU I will find it easier to get my package updates included and alleviate the burden on other sponsors.
Who I am
I am software engineer living in Leverkusen, Germany. I have been passionate about software development since my days at university. I cherish the the open software scene allowing to contribute to each others work.
In the U-Boot project I am maintainer of the UEFI implementation.
Since July 2021 I am working as RISC-V lead engineer in Canonical's foundation team since July 2021.
My Ubuntu story
I have been
using Ubuntu since 2010 on workstations, SoCs, and in Docker
- contributed to Debian packages like flash-kernel, mini-dinstall via patches to Debian since 2016
- contributed to Ubuntu packaging since I was employed by Canonical last year
For me contributing starts as high as possible in the flow from upstream, to Debian, to Ubuntu.
Upstream projects I have contributed to the following this year include
- Linux kernel
Debian packages I have been contributing to this year to include
Inside Ubuntu my focus has been on
- Making Ubuntu run on more RISC-V hardware
- Allowing more software to run on RISC-V
- Fixing bugs in Ubuntu packages
Examples of my work / Things I'm proud of
This year I had a focus on SPDK and DPDK. RISC-V enabled versions currently live in ppa:ubuntu-risc-v-team/release as we are waiting for the next DPDK LTS release before upgrading DPDK in the main repository. See my discourse article Accelerate network and storage applications on RISC-V with DPDK and SPDK.
Together with colleagues of the foundation team I have made more RISC-V hardware run on Ubuntu. See the RISC-V Download Page. And more boards to come with the Kinetic release.
A list of my sponsored uploads is available via the Ubuntu Sponsorship Miner.
These gave me a good overview over processes from new packages over release upgrades and bug fixes to SRU.
Most of the bug fixing stuff and release upgrade stuff is more on the trivial side. The most complex thing was getting a new version of DPDK packaged.
Areas of work
Due to my job description RISC-V enablement will remain a focus. But starting from an architecture results in a big scope of relevant packages: from basics over server to desktop. But also the snap world if of interest.
Things I could do better
- I sometimes opted to fix the easiest bugs first. I should pick some more intricate stuff and thereby expand my experience.
- debian/copyright was never my favorite but needs to be done with precision for legal reasons.
Plans for the future
I should spend some time on triage of incoming bugs and select a few packages where I try to fix whatever is incoming.
What I like least in Ubuntu
For many packages we carry a very large patch set. We should do a better job in upstreaming what we deem relevant.
Timely response to bug reports is often missing. Keeping 10 year old bugs does not make sense.
If you'd like to comment, but are not the applicant or a sponsor, do it here. Don't forget to sign with @SIG@.
As a sponsor, just copy the template below, fill it out and add it to this section.
In the recent cycles I've sponsored some fixes (focussed mostly on autopkgtests and riscv) and merges Heinrich worked on. There was no issues in the sponsoring request I reviewed for him, the technical work was right, the launchpad bugs correctly documented and the sponsors subscribed as expected.
Heinrich is also active on IRC on #ubuntu-devel
From my interactions with Heinrich and the reviews/sponsoring I did for him, I think he has the packaging knownledge needed and understands Ubuntu enough (release cycle, freezes, processes for proposed migration/SRU/etc) to become a MOTU
Specific Experiences of working together
Kinetic Merges https://bugs.launchpad.net/ubuntu/+source/u-boot-menu/+bug/1987295 https://bugs.launchpad.net/ubuntu/+source/unzip/+bug/1987401 https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1987305
u-boot riscv fixes https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1968174
Areas of Improvement
Nothing in particuar to suggest from me at this point
I've worked with Heinrich for just over one year, and in that time I've sponsored 21 uploads for him. The quality has been good and sometimes we've had discussions on different solutions. I trust that Heinrich has a good understanding of our procedures to become a MOTU a now, which will make him more effective at +1 maintenance, and allow him to gain the experience required to become a Core Dev in future.
Specific Experiences of working together
* The first upload of Heinrich's that I sponsored was an SRU to Focal https://launchpad.net/ubuntu/+source/opensbi/0.9-2~ubuntu0.20.04.1
* https://launchpad.net/ubuntu/+source/plfit/0.9.3+ds-1ubuntu1 was a fix for FTBFS on s390x, forwarded to Debian, but sadly not yet included there
* https://launchpad.net/ubuntu/+source/opensbi/1.0-1 , https://launchpad.net/ubuntu/+source/r-cran-openssl/2.0.1+dfsg-1 and https://launchpad.net/ubuntu/+source/mokutil/0.6.0-2 were syncs from Debian dropping the Ubuntu delta
* https://launchpad.net/ubuntu/+source/python-cheroot/8.6.0+ds1-3ubuntu1 was a fairly complicated merge from Debian
Areas of Improvement
I think Heinrich could pay a little more attention to detail, e.g. that the changelog closes the correct bug number, or that debian/copyright doesn't miss a license.
== <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 ===