public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andreas Voegele <voegelas@users.sourceforge.net>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Re: Proposed Issuetracker via PEST
Date: 28 Nov 2001 18:11:19 +0100	[thread overview]
Message-ID: <87snay4y88.fsf@columbus.localdomain> (raw)
In-Reply-To: <1006963000.697.12.camel@fry>

Mikael Hallendal writes:

> As said before, this is the _default_ interface too bugzilla which
> we have no intention of using (at least not for endusers).
  ^^
Has there already been a decision to use Bugzilla?

> Bugzilla is complex before it's _very_ powerful. But I agree, the
> default interface is too complex [...]

The problem is that web interfaces generally suck because of the poor
GUI elements that HTML provides.  For example, the text entry's
editing features are really poor compared to the features of real text
editors.

How will users select a package in the Bug Tracking System if there
are hundreds or even thousands of packages?  Do they have to scroll
through endless lists?

I prefer to write my reports with a text editor and to send the
reports by electronic mail.  It's much easier to add patches and
ebuild scripts to electronic mail than to add them to reports sent
through a web interface - at least if you're using Emacs to write your
mail :]

The Debian BTS uses electronic mail.  And there are at least two
programs, e.g. reportbug, which is written in Python, that end-users
can use to send bug reports.

> 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.

Hm, do you think that all the developers need/want the same things?

What's wrong with the Debian BTS?

-- 
Andreas


  parent reply	other threads:[~2001-11-28 17:12 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
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             ` Andreas Voegele [this message]
2001-11-28 17:56               ` [gentoo-dev] " 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=87snay4y88.fsf@columbus.localdomain \
    --to=voegelas@users.sourceforge.net \
    --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