From: "Andreas Kuckartz" <A.Kuckartz@ping.de>
To: alsa-user@lists.sourceforge.net, <alsa-devel@lists.sourceforge.net>
Subject: Bugtracking system
Date: 21 Jan 2004 11:48:20 +0100 [thread overview]
Message-ID: <02ff01c3e00c$176a07c0$a501a8c0@computer2> (raw)
In-Reply-To: 1074646711.2067.15.camel@Wizard.knechthome.com
In response to the recent discussions on alsa-user (regarding "complaints"
about the state of ALSA) I would like to make two suggestions:
1. Decide which bugtracking system should be used.
Currently there is one for ALSA at Sourceforge (see
http://sourceforge.net/tracker/?group_id=27464&atid=390601) and there is
another one at kernel.org (see http://bugzilla.kernel.org/ Choose
Category=Drivers and Component=Sound and click the search button)
As you can see there are lots of very old open entries in the Sourceforge
system. Maybe the problems have already been resolved, maybe not. If a bug
has been assigned to anyone at all then to Jaroslav Kysela ("perex").
Obviously Jaroslav will not be able to handle all these problems himself.
The kernel.org system mainly contains more recent entries (for kernel
versions 2.5 and 2.6) but also includes a small number of OSS-related
problems.
I clearly prefer Bugzilla to the sourceforge bugtracking system.
2. Add a link to the choosen bugtracking system (or - better - to a new
"bugtracking"-page on the site or the wiki) prominently to the front page of
http://alsa-project.org. Currently an inexperienced visitor has difficulties
to find the bugtracking system or might not even look for it at all if
he/she does not see it mentioned on the front page.
Cheers,
Andreas
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next parent reply other threads:[~2004-01-21 10:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a662904be22869df6c18097e559e8a7b@localhost.localdomain>
[not found] ` <1074646711.2067.15.camel@Wizard.knechthome.com>
2004-01-21 10:48 ` Andreas Kuckartz [this message]
2004-01-21 10:56 ` Bugtracking system Dan Hollis
2004-01-21 12:26 ` Re: [Alsa-devel] " Andreas Kuckartz
2004-01-22 1:41 ` [Alsa-user] " Dan Hollis
2004-01-22 11:32 ` Andreas Kuckartz
2004-01-23 2:45 ` Re: [Alsa-devel] " Sam Vilain
2004-01-23 9:59 ` [Alsa-user] " Andreas Kuckartz
2004-01-21 11:03 ` Takashi Iwai
2005-02-11 14:53 bugtracking system Jaroslav Kysela
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='02ff01c3e00c$176a07c0$a501a8c0@computer2' \
--to=a.kuckartz@ping.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.