public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: Proposed Issuetracker via PEST
Date: 28 Nov 2001 19:27:05 +0100	[thread overview]
Message-ID: <1006972025.13526.0.camel@zoidberg> (raw)
In-Reply-To: <87snay4y88.fsf@columbus.localdomain>

[-- Attachment #1: Type: text/plain, Size: 3582 bytes --]

ons 2001-11-28 klockan 18.11 skrev Andreas Voegele:
> 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?

No but there has been extensive discussions about using it and those
discussions has been based on writing a our own nice interface too it.
 
> > 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'm not sure how we should categorize the packages. Currently I think
that bugreports should go per team (ie. if you find a bug in a package
that is maintained by Desktop team you report it as such a bug rather
than that actuall package). This fits very well into the current setup
we have in Gentoo.

If we have as in Debian (which I hope we never have) that one person
only can make changes to a package it should be reported per package.
 
> 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 :]

I agree that there should be a way to report bugs through email. This is
afaik possible in the bugzilla used by GNOME. Also, BugBuddy is a GNOME
application to report bugs to bugzilla, we might be able to tweek it if
we decide to use Bugzilla.

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

I agree with Joshua that it's very important to have a nice webui to
look at the bugs, search among them etc.
We should (imho) also be able to connect the issuetracking system to IRC
(at least for lookups) using a bot. I don't know how easy this is with
Debbug or Roundup (I guess at least Debbug has something like this?)

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

Off course not, that's why we need something that fits all (and in my
opinion we should be able to make Bugzilla do so). If we use something
that hasn't all the features we want we will have to spend time to
implement them (This might not be a bad idea since we will be helping
another project that way).
 
> What's wrong with the Debian BTS?

I have never used it and I think most of us haven't. This is a
discussion about what to use. Nothing has been decided.

Currently we seem to be in the state where we collect information about
which ones are available. And those I can come up with right now that's
been suggested are:

* Roundup
* Bugzilla
* PEST
* Debian BTS
* GNATS
* Improve current dev-wiki

Regards,
  Mikael Hallendal

-- 

Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden


[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2001-11-28 18:28 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             ` [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 [this message]
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=1006972025.13526.0.camel@zoidberg \
    --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