public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Kohlsmith <akohlsmith-acpi-uiYP0llB1AZBDgjK7y7TUQ@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: making progress with ACPI was: ACPI small patch up date
Date: Thu, 31 Oct 2002 00:02:54 -0500	[thread overview]
Message-ID: <200210310002.54755@-mixdown.ca> (raw)
In-Reply-To: <1035944274.1275.32.camel-v8X+xWjPZDc@public.gmane.org>

> patches/bugreports/information I could. Usually, I'm not sure if its
> helpful, whether its important or got missed in the rush. To me
> ACPI-development is a "black-box" system. You post something to the list
> and either get a flaming, a pat on the head, a useful bit of help or
> dead silence. Other projects have roadmaps, FAQ's, etc to at least give
> people the option to inform themselves as to whats a priority, why
> bugtracking is a mailling list or what's currently being neglected. A
> few lines of html might save constant "are you insane, it'd be easier
> if.." and "why isn't...." threads when you've thought it through and
> have good reasons others might not immediately otherwise see.

*clap*clap*clap*clap*clap*

I appreciate all the hard work that the ACPI developers are putting into the 
project, but without the damned web site even hinting that anything is going 
on / broken links / etc., it is very much a black-box operation.

I've been able to help out on the KDE project because I can hit IRC and 
chat/get flamed/etc.  I can help out with the Jabber IM I prefer (Psi) 
because when I ask a question about the internals, I get some semblance of an 
answer that doesn't raise more questions than it clears.  The ACPI project is 
*very* important to me but I can't help because there is nothing to allow me 
to take the two steps I need to get up to a level where I can ask intelligent 
questions about the workings.

I'm not trying to flame the developers here, and lord knows you're working 
your asses off, but there are people who want to help but can't get the 
initial documentation they need to make a decent effort.

Regards,
Andrew


-------------------------------------------------------
This sf.net email is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en

  parent reply	other threads:[~2002-10-31  5:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-29 23:50 Re: making progress with ACPI was: ACPI small patch up date Grover, Andrew
     [not found] ` <EDC461A30AC4D511ADE10002A5072CAD04C7A489-OU+JdkIUtvd9zuciVAfUoVDQ4js95KgL@public.gmane.org>
2002-10-30  1:55   ` J
2002-10-30  2:17   ` Huw Hawkins
     [not found]     ` <1035944274.1275.32.camel-v8X+xWjPZDc@public.gmane.org>
2002-10-31  5:02       ` Andrew Kohlsmith [this message]
2002-10-30  6:08   ` Ernst Herzberg
     [not found]     ` <200210300708.37599.earny-euM3SP4ZHrg@public.gmane.org>
2002-10-30  6:09       ` Randy.Dunlap
2002-10-30  9:01 ` Valette Eric
  -- strict thread matches above, loose matches on Subject: below --
2002-10-30  7:12 joerg.beyer-htSm2yLGOjU
2002-10-30  9:07 ` Valette Eric

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=200210310002.54755@-mixdown.ca \
    --to=akohlsmith-acpi-uiyp0llb1azbdgjk7y7tuq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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