I, Marcin Juszkiewicz, apply for universe-contributor.

Who I am

• Debian user since 2000 year (m68k, x86, amd64)

• OpenEmbedded developer since 2004 (arm, x86, mipsel)

• OpenZaurus developer since 2004

• OpenZaurus release manager 2006-2007

• Ångstrom developer since 2006 (arm, x86)
• Maemo developer since 2007 (Nokia 770/n810/n900)
• Linaro developer since 2010
• Ubuntu user since 2010 (amd64, x86, armel)

I am working with embedded ARM devices since 2004 when I bought my first LinuxPDA (Sharp Zaurus SL-5500). Since then I was one of main developers of OpenEmbedded build system, contributed a lot to OpenZaurus distribution (released last few releases, maintained security and bugfix updates repository for them), did lot of UI tweaking for OPIE applications.

Experience with building software and packaging is one of my strong skills.

My Ubuntu story

Started using Debian in 2000 on my Amiga. Then moved to x86 land and stayed with it. Maintained "rox-filer" outside of Debian for nearly two years (then ended using it and someone other took it). Packaged "tex-skak" for friend and got it into Debian (gave maintainership for someone else).

I am using Ubuntu since April 2010 due to my move to Canonical. Before I used it only in virtual machines or on external servers - mostly for checking does OpenEmbedded and Poky Linux build systems works properly under new Ubuntu releases.

My involvement

As Linaro developer I am working on cross compilation support in Ubuntu. Most of my work is related to toolchain components (binutils, eglibc, gcc, linux).

Examples of my work / Things I'm proud of

Blueprints:

• Cross compilers for Maverick

• Cross compilers for Natty

Bugs which I was working on:

• replace dh_movefiles with dh_install

• merge cross build into "binary" target

• fix "control" target for cross builds

• [PR43847] fix wrong use of objdump during cross build

• Cross-compiler packages miss libgcc dbg packages breaking xdeb

• Cross-compilers fail to build twice in a row

• -source build-dep not needed when building cross-compilers

• Fix installing of libstdc++-pic for cross builds

• fix building for sysroot other then /

• Merge rules for cross builds into normal one

• Cross build needs rpath with xdeb

• [cross] cross-gcc-4.4 package should provide $triplet-gcc, g++ etc. symlinks

• [cross] Provide cross gcc-defaults package

• Allow to build just linux-libc-dev

• allow building intermediate stages for gcc

• allow building intermediate stages for eglibc

• provide packaging rules in gcc-4.5-source package

• provide packaging rules in linux-source binary package

• provide packaging rules in binutils-source binary package

• provide packaging rules in eglibc-source binary package

• provide unpatches sources in binutils-source package

• [cross] dpkg-genchanges: error: package binutils-arm-linux-gnueabi has priority optional in control file but extra in files list

• provide unpatches sources in eglibc-source package

• [cross] no gcc-4.4-arm-linux-gnueabi-base package

• sync rules.conf with gcc-4.5

• [cross] create libgcc1 and gcc-*-base packages for stage2 build

• OpenJDK Armel FTFBS

• [cross] gcc-4.5-armel-cross_1.35 fails to build due to genchanges warnings

• Packages built with modified gcc fail to install

• Add Efika MX Smartbook/Smarttop support

Areas of work

• Packages already present in Ubuntu: gcc-4.4, gcc-4.5, linux, eglibc, binutils, armel-cross-toolchain-base, gcc-4.4-armel-cross, gcc-4.5-armel-cross, gcc-defaults-armel-cross.
• Efika MX Smartbook related packages

Worked directly with maintainers of affected packages:

• Matthias Klose
• Andy Whitcroft
• Steve Langasek
• Oliver Grawert

Working also with Ubuntu/ARM members and Linaro developers.

Things I could do better

• triaging and fixing FTFBS
• improving cross compilation support

Plans for the future

General

• getting to moment when whole 'main' will be cross buildable

What I like least in Ubuntu

Too complicated descriptions of how to became Ubuntu developer/member. It looks like you can be UD but not UM etc.

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.''
=== Areas of Improvement ===

CategoryUniverseContributorApplication