public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mikael Hallendal <hallski@gentoo.org>
To: "Gentoo Dev." <gentoo-dev@cvs.gentoo.org>
Subject: Re: [gentoo-dev] What should be in place before 1.0 release
Date: Mon Oct 15 03:14:01 2001	[thread overview]
Message-ID: <1003137197.14313.8.camel@fry> (raw)
In-Reply-To: <20011014233423.6d54a2be.karltk@prosalg.no>

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

sön 2001-10-14 klockan 23.34 skrev Karl Trygve Kalleberg:
> On Sun, 14 Oct 2001 16:37:23 -0400
> Blue Lizard <webmaster@dofty.zzn.com> wrote:
> 
> > bugzilla _could_ handle this, but while it is technically ready enough 
> > our development team is in no way prepared to handle the influx of new 
> > users that would find it a pain in the neck to use.
> 
> Then we find something that's easier to use. We really want this to
> further Gentoo development, not hamper it. I do not think our current
> system with sporadic mails to the gentoo-dev (and sometimes
> gentoo-ebuild!) list is good enough. 

I don't think that anyone thinks that gnome-dev a good solution for
bugreporting. (After all it should be a developer-list for
devel-discussions).

I think that we should start using a bug-tracking system and that we
should start doing so soon. As I've said before, Bugzilla is really
powerful but can also be a large step for new users. However, this is
with the default-interface, we could do our own interface that's easier
to use.

Someone also mentioned roundup (http://roundup.sourceforge.net/). I
tried to get it running on my Gentoo-machine but it didn't want to play.
Someone (and me) should give it another try.

IMHO, we can choose either as long as it works. I also think that we
should use this system for our "todo"'s, in other words, start using the
bug-tracking system for what we currently uses Dev-wiki.

I'm not sure about Roundup but bugzilla can also be used for handling
ebuilds (instead of gentoo-ebuild-list).

Regards,
  Mikael Hallendal

-- 

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


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

  reply	other threads:[~2001-10-15  9:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-14  8:38 [gentoo-dev] What should be in place before 1.0 release Karl Trygve Kalleberg
2001-10-14 10:51 ` Dan C
2001-10-14 14:37 ` Blue Lizard
2001-10-14 15:36   ` Karl Trygve Kalleberg
2001-10-15  3:14     ` Mikael Hallendal [this message]
2001-10-15  3:36       ` Blue Lizard
2001-10-15  6:05         ` Mikael Hallendal

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=1003137197.14313.8.camel@fry \
    --to=hallski@gentoo.org \
    --cc=gentoo-dev@cvs.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