|Deletions are marked like this.||Additions are marked like this.|
|Line 15:||Line 15:|
|== Reason's for Applying to MOTU ==||== Applying to MOTU ==|
|Line 27:||Line 27:|
|* Getting packages upstreamed ( for eg. [[http://metadata.ftp-master.debian.org/changelogs//main/k/kscreen/kscreen_220.127.116.11-1_changelog|kscreen]] and [[http://metadata.ftp-master.debian.org/changelogs//main/libk/libkscreen/libkscreen_1.0.3-1_changelog|libkscreen]]||* Getting packages upstreamed ( for eg. [[http://metadata.ftp-master.debian.org/changelogs//main/k/kscreen/kscreen_18.104.22.168-1_changelog|kscreen]] and [[http://metadata.ftp-master.debian.org/changelogs//main/libk/libkscreen/libkscreen_1.0.3-1_changelog|libkscreen]] )|
|Line 38:||Line 38:|
|* New Driver Manager module for Kubuntu in 14.04 so we could move to the fancy new ubuntu-drivers backend|
I, Rohan Garg, apply for MOTU.
Who I am
I'm a Kubuntu developer, trying to make K/Ubuntu the best distro in the world
My Ubuntu story
Started using K/Ubuntu in late 2008 and found quite some bugs at which point I was invited to fix them in #kubuntu-devel. Got acquainted with packaging over the next couple of months after which most of my work has been with the Kubuntu team with the occasional fix to libraries that support KDE packages.
Applying to MOTU
I'd like to not be restricted to KDE stuff but also have a wider access to other Ubuntu packages in general so that I may be able to fix packages as I encounter them in the ubuntu archive.
Examples of my work / Things I'm proud of
Areas of work
- Packaging new KDE SC releases:
- Getting the newest KDE software releases into Kubuntu ASAP together with the rest of the Ninjas and the other kubuntu-devs.
- Orchrestrating ISO builds for Project Neon 5 which provide a easy mechanism to test the upcoming Plasma Workspaces 5 and KDE Frameworks 5
- Testing alpha releases:
- I'm usually using the devel release as my main environment to notice regressions as quickly as possible.
Co-maintaining Project Neon & Project Neon 5:
- Making sure current KDE svn trunk / git master builds on kubuntu and notifying upstream developers if something got broken on their side.
- Managing the KDE SC packaging of the ninjas:
- Informing people what work is to be done, coordinating it and keeping track of what the debian-qt-kde team does so we keep duplicating work to a minimum.
Full list of my package uploads:
- What of the work I've done so far ended up in the archive.
- New Driver Manager module for Kubuntu in 14.04 so we could move to the fancy new ubuntu-drivers backend
- Started merging KDE SC packaging from Debian
- Updating KDE Telepathy and getting it into the archives
- Mediating between upstream KDE projects and Kubuntu to get features that we required in Kubuntu and/or fixing bugs myself at times
- Successfully resurrecting Project Neon together with Philip and Michal and maintaining it.
- Merging KDE packages from debian.
- Getting upstream copyrights fixed during 4.7 split as most upstream maintainers forgot to fix that during the git move.
Getting twitter API keys replaced in choqok since they posed a security risk and twitter threatened to ban the keys choqok shipped http://arst.ch/ma1
Things I could do better
Better checking of SRU , sometimes I miss things, just need to check things a bit more thoroughly with those
Plans for the future
What I like least in Ubuntu
Currently, the thing I like the least is the Mir situation. Primarily because Unity is moving towards a Mir world and KDE/GNOME/etc have choosen to stick with Wayland. This represents a huge problem for users who are using one DE and want to try out Unity and vice versa. I fear that switching DE's is not going to be a pleasant experience for users, however, we still have some time to switch to Mir/Wayland, so we'll cross this bridge when we come to it, and when we do, I hope we can work out a solution that suits everyone's needs
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.
== <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.'' ## Full list of sponsored packages can be generated here: ## http://ubuntu-dev.alioth.debian.org/cgi-bin/ubuntu-sponsorships.cgi? === Areas of Improvement ===