[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: closing bugs products
From: "Jordi Polo" <mumismo () gmail ! com>
Date: 2008-12-02 6:04:54
Message-ID: a4162420812012204n67fe9f53lfff266c4994bfc91 () mail ! gmail ! com
[Download RAW message or body]
On Tue, Dec 2, 2008 at 1:53 AM, Friedrich W. H. Kossebau
<kossebau@kde.org>wrote:
> Hi,
>
> Hurra for all cleaning up of bko, in general :)
>
> Am Montag, 1. Dezember 2008, um 16:52 Uhr, schrieb Matt Rogers:
> > On Monday 01 December 2008 01:42:47 Mark Kretschmann wrote:
> > > On Mon, Dec 1, 2008 at 5:05 AM, Jordi Polo <mumismo@gmail.com> wrote:
> > > > There are products on bugs.kde.org that I think should be closed for
> > > > new bugs:
> > > >
> > > > configure: buildsystem can be used instead. No open bugs as this
> > > > writting.. binaries: downstream bugs should not be reported. No open
> > > > bugs as this writting.
> > > > daap kioslave: 1 open bug. Why not move it to kioslaves?
>
> Why shouldn't it stay a product of its own?
one open bug in all its life ... All the other kioslaves are just in
kioslaves. We split all or merge all.
>
> > > > spreadkde.org: No open bugs. Looks unmaintained ...
>
> Promo people still think of bringing it back to life, AFAIR.
>
> > > > printer-applet: 3 open bugs, 5 bugs reported in its life, surely
> should
> > > > merge with something.
> > >
> > > Makes sense. You should forward this to sysadmin@kde.org.
> >
> > isn't printer-applet new though?
>
> It is. Only part of KDE since 4.1. See e.g. here:
> http://utils.kde.org/projects/printer-applet/development.php
>
As above, applets are separated products or no, but the same policy for them
all.
>
> There should perhaps be one central database for the metadata of all KDE
> programs/modules, which is reused in techbase, userbase, bugzilla and
> elsewhere, containing data like homepage, maintainer, releases, icon/logo,
> etc. So such information is consistent and can be automatically made
> available.
>
> I guess it is lack of human resources here...
> Cheers
> Friedrich
> --
> Okteta - KDE 4 Hex Editor - http://utils.kde.org/projects/okteta
>
--
Jordi Polo Carres
NLP laboratory - NAIST
http://www.bahasara.org
[Attachment #3 (text/html)]
<br><br><div class="gmail_quote">On Tue, Dec 2, 2008 at 1:53 AM, Friedrich W. H. \
Kossebau <span dir="ltr"><<a \
href="mailto:kossebau@kde.org">kossebau@kde.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> Hi,<br>
<br>
Hurra for all cleaning up of bko, in general :)<br>
<br>
Am Montag, 1. Dezember 2008, um 16:52 Uhr, schrieb Matt Rogers:<br>
<div class="Ih2E3d">> On Monday 01 December 2008 01:42:47 Mark Kretschmann \
wrote:<br> > > On Mon, Dec 1, 2008 at 5:05 AM, Jordi Polo <<a \
href="mailto:mumismo@gmail.com">mumismo@gmail.com</a>> wrote:<br> > > > \
There are products on <a href="http://bugs.kde.org" target="_blank">bugs.kde.org</a> \
that I think should be closed for<br> > > > new bugs:<br>
> > ><br>
> > > configure: buildsystem can be used instead. No open bugs as this<br>
> > > writting.. binaries: downstream bugs should not be reported. No \
open<br> > > > bugs as this writting.<br>
> > > daap kioslave: 1 open bug. Why not move it to kioslaves?<br>
<br>
</div>Why shouldn't it stay a product of its own?</blockquote><div><br>one open \
bug in all its life ... All the other kioslaves are just in kioslaves. We split all \
or merge all. <br><br></div><blockquote class="gmail_quote" style="border-left: \
1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br>
<div class="Ih2E3d"><br>
> > > <a href="http://spreadkde.org" target="_blank">spreadkde.org</a>: No \
open bugs. Looks unmaintained ...<br> <br>
</div>Promo people still think of bringing it back to life, AFAIR.<br>
<div class="Ih2E3d"><br>
> > > printer-applet: 3 open bugs, 5 bugs reported in its life, surely \
should<br> > > > merge with something.<br>
> ><br>
> > Makes sense. You should forward this to <a \
href="mailto:sysadmin@kde.org">sysadmin@kde.org</a>.<br> ><br>
> isn't printer-applet new though?<br>
<br>
</div>It is. Only part of KDE since 4.1. See e.g. here:<br>
<a href="http://utils.kde.org/projects/printer-applet/development.php" \
target="_blank">http://utils.kde.org/projects/printer-applet/development.php</a><br> \
</blockquote><div><br>As above, applets are separated products or no, but the same \
policy for them all.<br><br> </div><blockquote class="gmail_quote" \
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; \
padding-left: 1ex;"> <br>
There should perhaps be one central database for the metadata of all KDE<br>
programs/modules, which is reused in techbase, userbase, bugzilla and<br>
elsewhere, containing data like homepage, maintainer, releases, icon/logo,<br>
etc. So such information is consistent and can be automatically made<br>
available.<br>
<br>
</blockquote><div>I guess it is lack of human resources \
here...<br><br><br> </div><blockquote class="gmail_quote" style="border-left: \
1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: \
1ex;">Cheers<br>
Friedrich<br>
<font color="#888888">--<br>
Okteta - KDE 4 Hex Editor - <a href="http://utils.kde.org/projects/okteta" \
target="_blank">http://utils.kde.org/projects/okteta</a><br> \
</font></blockquote></div><br><br clear="all"><br>-- <br>Jordi Polo Carres<br>NLP \
laboratory - NAIST<br><a \
href="http://www.bahasara.org">http://www.bahasara.org</a><br><br>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic