DeveloperApplication-MOTU
Contents |
I, Marcin Juszkiewicz, apply for MOTU. Name Marcin Juszkiewicz Launchpad Page Wiki Page Website LinkedIn
OpenEmbedded developer since 2004 (arm, x86, mipsel) OpenZaurus developer since 2004 OpenZaurus release manager 2006-2007 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.
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. Around May 2011 I got PPU permissions for my packages containing armel/armhf cross compiler which I maintain since June 2010. During last two years I had my fingers in many packages from main and universe mostly during ARM porting jams organized weekly by Linaro Developer Platform team (which I am part of).
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). Due to fact that I am working on ARM related things I apply for access to whole 'universe' archive.
Blueprints: Bugs which I was working on: Cross-compiler packages miss libgcc dbg packages breaking xdeb [cross] cross-gcc-4.4 package should provide $triplet-gcc, g++ etc. symlinks [cross] create libgcc1 and gcc-*-base packages for stage2 build [cross] gcc-4.5-armel-cross_1.35 fails to build due to genchanges warnings dpkg-cross does not do sensible things with multi-arch: same packages Merge dpkg-cross 2.6.2 (universe) from Debian unstable (main) PPA:
Worked directly with maintainers of affected packages: Working also with Ubuntu/ARM members, Linaro, and Emdebian developers.
Too complicated descriptions of how to became Ubuntu developer/member. It looks like you can be UD but not UM etc.
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.
I've sponsored some debdiffs from Marcin. Either on random small issues he was fixing, or on his own packages. As I knew Marcin came from an OpenEmbedded background, I was impressed by how fast he grasped Debian-style packaging. He faced some though problems when building cross-compiler packages over the maverick and natty cycles, often entangling complex and uncommon debian/rules and situations. He worked very hard until he killed each issue, and managed to deliver the UDS-specified functionality as expected. Sometimes, I fixed up minor things; often style issues rather than serious problems. Overall, I think Marcin is starting to develop a Debian packaging culture, and feels more and more confortable touching packages.
For the past six months Marcin has been wrangling the ARM cross-toolchain packages in maverick and natty, by far some of the trickiest bits of packaging we have in the archive, and he's given us the first ever set of official cross-toolchain packages in a form that's not only usable, but maintainable and reusable. There are still many fine details of Debian packaging that he's unfamiliar with, but he accepts feedback graciously and learns from mistakes.
Who I am
My Ubuntu story
My involvement
Examples of my work / Things I'm proud of
Areas of work
Things I could do better
Plans for the future
General
What I like least in Ubuntu
Comments
Endorsements
Loïc Minier
Steve Langasek
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 ===