[opensuse-kde] Membership Request
Hello Mates, i would like to request an membership in opensuse-kde. Most of my Time i'm building Packages (some are in KDE:KDE4:Community). But Will told me, that you are happy for new workers. So what can i do? Maybe:: Repository Maintaining or what you want. cu Sascha -- Sincerely yours Sascha Manns openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Tuesday 18 August 2009 19:53:39 Sascha 'saigkill' Manns wrote:
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@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Hi Will, Am Mittwoch 19 August 2009 11:01:57 wrote Will Stephenson:
Most of my Time i'm building Packages (some are in KDE:KDE4:Community).
Tell us about them, and why you build them... I have in KDE:KDE4:Community kde4-skrooge, mountmanager, freeremoted/q libtinyxml, lbdbus++, kpassgen and my newest assuma.
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. If i choose so i would like into KDE:KDE4:Factory as Package Maintainer. I have an Eye to the kdepms. I can review new requests and work on the Packages,
-- Sincerely yours Sascha Manns openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Thursday 20 of August 2009, Sascha 'saigkill' Manns wrote:
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.
If i choose so i would like into KDE:KDE4:Factory as Package Maintainer. I have an Eye to the kdepms. I can review new requests and work on the Packages,
Everybody can work on packages in KDE:KDE4:Factory, just branch them, do the changes and submit them (as explained in http://en.opensuse.org/Build_Service/Collaboration). -- Lubos Lunak KDE developer -------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: l.lunak@suse.cz , l.lunak@kde.org Lihovarska 1060/12 tel: +420 284 084 672 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Am Montag 24 August 2009 12:32:20 wrote Lubos Lunak:
On Thursday 20 of August 2009, Sascha 'saigkill' Manns wrote:
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.
If i choose so i would like into KDE:KDE4:Factory as Package Maintainer. I have an Eye to the kdepms. I can review new requests and work on the Packages,
Everybody can work on packages in KDE:KDE4:Factory, just branch them, do the changes and submit them (as explained in http://en.opensuse.org/Build_Service/Collaboration). Short Question. If i create an Branch, wait some days, and in that time anyone changed the original. Is my branch updated automaticly or must i do this manual?
-- Sincerely yours Sascha Manns openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Am Montag, 24. August 2009 16:55:53 schrieb Sascha 'saigkill' Manns:
Am Montag 24 August 2009 12:32:20 wrote Lubos Lunak:
On Thursday 20 of August 2009, Sascha 'saigkill' Manns wrote:
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.
If i choose so i would like into KDE:KDE4:Factory as Package Maintainer. I have an Eye to the kdepms. I can review new requests and work on the Packages,
Everybody can work on packages in KDE:KDE4:Factory, just branch them, do the changes and submit them (as explained in http://en.opensuse.org/Build_Service/Collaboration).
Short Question. If i create an Branch, wait some days, and in that time anyone changed the original. Is my branch updated automaticly or must i do this manual?
A branch has a source link and as long you do not specify a concret revision to link against, you have always the latest one. That is also the reason why the link might break (when someone submitted conflicting changes below). Just use "osc repairlink" in that case to sort out the conflict. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
participants (4)
-
Adrian Schröter -
Lubos Lunak -
Sascha 'saigkill' Manns -
Will Stephenson