gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] Re: GNUmed & blueprints


From: Jerzy Luszawski
Subject: Re: [Gnumed-devel] Re: GNUmed & blueprints
Date: Mon, 08 Sep 2008 13:56:02 +0200

Dnia 08-09-2008, pon o godzinie 12:14 +0200, Gour napisaƂ(a):
> >>>>> "Karsten" == Karsten Hilbert <address@hidden> writes:
> 
> >> With such a low number of users, it is not even unthinkable to
> >> request them to either register at LP in order to send back reports
> 
> Karsten> It is unthinkable.
(...)
> Ubuntu uses Launchpad to keep track of bugs and their fixes. To file a
> bug you first need to create an account. 

> So, if it's OK for Ubuntu...
If we want to limit Gnumed to <10 users we need neither Launchpad nor
any other bug tracking machines. We can PM each other.

> >> or have them GPG-setup ready
> 
> Karsten> This is, too.
GPG is required only if you want to *send* bug reports by e-mail. You
can always file a bug via web interface without GPG (but you need to log
in @ launchpad, which seems obvious)

> I must admit that I do not remember any distro and/or project where one
> does not need to register in order to submit bugs to bug trackers and I
> do not agree that requiring gpg-signed email when reporting bugs for
> application with userbase of ~10 users is too much, but well...
I think Gour made a good point here: automatic bug submit by exception
handler generates many "bugs" which are at best help requests, and not
real bugs in code. They come because of using outdated versions, not
properly installed prerequisities or strange config files. I don't
remember any recently reported bug requiring code change (but I may have
missed one).
If potential user had to register to file a bug report, he would have to
think it over, find FAQ, search for similar bugs, and check his config.
This should limit "pseudo-bugs" and save everyone's (especially Karsten)
time. This time can be spent to developing better doc/wiki, covering
potential installation pitfals.
BTW: As far as I recall from reporting bugs in Ubuntu, Launchpad has
nice feature of automatic checking for similar bugs when reporting new
one, displaying possible matches if there are any.

Tu summarize:
IMHO it doesn't matter where the bugs reports are redirected. Karsten -
subscribing to all bugs at Launchpad is no problem, really, you won't
miss a thing. 
I personally like the idea of preparing blueprints on Lauchpad. That can
eventually replace the corresponding branch in the wiki, being easier to
maintain. (remember the initial topic of this mail? ;-) Also bug/feature
assignments can be utilized when all developers register as gnumed team
members.
I would limit or even completely abandon automatic generation of bug
report. Perhaps good solution would be to generate an automatic bug
report no sooner then successful connection to database. This would
cut-off most config errors.

Have a nice day.

Jerzy Luszawski

PS. Karsten - think of being able to send an e-mail(no web interface!)
assigning someone to a bug, and forget about it. ;-)

(I hope I will have some time in the evening to clean up and send this
operation plugin)





reply via email to

[Prev in Thread] Current Thread [Next in Thread]