Re: Re: making progress with ACPI was: ACPI small patch up date

Andrew Kohlsmith
2002-10-31T05:02:54Z

> 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.