Mailinglist Archive: opensuse-kde (192 mails)
| < Previous | Next > |
Re: [opensuse-kde] Membership Request
- From: Will Stephenson <wstephenson@xxxxxxx>
- Date: Wed, 19 Aug 2009 11:01:57 +0200
- Message-id: <200908191101.57918.wstephenson@xxxxxxx>
On Tuesday 18 August 2009 19:53:39 Sascha 'saigkill' Manns wrote:
Granted! Anyone else like an opensuse-kde membership badge?
Tell us about them, and why you build them...
As I said on IRC, find an area that you enjoy working on. It can be a deep
area like single app that you use a lot and like getting the most out of, and
you have a good overview of the bugs and upstream developments. Then you can
use this expertise to help users, triage incoming bugs, integrate important
bugfixes from upstream into our Factory packages.
Or it can be a broad theme like notifications or usability, where you look all
over the desktop for little areas that can be improved, talk to upstream, make
little patches that get tested in openSUSE KKFD then merged upstream. As an
example take the Filter Toolbar in Dolphin, that during the last meeting we
realised was hard to add to the toolbar because it had no icon by default, so
I searched the code, added an icon, got upstream's approval and committed the
change.
Or you can become a packaging ninja, help everyone fix problems in their
packaging, and notice shortcuts and optimisations that make packaging easier
and higher quality for everyone.
Or you can become a pure coder, where you see something that is missing in
openSUSE-KDE and implement it - for example a Build Service plasmoid that lets
you keep track of build status - then let others package it.
The tried and tested route in is to try a few things, maintain a few packages,
then as your expertise grows you will find yourself naturally specialising in
fewer areas that really interest you.
HTH
Will
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kde+help@xxxxxxxxxxxx
Hello Mates,
i would like to request an membership in opensuse-kde.
Granted! Anyone else like an opensuse-kde membership badge?
Most of my Time i'm building Packages (some are in KDE:KDE4:Community).
Tell us about them, and why you build them...
But Will told me, that you are happy for new workers.
So what can i do?
Maybe:: Repository Maintaining or what you want.
As I said on IRC, find an area that you enjoy working on. It can be a deep
area like single app that you use a lot and like getting the most out of, and
you have a good overview of the bugs and upstream developments. Then you can
use this expertise to help users, triage incoming bugs, integrate important
bugfixes from upstream into our Factory packages.
Or it can be a broad theme like notifications or usability, where you look all
over the desktop for little areas that can be improved, talk to upstream, make
little patches that get tested in openSUSE KKFD then merged upstream. As an
example take the Filter Toolbar in Dolphin, that during the last meeting we
realised was hard to add to the toolbar because it had no icon by default, so
I searched the code, added an icon, got upstream's approval and committed the
change.
Or you can become a packaging ninja, help everyone fix problems in their
packaging, and notice shortcuts and optimisations that make packaging easier
and higher quality for everyone.
Or you can become a pure coder, where you see something that is missing in
openSUSE-KDE and implement it - for example a Build Service plasmoid that lets
you keep track of build status - then let others package it.
The tried and tested route in is to try a few things, maintain a few packages,
then as your expertise grows you will find yourself naturally specialising in
fewer areas that really interest you.
HTH
Will
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kde+help@xxxxxxxxxxxx
| < Previous | Next > |