[Pkg-kde-extras] Helping KDE Extra (klibido)

[Pierre Habouzit]

Le ven 28 juillet 2006 11:32, Jérôme Marant a écrit :
> Hello,
>
> I've been using KDE for many months now and I'd like to help a bit,
> especially Klibido I use a lot (I submitted a small patch recently).
>
> How can I help?
>
> Cheers,

by joining the team, not only kde extra btw.

You have the qt/kde team that handles (mostly) qt3/4 and kde official 
modules, and the kde extra team that handles third party applications.

The teams are a bit different especially because kde official modules 
are really big, and nasty to package, and that it's already a full time 
job. Though e.g. I do a lot of sponsoring for kde extra team members, 
that do not have upload rignts.

the kde team is mostly centered on the following lists:
 - debian-qt-kde at l.d.o (receive bug reports mostly)
 - pkg-kde-talk at l.a.d.o (the packager list)

the kde extra team on that one you mailed to.

both teams use pkg-kde-bugs-fwd at l.d.a.o to receive upstream bugzillas 
bug reports (for packages hosted on bugs.d.o) and 
pkg-kde-commits at l.a.d.o for svn commit mails.

there is also a #debian-qt-kde channel on OFTC.


In order to help, you have to get added to the pkg-kde alioth project 
(i'm not an admin, so you will have to ask to christopher martin or 
adeodato simó that are admins IIRC). and then to have commits rights on 
the svn.

then, it's the usual stuff: bug triaging (like dealing the nasty stupid 
automake detection for a recent stuff), preparing uploads, well 
maintenance basically.

the kde extra packages are packaged by the team to centralize bug 
reports, but are still maintained by the person(s) listed in the 
Uploader field. so if there is specifical packages you want to work on, 
you have to ask the Uploader if he seeks for co-maintenance (more than 
the urgency support that the rest of the team gives)

Else, I can tell you that help on the official modules is always 
welcomed. I did (and was helped a lot) a big work of bug triaging (we 
closed sth like 400 or 500 of obsolete bugs in sth like a month). It's 
also much apreciated to forward bugs into the bugs.kde.org bugzilla, 
and let bts-link triage it for us.

There is a lot of bad/useless bug reports on the BTS. the policy is:
 * ping the submitter, ask for more details (like a valid backtrace)
 * if no answer since more than a week, if you have time, still try to
   reproduce (else just don't), and if you can't get anything useful,
   just close it.

we have all the necessary -dbg packages in the archive to produce such 
backtraces, and the kde crash handler just do things fine. so it's not 
a big hassle to ask users to do that, and saves us a lot.

if you have that, forward the bug to the kde bugzilla (that's the long 
thing to do) and mark the BTS bug as forwarded. bts-link tracks 
upstream bug status change for us, and you just have to look at the 
bugs tagged 'fixed-upstream' when you will upload to see if they 
concern your upload.

Here are our ways. Just pick what you want to do, there is work for 
everyone.
-- 
·O·  Pierre Habouzit
··O                                                madcoder at debian.org
OOO                                                http://www.madism.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-kde-extras/attachments/20060728/7141907d/attachment.pgp