KubuntuDeveloperApplication
|
Size: 5636
Comment:
|
← Revision 46 as of 2017-02-09 16:30:10 ⇥
Size: 8750
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''<<BR>><<TableOfContents(2)>>|| | ## page was renamed from RikMills/DeveloperApplication ## page was copied from UbuntuDevelopment/DeveloperApplicationTemplate |
| Line 3: | Line 4: |
| ||<tablestyle="float:right; position:relative; top:-10px; font-size: 0.9em; width:30%; background:#F1F1ED; margin: 0 0 1em 1em;border: solid 1px LightGrey;" style="padding:0.5em;"><<TableOfContents>>|| | |
| Line 4: | Line 6: |
| ---- '''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. ---- '''I, <YOUR NAME>, apply for <universe-contributor|MOTU|core-dev|upload rights for package(s) <X>>.''' || '''Name''' || <YOUR NAME> || || '''Launchpad Page''' || <link to your launchpad page> || || '''Wiki Page''' || <link to your Wiki page> || |
||<tablestyle="position: relative; top: 0px;margin: 1em;">{{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 ([[http://www.timeanddate.com/worldclock/city.html?n=136|current time]]) || || {{https://launchpad.net/favicon.ico}} ` `'''Launchpad Profile:''' || [[https://launchpad.net/~rikmills|~rikmills]]|| || {{https://launchpad.net/@@/mail}} ` `'''Email:''' ||rikmills[@]kubuntu[DOT]org || || {{https://launchpad.net/@@/language}} ` `'''IRC:''' || acheronuk on irc.freenode.net || || {{https://launchpadlibrarian.net/44285406/kubuntu-circle-small.png}} ` `'''Forum (www.kubuntuforums.net''') || User: [[https://www.kubuntuforums.net/member.php?30786-acheron|acheron]] || |
| Line 20: | Line 15: |
| ''Tell us a bit about yourself.'' | |
| Line 22: | Line 16: |
| = My Ubuntu story = ''Tell us how and when you got involved, what you liked working on and what you could probably do better.'' |
Hi, I'm a long time Kubuntu user who has decided it is time to step up to help the distribution/flavour that has been of such benefit to me over the years. |
| Line 25: | Line 18: |
| == My involvement == == Examples of my work / Things I'm proud of == |
Kubuntu's strap-line is "Kubuntu, making your PC friendly" and I see this as a core aim of the project, and something to always aim to improve on. = My Kubuntu story = I started using Linux/Unix at University, and carried on using Linux/Unix for post-grad research. I have also used desktop Linux such as Suse - Mandrake - Mandriva over the years. After the Mandriva 'disappearance' I switched to Kubuntu, and have never regretted that move. At the very end on 2015 I popped onto the #kubuntu-dev IRC channel to report some issues with new plasma in the ppas, and progressively from then chatted more with the Kubuntu team and got involved in first testing, and than packaging and other aspects of development. = My involvement = |
| Line 28: | Line 29: |
| Non-checkbox areas of work within Ubuntu include [[https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/727416|Ubiquity]] and [[https://code.launchpad.net/~roadmr/ubuntu/natty/casper/709364||Casper]] (that bug resurfaced [[https://bugs.launchpad.net/ubuntu/+source/casper/+bug/809885|here]] and Stéphane Graber was kind enough to squash it). The folks in charge of these projects are always very responsive and patient, which I really appreciate. | === Kubuntu packaging === |
| Line 30: | Line 31: |
| Checkbox's situation has changed in the past several months. The Hardware Certification team has been growing in terms of people who can devote time working on Checkbox. This has meant we're much more able to tackle the large bug backlog the project had, while also adding new features and keeping up to date with Ubuntu's evolution. Since a large part of Checkbox are the test scripts, and these need to interact with the kernel and other APIs that keep evolving, they need constant maintenance and updating. Examples that come to mind are the recent migration to UDisks2 (for Ubuntu Quantal), the upgrade to Python3 (Quantal as well), migration to Gtk3 (for Ubuntu 11.10), and changes to APIs for Network Manager. | * Determining and making fixes for packages in the Kubuntu CI (continuous integration) system, fixing automatic branch merges made by the CI when required, and generally triggering and pausing jobs to ease the smooth running of the CI. Now in recent months, administering the Kubuntu CI, backporting and adding new build dependencies (inc. Qt). * Determining, making and uploading fixes for staged releases of KDE Frameworks, Plasma & Applications in the Kubuntu ppas. * Reviewing and carrying out merges proposed against the Kubuntu packaging git repositories. * Staging bugfix and version updates of frameworks and plasma and applications. * Backported builds of Qt to Kubuntu ppas prior to the landing of this Qt version in Ubuntu. This allowed the team to start working on the staging of dependent KDE versions (e.g. Plasma 5.7.x). Also added to the KCI to allow upstream builds to continue. * Attending Kubuntu Ninja Packaging Dojos. * Made member of Kubuntu Ninja packaging team on 2016-07-05. * My list of [[https://launchpad.net/~rikmills/+related-packages|package uploads]]. === Testing & bug reports === |
| Line 32: | Line 42: |
| As a team we've managed to greatly reduce the amount of open and new bugs for [https://bugs.launchpad.net/ubuntu/+source/checkbox/||ubuntu/checkbox]] (Currently 16 open bugs and 2 new ones). Checkbox's trunk/upstream branch still has a large number of open bugs (bug list [[https://bugs.launchpad.net/checkbox/|here]]). However we've drastically reduced the number of open (unlooked-at) ones, and I've been focusing on analyzing open bugs and giving them a clear "statement of work" for developers to work on; this way they can potentially jump straight into coding a solution. I felt this was more conducent to many people working on these triaged bugs, as opposed to i.e. me going over them one-by-one, analyzing, and fixing them. This way developers, both from our team and outside, can work in "parallel" to fix these bugs, and they also don't need to spare brainpower finding a bug to fix. | * Running the development version of Kubuntu on my main machine in order to test and understand the evolution of the user experience, and investigate issues. * Reporting, confirming and testing for bug reports; both in Kubuntu and upstream to KDE. * Testing on PC, laptop and various virtual machines newly staged versions of Frameworks, Plasma & Applications, and then continuing to test and report issues once these reach the landing ppas. * Testing of daily ISOs for function and install. * Testing of candidate ISOs for milestone releases (e.g. Xenial 16.04.1) |
| Line 34: | Line 48: |
| I've also been trying to tag smaller bugs with "bitesize" to encourage community participation. This has indeed resulted in a few of these bugs being fixed by community members. We've also tried to be extra responsive to contributions to Checkbox from outside the certification team, to further encourage contributions, this has also resulted in more people knowing about checkbox and potentially considering it when searching for a test runner application. As a result the number of commits per release has grown dramatically, from 30 for the Natty cycle to 217 for the Oneiric cycle, 334 for Precise and 301 for Quantal. Particularly for the Precise cycle, this resulted in our uploads to Ubuntu having very large changelogs, which made reviewers' lives difficult. So for Quantal, despite having slightly less commits and bugfixes, we had a more regular upload cadence, with smaller changesets to ease work for reviewers and sponsors. Also, in order to ensure our package uploads are sane, we've been ramping up our "unit test" coverage, which also validates that data files contain no errors, that translated versions don't cause crashes, and that the code passes some basic "lint" tests. These processes have already caught a few errors. We complement this with a daily from-trunk PPA build which sends a notification if these automated tests fail, so we can catch these basic problems even if some bogus code makes it into the trunk branch. |
|
| Line 42: | Line 51: |
| * My base coding skills could be improved. C++/Python namely * Better knowledge of autopackagetests * Really need to get to grips with copyright files |
|
| Line 43: | Line 56: |
| == General == == What I like least in Ubuntu == ''Please describe what you like least in Ubuntu and what thoughts do you have about fixing it.'' |
* Continue to increase my knowledge and skill base. * Try to work better with, and perhaps contribute to, other projects. For example KDE (including Neon) and Debian. * I would like to help Kubuntu regain some (perceived) lost ground, and get it back to being more of the 'goto' KDE Linux distribution. == What I like least in K/Ubuntu == To be frank, the limitations imposed by the release cycle and it's freezes and debian imports/syncs. This is a tough issue to make significant improvement on, but things like: * making sure we are as up to date as possible in our work. * giving a good offing of updates via the ppas, or archive when possible. * talking and cooperating with upstream (KDE/debian) or other projects such as Neon, to help them and us progress better and quicker. * maybe examine other delivery methods for applications that are otherwise problematic to provide as always up to date. e.g. via snaps, flatpak etc. can certainly help greatly. |
| Line 50: | Line 77: |
| I'm very happy to see Rik step up and apply for Kubuntu Developer. Since he first began contributing, he's cheerfully picked up whatever jobs needed doing, asking for help or explanations along the way if needed. That is so refreshing. In addition, Rik worked and still works with everybody, including the Plasma and Neon teams. Rik knows that becoming a Kubuntu Developer will help the project, so he's applying. That is awesome. -- [[LaunchpadHome:valorie-zimmerman]] <<DateTime(2017-01-05T19:21:10-0800)>> Rik has been a HUGE help and supportive member of the Kubuntu Community in everything from tech support to development. He has an amazing work ethic and works with very well with many teams in and out of the Ubuntu and KDE community. -- [[LaunchpadHome:aaronhoneycutt]] -- [[LaunchpadHome:aaronhoneycutt]] <<DateTime(2017-01-06T00:26:06-0500)>> |
|
| Line 54: | Line 88: |
| == Clive Johnston == === General feedback === I have worked very closely with Rik before and since being accepted as a Kubuntu Developer myself, in October 2016. To date, I have sponsored packages from KDE Frameworks and Plasma, and we are currently working on KDE Applications 16.12. Rik is extremely conscience regarding his work and often pulls me up on some of mine! I fully trust his decision making process and the conclusions he reaches. If he is unsure about anything, he will ask others and will only proceed when in posession of all facts and factors. |
|
| Line 55: | Line 92: |
| === Specific Experiences of working together === Rik and Santa worked well together in getting Yakkety released and out the door. Since then Rik has worked hard on the development branch 17.04, codenamed Zesty Zapus. He has also been heavily involved in moving the Kubuntu Continuous Integration (KCI) server to a new, faster server, a task that he has learned a lot and I think secretly enjoyed :) Rik has also been involved with helping users via bug reports and online forums, often trying to replicate the issue and then researching a fix. His ability to investigate problems never ceases to amaze me. A list of Rik's uploads can be found here - https://launchpad.net/~rikmills/+uploaded-packages === Areas of Improvement === I can't think of any area of improvement, only suggest that he keeps doing what he has been doing, learning new things and passing them on to the team. One area we are all lacking in is proper and up-to-date documentation, something that needs to be looked at and some progress made on. -- [[LaunchpadHome:clivejo]] <<DateTime(2017-01-03T21:31:12Z)>> |
|
| Line 65: | Line 113: |
| ## Full list of sponsored packages can be generated here: ## http://ubuntu-dev.alioth.debian.org/cgi-bin/ubuntu-sponsorships.cgi? |
Contents |
|
Rik Mills |
|
United Kingdom |
|
GMT/UTC, observe DST (current time) |
|
|
|
rikmills[@]kubuntu[DOT]org |
|
acheronuk on irc.freenode.net |
|
User: acheron |
Who I am
Hi, I'm a long time Kubuntu user who has decided it is time to step up to help the distribution/flavour that has been of such benefit to me over the years.
Kubuntu's strap-line is "Kubuntu, making your PC friendly" and I see this as a core aim of the project, and something to always aim to improve on.
My Kubuntu story
I started using Linux/Unix at University, and carried on using Linux/Unix for post-grad research. I have also used desktop Linux such as Suse - Mandrake - Mandriva over the years.
After the Mandriva 'disappearance' I switched to Kubuntu, and have never regretted that move.
At the very end on 2015 I popped onto the #kubuntu-dev IRC channel to report some issues with new plasma in the ppas, and progressively from then chatted more with the Kubuntu team and got involved in first testing, and than packaging and other aspects of development.
My involvement
Areas of work
Kubuntu packaging
- Determining and making fixes for packages in the Kubuntu CI (continuous integration) system, fixing automatic branch merges made by the CI when required, and generally triggering and pausing jobs to ease the smooth running of the CI. Now in recent months, administering the Kubuntu CI, backporting and adding new build dependencies (inc. Qt).
Determining, making and uploading fixes for staged releases of KDE Frameworks, Plasma & Applications in the Kubuntu ppas.
- Reviewing and carrying out merges proposed against the Kubuntu packaging git repositories.
- Staging bugfix and version updates of frameworks and plasma and applications.
- Backported builds of Qt to Kubuntu ppas prior to the landing of this Qt version in Ubuntu. This allowed the team to start working on the staging of dependent KDE versions (e.g. Plasma 5.7.x). Also added to the KCI to allow upstream builds to continue.
- Attending Kubuntu Ninja Packaging Dojos.
- Made member of Kubuntu Ninja packaging team on 2016-07-05.
My list of package uploads.
Testing & bug reports
- Running the development version of Kubuntu on my main machine in order to test and understand the evolution of the user experience, and investigate issues.
- Reporting, confirming and testing for bug reports; both in Kubuntu and upstream to KDE.
Testing on PC, laptop and various virtual machines newly staged versions of Frameworks, Plasma & Applications, and then continuing to test and report issues once these reach the landing ppas.
- Testing of daily ISOs for function and install.
- Testing of candidate ISOs for milestone releases (e.g. Xenial 16.04.1)
Things I could do better
- My base coding skills could be improved. C++/Python namely
- Better knowledge of autopackagetests
- Really need to get to grips with copyright files
Plans for the future
- Continue to increase my knowledge and skill base.
- Try to work better with, and perhaps contribute to, other projects. For example KDE (including Neon) and Debian.
- I would like to help Kubuntu regain some (perceived) lost ground, and get it back to being more of the 'goto' KDE Linux distribution.
What I like least in K/Ubuntu
To be frank, the limitations imposed by the release cycle and it's freezes and debian imports/syncs. This is a tough issue to make significant improvement on, but things like:
- making sure we are as up to date as possible in our work.
- giving a good offing of updates via the ppas, or archive when possible.
- talking and cooperating with upstream (KDE/debian) or other projects such as Neon, to help them and us progress better and quicker.
- maybe examine other delivery methods for applications that are otherwise problematic to provide as always up to date. e.g. via snaps, flatpak etc.
can certainly help greatly.
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@.
I'm very happy to see Rik step up and apply for Kubuntu Developer. Since he first began contributing, he's cheerfully picked up whatever jobs needed doing, asking for help or explanations along the way if needed. That is so refreshing. In addition, Rik worked and still works with everybody, including the Plasma and Neon teams.
Rik knows that becoming a Kubuntu Developer will help the project, so he's applying. That is awesome. -- valorie-zimmerman 2017-01-06 03:21:10
Rik has been a HUGE help and supportive member of the Kubuntu Community in everything from tech support to development. He has an amazing work ethic and works with very well with many teams in and out of the Ubuntu and KDE community.
-- aaronhoneycutt -- aaronhoneycutt 2017-01-06 05:26:06
Endorsements
As a sponsor, just copy the template below, fill it out and add it to this section.
Clive Johnston
General feedback
I have worked very closely with Rik before and since being accepted as a Kubuntu Developer myself, in October 2016. To date, I have sponsored packages from KDE Frameworks and Plasma, and we are currently working on KDE Applications 16.12. Rik is extremely conscience regarding his work and often pulls me up on some of mine! I fully trust his decision making process and the conclusions he reaches. If he is unsure about anything, he will ask others and will only proceed when in posession of all facts and factors.
Specific Experiences of working together
Rik and Santa worked well together in getting Yakkety released and out the door. Since then Rik has worked hard on the development branch 17.04, codenamed Zesty Zapus. He has also been heavily involved in moving the Kubuntu Continuous Integration (KCI) server to a new, faster server, a task that he has learned a lot and I think secretly enjoyed
Rik has also been involved with helping users via bug reports and online forums, often trying to replicate the issue and then researching a fix. His ability to investigate problems never ceases to amaze me.
A list of Rik's uploads can be found here - https://launchpad.net/~rikmills/+uploaded-packages
Areas of Improvement
I can't think of any area of improvement, only suggest that he keeps doing what he has been doing, learning new things and passing them on to the team. One area we are all lacking in is proper and up-to-date documentation, something that needs to be looked at and some progress made on.
-- clivejo 2017-01-03 21:31:12
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: ## http://ubuntu-dev.alioth.debian.org/cgi-bin/ubuntu-sponsorships.cgi? === Areas of Improvement ===
RikMills/KubuntuDeveloperApplication (last edited 2017-02-09 16:30:10 by rikmills)
Location:
Forum (www.kubuntuforums.net)