PerPackageUploaderApplication
19767
Comment:
|
20508
Minor adjustments (template related), and added endorsement section
|
Deletions are marked like this. | Additions are marked like this. |
Line 154: | Line 154: |
== General == |
|
Line 165: | Line 167: |
---- = 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 === }}} ---- |
Contents |
I, Luis Henriques, apply for upload rights for the linux-* packages.
Name
Luis Henriques
Launchpad Page
Wiki Page
Who I am
I am Luis Henriques and I work for Canonical as a member of the Ubuntu Kernel Team. Currently, I am a member of the Stable Kernel Team and my main focus is on the SRU process. I also help with bug triagging/fixing and I have interest in any areas relating the kernel, specially core subsystems.
My Ubuntu story
I have been using Debian since I found out about the GNU/Linux operating system (late 1990's). When Ubuntu first appeared, I quickly migrated to it and I've been using it since then.
My involvement
I have joined the Ubuntu Kernel Team in early 2012, and started working with the Stable Kernel Team packaging kernels for the Ubuntu stable releases. Although this has been my main focus, I've also been involved on kernel bugs triagging and fixing. This allowed me to increase my interaction with upstreams, for example by submitting patches to the community.
Examples of my work / Things I'm proud of
The following URL contains the activities I've been involved regarding bugs triage and fixing:
I've also been contacting upstreams (kernel subsystems maintainers, mainly) whenever required. For example, whenever I fix a bug that is also present upstreams.
As my main focus has been on kernel packaging, there are several Linux related packages that I have uploaded into Ubuntu repositories. As I do not have upload rights yet, I always need to find sponsors for these packages. Here's a list of all the packages I have already uploaded:
Summary
Sponsor |
# Packages |
12 |
|
14 |
|
30 |
|
17 |
|
8 |
|
8 |
|
6 |
|
Total packages |
95 |
Details
Package |
Version |
Sponsor |
linux |
||
linux |
||
linux |
||
linux-backports-modules-2.6.24 |
||
linux-ubuntu-modules-2.6.24 |
||
linux-restricted-modules-2.6.24 |
||
linux-meta |
||
linux-ec2 |
||
linux-ec2 |
||
linux-ec2 |
||
linux-backports-modules-2.6.32 |
||
linux |
||
linux |
||
linux |
||
linux-backports-modules-2.6.32 |
||
linux |
||
linux |
||
linux-meta-ec2 |
||
linux-ports-meta |
||
linux-meta |
||
linux-ports-meta |
||
linux-meta |
||
linux |
||
linux-lts-backport-maverick |
||
linux-backports-modules-2.6.38 |
||
linux |
||
linux-lts-backport-natty |
||
linux-backports-modules-2.6.38 |
||
linux |
||
linux-lts-backport-natty |
||
linux |
||
linux-lts-backport-natty |
||
linux |
||
linux-lts-backport-natty |
||
linux |
||
linux-lts-backport-natty |
||
linux |
||
linux-meta-lts-backport-natty |
||
linux-meta |
||
linux-meta-lts-backport-natty |
||
linux-meta |
||
linux-backports-modules-3.0.0 |
||
linux |
||
linux-lts-backport-oneiric |
||
linux-backports-modules-3.0.0 |
||
linux |
||
linux-lts-backport-oneiric |
||
linux-backports-modules-3.0.0 |
||
linux |
||
linux-lts-backport-oneiric |
||
linux-backports-modules-3.0.0 |
||
linux |
||
linux-lts-backport-oneiric |
||
linux-backports-modules-3.0.0 |
||
linux |
||
linux-lts-backport-oneiric |
||
linux-backports-modules-3.0.0 |
||
linux |
||
linux-lts-backport-oneiric |
||
linux-backports-modules-3.0.0 |
||
linux |
||
linux-lts-backport-oneiric |
||
linux-backports-modules-3.0.0 |
||
linux |
||
linux-meta |
||
linux-meta-lts-backport-oneiric |
||
linux-meta |
||
linux-meta |
||
linux-meta-lts-backport-oneiric |
||
linux-meta |
||
linux-meta-lts-backport-oneiric |
||
linux-meta-lts-backport-oneiric |
||
linux-meta |
||
linux-meta-lts-backport-oneiric |
||
linux-meta |
||
linux-meta-lts-backport-oneiric |
||
linux-meta |
||
linux-meta |
||
linux |
||
linux |
||
linux-backports-modules-3.2.0 |
||
linux |
||
linux-backports-modules-3.2.0 |
||
linux |
||
linux-backports-modules-3.2.0 |
||
linux-backports-modules-3.2.0 |
||
linux |
||
linux-backports-modules-3.2.0 |
||
linux |
||
linux |
||
linux-meta |
||
linux-meta |
||
linux-meta |
||
linux-meta |
||
linux-meta |
Areas of work
As referred, my main focus so far has been on kernel packaging for the Kernel Stable Team. Although I've been working more closely with HertonKrzesinski and BradFigg, all the team members that have upload rights have already sponsored my packages.
Things I could do better
Since I started working for Canonical, my main focus has been to learn the best way to do my job. However, I'm sure I've been missing important parts by keeping my focus on pure (stable) kernel issues, and not communicating/interacting with other people/teams. Improving my communication skills and increase my participation (both within the company and with the community) is something I will need to focus.
Plans for the future
General
My short term plan is to get kernel uploads rights so that I can do my job in a more autonomous way, without the overheads of getting sponsors for kernel packages.
I believe that another important area for my current job is to get more involved with QA activities, interacting with teams that are directly related with the testing and certification of kernel packages.
For the medium/long term, I would like to gain more knowledge on the core of the Ubuntu distro. This would allow me to contribute on other aspects that are not kernel-specific.
What I like least in Ubuntu
The only thing I can point at this moment is the fact that it is somewhat difficult to understand all the required interactions between the different teams within Ubuntu. Although I now have a comfortable understanding of the teams I need to communicate with during the SRU cycles, gathering this knowledge was not an easy job.
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 ===
LuisHenriques/PerPackageUploaderApplication (last edited 2012-09-17 10:21:01 by av-217-129-141-167)