public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Aaron Gaudio <prothonotar-2LEdZMXKCZJeeLb3ft/vUmD2FQJk+8+b@public.gmane.org>
To: acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org
Subject: Re: making progress with ACPI was: ACPI small patch update (20021024)
Date: Tue, 29 Oct 2002 07:43:29 -0500	[thread overview]
Message-ID: <20021029124329.GA25692@tarnation.dyndns.org> (raw)
In-Reply-To: <20021028213404.U27461-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>

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

Behold, Matthew Wilcox <willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org> hath decreed:

> i find it fascinating that there are so many people on this list who want
> to see a bug tracking system, but don't feel able to keep a list of bugs
> themselves.  why is that?  expecting andy to set it up seems unreasonable.
> 

By no means does the development maintainer have to also maintain
the bugtracking system or the webpage. In many projects these are
handled by different people. This might be an opportunity for those
with less coding skills to contribute more to the project.

An official bug-tracking system can be very beneficial to all involved.
It lets the developers keep track of what they need to work on, what
others are working on, what's already been fixed, etc. to avoid 
duplication of work, and to allow for prioritization of bugs. It lets
non-developer testers and part-time bugfixers see the status of bugs,
see if a bug they found is already known or new, etc. so that they
don't have to search through the mail archives and/or burden the
list with a known problem.

I think the web page does need someone to update and maintain it
regularly. If you go to http://acpi.sourceforge.net/ there are not
even any links to http://sourceforge.net/projects/acpi/ where the
source code is served. Anyone not familiar with sourceforge won't
understand where to get the kernel patches. There's not a lot of
other information at the home page, which could be useful towards
attracting more people to test and develop alike.

I also second the notion of having the list set up to automatically
fill in the Reply-To header with the list's address.

-- 

Aaron Gaudio
prothonotar at tarnation.dyndns.org
"From fullness, aspect. From aspect, being. From being, emptiness."
  

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

  parent reply	other threads:[~2002-10-29 12:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-28 20:31 making progress with ACPI was: ACPI small patch update (20021024) joerg.beyer-htSm2yLGOjU
     [not found] ` <200210282031.g9SKVAX06731-pb599fR3TxVkExQqqHjIK3sFFmKitW5W@public.gmane.org>
2002-10-28 21:16   ` Martin Waitz
     [not found]     ` <20021028211603.GD1402-4e/A4rHm86X2JYTphGNI2Q@public.gmane.org>
2002-10-28 21:34       ` Matthew Wilcox
2002-10-29 12:20         ` Derek Broughton
     [not found]           ` <005401c27f45$967de820$3746028e-dP0OE4Ef7fWw5LPnMra/2Q@public.gmane.org>
2002-10-29 14:02             ` Matthew Wilcox
     [not found]         ` <20021028213404.U27461-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2002-10-29 12:43           ` Aaron Gaudio [this message]
     [not found]             ` <20021029124329.GA25692-2LEdZMXKCZJeeLb3ft/vUmD2FQJk+8+b@public.gmane.org>
2002-10-29 14:03               ` Matthew Wilcox
2002-10-28 21:38   ` kneumann-4bfl1RV3iZDOEhgYWvzSCYQuADTiUCJX
  -- strict thread matches above, loose matches on Subject: below --
2002-10-29  7:30 Jens Haug
     [not found] ` <200210290730.g9T7UDD26513-sBhUd1W9t4xfrO0PeCDDO4ECbGbo6+O1OOFObY0sJ7w@public.gmane.org>
2002-10-29 10:45   ` Mark Pritchard
2002-10-28 20:02 Nakajima, Jun
2002-10-28 19:20 Grover, Andrew
     [not found] ` <EDC461A30AC4D511ADE10002A5072CAD04C7A476-OU+JdkIUtvd9zuciVAfUoVDQ4js95KgL@public.gmane.org>
2002-01-16 19:53   ` Pavel Machek
2002-10-28 19:56   ` Alan Cox
2002-10-29  2:30   ` J

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=20021029124329.GA25692@tarnation.dyndns.org \
    --to=prothonotar-2ledzmxkczjeelb3ft/vumd2fqjk+8+b@public.gmane.org \
    --cc=acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.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