[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Reporting bugs
From:       "Manuel Amador (Rudd-O)" <rudd-o () amautacorp ! com>
Date:       2003-09-11 17:11:04
[Download RAW message or body]

Hmmm..

Would it be possible to write an xmlrpc interface on bugzilla, then use
kxmlrpc to submit bugs?

El jue, 11 de 09 de 2003 a las 11:56, Nicolas Goutte escribió:
> Well, the problem is that KDE Bugs has no more email interface for new bugs 
> since it has switched to Bugzilla, because:
> - spamming (resulting that kde.org being banned from some ISPs as spammer, as 
> the kde-bugs mailing list had too much spamming traffic.)
> - uncomplete or not conforming bug reports
> - (some other reasons that I have forgotten. Sorry)
> 
> As there is probably no moderator willing to check the bugs before releasing 
> them to any public list, it is difficult to re-introduce the old email 
> interface.
> 
> So from the old email interface, only a few things remains:
> - the kde-cvs mailing list
> -.the email address for commenting: 12345@bugs.kde.org (where 12345 is the bug 
> number)
> - the email address for closing (now it is for RESOLVED/FIXED)
> 12345-close@bugs.kde.org
> or
> 12345-done@bugs.kde.org
> 
> Mailing list info: http://www.kde.org/mailinglists
> Archive: http://lists.kde.org
> 
> Have a nice day!
> 
> On Thursday 11 September 2003 18:01, Mikolaj Machowski wrote:
> > Hello,
> >
> > Official way of reporting bugs is: bugs.kde.org,mail-list, mail to author
> >
> > I understand merits of bugs.kde.org but it has also its drawbacks. Eg. for
> > dial-uper going through all this pages is costly.
> >
> > Probably in this hot time (preparing stable 3.2 release) nobody will have
> > enough time but it would be good to have mail front end to report bugs.
> > Template should looks like:
> >
> > Summary: moving whole description to summary if summary is empty
> > Product: korganizer
> > Version: CVS
> > Platform: Compiled Sources
> > OS/Version: Linux
> > Status: UNCONFIRMED
> > Severity: normal
> > Priority: NOR
> > Component: calendar conduits
> > ReportedBy: mikmach@wp.pl
> > Version:           CVS (using KDE Devel)
> > Installed from:    Compiled sources
> > Compiler:          gcc 3.2.2
> > OS:          Linux
> >
> > Description:
> > When summary is empty whole description is moved to Summary field. This is
> > disurbing. Better solution would be cut only first line and move it to S.
> >
> > Beside Description: field all others should be in one line. If field is
> > empty, return to sender with explanation. Also send explanation of all
> > fields and possible values if bugs@kde.org have in subject help or
> > something.
> >
> > To improve chances of good forms it could have mechanism of one-way mailing
> > list. When subscribing whole insctruction would be send back to subscriber.
> > He/she could use it later as reference.
> >
> > At least current mechanism of reporting bugs in applications could use
> > kmail and queuing...
> >
> > m.
> 
>  
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
> 

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]