CoredevApplication

Differences between revisions 67 and 68
⇤ ← Revision 67 as of 2018-08-14 20:02:49 →
Size: 16094
Editor: ahasenack
Comment:
← Revision 68 as of 2018-08-14 20:07:28 → ⇥
Size: 16267
Editor: ahasenack
Comment:
Deletions are marked like this. Additions are marked like this.
Line 122: Line 122:

 * Bileto usage:
  * I just got access, and used it to run squid-4.x DEP8 tests in all architectures, prior to an actual upload: https://bileto.ubuntu.com/#/ticket/3351

WORK IN PROGRESS

I, Andreas Hasenack, apply for Ubuntu Core Developer

Name

Andreas Hasenack

Launchpad Page

http://launchpad.net/~ahasenack

Wiki Page

https://wiki.ubuntu.com/AndreasHasenack

Who I am

I graduated in Electrical Engineering. Worked for a few years in a company in the aerospace industry, but in the civilian area, in a project about installing "black boxes" in trucks and buses to monitor several driving and engine parameters. I then came in contact with a customer who had a nice "intranet" (that's what it was called back then), with internal web sites and a big database backend (oracle). We had to do some development for them, but didn't have access to Oracle, and someone told me that I should try this thing called "linux", "postgresql" and "apache". I did, then installed it at home, and never looked back.

In 1998 I took a post-grad specialization course in the University (a degree higher than graduation, but below masters) in computer networks and went to work for Conectiva, the Brazilian Linux distribution, later renamed to Mandriva, where I stayed until 2008 doing lots of packaging work (RPM) and consulting for enterprise customers in the server area. My main area of expertise was email, authentication (kerberos, pam) and LDAP, and I also spent about half the time working in Conectiva's security team and doing security updates for the distro.

My Ubuntu story

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

My involvement

In 2008 I applied for a job in the Landscape team (https://landscape.canonical.com), and got hired as a QA engineer. I had never done any Debian packaging before, just had some ideas about how it worked, had grabbed a few packages here and there to inspect them, looked at patches, etc. apt-get wasn't a stranger, since Conectiva developed apt-rpm back in the day, and the concept of dependency resolution is the same everywhere.

Landscape has a client component, and that means a Debian package that gets installed on machines. It obviously needs to be QA'ed. So that's how I got exposed to Debian packaging "for real" that time.

In April 2017 I started working in the Ubuntu Server Team. That got me back in touch with my "Linux roots" (no pun intended) and immediately I started looking into my old friends kerberos, ldap, samba, etc and searching for bugs to fix. It is in the Ubuntu Server Team that I got introduced to the Debian Merge process, and how this team is looking into improving that process via the Git Ubuntu tooling.

Examples of my work / Things I'm proud of

DEP8 tests I added

Samba:

Autofs:

krb5:

FTBFS fixes I uploaded

Cooperation with debian and/or upstream

autofs:

ocfs2-tools:

Samba:

sssd:

squid4 dep8 fixes pushed to debian. Debian had adopted most of our DEP8 tests previously, but they never passed in their infrastructure (https://ci.debian.net/packages/s/squid/testing/amd64/):

bind9:

exim4:

dovecot:

Misc

  jul 31 15:44:10 <ahasenack>     and upgrading just bind, leaving isc-dhcp without a rebuild, also works: https://pastebin.ubuntu.com/p/zkw8nzryYV/
  • The packages would still not migrate. Looking at the update_output.txt, I found out that debian-installer is a reverse dependency as well. Asked for a rebuild/sponsorship: 

  ago 01 14:37:54 <ahasenack>     hi, my bind9 upload, which bumped the soname, also needs a debian-installer rebuild (ppa at https://launchpad.net/~ahasenack/+archive/ubuntu/bind-merge-9.11.4/+packages). Would someone sponsor this for me? https://pastebin.ubuntu.com/p/HPVtSzkPK7/

Areas of work

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

Things I could do better

  • I stopped updating the server guide
  • Create more bug patterns. Experience with triage has showed some patterns in bugs that we can leverage with automation

Plans for the future

General

  • Keep adding DEP8 tests to the Ubuntu and Debian packages
  • Reduce the delta with Debian by submitting changes upstream
  • Improve the LTS Server Guide in the areas of Authentication, Authorization and Samba

What I like least in Ubuntu

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

  • Lack of proper DEP3 headers in patches. This sometimes makes it hard to find out why a patch was introduced, or if it can be dropped. There are lintian checks for this already, but they are not enforced on upload. "What's obvious today, may not be obvious 12 months from now."

  • Many SRU bugs I see being accepted lack what I would call proper test cases. In many cases they are way too generic, or do not fulfill this requirement from the SRU template: these should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. We have to reach some sort of balance here. SRUs are already hard for newcomers, but without a proper test procedure, they are also hard on the members of the SRU team.

  • Communication and coordination in #ubuntu-release is a bit ad-hoc. One could argue it's agile, since pings from trusted people on IRC can be quickly acted upon, but if you happen to not know who is and isn't around, or by chance hit the channel when people are on holidays or in a sprint, you can be greeted by a black hole. Maybe there could be a vanguard for the week, or the day?

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:
## http://ubuntu-dev.alioth.debian.org/cgi-bin/ubuntu-sponsorships.cgi?
=== Areas of Improvement ===

AndreasHasenack/CoredevApplication (last edited 2018-09-23 10:08:31 by ahasenack)