--nextPart1725945.CfoZmBAjCg Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline After looking for a while at the current KDE status in Debian and after=20 several talks in IRC with dato, Heimy and suy, we identified several tasks=20 where people can help: * man pages Lots of important KDE commands lack man pages, for example, kstart, konqueror=20 or ksystraycmd. The kdegenman.pl script included in the kdesdk-scripts package can generate a=20 manpage automatically based on the output of the programs with the --help=20 parameter. May be the best method to keep man pages up-to-date for every KDE=20 program is to write a "dh_kdemanpage" helper based in kdegenman.pl. It should take the output of the --help stuff and also a description manually=20 written and create a manpage. * package descriptions Currently, lots of packages don''t have a worthy description, they just include=20 a paragraph talking about KDE and then a single line to describe the package. We need better descriptions for lots of packages, but IIRC there are people=20 already working on this. * check existing bugs Just now kdebase has 466 bugs, kdelibs 53, kdenetwork 83, kdepim 234, ..., we need to check/fix/... that bugs to try to lower the bugs to a reasonable=20 amount. I would like to get some feedback, tasks I''ve forget, ..., I will start=20 checking kdebase bugs this evening. Best regards --nextPart1725945.CfoZmBAjCg Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQBB2T/+QET2GFTmct4RAjwUAJ91KJfzthXCkxEm/VtXUSCWKAtR8ACfaw0J /pGfL3jRHv+2+iTGZt3BYaI=sQJb -----END PGP SIGNATURE----- --nextPart1725945.CfoZmBAjCg--
--nextPart1187924.7Qrgnj9nNc Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Le Lun 3 Janvier 2005 13:52, Isaac Clerencia a =E9crit :> * check existing bugs > Just now kdebase has 466 bugs, kdelibs 53, kdenetwork 83, kdepim 234, > ..., we need to check/fix/... that bugs to try to lower the bugs to a > reasonable amount.the problem is, a lot of them are unreproducible, since they occured=20 only in one version of the package. so what is the policy here ? do we close any bug older than a few month=20 that we cannot reproduce ? or do we try to contact submitter ? =2D-=20 =B7O=B7 Pierre Habouzit =B7=B7O OOO http://www.madism.org --nextPart1187924.7Qrgnj9nNc Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQBB2VDbvGr7W6HudhwRAi/dAJ4zlcCxbLunf6w44k7j0WX+2v6/GgCfcp77 PRWmtP5QzWHb6z0Vxpu2N2E=uGax -----END PGP SIGNATURE----- --nextPart1187924.7Qrgnj9nNc--
* Pierre Habouzit [Mon, 03 Jan 2005 15:04:11 +0100]:> so what is the policy here ? do we close any bug older than a few month > that we cannot reproduce ? or do we try to contact submitter ?no written policy, common sense applies. if you want to have a look, I did some work on kdemultimedia when preparing the experimental upload: http://bugs.debian.org/src:kdemultimedia search for bugs done by Adeodato and have a look at how were they handled. e.g., if I really check that the bug was fixed, I close directly. -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 A conference is a gathering of important people who singly can do nothing but together can decide that nothing can be done. -- Fred Allen
--nextPart3114680.zbaTDOGo6m Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Le Lun 3 Janvier 2005 15:30, Adeodato Sim=F3 a =E9crit :> * Pierre Habouzit [Mon, 03 Jan 2005 15:04:11 +0100]: > > so what is the policy here ? do we close any bug older than a few > > month that we cannot reproduce ? or do we try to contact submitter > > ? > > no written policy, common sense applies. if you want to have a > look, I did some work on kdemultimedia when preparing the > experimental upload: > > http://bugs.debian.org/src:kdemultimedia > > search for bugs done by Adeodato and have a look at how were they > handled. e.g., if I really check that the bug was fixed, I close > directly.OK, it seems reasonnable. another point is do we try by one way or the other to redirect ppl to=20 bugs.kde.org ? because a lot of the bugs (if not all) are upstream bugs. and=20 maintaining a database of 400 bugs where at least 350 should leave only=20 in bugs.kde.org is exhausting .... what can we do ? (yeah I know what we _should_ do : - tag the bug upstream,=20 - open a bug on bugs.k.o - tag the bug forwarded bugs.k.o/.... - follow the bug on bugs.k.o and then transmit all the stuff to the=20 submitter. but it''s clearly not feasible for 400 bugs over so many packages ! or I=20 take a secretary ...) So I''m asking myself if : 1/ there is a social (i mean non automatic) way to move ppl to submit=20 their upstream bugs directly to bugs.k.org OR 2/ we have to write some scripts that do the gateway -> i mean a soon=20 as we tag a bug upstream, this gateway open a bug on bugs.k.org, tags=20 the bug ''forward ....'' and regullary polls bugs.d.o for changes of=20 status and comments. OR a bit of both. I know it will not solve current situation, but at least, it could=20 really help to avoid to know the same situation later. thoughts ? =2D-=20 =B7O=B7 Pierre Habouzit =B7=B7O OOO http://www.madism.org --nextPart3114680.zbaTDOGo6m Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQBB2XJTvGr7W6HudhwRAgwvAJ4rgb+GMPY3kib+cSnKFt0UUxW+eACdECGT G/6KdlRMBwBqZUU2IXRH3RU=GY2+ -----END PGP SIGNATURE----- --nextPart3114680.zbaTDOGo6m--
* Pierre Habouzit [Mon, 03 Jan 2005 17:26:58 +0100]:> what can we do ?> (yeah I know what we _should_ do : > - tag the bug upstream, > - open a bug on bugs.k.o > - tag the bug forwarded bugs.k.o/.... > - follow the bug on bugs.k.o and then transmit all the stuff to the > submitter.all of the above. last point may become unnecessary, because if once you forward it upstream and notify the submitter about the bugs.k.o/nnn URL, many times they make themselves aware of the changes that happen there.> So I''m asking myself if : > 1/ there is a social (i mean non automatic) way to move ppl to submit > their upstream bugs directly to bugs.k.orgasking. e.g., I normally don''t create b.k.o entries for wishlist bugs, since these are very low priority and other bugs are more important. if I can, I mail the submitter stating so.> 2/ we have to write some scripts that do the gateway -> i mean a soon > as we tag a bug upstream, this gateway open a bug on bugs.k.org, tags > the bug ''forward ....'' and regullary polls bugs.d.o for changes of > status and comments.for the second part ("poll"), there is the list pkg-kde-bugs-fwd, which I announced on this post [1]. [1] http://lists.debian.org/debian-qt-kde/2004/11/msg00137.html as for a script that would create a new bug at b.k.o (when invoked manually, not unsupervised), I''ve been wanting that for ages now. I know there exists a python script somewere (by ESR, I believe) to send bugs to Bugzillas - not sure if it would work with bugs.kde.org.> thoughts ?that nobody should get too troubled/worried by the amount of existing (old) bugs. we can go cleaning those up at a low pace, and really focus in handle new bugs so that the list does not grow more. -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 Listening to: David Bowie - If I''m dreaming my life You''ve come to the right place. At debian-devel we are always willing to argue over the meanings of words. -- seen on debian-devel@l.d.o
--nextPart1156240.efjho87K6m Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline> > 2/ we have to write some scripts that do the gateway -> i mean a > > soon as we tag a bug upstream, this gateway open a bug on > > bugs.k.org, tags the bug ''forward ....'' and regullary polls > > bugs.d.o for changes of status and comments. > > for the second part ("poll"), there is the list pkg-kde-bugs-fwd, > which I announced on this post [1]. > > [1] http://lists.debian.org/debian-qt-kde/2004/11/msg00137.htmlyeah I''m already subscribed> as for a script that would create a new bug at b.k.o (when invoked > manually, not unsupervised), I''ve been wanting that for ages now. I > know there exists a python script somewere (by ESR, I believe) to > send bugs to Bugzillas - not sure if it would work with bugs.kde.org.ok, I''ll see what I can do. I believe it''s not that difficult to do :)> that nobody should get too troubled/worried by the amount of > existing (old) bugs. we can go cleaning those up at a low pace, and > really focus in handle new bugs so that the list does not grow more.well, I''m not troubled, but it''s quite ... a big amount of old non=20 closed since ages bugs :) =2D-=20 =B7O=B7 Pierre Habouzit =B7=B7O OOO http://www.madism.org --nextPart1156240.efjho87K6m Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQBB2YwhvGr7W6HudhwRAv4zAKChlIrH0xhAC/uY8hFYgdN6GW5dFQCfbmEe SuNUr+smnOp/kBQzSOlAIhM=D2ap -----END PGP SIGNATURE----- --nextPart1156240.efjho87K6m--
On Mon, Jan 03, 2005 at 07:13:05PM +0100, Adeodato Simó wrote:> > as for a script that would create a new bug at b.k.o (when invoked > manually, not unsupervised), I''ve been wanting that for ages now. I > know there exists a python script somewere (by ESR, I believe) to send > bugs to Bugzillas - not sure if it would work with bugs.kde.org.http://www.bugzilla.org/download/ There''s a "bugzilla-submit" by Christian Reis and ESR. That''s probably what you''re talking about.
* Ricardo Javier Cardenes Medina [Mon, 03 Jan 2005 22:47:44 +0000]:> There''s a "bugzilla-submit" by Christian Reis and ESR. That''s probably > what you''re talking about.yes. :) -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 A celebrity is a person who works hard all his life to become well known, then wears dark glasses to avoid being recognized. -- Fred Allen
--nextPart2018191.Ujh8dxQCEj Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Le Mar 4 Janvier 2005 10:44, Adeodato Sim=F3 a =E9crit :> * Ricardo Javier Cardenes Medina [Mon, 03 Jan 2005 22:47:44 +0000]: > > There''s a "bugzilla-submit" by Christian Reis and ESR. That''s > > probably what you''re talking about. > > yes. :)I did took a look at that. bugzilla is a big piece of shit (in our POV). You have to many things to=20 specify in order to make bugzilla-submit work : you HAVE to specify the=20 product, component, version, priority, .... and 1209172 things you=20 don''t really want to. moreover, it won''t help to follow the KDE-team answers. I''m really afraid we will have write a brand new script that does a lot=20 more that bugzilla-submit, or to continue our manual forward... damn, if only I had time to write such a thing :''( I''ll think at it. =2D-=20 =B7O=B7 Pierre Habouzit =B7=B7O OOO http://www.madism.org --nextPart2018191.Ujh8dxQCEj Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQBB5YvIvGr7W6HudhwRAno/AKCI5GxNyjqqipLBj2cksjqx5nr/tgCfaU91 ilNQKbUjio5mW0Mc+trfrVE=tPqC -----END PGP SIGNATURE----- --nextPart2018191.Ujh8dxQCEj--
* Pierre Habouzit [Wed, 12 Jan 2005 21:42:48 +0100]:> Le Mar 4 Janvier 2005 10:44, Adeodato Simó a écrit : > > * Ricardo Javier Cardenes Medina [Mon, 03 Jan 2005 22:47:44 +0000]: > > > There''s a "bugzilla-submit" by Christian Reis and ESR. That''s > > > probably what you''re talking about.> > yes. :)> I did took a look at that.thanks.> moreover, it won''t help to follow the KDE-team answers.uhm, just adding pkg-kde-bugs-fwd@l.a.d.o to CC should do, wouldn''t it? -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 Listening to: Lolita - Y no me importa nada If you think nobody cares if you''re alive, try missing a couple of car payments. -- Earl Wilson