From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Proposed Issuetracker via PEST
Date: 28 Nov 2001 16:56:40 +0100 [thread overview]
Message-ID: <1006963000.697.12.camel@fry> (raw)
In-Reply-To: <20011128093727.5516ba2e.jnelson@jamponi.net>
[-- Attachment #1: Type: text/plain, Size: 1740 bytes --]
ons 2001-11-28 klockan 16.37 skrev Jon Nelson:
> I would like to mention Roundup (written in Python, very perty, and
> very easy to use and setup -- took me 15 minutes and doesn't depend
> on anything other than mail and python.)
Did you set it up on a Gentoo machine. I just couldn't get it working on
my Gentoo (RC4) system, and I spent a couple of errors on it. Might have
been RC4 issues or my lack of Python-knowledge.
> Given my past experiences with gnats, rt, debbugs, and bugzilla,
> I'd say bugzilla is *way* too complex for people to use effectively,
> and has perhaps the most horrid interface I've ever experienced.
> debbugs was the easiest, and the little bit that I've used roundup
> makes me feel fairly comfortable in recommending it.
As said before, this is the _default_ interface too bugzilla which we
have no intention of using (at least not for endusers). Bugzilla is
complex before it's _very_ powerful. But I agree, the default interface
is too complex for endusers even though most people have no problems
adding a new bug. The complexety is when trying to find if a bug is
already in there.
> In summary, usability is far and away the most important thing
> in a bug tracking/issue tracking system, and a objective analysis
> is probably in order.
This is very true while talking about endusers. When talking about
developers I think the most important thing is that it can handle all
the things we need to work effectivly. I also think none of the Gentoo
developers will have problems learning Bugzilla if they set there mind
to it.
Regards,
Mikael Hallendal
--
Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-11-28 15:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1006817973.23206.0.camel@inspiron.theleaf.office>
[not found] ` <0GNG00DA5ULHBX@mxout1.netvision.net.il>
[not found] ` <20011127112204.B13783@atelier.offthehill.net>
[not found] ` <0GNH00F6Q78Z2Z@mxout1.netvision.net.il>
2001-11-27 20:27 ` [gentoo-dev] Re: [gentoo-ebuild] Ebuild integration / ignoring Joshua Pollak
2001-11-27 23:34 ` [gentoo-dev] " Bart Verwilst
2001-11-28 15:50 ` [gentoo-dev] Re: [gentoo-ebuild] " Karl Trygve Kalleberg
2001-11-28 15:21 ` [gentoo-dev] Re: [gentoo-user] " Karl Trygve Kalleberg
2001-11-28 14:37 ` Mikael Hallendal
2001-11-28 14:56 ` [gentoo-dev] Proposed Issuetracker via PEST Joshua Pollak
2001-11-28 15:27 ` Mikael Hallendal
2001-11-28 15:29 ` Mikael Hallendal
2001-11-28 15:37 ` Jon Nelson
2001-11-28 15:56 ` Mikael Hallendal [this message]
2001-11-28 16:28 ` Joshua Pollak
2001-11-28 17:06 ` Jon Nelson
2001-11-28 17:47 ` Joshua Pollak
2001-11-28 18:34 ` Mikael Hallendal
2001-11-28 20:38 ` [gentoo-dev] IssueTracker Requirements Joshua Pollak
2001-11-28 21:21 ` Jon Nelson
2001-11-28 18:37 ` [gentoo-dev] Proposed Issuetracker via PEST Bart Verwilst
2001-11-28 17:11 ` [gentoo-dev] " Andreas Voegele
2001-11-28 17:56 ` Joshua Pollak
2001-11-28 18:35 ` Jon Nelson
2001-11-28 20:08 ` Joshua Pollak
2001-11-28 18:27 ` Mikael Hallendal
2001-11-28 15:06 ` [gentoo-dev] Re: [gentoo-user] Re: [gentoo-ebuild] Ebuild integration / ignoring Chad Huneycutt
2001-12-04 18:06 ` Karl Trygve Kalleberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1006963000.697.12.camel@fry \
--to=hallski@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox