DeveloperApplication
|
Size: 2330
Comment:
|
Size: 4117
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
---- '''Please do not edit this page. It is a template to be used by people applying as an Ubuntu developer.''' Head over to https://wiki.ubuntu.com/YourName/YourDeveloperApplication instead and make use of this template. ---- |
|
| Line 20: | Line 12: |
| ''Tell us a bit about yourself.'' | ''Member of the Ubuntu Desktop Team, working as a integration engineer. My primary responsibility is to help the Desktop Experience and Ubuntu One teams get their software into the distro without causing much of a head ache for the rest of the Desktop Team. I have been into packaging since the late 90s, started with rpm, then a number of years with conary and the past couple years dpkg.'' |
| Line 23: | Line 15: |
| ''Tell us how and when you got involved, what you liked working on and what you could probably do better.'' | |
| Line 26: | Line 17: |
| I got involved in Ubuntu when I joined the desktop team, almost 2 years ago. I love working on improving the user experience, and looking at ways we can better tie the pieces of the desktop together with a consistent interaction experience. This passion of mine fits nicely with my role as integration engineer, I get to help deliver the awesome work the DX team does. When I am not helping DX and Ubuntu One with their packages, I am usually hacking on Gwibber, libgwibber or something telepathy related. I think there are good opportunities with those to break the mindset of "an application" vs. "integration points". I would rather people not think they are using gwibber to see what their friends are doing, or using empathy to chat with their friends, but instead realise they are using Ubuntu to socialise. We'll get there :) |
|
| Line 27: | Line 20: |
| Pretty much any package the begins with "indicator-", I maintain. I have also done lots of packaging and bug fixing for empathy, telepathy-* and gwibber packages and assist where ever I can with any of the GNOME packages. |
|
| Line 28: | Line 23: |
| ''Let us know what you worked on, with which development teams / developers you cooperated and how it worked out.'' ## As a per-package uploader, please give us some insight into the package maintenance and bug situation since you're working on it. |
As I mentioned above, I work on the Desktop Team, with a strong focus on the DX and Ubuntu One teams. I keep close tabs on the work those teams are doing, and communicate things that could cause concern to the Desktop Team. Also trying to spot issues early so they can be addressed and ensure their work lands with minimal friction. I drive those teams to a weekly release cadence, to help integrate early and often. This has worked out well for DX, but still working out the kinks for Ubuntu One, they have the added complexity of server side rollouts to match desktop releases. |
| Line 32: | Line 27: |
| Unassign bugs, I generally have way too many bugs assigned to me. I have a bad habit of assigning a bug to myself, knowing I might be the best person to work on it or feel an individual responsibility for the bug and then I end up with a long bug list. I need to get out of the habit and become better at tracking bugs without actually assigning them to myself. |
|
| Line 37: | Line 34: |
Contents |
I, Ken VanDine, apply for core-dev.
Name |
Ken VanDine |
Launchpad Page |
|
Wiki Page |
Who I am
Member of the Ubuntu Desktop Team, working as a integration engineer. My primary responsibility is to help the Desktop Experience and Ubuntu One teams get their software into the distro without causing much of a head ache for the rest of the Desktop Team. I have been into packaging since the late 90s, started with rpm, then a number of years with conary and the past couple years dpkg.
My Ubuntu story
My involvement
I got involved in Ubuntu when I joined the desktop team, almost 2 years ago. I love working on improving the user experience, and looking at ways we can better tie the pieces of the desktop together with a consistent interaction experience. This passion of mine fits nicely with my role as integration engineer, I get to help deliver the awesome work the DX team does. When I am not helping DX and Ubuntu One with their packages, I am usually hacking on Gwibber, libgwibber or something telepathy related. I think there are good opportunities with those to break the mindset of "an application" vs. "integration points". I would rather people not think they are using gwibber to see what their friends are doing, or using empathy to chat with their friends, but instead realise they are using Ubuntu to socialise. We'll get there 
Examples of my work / Things I'm proud of
Pretty much any package the begins with "indicator-", I maintain. I have also done lots of packaging and bug fixing for empathy, telepathy-* and gwibber packages and assist where ever I can with any of the GNOME packages.
Areas of work
As I mentioned above, I work on the Desktop Team, with a strong focus on the DX and Ubuntu One teams. I keep close tabs on the work those teams are doing, and communicate things that could cause concern to the Desktop Team. Also trying to spot issues early so they can be addressed and ensure their work lands with minimal friction. I drive those teams to a weekly release cadence, to help integrate early and often. This has worked out well for DX, but still working out the kinks for Ubuntu One, they have the added complexity of server side rollouts to match desktop releases.
Things I could do better
Unassign bugs, I generally have way too many bugs assigned to me. I have a bad habit of assigning a bug to myself, knowing I might be the best person to work on it or feel an individual responsibility for the bug and then I end up with a long bug list. I need to get out of the habit and become better at tracking bugs without actually assigning them to myself.
Plans for the future
General
What I like least in Ubuntu
Please describe what you like least in Ubuntu and what thoughts do you have about fixing it.
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 ===
KenVanDine/DeveloperApplication (last edited 2010-11-22 09:50:27 by lns-bzn-53-82-65-20-199)