MOTU

Differences between revisions 2 and 4 (spanning 2 versions)
Revision 2 as of 2019-03-19 19:58:05
Size: 3273
Editor: rikmills
Comment:
Revision 4 as of 2019-03-20 07:39:22
Size: 4579
Editor: rikmills
Comment:
Deletions are marked like this. Additions are marked like this.
Line 15: Line 15:
''Remove any reasons that don't apply, add any extra reasons and edit as
needed. These examples are the common cases, but are not a hard requirement for applications.''
The template suggested reasons do of course apply in my case, as in:
Line 20: Line 18:
However additional factors and nuances are:
 * Being able to upload new source packages to NEW queue in development releases. KDE development is fast moving and relentless, and does not wait for Debian. This applies both to KDE components and any new dependencies they may require. These would of course be subject to review, and would be taken with careful consideration and consultation, as has been the case in previous sponsored cases.
 * Helping with transitions. KDE packages have large range of dependencies across the archive, and as such often get entangled more than most packagesets in ongoing transitions. As such, and in a spirit of helping generally, it would be highly beneficial if I could myself do no-change rebuilds, clear fixes, retries of autopkgtests where appropriate, across the breadth of Universe and Multiverse. I already do as much as I practically can in this regard (Qt/poppler transitions etc), but am at times hampered.
 * In general be able to give back a bit more in terms of general work on Ubuntu and flavours. I (and Kubuntu) already receive a lot of generous help from Core Developers, existing MOTU, and other flavours. MOTU would enable me to give more back in return.
Line 22: Line 25:
''Tell us a bit about yourself.'' I am a long time Kubuntu (and other flavour) user who decided several years ago to step up to help the distribution/flavour that has been of such benefit to me over the years. I have been a Kubuntu developer since febuary 2017.

I, Rik Mills, apply for MOTU upload rights.

https://launchpad.net/@@/person  Name:

Rik Mills

https://launchpadlibrarian.net/16121192/gem-sm.png  Location:

United Kingdom

https://blueprints.launchpad.net/@@/meeting  Timezone:

GMT/UTC, observe DST (current time)

https://launchpad.net/favicon.ico  Launchpad Profile:

~rikmills

https://launchpad.net/@@/mail  Email:

rikmills[@]kubuntu[DOT]org

https://launchpad.net/@@/language  IRC:

acheronuk on irc.freenode.net

I am applying because:

The template suggested reasons do of course apply in my case, as in:

  • I'd like to eliminate delays in getting my work sponsored.
  • I'd like to reduce the burden on my sponsors.

However additional factors and nuances are:

  • Being able to upload new source packages to NEW queue in development releases. KDE development is fast moving and relentless, and does not wait for Debian. This applies both to KDE components and any new dependencies they may require. These would of course be subject to review, and would be taken with careful consideration and consultation, as has been the case in previous sponsored cases.
  • Helping with transitions. KDE packages have large range of dependencies across the archive, and as such often get entangled more than most packagesets in ongoing transitions. As such, and in a spirit of helping generally, it would be highly beneficial if I could myself do no-change rebuilds, clear fixes, retries of autopkgtests where appropriate, across the breadth of Universe and Multiverse. I already do as much as I practically can in this regard (Qt/poppler transitions etc), but am at times hampered.
  • In general be able to give back a bit more in terms of general work on Ubuntu and flavours. I (and Kubuntu) already receive a lot of generous help from Core Developers, existing MOTU, and other flavours. MOTU would enable me to give more back in return.

Who I am

I am a long time Kubuntu (and other flavour) user who decided several years ago to step up to help the distribution/flavour that has been of such benefit to me over the years. I have been a Kubuntu developer since febuary 2017.

My Ubuntu story

Tell us how and when you got involved, what you liked working on and what you could probably do better.

My involvement

Examples of my work / Things I'm proud of

Include your existing sponsored uploads for the packages for which you are seeking upload rights. You can link directly to an upload by following this pattern.

Areas of work

Let us know what you worked on, with which development teams / developers with whom you cooperated and how it worked out.

Things I could do better

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.''
## Full list of sponsored packages can be generated here:
##  https://udd.debian.org/cgi-bin/ubuntu-sponsorships.cgi
=== Areas of Improvement ===


RikMills/Applications/MOTU (last edited 2019-03-25 17:12:36 by rikmills)