I, Marcin Juszkiewicz, apply for upload rights for those packages:
Armel ones are in repository, armhf ones provide same features but for different target. There are no code differences between them.
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.
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.
Examples of my work / Things I'm proud of
Bugs which I was working on:
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. Recently started working with Emdebian team on getting my cross toolchain packages working in Debian.
- 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, Linaro, and Emdebian developers.
Things I could do better
- triaging and fixing FTFBS
- improving cross compilation support
Plans for the future
- 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.
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.
== <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 ===