From: Takashi Iwai <tiwai@suse.de>
To: Patrick Shirkey <pshirkey@boosthardware.com>
Cc: Jaroslav Kysela <perex@suse.cz>,
ALSA development <alsa-devel@alsa-project.org>
Subject: Re: Re: bug tracking?
Date: Tue, 20 May 2003 16:11:59 +0200 [thread overview]
Message-ID: <s5hbrxxd7ww.wl@alsa2.suse.de> (raw)
In-Reply-To: <3EC98C71.4090904@boosthardware.com>
At Tue, 20 May 2003 11:01:21 +0900,
Patrick Shirkey wrote:
>
> Takashi Iwai wrote:
>
> >
> > i'm familiar with bugzilla (not as an adamin but as a user :) and am
> > satisfied almost with it. it's enough powerful.
> > but bugzilla has many configurations and we'll need to find out the
> > fitting one for our purpose.
>
> I'm looking at it now. The first thing that jumps out at me is that all
> users have to login to make a submission online.
iirc, the current sf system requires also account..?
> IMO that will make it less likely for people to submit reports. However
> the rest of the system is very slick so I'm not sure what direction to
> take. There doesn't seem to be a way to turn of the login as it seems to
> be crucial to making sure the system works.
i don't think the account makes any problem. any bug reporter should
be responsible also for answering / following the thread. the
anonymous account makes it difficult.
also, if someone is lazy, there is still mailing list for help :)
> If we use bugzilla I will need full access to the mysql database on the
> server. I could code something with less features in php. It would work
> slower but it will work.
>
> Of course I would much prefer to have access to the mysql database as I
> can do some other funky things for the install docs then too. Like a
> card rating system.
>
> I have written to Jaroslav about this before but have never received an
> answer. I realise that I could be a huge security risk but I'm happy to
> sign some papers if that is what is required. I will send you my PO box
> address privately if that needs to be done.
>
> So my Suse friends. What does the boss say?
the alsa-project.org is managed by Jaroslav, and it's outside of
SuSE. so, the permission you can take is up to Jaroslav.
i think it's possible to provide a server space for this by SuSE, too,
if necessary. (for example, xfree86 cvs server is running on suse
machines.)
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
next prev parent reply other threads:[~2003-05-20 14:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 6:07 [Fwd: Re: [Jackit-devel] OSS Backend] Patrick Shirkey
2003-05-15 8:58 ` Takashi Iwai
2003-05-15 9:21 ` bug tracking? Jaroslav Kysela
2003-05-15 9:37 ` Takashi Iwai
2003-05-15 10:12 ` Patrick Shirkey
2003-05-15 12:53 ` Takashi Iwai
2003-05-20 2:01 ` Patrick Shirkey
2003-05-20 11:34 ` James Courtier-Dutton
2003-05-20 13:25 ` Patrick Shirkey
2003-05-20 14:11 ` Takashi Iwai [this message]
2003-05-20 14:51 ` Erik Inge Bolsø
2003-05-20 16:16 ` Patrick Shirkey
2003-05-20 16:46 ` Paul Davis
2003-05-20 16:02 ` Patrick Shirkey
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=s5hbrxxd7ww.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=perex@suse.cz \
--cc=pshirkey@boosthardware.com \
/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