UniverseContributorApplication

I, Ricardo Salveti, apply for universe-contributor.

Name

Ricardo Salveti

Launchpad Page

https://launchpad.net/~rsalveti

Wiki Page

https://wiki.ubuntu.com/RicardoSalveti

Who I am

  • Linux user since 2002
  • Ubuntu and Debian user since 2007 (x86, amd64, armel)
  • Canonical ARM developer since 2010 (working together with the Ubuntu ARM team)
  • Contributions to many OSS over the past few years (OE, Mamona, Maemo, Linux, Gentoo, Ubuntu, etc)

Working with OSS development since 2003, and doing general distro development since 2006. While Gentoo user I contributed with package and kernel fixes. From 2008-10 worked helping created an OpenEmbedded based distro called Mamona. Since 2010 I've being working at Canonical, at the Ubuntu on ARM team, doing development and fixes for the Omap images.

Large experience with SW development, mainly using Python and C. Being a generalist, worked from Kernel to X11, also doing a lot of distro development.

My Ubuntu story

After some long years using Gentoo (also Debian, but mostly at the University), I decided to move to a package oriented distro, and by 2007 Ubuntu seemed the best option around (it was getting quite famous, and most friends were using it already). After using it at most of my X86 servers, I started using it with my EeePC for desktop purposes, helping debugging and fixing the RT2860 wireless driver.

Since July 2010 I've being working at Canonical as an ARM developer, participating at the Ubuntu on ARM team, helping improving the Ubuntu on ARM experience in general.

As a free software enthusiastic I've being always promoting Linux as the main operation system, and Ubuntu was always my recommendation for new users. I'm really happy to see how easy Ubuntu is for general users nowadays.

My involvement

Examples of my work / Things I'm proud of

Contributions to existing packages:

Natty:

  • x-loader: new upstream releases and package maintenance (5 package updates)
  • netbook-launcher-efl: fixing the gnome-session call, and adding proper une-efl.session file to make it work again at Natty
  • evas:
    • Changing OpenGL backend from GL to GLES 2 for ARM
    • Enabling runtime shader compiler for GLES (LP: #727591)

  • mesa-demos: new release based on current git tree and fixes for es2gears
  • clutter: changing default OpenGL backend from GL to GLES2 plus 3 additional GLES patches
  • qt4-x11: changing OpenGL backend from GL to GLES 2 for ARM (LP: #707794)

  • webkit: fixing JIT ARM crashes (LP: #728211)

  • jasper-initramfs: workaround to increase kernel min_free_kbytes to avoid page allocation failures (LP: #746137)

  • opengles-sgx-omap3: new upstream release
  • powervr-omap3: new upstream release

Maverick:

  • pybootchartgui: make pybootchartgui run in devices like beagleboard (LP: #619026)

  • x-loader: make it properly work with Beagle xM (LP: #628243)

  • x-loader-omap4: added all needed patches to have proper Panda support (3 packages update).
  • rootstock: new upstream release
  • jasper-initramfs:
    • Add correct mem argument for Panda ES2 (for 1gb) (LP: #629269)

    • fixing swap file creation, as it can't use a sparse file (LP: #627201)

New Packages:

Kernel fixes:

  • 2.6.35-20.2 and 2.6.35-903.9: Fixing beagle and panda LED support
  • 2.6.35-23.36: Remove CONFIG_FIXED_PHY and move CONFIG_SMSC911X from m to y for omap (LP: #645689)

  • 2.6.38-1.28: fix display for Beagle
  • 2.6.38-2.29: don't warn the user with a trace in case of PM34XX_ERRATUM
  • 2.6.35-903.13: OMAP: Enable needed Errata for OMAP4 to work with DMA based device drivers
  • 2.6.35-903.21: Display fixes for Panda (LP: #653002)

  • 2.6.35-1101.4: enabling CONFIG_TASK_ options for iotop to work (LP: #694461)

  • Linaro 2.6.35-1007.13: Fixing IGEPv2 video output (LP: #607250)

  • 2.6.35-23.39 and Linaro 2.6.35-1008.15: SRU: Fix DVI for Beagle xM rev A3 (LP: #663642)

  • 2.6.38-1206.7: Making it work with SGX

Some few bugs bugs I worked on:

  • 619981: mono apps crash on omap4 due to no smp support for armel

  • 707794: libqt4-opengl on armel should be compiled with OpenGL ES 2.x support

  • 746023: No sound on omap4

  • 664431: Qt on armel is built with NEON by default

  • 770679: Missing proper support for Beagle XM rev B and C

  • 624652: Panda ES2.0: No working x-loader

  • 566645: OTG configuration is broken on omap kernel

  • 633227: instabilities with highmem activated

Worked with normal bugfixing and also with the SRU process (mostly with the kernel updates).

PPA Work (tiomap-dev):

  • New releases of the PowerVR SGX driver for both Maverick and Natty
  • Packages: pvr-omap4 and pvr-omap4-kernel
  • This PPA is activated once the user click at the TI Add-ons icon at the Ubuntu ARM Omap images

Areas of work

  • Ubuntu Kernel fixes
  • X-Loader maintenance
  • GLES support at the archive
  • Usual image testing and bugfixing (jasper, webkit, pvr support for omap)

As a result of my work I've being mostly working with the Ubuntu on ARM team, with the following core developers:

  • Oliver Grawert
  • Michael Casadevall
  • Jani Monoses

Also worked with the Kernel Team improving the ARM support when possible.

Things I could do better

Spending more time helping and fixing the FTBFS for ARM (usually the arch with most FTBFS).

Plans for the future

General

Continue working on improving the ARM experience on Ubuntu, by helping fixing the images and developing new features. Also plan to help maintaining the Beagleboard support, by providing kernel fixes and new releases of the PVR driver.

What I like least in Ubuntu

The SRU process for the kernel takes too much time. During Maverick one simple fix took more than one month to hit the archive, with many test requests until it was released (same test request).

I believe the SRU process could have an easier way to work with, trying to spend less time between bugfixing and actual release of new packages. It's quite frustrated to have a fix and know that it'll only be released for users in a few weeks, or even months.


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@.

Alexandros Frantzis (afrantzis)

Ricardo is a very prolific and capable packager and engineer in general (as the list above clearly shows). Although I haven't been involved in sponsoring any of Ricardo's packages, I have been relying on a number of them for my linaro work (mesa-utils-extra, clutter, pvr-omap4) and his work has always been superb. Beyond his technical skills, he is also a great person to work with: when I found some some issues in the pvr-omap4 packaging that were blocking my work, Ricardo was very responsive and open to ideas and discussion and produced an excellent solution to the problem. I believe he is a valuable addition to the Ubuntu community.


Endorsements

Jani Monoses

General feedback

I trust Ricardo to create great package uploads. I have sponsored some of his recent work related to ARM boot loaders, miscellaneous FTBFS fixes concerning ARM GLES, and OMAP graphics driver packages. He always does extensive testing before requesting sponsoring so I never had to ask for any change nor did any of the uploads need further fixing after in the archive. He works well with upstreams, picking relevant fixes and attributing them correctly in the changelogs. He understands well the packages he works on.

Specific Experiences of working together

He'd ping me on IRC or via email (or ask for any sponsor on IRC and I'd offer) with a short description of why an upload is needed, and links to debdiff/bzr branch and link to tested src (and sometimes deb) packages to try out. They were all short experiences, as there was not much to discuss. He only needs sponsoring, not mentoring.

Areas of Improvement

UDD, the keeping in sync of packages and bzr branches is not the easiest thing. The only occasion I remember needing to do a bit more work when sponsoring Ricardo is fixing up UNRELEASED/natty in the changelog and setting a proper bzr release tag. But I suspect my lack of experience (and discomfort) with UDD also played a significant role in this taking more time than it should have.

Oliver Grawert

Working with Ricardo is a pleasure, i sponsored plenty of uploads for him which were in a good enough quality that nobody had to touch them. Technically his packaging work is outstanding and at a level where he definitely should get the ability to upload his changes himself.

Even though Ricardo works on ARM stuff on a day to day basis, he additionally puts spare time and after hour work into helping the community and giving support in areas that don't necessarily touch his work area.

Ricardo is a big addition to our ARM community and a person that will give you reliable help in the #ubuntu-arm channel if you have any issue.

Since working in the ARM world usually means that you have to touch packages all across the archive so his granted upload rights should cover this.

When Ricardo joined the ARM team he immediately took over rootstock which is a tool to enable the wider community to roll rootfses for unsupported hardware. He improved the existing code massively and is very responsive on bugs, if a community person has problems building images you can rely on him providing or merging a fix in nearly no time. The same goes for his other areas of work (bootloaders, graphics drivers on ARM, the GLES stack) as well.

Michael Casadevall (NCommander)

I've worked with Ricardo on the Ubuntu on ARM project for several months now, and have worked with sponsoring various packages in archive. His work is extremely solid, and has been able to been uploaded as is. He has done considerable and highly impressive work on working on OMAP graphics stack, and I highly recommend him for MOTU status.


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 ===


RicardoSalveti/UniverseContributorApplication (last edited 2011-05-09 14:02:57 by business-89-133-214-82)